devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sukrut Bellary <sbellary@baylibre.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Angelo Compagnucci <angelo.compagnucci@gmail.com>,
	Nishanth Menon <nm@ti.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Matti Vaittinen <mazziesaccount@gmail.com>
Subject: Re: [PATCH 0/2] iio: adc: ti-adc128s052: Add support for adc102s021
Date: Tue, 15 Apr 2025 15:17:46 -0700	[thread overview]
Message-ID: <Z/7bCn1S5wFQFaiT@dev-linux> (raw)
In-Reply-To: <20250412141047.4273a8b1@jic23-huawei>

On Sat, Apr 12, 2025 at 02:10:47PM +0100, Jonathan Cameron wrote:
> On Tue,  8 Apr 2025 06:21:18 -0700
> Sukrut Bellary <sbellary@baylibre.com> wrote:
> 
> > The patch series adds the support for adc102s021 and family.
> > 
> > The family of devices are easier to
> > support since they all (no matter the resolution) seem to respond in
> > 12-bits with the LSBs set to 0 for the reduced resolution devices.
> 
> This has raced against Matti's series
> https://lore.kernel.org/linux-iio/cover.1744022065.git.mazziesaccount@gmail.com/
> Support ROHM BD79104 ADC
> 
> With hindsight that wasn't obvious from the patch series name though
> which should ideally have been
> iio: adc: ti-adc128s052: Support ROHM BD79104 ADC
> 
> Please rebase on the iio testing branch on kernel.org or on top of that series.
> Technically I've only applied the first 7 patches so far, but the 8th
> should be a simple change from that v3.
>  
> Matti, you volunteered as maintainer :)  Hence please take a look at
> this one.
> 
> One nice thing in there is we now have a __be16 buffer16 element that
> can avoid at least one cast in patch 2.

Ok, thanks.
I will work on the top of this series.

> Thanks,
> 
> Jonathan
> 
> > 
> > Changes in v3:
> > 	Patch 1:
> >         - No changes in dt-bindings
> > 
> > 	Patch 2:
> > 	- used be16_to_cpu() for the endian conversion.
> > 	- used config index enum while setting up the adc128_config[]
> > 
> > - Link to v2:
> > 	https://lore.kernel.org/lkml/20231022031203.632153-1-sukrut.bellary@linux.com/
> > 
> > Changes in v2:
> > 	Patch 1:
> > 	- No changes in dt-bindings
> > 
> > 	Patch 2:
> > 	- Arranged of_device_id and spi_device_id in numeric order.
> > 	- Used enum to index into adc128_config.
> > 	- Reorder adc128_config in alphabetical.
> > 	- Include channel resolution information.
> > 	- Shift is calculated per resolution and used in scaling and
> > 	raw data read.
> > 
> > - Link to v1: https://lore.kernel.org/all/20220701042919.18180-1-nm@ti.com/
> > 
> > Sukrut Bellary (2):
> >   dt-bindings: iio: adc: ti,adc128s052: Add adc08c and adc10c family
> >   iio: adc: ti-adc128s052: Add lower resolution devices support
> > 
> >  .../bindings/iio/adc/ti,adc128s052.yaml       |   6 +
> >  drivers/iio/adc/ti-adc128s052.c               | 149 +++++++++++++-----
> >  2 files changed, 118 insertions(+), 37 deletions(-)
> > 
> 

      parent reply	other threads:[~2025-04-15 22:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 13:21 [PATCH 0/2] iio: adc: ti-adc128s052: Add support for adc102s021 Sukrut Bellary
2025-04-08 13:21 ` [PATCH 1/2] dt-bindings: iio: adc: ti,adc128s052: Add adc08c and adc10c family Sukrut Bellary
2025-04-08 14:33   ` Krzysztof Kozlowski
2025-04-08 13:21 ` [PATCH 2/2] iio: adc: ti-adc128s052: Add lower resolution devices support Sukrut Bellary
2025-04-08 20:57   ` David Lechner
2025-04-09 21:42     ` Sukrut Bellary
2025-04-12 13:12   ` Jonathan Cameron
2025-04-15 22:20     ` Sukrut Bellary
2025-04-16  5:58       ` Matti Vaittinen
2025-04-14  6:40   ` Matti Vaittinen
2025-04-14 14:52     ` Nishanth Menon
2025-04-15 22:25     ` Sukrut Bellary
2025-04-12 13:10 ` [PATCH 0/2] iio: adc: ti-adc128s052: Add support for adc102s021 Jonathan Cameron
2025-04-14  6:15   ` Matti Vaittinen
2025-04-15 22:17   ` Sukrut Bellary [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=Z/7bCn1S5wFQFaiT@dev-linux \
    --to=sbellary@baylibre.com \
    --cc=angelo.compagnucci@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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=mazziesaccount@gmail.com \
    --cc=nm@ti.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;
as well as URLs for NNTP newsgroup(s).