From: Lars-Peter Clausen <lars@metafoo.de>
To: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>,
"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 16:55:40 +0200 [thread overview]
Message-ID: <5d3d6bad-934d-41c5-d167-dd69734e8015@metafoo.de> (raw)
In-Reply-To: <761fb0aef92e5e026df78b6679329dbbb55b6226.camel@analog.com>
On 4/15/20 3:56 PM, Ardelean, Alexandru wrote:
> 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.
I think you also have to make the `indio_dev->dev.devt = ...`
conditional. Or conditionally use device_add() instead of device_add_cdev().
If you go for the former you need to call cdev_device_del()
unconditionally, for the latter call device_del() or cdev_device_del()
depending on whether the cdev was registered.
- Lars
next prev parent reply other threads:[~2020-04-15 14:56 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
2020-04-15 14:55 ` Lars-Peter Clausen [this message]
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=5d3d6bad-934d-41c5-d167-dd69734e8015@metafoo.de \
--to=lars@metafoo.de \
--cc=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).