zephyr,sdhc-emul
Description
These nodes are “sd” bus nodes.
Zephyr SDHC emulator
Software emulation of an SD host controller that supports SD, SDHC,
SDXC, eMMC, and SDIO card personalities. Intended for native_sim
testing and CI pipelines.
Properties
Properties not inherited from the base binding file.
Name |
Type |
Details |
|---|---|---|
|
|
Max drive current in mA at 3.3V. A value of zero indicates no maximum
is specified by the driver.
Default value: |
|
|
Max drive current in mA at 3.0V. A value of zero indicates no maximum
is specified by the driver.
Default value: |
|
|
Max drive current in mA at 1.8V. A value of zero indicates no maximum
is specified by the driver.
Default value: |
|
|
Maximum bus frequency for SD card. This should be the highest frequency
the SDHC is capable of negotiating with cards on the bus.
Default value: |
|
|
Minimum bus frequency for SD card. This should be the frequency that
cards first will select when attached to the SDHC bus
Default value: |
|
|
time in ms for SDHC to delay when toggling power to the SD card. This
delay gives the card time to power up or down fully
Default value: |
|
|
UHS-I bus speed modes the slot supports for SD and SDIO cards. The
host reports a mode only if it is in this list and the controller
supports it. Without this property, the modes the controller
supports are not restricted.
Use this property when a mode the controller supports is not
reliable on the board, for example on a bus that is shared between
slots. A slot where SDR104 tuning fails can be limited to DDR50:
sd-uhs-modes = "ddr50";
Legal values: |
|
|
The host controller supports HS200 at 1.8V
|
|
|
The host controller supports HS400 at 1.8V
|
|
|
The host controller and board support eMMC HS400 enhanced strobe.
This mode also requires HS400 at 1.8V and an 8-bit data bus.
|
|
|
SDHC data bus width (in bits).
Default value: Legal values: |
|
|
Host controller supports SD/eMMC high speed (up to 50 MHz) timing.
|
|
|
Host controller can supply 3.3 V to the card.
|
|
|
Host controller can supply 1.8 V signalling.
|
|
|
Virtual card personality.
sd - SDSC up to 2 GB
sdhc - SDHC 4-32 GB (default)
sdxc - SDXC above 32 GB
emmc - eMMC 5.1, supports CMD6 EXT_CSD, HS200/HS400
sdio - SDIO-only, triggers function enumeration
Default value: Legal values: |
|
|
Number of blocks in the virtual storage.
Default 131072 blocks = 64 MiB at 512 bytes/block.
Default value: |
|
|
Block size in bytes. The emulator only supports 512-byte blocks.
Any other value is rejected.
Default value: Constant value: |
|
|
CMD index that returns an error for fault injection.
255 disables fault injection.
Default value: |
|
|
If present, the virtual card is inserted at boot.
|
|
|
OCR (Operating Conditions Register) value reported by the emulated
card in response to CMD1 (eMMC) or ACMD41 (SD).
The default 0x00FF8000 sets bits 15-23, advertising every supported
VDD window from 2.7 V to 3.6 V (equivalent to MMC_OCR_VDD27_36FLAG).
Notable bits:
bit 7 - VDD 1.65-1.95 V supported (eMMC only)
bits 15-23 - VDD 2.7-3.6 V windows, one bit per 100 mV step
bit 24 - S18A: card supports switching to 1.8 V signalling
bit 30 - Sector mode for eMMC; for SD cards, CCS is derived
from card-type
bit 31 - Power-up busy status; set by the emulator at
runtime and must not be set here
For SD cards, the emulator sets CCS for "sdhc" and "sdxc" and
clears it for "sd", regardless of bit 30 in this property.
Default value: |
|
|
Number of SDIO functions to emulate (1-7).
Default value: |
Deprecated properties not inherited from the base binding file.
(None)
Properties inherited from the base binding file, which defines common properties that may be set on many nodes. Not all of these may apply to the “zephyr,sdhc-emul” compatible.
Name |
Type |
Details |
|---|---|---|
|
|
Indicates the operational status of the hardware or other
resource that the node represents. In particular:
- "okay" means the resource is operational and, for example,
can be used by device drivers
- "disabled" means the resource is not operational and the system
should treat it as if it is not present
For details, see "2.3.4 status" in Devicetree Specification v0.4.
Legal values: See Important properties for more information. |
|
|
This property is a list of strings that essentially define what
type of hardware or other resource this devicetree node
represents. Each device driver checks for specific compatible
property values to find the devicetree nodes that represent
resources that the driver should manage.
The recommended format is "vendor,device", The "vendor" part is
an abbreviated name of the vendor. The "device" is usually from
the datasheet.
The compatible property can have multiple values, ordered from
most- to least-specific. Having additional values is useful when the
device is a specific instance of a more general family, to allow the
system to match the most specific driver available.
For details, see "2.3.1 compatible" in Devicetree Specification v0.4.
This property is required. See Important properties for more information. |
|
|
Information used to address the device. The value is specific to
the device (i.e. is different depending on the compatible
property).
The "reg" property is typically a sequence of (address, length) pairs.
Each pair is called a "register block". Values are
conventionally written in hex.
For details, see "2.3.6 reg" in Devicetree Specification v0.4.
See Important properties for more information. |
|
|
Optional names given to each register block in the "reg" property.
For example:
/ {
soc {
#address-cells = <1>;
#size-cells = <1>;
uart@1000 {
reg = <0x1000 0x2000>, <0x3000 0x4000>;
reg-names = "foo", "bar";
};
};
};
The uart@1000 node has two register blocks:
- one with base address 0x1000, size 0x2000, and name "foo"
- another with base address 0x3000, size 0x4000, and name "bar"
|
|
|
Information used to define a mapping (or translation) between the address
space of a bus (the "child address space") and the address space of the
bus node's parent (the "parent address space").
The "ranges" property is typically empty, or a sequence of triplets
(child bus address, parent bus address, length).
If the "ranges" property is empty, it specifies that the parent and child
address spaces are identical and no address translation is required.
If the "ranges" property is not present in a bus node, it is assumed that
no mapping exists between children of the node and the parent address space.
For details, see "2.3.8 ranges" in Devicetree Specification v0.4.
|
|
|
Information about interrupts generated by the device, encoded as an array
of one or more interrupt specifiers. The format of the data in this property
varies by where the device appears in the interrupt tree. Devices with the same
"interrupt-parent" will use the same format in their interrupts properties.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
See Important properties for more information. |
|
|
Extended interrupt specifier for device, used as an alternative to
the "interrupts" property.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
Optional names given to each interrupt generated by a device.
The interrupts themselves are defined in either "interrupts" or
"interrupts-extended" properties.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
If present, this refers to the node which handles interrupts generated
by this device.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
Human readable string describing the device. Use of this property is
deprecated except as needed on a case-by-case basis.
For details, see "4.1.2 Miscellaneous Properties" in Devicetree
Specification v0.4.
See Important properties for more information. |
|
|
Information about the device's clock providers. In general, this property
should follow conventions established in the dt-schema binding:
https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/clock/clock.yaml
|
|
|
Optional names given to each clock provider in the "clocks" property.
|
|
|
This property encodes the number of <u32> cells used by address fields
in "reg" properties in this node's children.
For details, see "2.3.5 #address-cells and #size-cells" in Devicetree
Specification v0.4.
|
|
|
This property encodes the number of <u32> cells used by size fields in
"reg" properties in this node's children.
For details, see "2.3.5 #address-cells and #size-cells" in Devicetree
Specification v0.4.
|
|
|
Indicates that the device is capable of coherent DMA operations.
For details, see "2.3.10 dma-coherent" in Devicetree Specification v0.4.
|
|
|
DMA channel specifiers relevant to the device.
|
|
|
Optional names given to the DMA channel specifiers in the "dmas" property.
|
|
|
The dma-ranges provides a means of defining a mapping or translation between the
physical address space of the bus and the physical address space of the parent of the bus.
For details, see "2.3.9 dma-ranges" in Devicetree Specification v0.4.
|
|
|
IO channel specifiers relevant to the device.
|
|
|
Optional names given to the IO channel specifiers in the "io-channels" property.
|
|
|
Mailbox / IPM channel specifiers relevant to the device.
|
|
|
Optional names given to the mbox specifiers in the "mboxes" property.
|
|
|
Power domain specifiers relevant to the device.
|
|
|
Optional names given to the power domain specifiers in the "power-domains" property.
|
|
|
Number of cells in power-domains property
|
|
|
HW spinlock id relevant to the device.
|
|
|
Optional names given to the hwlock specifiers in the "hwlocks" property.
|
|
|
Do not initialize device automatically on boot. Device should be manually
initialized using device_init().
|
|
|
Property to identify that a device can be used as wake up source.
When this property is provided a specific flag is set into the
device that tells the system that the device is capable of
wake up the system.
Wake up capable devices are disabled (interruptions will not wake up
the system) by default but they can be enabled at runtime if necessary.
|
|
|
Automatically configure the device for runtime power management after the
init function runs.
|
|
|
List of power states that will disable this device power.
|