When voltage-ranges property is not present the driver assumes that it is 3.3v (3.2v..3.4v). But at the same time it disallows polling. Fix that by dropping the comparison to 0 when no property is provided. While at it, mark voltage-ranges property optional as it was initially. Fixes: 9c43df57910b ("mmc_spi: Add support for OpenFirmware bindings") Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Link: https://lore.kernel.org/r/20210419112459.25241-3-andriy.shevchenko@linux.intel.com Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
30 lines
940 B
Plaintext
30 lines
940 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).
|
|
|
|
Optional properties:
|
|
- 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. If not provided, 3.2v..3.4v is assumed.
|
|
- 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>;
|
|
};
|