You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is not yet a PR in Zephyr to support querying any kind of state from GPIO devices.
It has previously been stated that the application should keep track of any such state.
However, as a generalization, the hardware itself keeps track of GPIO state. Whether or not it's possible to query those values from hardware is another issue. Also synchronization of those values is yet another issue.
The existing patch simply keeps track of GPIO state in software, but the eventual API should be flexible enough to allow specific drivers to implement it with hardware-specific register accesses or alternatively using the basic software approach.
The README.rst file should be updated to reflect the patches that must be applied.
The text was updated successfully, but these errors were encountered:
The change was merged in zephyrproject-rtos/zephyr#40325. It likely will not be backported, so perhaps pinning to LTSv2 is unrealistic. May need to revisit #70
There is not yet a PR in Zephyr to support querying any kind of state from GPIO devices.
It has previously been stated that the application should keep track of any such state.
However, as a generalization, the hardware itself keeps track of GPIO state. Whether or not it's possible to query those values from hardware is another issue. Also synchronization of those values is yet another issue.
The existing patch simply keeps track of GPIO state in software, but the eventual API should be flexible enough to allow specific drivers to implement it with hardware-specific register accesses or alternatively using the basic software approach.
The README.rst file should be updated to reflect the patches that must be applied.
The text was updated successfully, but these errors were encountered: