From: Jonathan Cameron <jic23@kernel.org>
To: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Cc: Sean Nyekjaer <sean@geanix.com>, <lars@metafoo.de>,
<alexandre.torgue@foss.st.com>, <nuno.sa@analog.com>,
<linux-iio@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
Olivier Moysan <olivier.moysan@foss.st.com>
Subject: Re: [Linux-stm32] [PATCH 1/3] iio: adc: stm32-adc: warn if dt uses legacy channel config
Date: Sat, 1 Apr 2023 15:04:55 +0100 [thread overview]
Message-ID: <20230401150455.3e426d1e@jic23-huawei> (raw)
In-Reply-To: <56c019d4-832e-17e1-19f8-7d8bd927c1bb@foss.st.com>
On Thu, 30 Mar 2023 17:30:32 +0200
Fabrice Gasnier <fabrice.gasnier@foss.st.com> wrote:
> On 3/27/23 10:34, Sean Nyekjaer wrote:
> > Since nearly all stm32 dt's are using the legacy adc channel config,
> > we should warn users about using it.
> >
> > Signed-off-by: Sean Nyekjaer <sean@geanix.com>
> > ---
> > drivers/iio/adc/stm32-adc.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/iio/adc/stm32-adc.c b/drivers/iio/adc/stm32-adc.c
> > index 1aadb2ad2cab..d8e755d0cc52 100644
> > --- a/drivers/iio/adc/stm32-adc.c
> > +++ b/drivers/iio/adc/stm32-adc.c
> > @@ -1993,6 +1993,8 @@ static int stm32_adc_get_legacy_chan_count(struct iio_dev *indio_dev, struct stm
> > const struct stm32_adc_info *adc_info = adc->cfg->adc_info;
> > int num_channels = 0, ret;
> >
> > + dev_warn(&indio_dev->dev, "using legacy channel config\n");
> > +
>
> Hi Sean,
>
> I'd recommend to avoid adding a dev_warn() on a per driver basis, for
> depreacted DT properties. Still I'm not sure if there's some policy in
> this area.
>
> IMHO, deprecated properties should be checked by using dt tools
> (dt_binding_check / dtbs_check or other mean?). But I have no idea if
> this is going to report warnings and when. Purpose would be to avoid
> introducing no dts files with these. As commented by Olivier on Patch 3,
> we've some downstream patches to adopt the generic bindings (not
> upstream 'yet').
>
> Another downside is regarding backward compatibility. In case an old dtb
> is used to boot the kernel, as long as there's no functionality loss,
> I'd advise not to use any warning here. That's a valid use of an old dt.
>
> In all case, thanks for pointing issues (e.g. Patch 2 & 3), regarding
> this patch, I'd nack adding this warning. Please drop this change if you
> re-submit or turn this into a dev_dbg().
>
Agreed. Better to change to dev_dbg().
Other two patches look good to me, but will leave a bit more time for others
to comment before I pick them up. As a small side note. They are fixes and
this first patch is not, so they should have been before it in the series
so I can route them to mainline faster than the non fix.
Jonathan
> Best Regards,
> Fabrice
>
> > ret = device_property_count_u32(dev, "st,adc-channels");
> > if (ret > adc_info->max_channels) {
> > dev_err(&indio_dev->dev, "Bad st,adc-channels?\n");
next prev parent reply other threads:[~2023-04-01 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 8:34 [PATCH 1/3] iio: adc: stm32-adc: warn if dt uses legacy channel config Sean Nyekjaer
2023-03-27 8:34 ` [PATCH 2/3] iio: adc: stm32-adc: skip adc-diff-channels setup if none is present Sean Nyekjaer
2023-03-27 8:34 ` [PATCH 3/3] iio: adc: stm32-adc: skip adc-channels " Sean Nyekjaer
2023-04-03 9:29 ` [Linux-stm32] " Olivier MOYSAN
2023-03-30 15:30 ` [Linux-stm32] [PATCH 1/3] iio: adc: stm32-adc: warn if dt uses legacy channel config Fabrice Gasnier
2023-04-01 14:04 ` Jonathan Cameron [this message]
2023-04-01 15:37 ` Sean Nyekjær
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=20230401150455.3e426d1e@jic23-huawei \
--to=jic23@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=fabrice.gasnier@foss.st.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=nuno.sa@analog.com \
--cc=olivier.moysan@foss.st.com \
--cc=sean@geanix.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