| Benoit Cousson | d5a8003 | 2012-02-15 18:37:34 +0100 | [diff] [blame] | 1 | OMAP2+ McSPI device |
| 2 | |
| 3 | Required properties: |
| 4 | - compatible : |
| 5 | - "ti,omap2-spi" for OMAP2 & OMAP3. |
| 6 | - "ti,omap4-spi" for OMAP4+. |
| 7 | - ti,spi-num-cs : Number of chipselect supported by the instance. |
| 8 | - ti,hwmods: Name of the hwmod associated to the McSPI |
| Daniel Mack | 2cd4517 | 2012-11-14 11:14:26 +0800 | [diff] [blame] | 9 | - ti,pindir-d0-out-d1-in: Select the D0 pin as output and D1 as |
| 10 | input. The default is D0 as input and |
| 11 | D1 as output. |
| Benoit Cousson | d5a8003 | 2012-02-15 18:37:34 +0100 | [diff] [blame] | 12 | |
| Matt Porter | 0b9e49e | 2013-06-24 17:31:59 +0530 | [diff] [blame] | 13 | Optional properties: |
| 14 | - dmas: List of DMA specifiers with the controller specific format |
| 15 | as described in the generic DMA client binding. A tx and rx |
| 16 | specifier is required for each chip select. |
| 17 | - dma-names: List of DMA request names. These strings correspond |
| 18 | 1:1 with the DMA specifiers listed in dmas. The string naming |
| 19 | is to be "rxN" and "txN" for RX and TX requests, |
| 20 | respectively, where N equals the chip select number. |
| 21 | |
| 22 | Examples: |
| 23 | |
| 24 | [hwmod populated DMA resources] |
| Benoit Cousson | d5a8003 | 2012-02-15 18:37:34 +0100 | [diff] [blame] | 25 | |
| 26 | mcspi1: mcspi@1 { |
| 27 | #address-cells = <1>; |
| 28 | #size-cells = <0>; |
| 29 | compatible = "ti,omap4-mcspi"; |
| 30 | ti,hwmods = "mcspi1"; |
| 31 | ti,spi-num-cs = <4>; |
| 32 | }; |
| 33 | |
| Matt Porter | 0b9e49e | 2013-06-24 17:31:59 +0530 | [diff] [blame] | 34 | [generic DMA request binding] |
| 35 | |
| 36 | mcspi1: mcspi@1 { |
| 37 | #address-cells = <1>; |
| 38 | #size-cells = <0>; |
| 39 | compatible = "ti,omap4-mcspi"; |
| 40 | ti,hwmods = "mcspi1"; |
| 41 | ti,spi-num-cs = <2>; |
| 42 | dmas = <&edma 42 |
| 43 | &edma 43 |
| 44 | &edma 44 |
| 45 | &edma 45>; |
| 46 | dma-names = "tx0", "rx0", "tx1", "rx1"; |
| 47 | }; |