d1e1643b84
This commit introduces 2 new fields in the onewire_master_s struct: uint64_t selected_rom, uint64_t *available_roms. The key point behind this is to allow onewire_search to capture all devices on the bus into the kernel struct. While this commit is keeping the old API (for the sake of not messing everything up), you don't have to reimplement the search of all roms in very strange ways (such as custom callbacks into the userspace). Instead of that, a generic ioctl (only a function to be called from the device driver) was implemented, that searches the bus (for a particular 1wire family), saves it and then copies it in a standard way to your application. The ioctl is called ONEWIREIOC_GETFAMILYROMS. Also as 1wire can interface multiple devices, a API telling the driver which ROM to interface was missing, this commit fixes this with the ONEWIREIOC_SETROM call. The example usage is you first get all the devices on the bus using ONEWIREIOC_GETFAMILYROMS. In your application, you choose the correct device you want to talk to. Then you call ONEWIREIOC_SETROM. And then writes, reads, ... Signed-off-by: Stepan Pressl <pressl.stepan@gmail.com> |
||
|---|---|---|
| .github | ||
| arch | ||
| audio | ||
| binfmt | ||
| boards | ||
| cmake | ||
| crypto | ||
| Documentation | ||
| drivers | ||
| dummy | ||
| fs | ||
| graphics | ||
| include | ||
| libs | ||
| mm | ||
| net | ||
| openamp | ||
| pass1 | ||
| sched | ||
| syscall | ||
| tools | ||
| video | ||
| wireless | ||
| .asf.yaml | ||
| .codespell-ignore-lines | ||
| .codespellrc | ||
| .editorconfig | ||
| .gitignore | ||
| .gitmessage | ||
| .pre-commit-config.yaml | ||
| .yamllint | ||
| AUTHORS | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| INVIOLABLES.md | ||
| Kconfig | ||
| LICENSE | ||
| Makefile | ||
| NOTICE | ||
| README.md | ||
| ReleaseNotes | ||
Apache NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOSs (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).
For brevity, many parts of the documentation will refer to Apache NuttX as simply NuttX.
Getting Started
First time on NuttX? Read the Getting Started guide! If you don't have a board available, NuttX has its own simulator that you can run on terminal.
Documentation
You can find the current NuttX documentation on the Documentation Page.
Alternatively, you can build the documentation yourself by following the Documentation Build Instructions.
The old NuttX documentation is still available in the Apache wiki.
Supported Boards
NuttX supports a wide variety of platforms. See the full list on the Supported Platforms page.
Contributing
If you wish to contribute to the NuttX project, read the Contributing guidelines for information on Git usage, coding standard, workflow and the NuttX principles.
License
The code in this repository is under either the Apache 2 license, or a license compatible with the Apache 2 license. See the License Page for more information.