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

No way to get clock control subsystem type #5376

Closed
askawu opened this issue Dec 13, 2017 · 1 comment
Closed

No way to get clock control subsystem type #5376

askawu opened this issue Dec 13, 2017 · 1 comment
Assignees
Labels
bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@askawu
Copy link

askawu commented Dec 13, 2017

The clock control API is introduced since 1.9. clock_control_subsys_t is an opaque data structure used to abstract the platform-dependent information. However, there's no way for an application to get a clock_control_subsys_t from somewhere and use it to access clock control API.

For example, on the frdm k64f, the clock control should be configured correctly before accessing pins in port D because the clock control of port D is disabled by default.

IMHO, we should provide a function like device_get_binding() to get the desired clock control subsystem.

@nashif nashif added the bug The issue is a bug, or the PR is fixing a bug label Jan 30, 2018
@nashif nashif added the priority: low Low impact/importance bug label Feb 15, 2018
@carlescufi
Copy link
Member

@askawu I see that device_get_binding() is being used to obtain a reference to an instance of the clock subsystem. Closing this, please reopen if you think this is still an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Development

No branches or pull requests

3 participants