From: Nishanth Menon <nm@ti.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Angelo Compagnucci" <angelo.compagnucci@gmail.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Christophe JAILLET" <christophe.jaillet@wanadoo.fr>,
"Alexandru Ardelean" <ardeleanalex@gmail.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Florian Eckert" <fe@dev.tdt.de>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: adc: ti-adc128s052: Add lower resolution devices support
Date: Wed, 6 Jul 2022 13:06:17 -0500 [thread overview]
Message-ID: <20220706180617.hkogg3znw7dceny6@going> (raw)
In-Reply-To: <20220701174011.14d17f43@jic23-huawei>
On 17:40-20220701, Jonathan Cameron wrote:
> On Thu, 30 Jun 2022 23:29:19 -0500
> Nishanth Menon <nm@ti.com> wrote:
>
> > The adcxx4s communicates with a host processor via an SPI/Microwire Bus
> > interface. The device family responds with 12bit data, of which the LSB
> > bits are transmitted by the lower resolution devices as 0. We don't need
> > to mess with ADC108S102_BITS as a result for the lower resolution
> > devices.
>
> whilst not strictly necessary I would prefer we did as it may reduce
> storage requirements, computation complexity etc for userspace (particularly
> if they are 8 bits).
>
> Would affect scale and shift so slightly more complex, but not a lot
> so still a fairly simple change. Just add resolution to your config
> structure and duplicate it where necessary to allow whatever resolutions
> we support.
>
> >
[...]
> > #include <linux/acpi.h>
> > @@ -185,6 +199,12 @@ static const struct of_device_id adc128_of_match[] = {
> > { .compatible = "ti,adc122s021", .data = 1},
> > { .compatible = "ti,adc122s051", .data = 1},
> > { .compatible = "ti,adc122s101", .data = 1},
> > + { .compatible = "ti,adc102s021", .data = 1},
> > + { .compatible = "ti,adc102s051", .data = 1},
> > + { .compatible = "ti,adc102s101", .data = 1},
>
> Numeric order preferred. Not sure why these are in the middle.
>
> > + { .compatible = "ti,adc082s021", .data = 1},
> > + { .compatible = "ti,adc082s051", .data = 1},
> > + { .compatible = "ti,adc082s101", .data = 1},
>
> Andy's comment on using pointers instead follows through to here.
> To describe the channels more fully you'll need additional
> _config[] structures.
Thanks folks for the feedback. Will try to do a better job on the next
rev.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2022-07-06 18:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 4:29 [PATCH 0/2] iio: adc: ti-adc128s052: Add support for adc102s021 and family Nishanth Menon
2022-07-01 4:29 ` [PATCH 1/2] dt-bindings: iio: adc: ti,adc128s052: Add adc08c and adc10c family Nishanth Menon
2022-07-01 6:38 ` Krzysztof Kozlowski
2022-07-01 8:27 ` Krzysztof Kozlowski
2022-07-01 4:29 ` [PATCH 2/2] iio: adc: ti-adc128s052: Add lower resolution devices support Nishanth Menon
2022-07-01 16:40 ` Jonathan Cameron
2022-07-06 18:06 ` Nishanth Menon [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-08 13:21 [PATCH 0/2] iio: adc: ti-adc128s052: Add support for adc102s021 Sukrut Bellary
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
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=20220706180617.hkogg3znw7dceny6@going \
--to=nm@ti.com \
--cc=angelo.compagnucci@gmail.com \
--cc=ardeleanalex@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=devicetree@vger.kernel.org \
--cc=fe@dev.tdt.de \
--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=nuno.sa@analog.com \
--cc=robh+dt@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