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
Is your feature request related to a problem? Please describe.
I'd like to use the externally driven trigger/clock source for counters (edge causes counter to
increment) for frequency counting in a hardware agnostic way.
Describe the solution you'd like
A way to tell the counter it should be driven by an external pin. It would make sense I think to use DTS to describe the pin/clock source to use and on which edge(s) to increment on.
Describe alternatives you've considered
I can of course use the vender specific driver libraries as needed, and I will be for
an upcoming project. I'd like to do it in a vendor agnostic way.
The text was updated successfully, but these errors were encountered:
As far I see it, that is already fully supported by the current counter API. It is just a matter of having a driver, that configures the underlying counter hardware for counting external events (I have implemented a few these out-of-tree using the counter API already).
Is your feature request related to a problem? Please describe.
I'd like to use the externally driven trigger/clock source for counters (edge causes counter to
increment) for frequency counting in a hardware agnostic way.
Describe the solution you'd like
A way to tell the counter it should be driven by an external pin. It would make sense I think to use DTS to describe the pin/clock source to use and on which edge(s) to increment on.
Describe alternatives you've considered
I can of course use the vender specific driver libraries as needed, and I will be for
an upcoming project. I'd like to do it in a vendor agnostic way.
The text was updated successfully, but these errors were encountered: