sensors: lps22hb: Enhance driver with trigger

[stubb0rnCoder]

Using the LPS22HH driver as a basis, this PR replaces the very limited existing driver for the HB variant with a more sophisticated one that allows setting a trigger and gives a basis for further improvements.

[github-actions[bot]]

Hello @stubb0rnCoder, and thank you very much for your first pull request to the Zephyr project! Our Continuous Integration pipeline will execute a series of checks on your Pull Request commit messages and code, and you are expected to address any failures by updating the PR. Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request. If you haven't already, please make sure to review the project's Contributor Expectations and update (by amending and force-pushing the commits) your pull request if necessary. If you are stuck or need help please join us on Discord and ask your question there. Additionally, you can escalate the review when applicable. 😊

[stubb0rnCoder]

Also split the work into atomic commits

Would you like me to split the already commited work or for future work?

PS. This is my first PR to Zephyr and I struggled a bit with signing-off so I ended up with a single commit to fix commits accidently not singed off

[avisconti]

Also split the work into atomic commits

Would you like me to split the already commited work or for future work?

PS. This is my first PR to Zephyr and I struggled a bit with signing-off so I ended up with a single commit to fix commits accidently not singed off

I think you need to rebase. Then what I was asking was to arrange the work into a proper commit flow. If the only thing you did was to change lps22hb into a modern form (like lps22hh), then I guess a single commit is enough. And remember to provide a proper commit message as well.

[glenn-andrews]

Also, if you do make it so that existing code does not need updating, I'd split this into two PRs: One PR for the driver code, which will still work with the existing boards and samples, and a PR updating the boards and samples to the new name.

Multiple smaller PRs are easier to review.

[github-actions[bot]]

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.

[glenn-andrews]

@stubb0rnCoder If you're still around I'd love to work with you on landing this.