From: Guenter Roeck <linux@roeck-us.net>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: Jean Delvare <jdelvare@suse.com>,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org
Subject: Re: [PATCH] hwmon: (max6639) : Add DT support
Date: Tue, 24 Sep 2024 08:43:23 -0700 [thread overview]
Message-ID: <84ba0d7f-cb85-4f00-a8a9-ad8e8a56840f@roeck-us.net> (raw)
In-Reply-To: <CABqG17h0+HWSCF0PRVBaj37WYYsz17+n1MD1Uiuscqy_dvU41g@mail.gmail.com>
On 9/24/24 07:44, Naresh Solanki wrote:
> Hi Guenter,
>
> On Tue, 24 Sept 2024 at 19:42, Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> On 9/24/24 02:29, Naresh Solanki wrote:
>>> Hi Guenter,
>>>
>>> Sorry for the late reply,
>>>
>>> On Fri, 28 Jun 2024 at 20:30, Guenter Roeck <linux@roeck-us.net> wrote:
>>>>
>>>> On 6/28/24 04:54, Naresh Solanki wrote:
>>>>> Remove platform data & add devicetree support.
>>>>>
>>>>
>>>> Unless I am missing something, this doesn't just add devicetree support,
>>>> it actually _mandates_ devicetree support. There are no defaults.
>>>> That is not acceptable.
>>> I agree with you. It is best to have some defaults & then overwrite
>>> based on DT properties.
>>> But in that case we would have to assume that all fans are enabled
>>> irrespective of their hardware connections in the schematics(example
>>> fan_enable).
>>>
>>> I'm not sure if that is fine. But if you feel that is alright then
>>> I'll rewrite the driver to assume
>>> everything is enabled with default values.
>>
>> That would still be a functional change, or am I missing something ?
>> It would overwrite any configuration written by a BIOS/ROMMON.
> With that, driver would take the current chip configuration as default &
> just configure specific config specified in DT(if any) & continue with
> initialization?
Yes.
Thanks,
Guenter
prev parent reply other threads:[~2024-09-24 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 11:54 Naresh Solanki
2024-06-28 15:00 ` Guenter Roeck
2024-09-24 9:29 ` Naresh Solanki
2024-09-24 14:12 ` Guenter Roeck
2024-09-24 14:44 ` Naresh Solanki
2024-09-24 15:43 ` Guenter Roeck [this message]
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=84ba0d7f-cb85-4f00-a8a9-ad8e8a56840f@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@9elements.com \
/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
all inboxes | Powered by JetHome®