All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marten Lindahl <martenli@axis.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Mårten Lindahl" <Marten.Lindahl@axis.com>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	kernel <kernel@axis.com>, "Sudeep Holla" <sudeep.holla@arm.com>
Subject: Re: [PATCH] iio: light: vcnl4000: Don't create sysfs PM nodes for child
Date: Mon, 7 Nov 2022 08:22:05 +0100	[thread overview]
Message-ID: <Y2iyHfNNHmoiCcqJ@axis.com> (raw)
In-Reply-To: <20221106152307.4bfb4e49@jic23-huawei>

On Sun, Nov 06, 2022 at 04:23:07PM +0100, Jonathan Cameron wrote:
> On Tue, 1 Nov 2022 13:21:51 +0100
> Mårten Lindahl <marten.lindahl@axis.com> wrote:
> 
> > PM runtime is enabled for the parent i2c device, but it is disabled for
> > the iio child device and remains so in this driver. But as the child
> > sysfs PM directory is created by default by iio_device_register =>
> > cdev_device_add => dpm_sysfs_add it doesn't bring any value exposing it
> > since it won't give any usable data for the user.
> > 
> > Tell dpm_sysfs to not create the PM directory for the iio device.
> > 
> > Signed-off-by: Mårten Lindahl <marten.lindahl@axis.com>
> 
> Ah this one..  +CC Sudeep who I am sure has considered such changes in other
> similar cases (he did the original ones that mean this infastructure exists).
> 
> So, the problem here is that it drops an ABI that has existed in IIO for
> a long time. I fully admit the ABI is confusing and pointless.  What
> I'm not sure on is that we are entirely safe to remove it.
> 
> If we are going to do this, it shouldn't be on a per driver basis, but rather
> a global change for all IIO drivers with the proviso that we are relying on
> the 'if no one notices an ABI change, it is fine' exception to never changing
> userspace ABI.
> 
> Until now this has more or less only been used for new subsystems or where
> there were warnings generated due to spurious interface usage in normal flows.
> 
> In IIO, nothing should touch these and I 'think' they don't do anything if
> anyone pokes them.
> 
> Jonathan

Hi Jonathan!

Thanks. I'll drop this change then.

Kind regards
Mårten
> 
> 
> > ---
> >  drivers/iio/light/vcnl4000.c | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/iio/light/vcnl4000.c b/drivers/iio/light/vcnl4000.c
> > index f6c83ecaad8b..400dc1155559 100644
> > --- a/drivers/iio/light/vcnl4000.c
> > +++ b/drivers/iio/light/vcnl4000.c
> > @@ -1072,6 +1072,7 @@ static int vcnl4000_probe(struct i2c_client *client,
> >  	if (ret < 0)
> >  		goto fail_poweroff;
> >  
> > +	device_set_pm_not_required(&indio_dev->dev);
> >  	ret = iio_device_register(indio_dev);
> >  	if (ret < 0)
> >  		goto fail_poweroff;
> 

  reply	other threads:[~2022-11-07  7:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 12:21 [PATCH] iio: light: vcnl4000: Don't create sysfs PM nodes for child Mårten Lindahl
2022-11-06 15:23 ` Jonathan Cameron
2022-11-07  7:22   ` Marten Lindahl [this message]
2022-11-07 10:36   ` Sudeep Holla
2022-11-07 17:08     ` Jonathan Cameron
2022-11-07 17:14       ` Sudeep Holla

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=Y2iyHfNNHmoiCcqJ@axis.com \
    --to=martenli@axis.com \
    --cc=Marten.Lindahl@axis.com \
    --cc=jic23@kernel.org \
    --cc=kernel@axis.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=sudeep.holla@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.