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

Power feature design #9

Open
MrKevinWeiss opened this issue Feb 13, 2024 · 0 comments
Open

Power feature design #9

MrKevinWeiss opened this issue Feb 13, 2024 · 0 comments

Comments

@MrKevinWeiss
Copy link
Contributor

So after a bit of talking we determined the following:

  • Power should be an opt-in feature as developers would probably not need or use it.
  • Better if we don't need caching
  • Every command would start by turning everything on (or maybe turn on as much as possible before error)
  • After the acquire of all devices in a command, all unused boards would turn off
  • After the release of all devices in a command, all unused boards would turn off
  • Once all boards in that batch are done, other remaining devices could attempt to be processed

Assumptions:

  • Boards will not be changed when running a command
  • The time after turning on all boards and acquiring would block any other commands from being used

More eval of uhubctrl will be needed to see if groups of devices can be supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant