Difference between revisions of "Device tree"
m (→^ Device Tree bindings files are yml format files) |
m (Add link to Toradex Device Tree document, plus clean up.) |
||
| Line 1: | Line 1: | ||
| − | + | <!-- - SECTION - Manually maintained within-NN-wiki links --> | |
<center> | <center> | ||
[[Unix_and_Linux_config|Unix and Linux config]] :: [[Containers_and_virtual_machines|Containers]] :: [[Zephyr_device_driver_model|Zephyr device drivers]] <!-- <link> --><br /> | [[Unix_and_Linux_config|Unix and Linux config]] :: [[Containers_and_virtual_machines|Containers]] :: [[Zephyr_device_driver_model|Zephyr device drivers]] <!-- <link> --><br /> | ||
| Line 6: | Line 6: | ||
</center> | </center> | ||
| − | <!-- | + | <!-- comentario --> |
| Line 16: | Line 16: | ||
* https://github.com/devicetree-org/devicetree-specification/releases/tag/v0.3 | * https://github.com/devicetree-org/devicetree-specification/releases/tag/v0.3 | ||
</ul>https://docs.zephyrproject.org/2.6.0/reference/devicetree/api.html | </ul>https://docs.zephyrproject.org/2.6.0/reference/devicetree/api.html | ||
| + | |||
| + | * https://developer.toradex.com/linux-bsp/how-to/device-tree/device-tree-customization/ | ||
| + | |||
| + | |||
Today Monday studying section 4.0, "Device Bindings" and binding guidelines. May have questions for [https://community.jaredwolff.com/ Jared Wolff] of CircuitDojo, relating to his [https://github.com/circuitdojo/air-quality-wing-zephyr-drivers/|Air Quality Wing] Zephyr driver project and specifically the [https://github.com/circuitdojo/air-quality-wing-zephyr-drivers/tree/main/dts/bindings|dts files in Jared's AQW project]. | Today Monday studying section 4.0, "Device Bindings" and binding guidelines. May have questions for [https://community.jaredwolff.com/ Jared Wolff] of CircuitDojo, relating to his [https://github.com/circuitdojo/air-quality-wing-zephyr-drivers/|Air Quality Wing] Zephyr driver project and specifically the [https://github.com/circuitdojo/air-quality-wing-zephyr-drivers/tree/main/dts/bindings|dts files in Jared's AQW project]. | ||
| Line 101: | Line 105: | ||
<!-- comentario --> | <!-- comentario --> | ||
| − | == [[#top|^]] | + | == [[#top|^]] Device Tree Undocumented Features == |
0408 - Undocumented Device Tree syntax and features . . . | 0408 - Undocumented Device Tree syntax and features . . . | ||
Early Google search result when seeking info on `/delete-property/` token in Device Tree Source file, observed specifically in Jared Wolff (Circuit Dojo) nfed release tag v1.7.1, active_sleep sample app board overlay file. | Early Google search result when seeking info on `/delete-property/` token in Device Tree Source file, observed specifically in Jared Wolff (Circuit Dojo) nfed release tag v1.7.1, active_sleep sample app board overlay file. | ||
| Line 107: | Line 111: | ||
<!-- comentario --> | <!-- comentario --> | ||
| + | |||
| + | |||
<!-- end of page --> | <!-- end of page --> | ||
Revision as of 19:49, 5 August 2022
Unix and Linux config :: Containers :: Zephyr device drivers
Zephyr RTOS building blocks :: Device Tree Source :: Kconfig :: cmake :: `west` manifest files
2021-08-23 Monday
Starting notes for Device Tree, an OS independent framework with its own governance and steering committee, community, web site and on-line documentation. First Device Tree documentation noted here is:
Today Monday studying section 4.0, "Device Bindings" and binding guidelines. May have questions for Jared Wolff of CircuitDojo, relating to his Quality Wing Zephyr driver project and specifically the files in Jared's AQW project.
Latest Zephyr documentation as of 2021-08-23 is here:
Related to or came up in search result in regards to '_P_label' no such symbol defined errors, when board overlay file not specified or not found:
Contents
^ Some Historical Context
Some device tree historical context given in this Power Point presentation by Thomas Petazzoni of Free Electrons:
^ Device Tree Bindings Files
Noting that in AQW bindings file for SHCT3 sensor there is an include line:
Code excerpt, full file from Jared Wolff AQW driver:
# # Copyright (c) 2021 Circuit Dojo LLC # description: Sensirion SHTC3 Temp/Humidity Sensor compatible: "sensirion,shtc3" include: i2c-device.yaml
The file i2c-device.yaml is found locally in /usr/local/share/ncs/v1.6.1/zephyr/dts/bindings/i2c/i2c-device.yaml, and this file contains:
Code excerpt, full file from Zephyr project:
# Copyright (c) 2017, Linaro Limited
# SPDX-License-Identifier: Apache-2.0
# Common fields for I2C devices
include: [base.yaml, power.yaml]
on-bus: i2c
properties:
reg:
required: true
description: device address on i2c bus
label:
required: true
QUESTION: how does a developer know to include i2c-device.yaml?
A cerca 2022-06-24 post to Jared Wolff community forum:
^ Zephyr Device Tree API - A System Of Macros
^ Device Tree Undocumented Features
0408 - Undocumented Device Tree syntax and features . . . Early Google search result when seeking info on `/delete-property/` token in Device Tree Source file, observed specifically in Jared Wolff (Circuit Dojo) nfed release tag v1.7.1, active_sleep sample app board overlay file.
