mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-28 11:18:45 +07:00
791d3ef2e1
'interrupt-parent' is often documented as part of define bindings, but it is really outside the scope of a device binding. It's never required in a given node as it is often inherited from a parent node. Or it can be implicit if a parent node is an 'interrupt-controller' node. So remove it from all the binding files. Cc: Mark Rutland <mark.rutland@arm.com> Cc: devicetree@vger.kernel.org Signed-off-by: Rob Herring <robh@kernel.org>
30 lines
900 B
Plaintext
30 lines
900 B
Plaintext
MMC/SD/SDIO slot directly connected to a SPI bus
|
|
|
|
This file documents differences between the core properties described
|
|
by mmc.txt and the properties used by the mmc_spi driver.
|
|
|
|
Required properties:
|
|
- spi-max-frequency : maximum frequency for this device (Hz).
|
|
- voltage-ranges : two cells are required, first cell specifies minimum
|
|
slot voltage (mV), second cell specifies maximum slot voltage (mV).
|
|
Several ranges could be specified.
|
|
|
|
Optional properties:
|
|
- gpios : may specify GPIOs in this order: Card-Detect GPIO,
|
|
Write-Protect GPIO. Note that this does not follow the
|
|
binding from mmc.txt, for historical reasons.
|
|
|
|
Example:
|
|
|
|
mmc-slot@0 {
|
|
compatible = "fsl,mpc8323rdb-mmc-slot",
|
|
"mmc-spi-slot";
|
|
reg = <0>;
|
|
gpios = <&qe_pio_d 14 1
|
|
&qe_pio_d 15 0>;
|
|
voltage-ranges = <3300 3300>;
|
|
spi-max-frequency = <50000000>;
|
|
interrupts = <42>;
|
|
interrupt-parent = <&PIC>;
|
|
};
|