-
Notifications
You must be signed in to change notification settings - Fork 8.2k
[TOPIC-GPIO] drivers: sensor: lsm6dsl: update to new GPIO API #19839
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TOPIC-GPIO] drivers: sensor: lsm6dsl: update to new GPIO API #19839
Conversation
|
All checks passed. checkpatch (informational only, not a failure)Tip: The bot edits this comment instead of posting a new one, so you can check the comment's history to see earlier messages. |
|
@pabigot, can't get it work on |
|
@erwango Sorry, that was a simple error of re-invoking the fetch operation instead of re-enabling the interrupt once the worker completed. Should work now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I already addressed it in #21203. I think it is the proper place (96b_argonkey changes)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But can be done also in this commit honestly.
What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't care where it's done. I'll leave it in here for now, there should be no conflict no matter which gets merged first.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@avisconti Do you have objections to this PR other than that it updates the devicetree binding that it depends on? I don't think I can remove that, unless #21203 is merged first and then this is rebased on it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@avisconti Do you have objections to this PR other than that it updates the devicetree binding that it depends on? I don't think I can remove that, unless #21203 is merged first and then this is rebased on it.
Sure.
dbkinder
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doc change LGTM
avisconti
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it is good!
2b8350e to
260deeb
Compare
MaureenHelm
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update the commit message to say active high rather than active low.
Correct IRQ active level to default active-high, switch to new interrupt configuration. Signed-off-by: Peter Bigot <[email protected]>
260deeb to
b65d799
Compare
Done. |
Correct IRQ active level to default active-low, switch to new interrupt configuration.
Tested with frdm_k64f and nucleo_l476rg with x-nucleo-iks01a2.
NOTE This is based on #19862, #19866, and #19870 on which it depends. It's DNM solely for those inclusions.