schemas: introduce assigned-clock-rates-u64 #140
Conversation
|
@robherring do you have time to give a look on this? Thanks. |
To support rates that exceeds UINT32_MAX, introduce assigned-clock-rates-u64 Signed-off-by: Peng Fan <[email protected]>
BTW, before pinging someone you could answer to existing review. You do not need two reviewers telling you that 32-bit would not work. One reviewer is enough... |
dtschema/schemas/clock/clock.yaml
Outdated
| @@ -129,6 +129,8 @@ properties: | |||
| $ref: /schemas/types.yaml#/definitions/phandle-array | |||
| assigned-clock-rates: | |||
| $ref: /schemas/types.yaml#/definitions/uint32-array | |||
| assigned-clock-rates-u64: | |||
| $ref: /schemas/types.yaml#/definitions/uint32-array | |||
There was a problem hiding this comment.
So how does this exactly work for you? Can you show DTS example using this?
There was a problem hiding this comment.
`
assigned-clocks =<&scmi_clk IMX95_CLK_HSIOPLL_VCO>;
assigned-clock-rates-u64 = <0x1 0x1e1a3000>;
`
The linux patch: https://lore.kernel.org/all/[email protected]/
There was a problem hiding this comment.
So you can see it is not u32 value... Never mind.
@krzk sorry, I not see comment in this page before I asked Rob to comment. From go through this page, I only see Rob has a comment several hours before. |
My gmail shows |
To support rates that exceeds UINT32_MAX, introduce assigned-clock-rates-u64