From: Rob Herring <robh@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Naresh Solanki" <naresh.solanki@9elements.com>,
devicetree@vger.kernel.org, "Jean Delvare" <jdelvare@suse.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
"Patrick Rudolph" <patrick.rudolph@9elements.com>,
"Marcello Sylvester Bauer" <sylv@sylv.io>,
linux-pwm@vger.kernel.org
Subject: Re: [PATCH v6 3/3] hwmon: (max6639) Change from pdata to dt configuration
Date: Sun, 20 Nov 2022 11:14:48 -0600 [thread overview]
Message-ID: <20221120171448.GA3204528-robh@kernel.org> (raw)
In-Reply-To: <20221120151946.GA1791682@roeck-us.net>
On Sun, Nov 20, 2022 at 07:19:46AM -0800, Guenter Roeck wrote:
> On Thu, Nov 17, 2022 at 10:13:24AM +0100, Uwe Kleine-König wrote:
> > On Thu, Nov 17, 2022 at 02:10:45PM +0530, Naresh Solanki wrote:
> > >
> > >
> > > On 17-11-2022 01:15 pm, Uwe Kleine-König wrote:
> > > > Hello,
> > > >
> > > > On Wed, Nov 16, 2022 at 10:36:15PM +0100, Naresh Solanki wrote:
> > > > > max6639_platform_data is not used by any in-kernel driver and does not
> > > > > address the MAX6639 fans separately.
> > > > > Move to device tree configuration with explicit properties to configure
> > > > > each fan.
> > > > >
> > > > > Non-DT platform can still use this module with its default
> > > > > configuration.
> > > > >
> > > > > Signed-off-by: Marcello Sylvester Bauer <sylv@sylv.io>
> > > > > Signed-off-by: Naresh Solanki <Naresh.Solanki@9elements.com>
> > > >
> > > > What changed here since v5? Please either add a changelog below the
> > > > tripple-dash for a new revision, or make sure that all relevant people
> > > > get the cover letter.
> > > >
> > > > It seems you didn't address my comments for v5 :-\
> > > Not sure what I missed but did following changes:
> > > Removed unused header max6639.h
> > > Used dev_err_probe instead,
> > > Removed of_pwm_n_cells,
> > > if condition for freq_table
> > > removed pwm_get_state & instead use pwm->state
> > > division/multiplication optimizations,
> > > indentation of freq_table,
> >
> > In the cover letter you just wrote:
> >
> > | Changes in V6:
> > | - Remove unused header file
> > | - minor cleanup
> >
> > which is too short in my eyes. If you wrote instead:
> >
> > Address review feedback by Uwe Kleine-König in patch #3, patches #1 and
> > #2 unchanged.
> >
> > This would be much more helpful as people that were already happy with
> > v5 wouldn't need to look at the first two patches and I would know that
> > you addressed my feedback and would have looked in more detail.
> >
> > What I miss is the most critical part of my feedback, i.e.:
> > | My overall impression is that this patch mixes too much things. IMHO it
> > | should be split in (at least)
> > |
> > | - Add dt support
> > | - Drop platform support
> > | - Add PWM provider support
> > | - Make use of the PWM API
> > |
> > | maybe also add the 2nd PWM in a separate step.
>
> Those will definitely need to be separate patches. I am far from convinced
> that all fan controllers in the hwmon subsystem should implement pwm
> providers just to match devicetree requirements. That adds zero value in
> 99% of all use cases. Actually, I don't know of any use cases where it
> would add value or even make sense.
There's no requirement that using a binding means using corresponding
Linux subsystem. Convenient usually, but not required.
Rob
prev parent reply other threads:[~2022-11-20 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221116213615.1256297-1-Naresh.Solanki@9elements.com>
2022-11-16 21:36 ` [PATCH v6 3/3] hwmon: (max6639) Change from pdata to dt configuration Naresh Solanki
2022-11-17 7:45 ` Uwe Kleine-König
2022-11-17 8:40 ` Naresh Solanki
2022-11-17 9:13 ` Uwe Kleine-König
2022-11-18 10:25 ` Naresh Solanki
2022-11-20 15:19 ` Guenter Roeck
2022-11-20 17:14 ` Rob Herring [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=20221120171448.GA3204528-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.com \
--cc=sylv@sylv.io \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).