From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Shreeya Patel <shreeya.patel@collabora.com>,
Zhigang Shi <Zhigang.Shi@liteon.com>,
Paul Gazzillo <paul@pgazz.com>,
Dmitry Osipenko <dmitry.osipenko@collabora.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 4/5] iio: light: ROHM BU27008 color sensor
Date: Mon, 8 May 2023 15:40:05 +0300 [thread overview]
Message-ID: <6e2c9f59-296c-7382-6490-8e344f3e0210@gmail.com> (raw)
In-Reply-To: <ZFjpqwOo3DxnWahM@smile.fi.intel.com>
Hi Andy,
On 5/8/23 15:23, Andy Shevchenko wrote:
> On Fri, May 05, 2023 at 04:56:47AM +0000, Vaittinen, Matti wrote:
>> On 5/4/23 17:33, Andy Shevchenko wrote:
>>> On Wed, May 03, 2023 at 12:50:14PM +0300, Matti Vaittinen wrote:
>
> ...
>
>>>> +config ROHM_BU27008
>>>> + tristate "ROHM BU27008 color (RGB+C/IR) sensor"
>>>> + depends on I2C
>>>> + select REGMAP_I2C
>>>> + select IIO_GTS_HELPER
>>>> + help
>>>> + Enable support for the ROHM BU27008 color sensor.
>>>> + The ROHM BU27008 is a sensor with 5 photodiodes (red, green,
>>>> + blue, clear and IR) with four configurable channels. Red and
>>>> + green being always available and two out of the rest three
>>>> + (blue, clear, IR) can be selected to be simultaneously measured.
>>>> + Typical application is adjusting LCD backlight of TVs,
>>>> + mobile phones and tablet PCs.
>>>
>>> Module name?
>>
>> We have discussed this several times already.
>>
>> https://lore.kernel.org/all/10c4663b-dd65-a545-786d-10aed6e6e5e9@fi.rohmeurope.com/
>>
>> Module name is completely irrelevant when selecting a kernel configuration.
>
> This option is also selectable by user.
I don't think the name is selectable. Yes, user selects whether to
compile driver as a module or in-kernel - but the module name is
completely irrelevant what comes to this decision.
> ...
>
>>> Do you need regmap lock? If so, why (since you have mutex)?
>>
>> I believe you know that regmap uses a default lock when no external lock
>> is given. So, I assume you mean that maybe we could set
>> 'disable_locking' for the regmap here.
>
> Correct.
>
>> It's nice to be occasionally pushed to think "out of the box". And yes,
>> disabling regmap lock is really out of my "normal box" :)
>>
>> I didn't go through all of the code yet, but I think pretty much all of
>> the sequences which end up to register writes are indeed protected by
>> the mutex. (Well, probe is not but it is expected to only update one bit
>> while rest of the register should stay fixed).
>>
>> It may be we could live without regmap_lock when driver is in it's
>> current state, but I am not convinced the performance improvement is
>> worth the risk. Having regmap unprotected is not common, and it is also
>> not easy to spot when making changes to the driver. In my opinion it is
>> a bit like asking for a nose-bleed unless there is really heavy reasons
>> to drop the lock... In this case, having the regmap_lock (which is
>> pretty much never locked because we have the mutex as you said) is
>> probably not a penalty that matters.
>
> Basically you try to justify a hidden mine field in case somebody will think
> "oh, we are protected by regmap lock, so why to bother call mutex_lock()" and
> at the end it become a subtle bugs in the code. With disable_locking = true
> I can see that code author _carefully thought through_ the locking schema and
> understands the hardware and the code.
I added the disable_locking = true in v5 - but I am not convinced that
was a great idea. I am afraid disabling regmap lock is the hidden
minefield for average users. I didn't grep the kernel for it but I am
afraid the percentage of regmap users who disable locking is very low.
Thus, I'd say this is unexpected to many and may lead to bugs although I
try to watch out for them. Well, time will tell.
> P.S. I'm wondering why your lines of text have a single trailing whitespace
> but the last line.
I guess it must be Thunderbird client then. Well, at least it can send
out plain-text decently well while working with the exchange servers
used by ROHM as well as with the gmail. I am not super happy with
Thunderbird, it tends to eat way more resources I wished it did, but it
is a working compromise for me. I am interested in hearing if anyone
knows a way to configure the Thunderbird to drop these extra spaces.
Yours,
-- Matti
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
next prev parent reply other threads:[~2023-05-08 12:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 9:44 [PATCH v4 0/5] Support ROHM BU27008 RGB sensor Matti Vaittinen
2023-05-03 9:48 ` [PATCH v4 1/5] dt-bindings: iio: light: ROHM BU27008 Matti Vaittinen
2023-05-03 9:48 ` [PATCH v4 2/5] iio: trigger: Add simple trigger_validation helper Matti Vaittinen
2023-05-07 14:34 ` Jonathan Cameron
2023-05-03 9:49 ` [PATCH v4 3/5] iio: kx022a: Use new iio_validate_own_trigger() Matti Vaittinen
2023-05-03 9:50 ` [PATCH v4 4/5] iio: light: ROHM BU27008 color sensor Matti Vaittinen
2023-05-04 14:33 ` Andy Shevchenko
2023-05-05 4:56 ` Vaittinen, Matti
2023-05-08 12:23 ` Andy Shevchenko
2023-05-08 12:40 ` Matti Vaittinen [this message]
2023-05-07 14:54 ` Jonathan Cameron
2023-05-08 6:32 ` Matti Vaittinen
2023-05-13 17:52 ` Jonathan Cameron
2023-05-15 12:31 ` Matti Vaittinen
2023-05-03 9:50 ` [PATCH v4 5/5] MAINTAINERS: Add ROHM BU27008 Matti Vaittinen
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=6e2c9f59-296c-7382-6490-8e344f3e0210@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=Matti.Vaittinen@fi.rohmeurope.com \
--cc=Zhigang.Shi@liteon.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.osipenko@collabora.com \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@pgazz.com \
--cc=robh+dt@kernel.org \
--cc=shreeya.patel@collabora.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