Lines Matching +full:0 +full:a
6 Shields, also known as "add-on" or "daughter boards", attach to a board
26 * **<shield>.overlay**: This file provides a shield description in devicetree
42 to provide a device nodelabel is the form <device>_<shield>, for instance:
54 It is possible to add source code to shields, as a way to meet configuration
65 To effectively incorporate source code: add a :file:`CMakeLists.txt` file, as
74 software compatibility, boards must also provide a configuration matching
81 * Devicetree: A board :ref:`devicetree <dt-guide>` file,
92 If modifications are needed to fit a shield to a particular board or board
93 revision, you can override a shield description for a specific board by adding
94 board or board revision overriding files to a shield, as follows:
119 Alternatively, it could be set by default in a project's CMakeLists.txt:
139 In this case, a shield-particular revision name can be used:
146 You can also provide a board-specific configuration to a specific shield
167 to SOC-specific pins. This is accomplished by including a `nexus
178 gpio-map-mask = <0xffffffff 0xffffffc0>;
179 gpio-map-pass-thru = <0 0x3f>;
180 gpio-map = <0 0 &gpioa 0 0>, /* A0 */
181 <1 0 &gpioa 1 0>, /* A1 */
182 <2 0 &gpioa 4 0>, /* A2 */
183 <3 0 &gpiob 0 0>, /* A3 */
184 <4 0 &gpioc 1 0>, /* A4 */
185 <5 0 &gpioc 0 0>, /* A5 */
186 <6 0 &gpioa 3 0>, /* D0 */
187 <7 0 &gpioa 2 0>, /* D1 */
188 <8 0 &gpioa 10 0>, /* D2 */
189 <9 0 &gpiob 3 0>, /* D3 */
190 <10 0 &gpiob 5 0>, /* D4 */
191 <11 0 &gpiob 4 0>, /* D5 */
192 <12 0 &gpiob 10 0>, /* D6 */
193 <13 0 &gpioa 8 0>, /* D7 */
194 <14 0 &gpioa 9 0>, /* D8 */
195 <15 0 &gpioc 7 0>, /* D9 */
196 <16 0 &gpiob 6 0>, /* D10 */
197 <17 0 &gpioa 7 0>, /* D11 */
198 <18 0 &gpioa 6 0>, /* D12 */
199 <19 0 &gpioa 5 0>, /* D13 */
200 <20 0 &gpiob 9 0>, /* D14 */
201 <21 0 &gpiob 8 0>; /* D15 */
205 0>`` are converted to SOC gpio pin references like ``<&gpiob 4 0>``.
208 ``#gpio-cells = <2>``): the pin number and a set of flags. The low 6
210 devicetree. In some cases it's necessary to use a non-zero flag value
211 to tell the driver how a particular pin behaves, as with:
218 the presence of such a flag would cause the map lookup to fail,
219 because there is no map entry with a non-zero flags value. The