On Tue, May 13, 2014 at 8:03 PM, Thomas Abraham <ta.omasab@xxxxxxxxx> wrote: > From: Thomas Abraham <thomas.ab@xxxxxxxxxxx> > > Add a new optional boost-frequency binding for specifying the frequencies > usable in boost mode. > > Cc: Nishanth Menon <nm@xxxxxx> > Cc: Lukasz Majewski <l.majewski@xxxxxxxxxxx> > Cc: Rob Herring <robh+dt@xxxxxxxxxx> > Cc: Pawel Moll <pawel.moll@xxxxxxx> > Cc: Mark Rutland <mark.rutland@xxxxxxx> > Cc: Ian Campbell <ijc+devicetree@xxxxxxxxxxxxxx> > Cc: Kumar Gala <galak@xxxxxxxxxxxxxx> > Signed-off-by: Thomas Abraham <thomas.ab@xxxxxxxxxxx> > --- > .../devicetree/bindings/cpufreq/cpufreq-boost.txt | 11 +++++++++++ > 1 files changed, 11 insertions(+), 0 deletions(-) > create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-boost.txt > > diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-boost.txt b/Documentation/devicetree/bindings/cpufreq/cpufreq-boost.txt > new file mode 100644 > index 0000000..d925e38 > --- /dev/null > +++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-boost.txt > @@ -0,0 +1,11 @@ > +* Device tree binding for CPU boost frequency (aka over-clocking) > + > +Certain CPU's can be operated in optional 'boost' mode (or sometimes referred as > +overclocking) in which the CPU can operate in frequencies beyond the normal "operate at"? > +operating conditions. "normal operating conditions" probably need a little bit of an expansion here perhaps? > + > +Optional Properties: > +- boost-frequency: list of frequencies in KHz to be used only in boost mode. probably boost-frequencies? > + This list should be a subset of frequencies listed in "operating-points" > + property. Refer to Documentation/devicetree/bindings/power/opp.txt for > + details about "operating-points" property. an example is expected here. personally, I think I understand the intent here, but as a hardware description, will let folks comment if it is acceptable. -- Regards, Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
