Lines Matching refs:code

60 .. code-block:: c
105 and such things in your driver, or the code may become complicated. You must
136 .. code-block:: c
208 .. code-block:: c
285 .. code-block:: c
345 .. code-block:: c
363 .. code-block:: c
520   .. code-block:: c
581 .. code-block:: c
752 interface ``<linux/gpio/consumer.h>``: a pin that you grab from kernel code and then
874 .. code-block:: c
893 .. code-block:: c
957 .. code-block:: c
994 .. code-block:: c
1002 .. code-block:: c
1014 .. code-block:: c
1044 .. code-block:: c
1057 .. code-block:: c
1087 .. code-block:: c
1143 .. code-block:: c
1151 .. code-block:: c
1167 This way driver writers do not need to add any of the boilerplate code
1178 control. So if possible, handle the pin control in platform code or some other
1191 .. code-block:: c
1287 .. code-block:: c
1337 .. code-block:: c
1351 .. code-block:: c
1373 .. code-block:: c
1453   .. code-block:: sh