-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Add global HSFLL clock control device driver #81735
base: main
Are you sure you want to change the base?
Add global HSFLL clock control device driver #81735
Conversation
Note @ppelikan-nordic |
The following west manifest projects have changed revision in this Pull Request:
⛔ DNM label due to: 1 project with PR revision Note: This message is automatically posted and updated by the Manifest GitHub Action. |
I need the to update the frequencies to match the opaque |
cbea899
to
197adff
Compare
197adff
to
c71d0d0
Compare
c71d0d0
to
49f2189
Compare
49f2189
to
6b3e913
Compare
6b3e913
to
05a3ac4
Compare
b3d56ce
to
de3678e
Compare
320000000>; | ||
}; | ||
|
||
compatible: "nordic,nrf-global-hsfll" |
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 suggest nordic,nrf-hsfll-global
to align with other Nordic bindings. Maybe even rename the local domain HSFLL binding to nordic,nrf-hsfll-local
.
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 would like to do that, what about renaming hsfll120:
to hsfll_global:
in the devicetree?
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.
It can stay as hsfll120
to match the datasheet.
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.
deal, and done
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.
Okay, you used nordic,nrf-local-hsfll
instead?
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.
oh, sorry, did not notice the change of order :) will update
de3678e
to
4bebaa1
Compare
Update hal_nordic revision to include nrfs services: - GDPWR - GDFS Signed-off-by: Bjarki Arge Andreasen <[email protected]>
nRFs exposes now all power domains, following their actual name in the specification. Add support for all of them in the GPD service. Note that this is a breaking change: running this code requires a new SCFW as IDs have changed in nRFs and so SCFW. Signed-off-by: Gerard Marull-Paretas <[email protected]>
Adding the implementation for the GDFS service Signed-off-by: Paweł Pelikan <[email protected]>
d8652b0
to
1674732
Compare
Add specific device model for global hsfll clock and update dts tree to use specific model. The clock is not fixed, and configurable at runtime to predefined frequencies specified by the platform. Signed-off-by: Bjarki Arge Andreasen <[email protected]>
The nrf-hsfll was previously the only supported HSFLL clock, hence it was not namespaced fully. Since we added nrf-hsfll-global, we should add the namespace to nrf-hsfll as well. Updates drivers and devicetree uses of HSFLL as well. Signed-off-by: Bjarki Arge Andreasen <[email protected]>
Add device driver support for global hsfll clock. Signed-off-by: Bjarki Arge Andreasen <[email protected]>
Extend sample to support global hsfll clock control. Signed-off-by: Bjarki Arge Andreasen <[email protected]>
Extend test suite to test global HSFLL clock. Signed-off-by: Bjarki Arge Andreasen <[email protected]>
Introduce feature which restricts the minimum global hsfll frequency. This feature is selected by default to preserve the behavior of the global hsfll before the clock control driver for it was introduced, which configured it as a fixed clock at 320MHz. Signed-off-by: Bjarki Arge Andreasen <[email protected]>
1674732
to
1d3ce03
Compare
Draft for now since testing is blocked by missing firmware for the nRF54H20