From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
Arthur Becker <arthur.becker@sentec.com>,
Emil Gedenryd <emil.gedenryd@axis.com>,
Marek Vasut <marex@denx.de>,
Mudit Sharma <muditsharma.info@gmail.com>,
Subhajit Ghosh <subhajit.ghosh@tweaklogic.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Drop BU27008 and BU27010
Date: Sat, 30 Nov 2024 16:48:34 +0200 [thread overview]
Message-ID: <19ab6891-0549-4cf3-9baf-661e867f1234@gmail.com> (raw)
In-Reply-To: <Z0nOxEtNk6APoNo0@smile.fi.intel.com>
On 29/11/2024 16:25, Andy Shevchenko wrote:
> On Thu, Nov 28, 2024 at 09:34:54PM +0200, Matti Vaittinen wrote:
>> Drop the support for ROHM BD72008 and BD72010 RGB sensors
>>
>> I accidentally hit a BU27008 data-sheet which had a big red text saying
>> "Obsolete". After a few queries I received a word that the ROHM BU27008
>> and BU27010 RGB sensors were cancelled and never entered mass production.
>> Supporting not existing hardware makes no sense, so it's probably best
>> to drop the drivers and dt-bindings.
>>
>> There is still a RGB sensor from ROHM called BU27006.
>> https://www.rohm.com/products/sensors-mems/color-sensor-ics/bu27006muc-z-product
>> Based on a quick glance this should be very similar to the BU27010. If
>> someone wants to create a driver for this, then the bu27008.c might be
>> worth looking at.
>>
>> As writing of this I don't have the BU27006 at my hands, and when I
>> asked about creating a driver for this IC from the HQ ... I got an
>> impression that at the moment ROHM rather pays me for doing something
>> else. So, currently I have no plan to add support for the BD27006.
>> We can always dig the bu27008.c from the depths of the git, if it later
>> appears such a driver would be a good idea.
>
> The best series ever from you, Matti, on which I have
> not a tiny disagreement with!
>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Thanks for the review. I guess you might've had something to comment
regarding the recipient list though XD
I don't really know what I did to get the patch names in recipients. Sorry.
next prev parent reply other threads:[~2024-11-30 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 19:34 [PATCH 0/2] Drop BU27008 and BU27010 Matti Vaittinen
2024-11-28 19:35 ` [PATCH 1/2] iio: light: " Matti Vaittinen
2024-11-28 19:35 ` [PATCH 2/2] dt-bindings: " Matti Vaittinen
2024-11-29 15:32 ` Conor Dooley
2024-11-29 14:25 ` [PATCH 0/2] " Andy Shevchenko
2024-11-30 14:48 ` Matti Vaittinen [this message]
2024-11-30 14:38 ` Jonathan Cameron
2024-11-30 14:53 ` 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=19ab6891-0549-4cf3-9baf-661e867f1234@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arthur.becker@sentec.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=emil.gedenryd@axis.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=muditsharma.info@gmail.com \
--cc=robh@kernel.org \
--cc=subhajit.ghosh@tweaklogic.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