cnxt,cx92755-pinctrl.txt 2.9 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586
  1. Conexant Digicolor CX92755 General Purpose Pin Mapping
  2. This document describes the device tree binding of the pin mapping hardware
  3. modules in the Conexant Digicolor CX92755 SoCs. The CX92755 in one of the
  4. Digicolor series of SoCs.
  5. === Pin Controller Node ===
  6. Required Properties:
  7. - compatible: Must be "cnxt,cx92755-pinctrl"
  8. - reg: Base address of the General Purpose Pin Mapping register block and the
  9. size of the block.
  10. - gpio-controller: Marks the device node as a GPIO controller.
  11. - #gpio-cells: Must be <2>. The first cell is the pin number and the
  12. second cell is used to specify flags. See include/dt-bindings/gpio/gpio.h
  13. for possible values.
  14. For example, the following is the bare minimum node:
  15. pinctrl: pinctrl@f0000e20 {
  16. compatible = "cnxt,cx92755-pinctrl";
  17. reg = <0xf0000e20 0x100>;
  18. gpio-controller;
  19. #gpio-cells = <2>;
  20. };
  21. As a pin controller device, in addition to the required properties, this node
  22. should also contain the pin configuration nodes that client devices reference,
  23. if any.
  24. For a general description of GPIO bindings, please refer to ../gpio/gpio.txt.
  25. === Pin Configuration Node ===
  26. Each pin configuration node is a sub-node of the pin controller node and is a
  27. container of an arbitrary number of subnodes, called pin group nodes in this
  28. document.
  29. Please refer to the pinctrl-bindings.txt in this directory for details of the
  30. common pinctrl bindings used by client devices, including the definition of a
  31. "pin configuration node".
  32. === Pin Group Node ===
  33. A pin group node specifies the desired pin mux for an arbitrary number of
  34. pins. The name of the pin group node is optional and not used.
  35. A pin group node only affects the properties specified in the node, and has no
  36. effect on any properties that are omitted.
  37. The pin group node accepts a subset of the generic pin config properties. For
  38. details generic pin config properties, please refer to pinctrl-bindings.txt
  39. and <include/linux/pinctrl/pinconfig-generic.h>.
  40. Required Pin Group Node Properties:
  41. - pins: Multiple strings. Specifies the name(s) of one or more pins to be
  42. configured by this node. The format of a pin name string is "GP_xy", where x
  43. is an uppercase character from 'A' to 'R', and y is a digit from 0 to 7.
  44. - function: String. Specifies the pin mux selection. Values must be one of:
  45. "gpio", "client_a", "client_b", "client_c"
  46. Example:
  47. pinctrl: pinctrl@f0000e20 {
  48. compatible = "cnxt,cx92755-pinctrl";
  49. reg = <0xf0000e20 0x100>;
  50. uart0_default: uart0_active {
  51. data_signals {
  52. pins = "GP_O0", "GP_O1";
  53. function = "client_b";
  54. };
  55. };
  56. };
  57. uart0: uart@f0000740 {
  58. compatible = "cnxt,cx92755-usart";
  59. ...
  60. pinctrl-0 = <&uart0_default>;
  61. pinctrl-names = "default";
  62. };
  63. In the example above, a single pin group configuration node defines the
  64. "client select" for the Rx and Tx signals of uart0. The uart0 node references
  65. that pin configuration node using the &uart0_default phandle.