From: Jonathan Cameron <jic23@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] ROHM BU27034NUC to ROHM BU27034ANUC
Date: Sat, 13 Jul 2024 12:01:19 +0100 [thread overview]
Message-ID: <20240713120119.7739ed74@jic23-huawei> (raw)
In-Reply-To: <cover.1720176341.git.mazziesaccount@gmail.com>
On Fri, 5 Jul 2024 13:53:35 +0300
Matti Vaittinen <mazziesaccount@gmail.com> wrote:
> As discussed here:
> https://lore.kernel.org/all/ff8d6d14-6b48-4347-8525-e05eeb9721ff@gmail.com/
>
> The ROHM BU27034NUC was cancelled before it entered mass-production. A
> replacement was developed and named to BU27034ANUC. (Note the added
> 'A' in the model name). The BU27034ANUC has several changes that make
> the old BU27034NUC driver unusable with it. I was told the old BU27034NUC
> should not be encountered anywhere.
>
> Hence, this series converts the rohm-bu27034.c to support the new
> BU27034ANUC instead of the obsoleted BU27034NUC. Additionally, the
> series adds a read-only entry for the HARDWAREGAIN to help understanding
> what part of the scale is contributed by the gain, and what by the
> integration time. This is useful when figuring out why some transitions
> from one 'scale' to other are failing.
Series applied with that tweak to fix the typo that is getting moved in patch 1
and to squash the first 2 patches.
Applied for now only to the testing branch of iio.git which will become
togreg after I can rebase on rc1.
Thanks,
Jonathan
>
> Revision history:
> v1 => v2:
> - Split the one large patch to patches 3 - 6 for easier
> review. (Please let me know if you wish me to squash
> them to one).
> - Introduce new compatible for the BU27034ANUC and drop
> the old one.
> - Add styling fixes as suggested by Jonathan
> - Fix the lux calculation coefficient selection logic
> link to v1:
> https://lore.kernel.org/all/cover.1718013518.git.mazziesaccount@gmail.com/
>
> ---
>
> Matti Vaittinen (7):
> dt-bindings: iio: BU27034 => BU27034ANUC
> dt-bindings: iio: rename bu27034 file
> bu27034: ROHM BU27034NUC to BU27034ANUC
> bu27034: ROHM BU27034NUC to BU27034ANUC drop data2
> bu27034: ROHM BU27034ANUC correct gains and times
> bu27034: ROHM BU27034ANUC correct lux calculation
> iio: bu27034: Add a read only HWARDWAREGAIN
>
> ...ohm,bu27034.yaml => rohm,bu27034anuc.yaml} | 11 +-
> drivers/iio/light/rohm-bu27034.c | 343 +++++-------------
> 2 files changed, 89 insertions(+), 265 deletions(-)
> rename Documentation/devicetree/bindings/iio/light/{rohm,bu27034.yaml => rohm,bu27034anuc.yaml} (66%)
>
>
> base-commit: 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0
prev parent reply other threads:[~2024-07-13 11:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 10:53 [PATCH v2 0/7] ROHM BU27034NUC to ROHM BU27034ANUC Matti Vaittinen
2024-07-05 10:54 ` [PATCH v2 1/7] dt-bindings: iio: BU27034 => BU27034ANUC Matti Vaittinen
2024-07-07 13:05 ` Jonathan Cameron
2024-07-08 12:43 ` Matti Vaittinen
2024-07-08 17:06 ` Conor Dooley
2024-07-05 10:54 ` [PATCH v2 2/7] dt-bindings: iio: rename bu27034 file Matti Vaittinen
2024-07-08 17:05 ` Conor Dooley
2024-07-09 18:33 ` Matti Vaittinen
2024-07-13 11:00 ` Jonathan Cameron
2024-07-05 10:54 ` [PATCH v2 3/7] bu27034: ROHM BU27034NUC to BU27034ANUC Matti Vaittinen
2024-07-05 10:55 ` [PATCH v2 4/7] bu27034: ROHM BU27034NUC to BU27034ANUC drop data2 Matti Vaittinen
2024-07-05 10:55 ` [PATCH v2 5/7] bu27034: ROHM BU27034ANUC correct gains and times Matti Vaittinen
2024-07-05 10:55 ` [PATCH v2 6/7] bu27034: ROHM BU27034ANUC correct lux calculation Matti Vaittinen
2024-07-05 10:55 ` [PATCH v2 7/7] iio: bu27034: Add a read only HWARDWAREGAIN Matti Vaittinen
2024-07-07 13:14 ` Jonathan Cameron
2024-07-13 11:01 ` 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=20240713120119.7739ed74@jic23-huawei \
--to=jic23@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=robh@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