From: Nishanth Menon <nm@ti.com>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Sukrut Bellary <sbellary@baylibre.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>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>,
<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] iio: adc: ti-adc128s052: Add lower resolution devices support
Date: Mon, 14 Apr 2025 09:52:12 -0500 [thread overview]
Message-ID: <20250414145212.7fcybmngv7rnuvnm@hatchet> (raw)
In-Reply-To: <cb81cba4-0fa3-431a-924f-b362fd0c4638@gmail.com>
On 09:40-20250414, Matti Vaittinen wrote:
> On 08/04/2025 16:21, Sukrut Bellary wrote:
> > The adcxx4s communicates with a host processor via an SPI/Microwire Bus
> > interface. The device family responds with 12-bit data, of which the LSB
> > bits are transmitted by the lower resolution devices as 0.
> > The unavailable bits are 0 in LSB.
> > Shift is calculated per resolution and used in scaling and
> > raw data read.
> >
> > Lets reuse the driver to support the family of devices with name
> > ADC<bb><c>S<sss>, where
> > * bb is the resolution in number of bits (8, 10, 12)
> > * c is the number of channels (1, 2, 4, 8)
> > * sss is the maximum conversion speed (021 for 200 kSPS, 051 for 500 kSPS
> > and 101 for 1 MSPS)
> >
> > Complete datasheets are available at TI's website here:
> > https://www.ti.com/lit/gpn/adc<bb><c>s<sss>.pdf
>
> I tried looking up:
> https://www.ti.com/lit/gpn/adc102s051.pdf
Gaah - the IT folks keep messing with the URLs :( -> dropping .pdf in
the url should get you to the pdf #facepalm :( (sidenote: that wasn't
the case a year back :( - hopefully this will stay).
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2025-04-14 14:52 UTC|newest]
Thread overview: 18+ 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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 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
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=20250414145212.7fcybmngv7rnuvnm@hatchet \
--to=nm@ti.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=robh@kernel.org \
--cc=sbellary@baylibre.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