Merge remote-tracking branches 'spi/topic/bfin-sport', 'spi/topic/bfin5xx', 'spi/topic/clps711x', 'spi/topic/doc' and 'spi/topic/dt' into spi-next
This commit is contained in:
@@ -8,11 +8,10 @@ in slave mode.
|
||||
|
||||
The SPI master node requires the following properties:
|
||||
- #address-cells - number of cells required to define a chip select
|
||||
address on the SPI bus.
|
||||
address on the SPI bus.
|
||||
- #size-cells - should be zero.
|
||||
- compatible - name of SPI bus controller following generic names
|
||||
recommended practice.
|
||||
- cs-gpios - (optional) gpios chip select.
|
||||
recommended practice.
|
||||
No other properties are required in the SPI bus node. It is assumed
|
||||
that a driver for an SPI bus device will understand that it is an SPI bus.
|
||||
However, the binding does not attempt to define the specific method for
|
||||
@@ -22,11 +21,12 @@ assumption that board specific platform code will be used to manage
|
||||
chip selects. Individual drivers can define additional properties to
|
||||
support describing the chip select layout.
|
||||
|
||||
Optional property:
|
||||
- num-cs : total number of chipselects
|
||||
Optional properties:
|
||||
- cs-gpios - gpios chip select.
|
||||
- num-cs - total number of chipselects.
|
||||
|
||||
If cs-gpios is used the number of chip select will automatically increased
|
||||
with max(cs-gpios > hw cs)
|
||||
If cs-gpios is used the number of chip selects will be increased automatically
|
||||
with max(cs-gpios > hw cs).
|
||||
|
||||
So if for example the controller has 2 CS lines, and the cs-gpios
|
||||
property looks like this:
|
||||
@@ -45,29 +45,30 @@ SPI slave nodes must be children of the SPI master node and can
|
||||
contain the following properties.
|
||||
- reg - (required) chip select address of device.
|
||||
- compatible - (required) name of SPI device following generic names
|
||||
recommended practice
|
||||
- spi-max-frequency - (required) Maximum SPI clocking speed of device in Hz
|
||||
recommended practice.
|
||||
- spi-max-frequency - (required) Maximum SPI clocking speed of device in Hz.
|
||||
- spi-cpol - (optional) Empty property indicating device requires
|
||||
inverse clock polarity (CPOL) mode
|
||||
inverse clock polarity (CPOL) mode.
|
||||
- spi-cpha - (optional) Empty property indicating device requires
|
||||
shifted clock phase (CPHA) mode
|
||||
shifted clock phase (CPHA) mode.
|
||||
- spi-cs-high - (optional) Empty property indicating device requires
|
||||
chip select active high
|
||||
chip select active high.
|
||||
- spi-3wire - (optional) Empty property indicating device requires
|
||||
3-wire mode.
|
||||
3-wire mode.
|
||||
- spi-lsb-first - (optional) Empty property indicating device requires
|
||||
LSB first mode.
|
||||
- spi-tx-bus-width - (optional) The bus width(number of data wires) that
|
||||
- spi-tx-bus-width - (optional) The bus width (number of data wires) that is
|
||||
used for MOSI. Defaults to 1 if not present.
|
||||
- spi-rx-bus-width - (optional) The bus width(number of data wires) that
|
||||
- spi-rx-bus-width - (optional) The bus width (number of data wires) that is
|
||||
used for MISO. Defaults to 1 if not present.
|
||||
- spi-rx-delay-us - (optional) Microsecond delay after a read transfer.
|
||||
- spi-tx-delay-us - (optional) Microsecond delay after a write transfer.
|
||||
|
||||
Some SPI controllers and devices support Dual and Quad SPI transfer mode.
|
||||
It allows data in the SPI system to be transferred in 2 wires(DUAL) or 4 wires(QUAD).
|
||||
It allows data in the SPI system to be transferred using 2 wires (DUAL) or 4
|
||||
wires (QUAD).
|
||||
Now the value that spi-tx-bus-width and spi-rx-bus-width can receive is
|
||||
only 1(SINGLE), 2(DUAL) and 4(QUAD).
|
||||
only 1 (SINGLE), 2 (DUAL) and 4 (QUAD).
|
||||
Dual/Quad mode is not allowed when 3-wire mode is used.
|
||||
|
||||
If a gpio chipselect is used for the SPI slave the gpio number will be passed
|
||||
|
33
Documentation/devicetree/bindings/spi/spi-clps711x.txt
Normal file
33
Documentation/devicetree/bindings/spi/spi-clps711x.txt
Normal file
@@ -0,0 +1,33 @@
|
||||
Serial Peripheral Interface on Cirrus Logic CL-PS71xx, EP72xx, EP73xx
|
||||
|
||||
Required properties
|
||||
- #address-cells: must be <1>
|
||||
- #size-cells: must be <0>
|
||||
- compatible: should include "cirrus,ep7209-spi"
|
||||
- reg: Address and length of one register range
|
||||
- interrupts: one interrupt line
|
||||
- clocks: One entry, refers to the SPI bus clock
|
||||
- cs-gpios: Specifies the gpio pins to be used for chipselects.
|
||||
See: Documentation/devicetree/bindings/spi/spi-bus.txt
|
||||
|
||||
An additional register is present in the system controller,
|
||||
which is assumed to be in the same device tree, with and marked
|
||||
as compatible with "cirrus,ep7209-syscon3".
|
||||
|
||||
Example:
|
||||
|
||||
spi@80000500 {
|
||||
#address-cells = <1>;
|
||||
#size-cells = <0>;
|
||||
compatible = "cirrus,ep7209-spi";
|
||||
reg = <0x80000500 0x4>;
|
||||
interrupts = <15>;
|
||||
clocks = <&clks CLPS711X_CLK_SPI>;
|
||||
status = "disabled";
|
||||
};
|
||||
|
||||
syscon3: syscon@80002200 {
|
||||
compatible = "cirrus,ep7209-syscon3", "syscon";
|
||||
reg = <0x80002200 0x40>;
|
||||
};
|
||||
|
@@ -21,7 +21,7 @@ Required properties:
|
||||
IP to the interrupt controller within the SoC. Possible values
|
||||
are 0 and 1. Manual says one of the two possible interrupt
|
||||
lines can be tied to the interrupt controller. Set this
|
||||
based on a specifc SoC configuration.
|
||||
based on a specific SoC configuration.
|
||||
- interrupts: interrupt number mapped to CPU.
|
||||
- clocks: spi clk phandle
|
||||
|
||||
|
@@ -20,7 +20,7 @@ Optional properties:
|
||||
chipselect register and offset of that register.
|
||||
|
||||
NOTE: TI QSPI controller requires different pinmux and IODelay
|
||||
paramaters for Mode-0 and Mode-3 operations, which needs to be set up by
|
||||
parameters for Mode-0 and Mode-3 operations, which needs to be set up by
|
||||
the bootloader (U-Boot). Default configuration only supports Mode-0
|
||||
operation. Hence, "spi-cpol" and "spi-cpha" DT properties cannot be
|
||||
specified in the slave nodes of TI QSPI controller without appropriate
|
||||
|
Reference in New Issue
Block a user