linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
To: "jic23@kernel.org" <jic23@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH v2] iio: core: register chardev only if needed
Date: Wed, 15 Apr 2020 13:56:13 +0000	[thread overview]
Message-ID: <761fb0aef92e5e026df78b6679329dbbb55b6226.camel@analog.com> (raw)
In-Reply-To: <20200414190629.2d85759e@archlinux>

On Tue, 2020-04-14 at 19:06 +0100, Jonathan Cameron wrote:
> [External]
> 
> On Tue, 14 Apr 2020 11:36:56 +0300
> Alexandru Ardelean <alexandru.ardelean@analog.com> wrote:
> 
> > The final intent is to localize all buffer ops into the
> > industrialio-buffer.c file, to be able to add support for multiple buffers
> > per IIO device.
> > 
> > We only need a chardev if we need to support buffers and/or events.
> > 
> > With this change, a chardev will be created:
> > 1. if there is an IIO buffer attached OR
> > 2. if there is an event_interface configured
> > 
> > Otherwise, no chardev will be created.
> > Quite a lot of IIO devices don't really need a chardev, so this is a minor
> > improvement to the IIO core, as the IIO device will take up fewer
> > resources.
> > 
> > Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
> > ---
> > 
> > Changelog v1 -> v2:
> > * split away from series 'iio: core,buffer: re-organize chardev creation';
> >   i'm getting the feeling that this has some value on it's own;
> >   no idea if it needs 'Fixes' tag; it is a bit fuzzy to point to a patch
> >   which this would be fixed by this; i'm guessing it would be fine
> >   without one
> 
> I'd argue it's an 'optimization' rather than a fix :)
> 
> Still looks good to me but I'd like it to sit for a little while to
> see if anyone points out something we are both missing!
> 

This is not good.
It seems that I did not properly test all cases.
I had to break a device to not have an event_interface to notice that the sysfs
doesn't get instantiated either because device_add is missing.

Will do another try.


> Thanks for tidying this up.
> 
> Jonathan
> 
> >  drivers/iio/industrialio-core.c | 17 +++++++++++++++--
> >  1 file changed, 15 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/iio/industrialio-core.c b/drivers/iio/industrialio-
> > core.c
> > index f4daf19f2a3b..32e72d9fd1e9 100644
> > --- a/drivers/iio/industrialio-core.c
> > +++ b/drivers/iio/industrialio-core.c
> > @@ -1676,6 +1676,15 @@ static int iio_check_unique_scan_index(struct iio_dev
> > *indio_dev)
> >  
> >  static const struct iio_buffer_setup_ops noop_ring_setup_ops;
> >  
> > +static const struct file_operations iio_event_fileops = {
> > +	.release = iio_chrdev_release,
> > +	.open = iio_chrdev_open,
> > +	.owner = THIS_MODULE,
> > +	.llseek = noop_llseek,
> > +	.unlocked_ioctl = iio_ioctl,
> > +	.compat_ioctl = compat_ptr_ioctl,
> > +};
> > +
> >  int __iio_device_register(struct iio_dev *indio_dev, struct module
> > *this_mod)
> >  {
> >  	int ret;
> > @@ -1726,7 +1735,10 @@ int __iio_device_register(struct iio_dev *indio_dev,
> > struct module *this_mod)
> >  		indio_dev->setup_ops == NULL)
> >  		indio_dev->setup_ops = &noop_ring_setup_ops;
> >  
> > -	cdev_init(&indio_dev->chrdev, &iio_buffer_fileops);
> > +	if (indio_dev->buffer)
> > +		cdev_init(&indio_dev->chrdev, &iio_buffer_fileops);
> > +	else if (indio_dev->event_interface)
> > +		cdev_init(&indio_dev->chrdev, &iio_event_fileops);
> >  
> >  	indio_dev->chrdev.owner = this_mod;
> >  
> > @@ -1754,7 +1766,8 @@ EXPORT_SYMBOL(__iio_device_register);
> >   **/
> >  void iio_device_unregister(struct iio_dev *indio_dev)
> >  {
> > -	cdev_device_del(&indio_dev->chrdev, &indio_dev->dev);
> > +	if (indio_dev->buffer || indio_dev->event_interface)
> > +		cdev_device_del(&indio_dev->chrdev, &indio_dev->dev);
> >  
> >  	mutex_lock(&indio_dev->info_exist_lock);
> >  

  reply	other threads:[~2020-04-15 13:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14  8:36 [PATCH v2] iio: core: register chardev only if needed Alexandru Ardelean
2020-04-14 18:06 ` Jonathan Cameron
2020-04-15 13:56   ` Ardelean, Alexandru [this message]
2020-04-15 14:55     ` Lars-Peter Clausen
2020-04-16  7:04       ` Ardelean, Alexandru
2020-12-03  9:53 Alexandru Ardelean
2020-12-09 15:19 ` Andy Shevchenko
2020-12-09 15:45   ` Alexandru Ardelean
2020-12-09 15:54     ` Andy Shevchenko
2020-12-09 15:55       ` Alexandru Ardelean
2020-12-13 14:31         ` Jonathan Cameron
2021-01-19  8:18           ` Alexandru Ardelean

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=761fb0aef92e5e026df78b6679329dbbb55b6226.camel@analog.com \
    --to=alexandru.ardelean@analog.com \
    --cc=jic23@kernel.org \
    --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).