lkml.org 
[lkml]   [2014]   [Dec]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 2/9] hwmon: dts: Doc: Add DTS doc to explain how to use PWM FAN as a cooling device
    On 12/18/2014 02:13 AM, Lukasz Majewski wrote:
    > Several new properties to allow PWM fan working as a cooling device have been
    > combined into this single commit.
    >
    > Signed-off-by: Lukasz Majewski <l.majewski@samsung.com>
    > ---
    > .../devicetree/bindings/hwmon/pwm-fan.txt | 28 ++++++++++++++++++++++
    > 1 file changed, 28 insertions(+)
    >
    > diff --git a/Documentation/devicetree/bindings/hwmon/pwm-fan.txt b/Documentation/devicetree/bindings/hwmon/pwm-fan.txt
    > index 610757c..3877810 100644
    > --- a/Documentation/devicetree/bindings/hwmon/pwm-fan.txt
    > +++ b/Documentation/devicetree/bindings/hwmon/pwm-fan.txt
    > @@ -3,10 +3,38 @@ Bindings for a fan connected to the PWM lines
    > Required properties:
    > - compatible : "pwm-fan"
    > - pwms : the PWM that is used to control the PWM fan
    > +- cooling-pwm-values : PWM duty cycle values relative to
    > + cooling-max-pwm-value correspondig to
    > + proper cooling states

    I don't understand what you mean with "relative to". Please elaborate.
    Do you mean "associated with" ?

    Where is "cooling-max-pwm-value" defined, and how is this all expected
    to relate to the maximum duty cycle value provided by the pwm device ?

    > +- default-pulse-width : Property specifying default pulse width for FAN
    > + at system boot (zero to disable FAN on boot).
    > + Allowed range is 0 to 255

    You'll need dt maintainer approval for the new properties.

    One thing I wonder about though is why you use "default-pulse-width"
    and not "default-pwm". Seems to be arbitrary. I don't see "pulse-width"
    used anywhere in the upstream kernel.

    I am somewhat concerned that you define the new properties as mandatory.
    That means existing configurations will fail, which does not seem to be
    a good idea. It would be more appropriate to not configure the thermal device
    if the new properties are not provided.

    The newly introduced semantics also conflicts with the current semantics,
    which sets the initial duty cycle initially to the maximum allowed duty cycle
    as reported by the pwm device itself.

    Guenter

    > +
    > +Thorough description of the following bindings:
    > + cooling-min-state = <0>;
    > + cooling-max-state = <3>;
    > + #cooling-cells = <2>;
    > + thermal-zone {
    > + cpu_thermal: cpu-thermal {
    > + cooling-maps {
    > + map0 {
    > + trip = <&cpu_alert1>;
    > + cooling-device = <&fan0 0 1>;
    > + };
    > + };
    > + };
    > +
    > +for PWM FAN used as cooling device can be found at:
    > +./Documentation/devicetree/bindings/thermal/thermal.txt
    >
    > Example:
    > pwm-fan {
    > compatible = "pwm-fan";
    > status = "okay";
    > pwms = <&pwm 0 10000 0>;
    > + cooling-min-state = <0>;
    > + cooling-max-state = <3>;
    > + #cooling-cells = <2>;
    > + cooling-pwm-values = <0 102 170 255>;
    > + default-pulse-width = <0>;
    > };
    >



    \
     
     \ /
      Last update: 2014-12-18 16:01    [W:3.727 / U:0.280 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site