Skip to content
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

doc/configuration: update/fix bindings, protocols and resource usage #1322

Merged
merged 15 commits into from
Mar 14, 2024

Conversation

Bastian-Krause
Copy link
Member

@Bastian-Krause Bastian-Krause commented Jan 26, 2024

Description
Initially, all driver bindings were documented with their respective binding key. This wasn't documented consistently since then.

Especially when using multiple instances of a single driver class, the bindings are needed to specify on which resource or other driver a driver should bind on. Until now, most binding keys had to be looked up in the source code. So improve this situation by fixing and adding binding keys as well as also adding all Remote/Network resource variants a driver is able to bind to.

Also update protocol implementations and resource usage. While at it, document drivers not expecting arguments, drop driver usage from network resouces, fix header underlines and remove unnecessary new lines.

Checklist

  • PR has been tested

Copy link

codecov bot commented Jan 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (91c7e9c) 62.8% compared to head (9e43814) 62.8%.

Additional details and impacted files
@@           Coverage Diff            @@
##           master   #1322     +/-   ##
========================================
- Coverage    62.8%   62.8%   -0.1%     
========================================
  Files         163     163             
  Lines       12019   12019             
========================================
- Hits         7550    7549      -1     
- Misses       4469    4470      +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Bastian-Krause
Copy link
Member Author

CI fails due to #1327.

This fixes list rendering.

Signed-off-by: Bastian Krause <bst@pengutronix.de>
Signed-off-by: Bastian Krause <bst@pengutronix.de>
Signed-off-by: Bastian Krause <bst@pengutronix.de>
Signed-off-by: Bastian Krause <bst@pengutronix.de>
Signed-off-by: Bastian Krause <bst@pengutronix.de>
Other network resourced do not list the drivers using them, neither.

Signed-off-by: Bastian Krause <bst@pengutronix.de>
Initially, all driver bindings were documented with their respective
binding key. This wasn't documented consistently since then.

Especially when using multiple instances of a single driver class, the
bindings are needed to specify on which resource or other driver the
driver should bind on. Until now, most binding keys had to be looked up
in the source code. So improve this situation by fixing and adding
binding keys as well as also adding all Remote/Network resource variants
a driver is able to bind to.

Signed-off-by: Bastian Krause <bst@pengutronix.de>
Signed-off-by: Bastian Krause <bst@pengutronix.de>
Signed-off-by: Bastian Krause <bst@pengutronix.de>
Explicitly quote string top prevent strange yaml string auto dection
issues. Also use better readable dict notation everywhere.

Signed-off-by: Bastian Krause <bst@pengutronix.de>
Signed-off-by: Bastian Krause <bst@pengutronix.de>
Signed-off-by: Bastian Krause <bst@pengutronix.de>
…yaml snippet

In the previous form, it looks like the environemnt's "drivers" section
also contains the "images" section, which is not the case. Make that
clear by splitting both sections into their own snippet.

Signed-off-by: Bastian Krause <bst@pengutronix.de>
…busRTUDriver

Signed-off-by: Bastian Krause <bst@pengutronix.de>
Signed-off-by: Bastian Krause <bst@pengutronix.de>
@Bastian-Krause
Copy link
Member Author

Rebased on current master.

@Bastian-Krause Bastian-Krause merged commit be28ac1 into labgrid-project:master Mar 14, 2024
10 of 11 checks passed
@Bastian-Krause Bastian-Krause deleted the bst/doc-update branch March 14, 2024 07:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants