Simon Glass | 09d71aa | 2016-02-29 15:25:55 -0700 | [diff] [blame] | 1 | config BLK |
| 2 | bool "Support block devices" |
| 3 | depends on DM |
Simon Glass | 6b03b9d | 2022-08-11 19:34:41 -0600 | [diff] [blame] | 4 | default y if MMC || USB || SCSI || NVME || IDE || AHCI || SATA |
| 5 | default y if EFI_MEDIA || VIRTIO_BLK || PVBLOCK |
Simon Glass | 09d71aa | 2016-02-29 15:25:55 -0700 | [diff] [blame] | 6 | help |
| 7 | Enable support for block devices, such as SCSI, MMC and USB |
| 8 | flash sticks. These provide a block-level interface which permits |
| 9 | reading, writing and (in some cases) erasing blocks. Block |
| 10 | devices often have a partition table which allows the device to |
| 11 | be partitioned into several areas, called 'partitions' in U-Boot. |
| 12 | A filesystem can be placed in each partition. |
| 13 | |
Simon Glass | 7f8967c | 2022-08-11 19:34:48 -0600 | [diff] [blame] | 14 | config SPL_LEGACY_BLOCK |
Adam Ford | 1811a92 | 2018-02-06 12:43:56 -0600 | [diff] [blame] | 15 | bool "Enable Legacy Block Device" |
Simon Glass | ca28baf | 2022-08-11 19:34:49 -0600 | [diff] [blame^] | 16 | depends on SPL && !DM_SPL |
| 17 | default y if SPL_MMC || SPL_USB_STORAGE || SCSI || NVME || IDE |
| 18 | default y if SPL_AHCI_PCI |
Adam Ford | 1811a92 | 2018-02-06 12:43:56 -0600 | [diff] [blame] | 19 | help |
Simon Glass | ca28baf | 2022-08-11 19:34:49 -0600 | [diff] [blame^] | 20 | Some devices require block support whether or not DM is enabled. This |
| 21 | is only supported in SPL. With this, the blk uclass is not used, but |
| 22 | instead a legacy implementation of block devices is used, with all |
| 23 | devices consisting of 'struct blk_desc' records. |
Adam Ford | 1811a92 | 2018-02-06 12:43:56 -0600 | [diff] [blame] | 24 | |
Simon Glass | c4d660d | 2017-07-04 13:31:19 -0600 | [diff] [blame] | 25 | config SPL_BLK |
| 26 | bool "Support block devices in SPL" |
| 27 | depends on SPL_DM && BLK |
| 28 | default y |
| 29 | help |
| 30 | Enable support for block devices, such as SCSI, MMC and USB |
| 31 | flash sticks. These provide a block-level interface which permits |
| 32 | reading, writing and (in some cases) erasing blocks. Block |
| 33 | devices often have a partition table which allows the device to |
| 34 | be partitioned into several areas, called 'partitions' in U-Boot. |
| 35 | A filesystem can be placed in each partition. |
| 36 | |
Simon Glass | ef39151 | 2018-10-01 12:22:13 -0600 | [diff] [blame] | 37 | config TPL_BLK |
| 38 | bool "Support block devices in TPL" |
| 39 | depends on TPL_DM && BLK |
| 40 | default y |
| 41 | help |
| 42 | Enable support for block devices, such as SCSI, MMC and USB |
| 43 | flash sticks. These provide a block-level interface which permits |
| 44 | reading, writing and (in some cases) erasing blocks. Block |
| 45 | devices often have a partition table which allows the device to |
| 46 | be partitioned into several areas, called 'partitions' in U-Boot. |
| 47 | A filesystem can be placed in each partition. |
| 48 | |
Simon Glass | 747093d | 2022-04-30 00:56:53 -0600 | [diff] [blame] | 49 | config VPL_BLK |
| 50 | bool "Support block devices in VPL" |
| 51 | depends on VPL_DM && BLK |
| 52 | default y |
| 53 | help |
| 54 | Enable support for block devices, such as SCSI, MMC and USB |
| 55 | flash sticks. These provide a block-level interface which permits |
| 56 | reading, writing and (in some cases) erasing blocks. Block |
| 57 | devices often have a partition table which allows the device to |
| 58 | be partitioned into several areas, called 'partitions' in U-Boot. |
| 59 | A filesystem can be placed in each partition. |
| 60 | |
Eric Nelson | e40cf34 | 2016-03-28 10:05:44 -0700 | [diff] [blame] | 61 | config BLOCK_CACHE |
| 62 | bool "Use block device cache" |
Tom Rini | 46960ad | 2018-05-22 12:24:16 -0400 | [diff] [blame] | 63 | depends on BLK |
| 64 | default y |
Eric Nelson | e40cf34 | 2016-03-28 10:05:44 -0700 | [diff] [blame] | 65 | help |
| 66 | This option enables a disk-block cache for all block devices. |
| 67 | This is most useful when accessing filesystems under U-Boot since |
| 68 | it will prevent repeated reads from directory structures and other |
| 69 | filesystem data structures. |
Michal Simek | e8a016b | 2016-09-08 15:06:45 +0200 | [diff] [blame] | 70 | |
Adam Ford | 6fef62c | 2018-06-11 17:17:48 -0500 | [diff] [blame] | 71 | config SPL_BLOCK_CACHE |
| 72 | bool "Use block device cache in SPL" |
| 73 | depends on SPL_BLK |
Adam Ford | 6fef62c | 2018-06-11 17:17:48 -0500 | [diff] [blame] | 74 | help |
| 75 | This option enables the disk-block cache in SPL |
| 76 | |
Simon Glass | 731ba3c | 2019-05-18 11:59:53 -0600 | [diff] [blame] | 77 | config TPL_BLOCK_CACHE |
| 78 | bool "Use block device cache in TPL" |
| 79 | depends on TPL_BLK |
Simon Glass | 731ba3c | 2019-05-18 11:59:53 -0600 | [diff] [blame] | 80 | help |
| 81 | This option enables the disk-block cache in TPL |
| 82 | |
Simon Glass | 42b7f42 | 2021-12-04 08:56:31 -0700 | [diff] [blame] | 83 | config EFI_MEDIA |
| 84 | bool "Support EFI media drivers" |
| 85 | default y if EFI || SANDBOX |
| 86 | help |
| 87 | Enable this to support media devices on top of UEFI. This enables |
| 88 | just the uclass so you also need a specific driver to make this do |
| 89 | anything. |
| 90 | |
| 91 | For sandbox there is a test driver. |
| 92 | |
| 93 | if EFI_MEDIA |
| 94 | |
| 95 | config EFI_MEDIA_SANDBOX |
| 96 | bool "Sandbox EFI media driver" |
| 97 | depends on SANDBOX |
| 98 | default y |
| 99 | help |
| 100 | Enables a simple sandbox media driver, used for testing just the |
| 101 | EFI_MEDIA uclass. It does not do anything useful, since sandbox does |
| 102 | not actually support running on top of UEFI. |
| 103 | |
Simon Glass | d8063dc | 2021-12-04 08:56:32 -0700 | [diff] [blame] | 104 | config EFI_MEDIA_BLK |
| 105 | bool "EFI media block driver" |
| 106 | depends on EFI_APP |
| 107 | default y |
| 108 | help |
| 109 | Enables a block driver for providing access to UEFI devices. This |
| 110 | allows use of block devices detected by the underlying UEFI |
| 111 | implementation. With this it is possible to use filesystems on these |
| 112 | devices, for example. |
| 113 | |
Simon Glass | 42b7f42 | 2021-12-04 08:56:31 -0700 | [diff] [blame] | 114 | endif # EFI_MEDIA |
| 115 | |
Simon Glass | fc843a0 | 2017-05-17 03:25:30 -0600 | [diff] [blame] | 116 | config IDE |
| 117 | bool "Support IDE controllers" |
| 118 | help |
| 119 | Enables support for IDE (Integrated Drive Electronics) hard drives. |
| 120 | This allows access to raw blocks and filesystems on an IDE drive |
| 121 | from U-Boot. See also CMD_IDE which provides an 'ide' command for |
| 122 | performing various IDE operations. |
Simon Glass | d2da54b | 2022-01-22 05:53:24 -0700 | [diff] [blame] | 123 | |
| 124 | if IDE |
| 125 | |
| 126 | config SYS_IDE_MAXBUS |
| 127 | hex "Maximumm number of IDE buses" |
| 128 | default 2 |
| 129 | help |
| 130 | This is the number of IDE buses provided by the board. Each one |
| 131 | can have one or two devices. One is designated the master and the |
| 132 | other one the slave. It is not required to have one or both on any |
| 133 | controller. |
| 134 | |
| 135 | config SYS_IDE_MAXDEVICE |
| 136 | hex "Maximum number of IDE devices" |
| 137 | default 2 |
| 138 | help |
| 139 | This is the number of IDE devices which can be connected to the |
| 140 | board. Normally this is 2 * CONFIG_SYS_IDE_MAXBUS since up to two |
| 141 | devices can be connected to each bus. The number of devices actually |
| 142 | connected is determined by probing. |
| 143 | |
| 144 | config SYS_ATA_BASE_ADDR |
| 145 | hex "Base address of IDE controller" |
| 146 | default 0 |
| 147 | help |
| 148 | This is the address of the IDE controller, from which other addresses |
| 149 | are calculated. Each bus is at a fixed offset from this address, |
| 150 | so it assumed that they are in the same area of the I/O space or |
| 151 | memory. |
| 152 | |
| 153 | config SYS_ATA_STRIDE |
| 154 | hex "IDE port stride" |
| 155 | default 0x1 |
| 156 | help |
| 157 | This is the distance between each IDE register, in bytes. For an |
| 158 | 8-bit controller this is typically 1, meaning that the registers |
| 159 | appear at consecutive bytes. If the value 2 two, that might indicate |
| 160 | a 16-bit register space. |
| 161 | |
| 162 | config SYS_ATA_DATA_OFFSET |
| 163 | hex "Offset of the data register" |
| 164 | default 0x0 |
| 165 | help |
| 166 | This is the offset of the controller's data register from the base |
| 167 | address of the controller. This is typically 0, but may be something |
| 168 | else if there are some other registers at the start of the |
| 169 | controller space. |
| 170 | |
| 171 | config SYS_ATA_REG_OFFSET |
| 172 | hex "Offset of the register space" |
| 173 | default 0x0 |
| 174 | help |
| 175 | This is the offset of the controller's 'register' space from the base |
| 176 | address of the controller. The data register (which is typically at |
| 177 | offset 0) has its own CONFIG, to deal with controllers where it is |
| 178 | somewhere else. Register 1 will be at this offset + 1, register 2 at |
| 179 | CONFIG_SYS_ATA_REG_OFFSET + 2, etc. |
| 180 | |
| 181 | config SYS_ATA_ALT_OFFSET |
| 182 | hex "Offset of the alternative registers" |
| 183 | default 0x0 |
| 184 | help |
| 185 | This is the offset of the controller's 'alternative' space from the |
| 186 | base address of the controller. This allows these registers to be |
| 187 | located separately from the data and register space. |
| 188 | |
| 189 | config SYS_ATA_IDE0_OFFSET |
| 190 | hex "Offset of bus 0" |
| 191 | default 0x1f0 |
| 192 | help |
| 193 | This is the start offset of bus 0 from the start of the |
| 194 | controller registers. All the other registers are calculated from |
| 195 | this address. using the above options. For x86 hardware this is often |
| 196 | 0x1f0. |
| 197 | |
| 198 | config SYS_ATA_IDE1_OFFSET |
| 199 | hex "Offset of bus 1" |
| 200 | default 0x170 |
| 201 | help |
| 202 | This is the start offset of bus 1 from the start of the |
| 203 | controller registers. All the other registers are calculated from |
| 204 | this address. using the above options. For x86 hardware this is often |
| 205 | 0x170. |
| 206 | |
| 207 | config ATAPI |
| 208 | bool "Enable ATAPI support" |
| 209 | help |
| 210 | This enabled Advanced Technology Attachment Packet Interface (ATAPI), |
| 211 | a protocol that allows a greater variety of devices to be connected |
| 212 | to the IDE port than with plain ATA. It allows SCSI commands to be |
| 213 | sent across the bus, e.g. to support optical drives. |
| 214 | |
| 215 | config IDE_RESET |
| 216 | bool "Support board-specific reset" |
| 217 | help |
| 218 | If this is defined, IDE Reset will be performed by calling the |
| 219 | function: |
| 220 | |
| 221 | ide_set_reset(int reset) |
| 222 | |
| 223 | where reset is 1 to assert reset and 0 to de-assert it. This function |
| 224 | must be defined in a board-specific file. |
| 225 | |
| 226 | endif # IDE |
Tom Rini | aca1f67 | 2022-06-10 22:59:28 -0400 | [diff] [blame] | 227 | |
| 228 | config LBA48 |
| 229 | bool "Enable LBA support for disks larger than 137GB" |
Tom Rini | aca1f67 | 2022-06-10 22:59:28 -0400 | [diff] [blame] | 230 | help |
| 231 | Set this to enable support for disks larger than 137GB. |
| 232 | Also look at CONFIG_SYS_64BIT_LBA. Without both of these, LBA48 |
| 233 | support uses 32bit variables and will 'only' support disks up to |
| 234 | 2.1TB. |
| 235 | |
| 236 | config SYS_64BIT_LBA |
| 237 | bool "Enable 64bit number of blocks on a block device" |
Tom Rini | aca1f67 | 2022-06-10 22:59:28 -0400 | [diff] [blame] | 238 | help |
| 239 | Make the block subsystem use 64bit sector addresses, rather than the |
| 240 | default of 32bit. |