Add a property "clock-N-frequency" to the clock consumer bindings to specify the frequency that a clock should be configured to when it is made use of. N is the index of a clock specifier in the clocks property, starting at 0.
This avoids the need to add clock-frequency properties to individual device bindings or modify drivers to set the frequency of clocks to that requested in device tree. Instead the driver can just read the rate of the clock as if it was fixed. This is aimed at devices where it's difficult for drivers to determine what a clock should be set to, and either there is a recommended frequency for the particular system or a chosen frequency for the particular application of the system (which makes it essentially configuration data). Signed-off-by: James Hogan <[email protected]> Cc: Mike Turquette <[email protected]> Cc: Russell King <[email protected]> Cc: [email protected] Cc: Ian Campbell <[email protected]> Cc: Mark Rutland <[email protected]> Cc: Pawel Moll <[email protected]> Cc: Rob Herring <[email protected]> Cc: Stephen Warren <[email protected]> Cc: [email protected] Cc: Rob Landley <[email protected]> Cc: [email protected] --- Documentation/devicetree/bindings/clock/clock-bindings.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation/devicetree/bindings/clock/clock-bindings.txt b/Documentation/devicetree/bindings/clock/clock-bindings.txt index eb65d41..e8bca1a 100644 --- a/Documentation/devicetree/bindings/clock/clock-bindings.txt +++ b/Documentation/devicetree/bindings/clock/clock-bindings.txt @@ -60,6 +60,9 @@ clock-names: List of clock input name strings sorted in the same clock-ranges: Empty property indicating that child nodes can inherit named clocks from this node. Useful for bus nodes to provide a clock to their children. +clock-N-frequency: Single cell specifying the frequency in HZ to set the N'th + clock to when it is used. N=0 corresponds to the first clock + specifier in the clocks property. For example: -- 1.8.3.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
