From: Naresh Solanki <naresh.solanki@9elements.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <jdelvare@suse.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
Patrick Rudolph <patrick.rudolph@9elements.com>
Subject: Re: [PATCH v4 1/3] dt-bindings: hwmon: fan: Add fan binding to schema
Date: Tue, 25 Oct 2022 14:46:27 +0530 [thread overview]
Message-ID: <dcd22f70-e51c-290e-c11f-9a5ce32748c1@9elements.com> (raw)
In-Reply-To: <20221024161806.GA1855651-robh@kernel.org>
On 24-10-2022 09:48 pm, Rob Herring wrote:
> So if we unload and reload the driver module, it should go back to the
> default?
This is RPM to be set during probe if desired.
>
> I think it is really, 'target RPM if not already configured' which could
> be keep the setting from a register (e.g. what the bootloader set) or
> perhaps you already have temperature information to use...
Yes. missed it. It should be target-rpm will correct this. in next version.
>
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + pwm-frequency:
>> + description:
>> + PWM frequency for fan in Hertz(Hz).
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> +
>> + pwm-polarity-inverse:
>> + description:
>> + Inverse PWM polarity for fan.
>> + type: boolean
> As I said before, the PWM binding handles these 2 settings. Use it. Yes,
> it's a bit of an overkill when the child is the consumer of the parent.
> Until some 'clever' h/w engineer decides to use one of the PWMs for
> something else like a backlight.
I would like you to consider this as something recommended by fan
datasheet for the given fan instance.
This info can be used by fan controller driver to configure PWM
source/provider accordingly.
If you still feel that may not make sense then I'll remove this property.
Thanks,
Naresh
next prev parent reply other threads:[~2022-10-25 9:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 9:48 [PATCH v4 0/3] Add devicetree support for max6639 Naresh Solanki
2022-10-13 9:48 ` [PATCH v4 1/3] dt-bindings: hwmon: fan: Add fan binding to schema Naresh Solanki
2022-10-24 16:18 ` Rob Herring
2022-10-25 9:16 ` Naresh Solanki [this message]
2022-10-26 13:37 ` Rob Herring
2022-10-31 8:05 ` Naresh Solanki
2022-11-01 18:44 ` Rob Herring
2022-11-01 19:22 ` Naresh Solanki
2022-11-11 21:07 ` Naresh Solanki
2022-10-13 9:48 ` [PATCH v4 2/3] dt-bindings: hwmon: Add binding for max6639 Naresh Solanki
2022-10-13 9:48 ` [PATCH v4 3/3] hwmon: (max6639) Change from pdata to dt configuration Naresh Solanki
2022-10-23 5:53 ` [PATCH v4 0/3] Add devicetree support for max6639 Naresh Solanki
2022-10-25 18:01 ` Guenter Roeck
2022-10-26 7:08 ` Naresh Solanki
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 0:56 [PATCH v4 0/3] hwmon: Driver for Nuvoton NCT7363Y baneric926
2024-02-27 0:56 ` [PATCH v4 1/3] dt-bindings: hwmon: fan: Add fan binding to schema baneric926
2024-03-05 0:22 ` Zev Weiss
2024-03-05 0:41 ` Guenter Roeck
2024-03-05 0:49 ` Guenter Roeck
2024-03-07 7:41 ` Ban Feng
2024-03-07 18:53 ` Guenter Roeck
2024-03-18 0:58 ` Ban Feng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dcd22f70-e51c-290e-c11f-9a5ce32748c1@9elements.com \
--to=naresh.solanki@9elements.com \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=patrick.rudolph@9elements.com \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).