From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Victor Chernyakin <chernyakin.victor.j@outlook.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] iio: cdc: add Texas Instruments FDC1004 driver
Date: Sun, 25 Oct 2026 17:18:33 +0200 [thread overview]
Message-ID: <at4dyW-XNABCF51c@ashevche-desk.local> (raw)
In-Reply-To: <SN1PR12MB2528B54E68524DC62C378CD7A5622@SN1PR12MB2528.namprd12.prod.outlook.com>
On Sun, Oct 25, 2026 at 12:55:25AM -0500, Victor Chernyakin wrote:
> > > > I'd look at using regmap even though you only have a single bus. It provides
> > > > a rich set of helpers and the caching functionality that will save a bunch
> > > > of bus traffic.
> > >
> > > Ah... is that a strong preference in new drivers? That would be quite
> > > a bit of rewrite work...
> >
> > Yes, usually drivers start being looked cleaner. On top you got a few benefits
> > of regmap for free (cache, debugfs, tracing, maybe even more).
>
> Alright, v2 is now regmap-based!
>
> > > > Looking at these data types, can you check if linear_range.h APIs
> > > > can be applied instead?
> > >
> > > Doesn't look like they can, since they only work with unsigned int, but
> > > these values are s64.
> >
> > The types in the software is a result, but what is the cause? Do you have
> > ranges with a sign?
>
> Yes, fdc1004_calibbias needs a sign.
Need a sign and having it in the data tables is different. Do you mean that min
of some ranges in your case are negative?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-10-25 15:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 23:40 [PATCH 0/3] " Victor Chernyakin
2026-10-22 23:40 ` [PATCH 1/3] iio: add IIO_VAL_DECIMAL64_{ATTO,ZEPTO,YOCTO} formats Victor Chernyakin
2026-10-23 3:06 ` Jonathan Cameron
2026-10-25 6:03 ` [PATCH 1/3] iio: cdc: add Texas Instruments FDC1004 driver Victor Chernyakin
2026-10-22 23:40 ` [PATCH 2/3] dt-bindings: iio: cdc: add Texas Instruments FDC1004 Victor Chernyakin
2026-10-23 3:09 ` Jonathan Cameron
2026-10-24 0:18 ` Victor Chernyakin
2026-10-22 23:40 ` [PATCH 3/3] iio: cdc: add Texas Instruments FDC1004 driver Victor Chernyakin
2026-10-23 3:01 ` Jonathan Cameron
2026-10-23 7:29 ` Andy Shevchenko
2026-10-24 0:16 ` Victor Chernyakin
2026-10-24 0:13 ` Victor Chernyakin
2026-10-24 2:28 ` Jonathan Cameron
2026-10-25 6:19 ` Victor Chernyakin
2026-10-24 10:19 ` Andy Shevchenko
2026-10-24 10:21 ` Andy Shevchenko
2026-10-25 5:55 ` Victor Chernyakin
2026-10-25 15:18 ` Andy Shevchenko [this message]
2026-10-23 7:09 ` [PATCH 0/3] " Andy Shevchenko
2026-10-24 0:05 ` Victor Chernyakin
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=at4dyW-XNABCF51c@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=chernyakin.victor.j@outlook.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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
all inboxes | Powered by JetHome®