omap-spi.txt 1.3 KB

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