linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Gwendal Grignou <gwendal@chromium.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	linux-iio <linux-iio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v1 1/1] iio: proximity: sx_common: Allow IIO core to take care of firmware node
Date: Tue, 14 Jun 2022 11:53:43 +0100	[thread overview]
Message-ID: <20220614115343.057f1e8f@jic23-huawei> (raw)
In-Reply-To: <CAHp75VdLMCBhhM4P_asTf7r+OhBHmgJVCg7MADkOYRTf1JvRaA@mail.gmail.com>

On Tue, 14 Jun 2022 11:27:21 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:

> On Mon, Jun 13, 2022 at 11:31 PM Gwendal Grignou <gwendal@chromium.org> wrote:
> >
> > The reason we have the code ACPI_COMPANION_SET and dev.of_node set (by
> > commit 74a53a959028e ("iio:proximity:sx_common: Fix device property
> > parsing on DT systems") from Stephen is we are getting device propery
> > in ->get_default_reg(), which is called in sx_common_init_device(),
> > before devm_iio_device_register().
> >
> > We have the same code path in other driver, like adc/stm32-adc.c,
> > where indio_dev->dev.of_node is set manually to be able to set the
> > resolution based on device tree properties.  
> 
> Ah, thanks for this insight! I will rework the patch accordingly (yes,
> there is something to clean up even in this case).
> 
> > On Fri, Jun 3, 2022 at 9:57 AM Jonathan Cameron <jic23@kernel.org> wrote:  
> > > On Mon, 30 May 2022 20:43:26 +0300
> > > Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> > >  
> > > > IIO core correctly will take care of firmware node if it's not set in
> > > > the driver. Drop ACPI and OF specifics from the driver and allow IIO
> > > > core to handle this.
> > > >
> > > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>  
> > > Looks fine to me.  As such I'll apply it now, but Gwendal, you've
> > > been active with this driver recently so if you have time to sanity check
> > > that would be great.  Once I've caught up with new stuff I plan to check
> > > where we are with your various series on this driver.  
> 
Dropped patch


      reply	other threads:[~2022-06-14 10:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 17:43 [PATCH v1 1/1] iio: proximity: sx_common: Allow IIO core to take care of firmware node Andy Shevchenko
2022-06-03 17:06 ` Jonathan Cameron
2022-06-13 21:25   ` Gwendal Grignou
2022-06-14  9:27     ` Andy Shevchenko
2022-06-14 10:53       ` Jonathan Cameron [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=20220614115343.057f1e8f@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=gwendal@chromium.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.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).