From: David Lechner <dlechner@baylibre.com>
To: Joshua Crofts <joshua.crofts1@gmail.com>,
Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: dac: mcp47a1: add support for new device
Date: Sat, 25 Jul 2026 11:52:32 -0500 [thread overview]
Message-ID: <b138904a-c095-492d-9c52-cfd5ee10a6e7@baylibre.com> (raw)
In-Reply-To: <20260722083016.000062c4@gmail.com>
On 7/22/26 1:30 AM, Joshua Crofts wrote:
> On Tue, 21 Jul 2026 23:47:58 +0300
> Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
>
>> On Tue, Jul 21, 2026 at 08:24:39PM +0200, Joshua Crofts wrote:
>>> The Microchip MCP47A1 is a 6-bit volatile Digital-to-Analog converted
>>> which communicates via I2C.
>>
>>
>> ...
>>
>>> +static const struct regmap_config mcp47a1_regmap_config = {
>>> + .name = "mcp47a1",
>>> + .reg_bits = 8,
>>> + .val_bits = 8,
>>> + .max_register = MCP47A1_CMD_CODE,
>>> +};
>>
>> No cache?
>
> Hmmm, could you elaborate a bit more? I assume you're talking about
> regcache but I'm not sure on how to use it here.
>
normally one would select the maple regcache type and add a callback
for indicating which registers are volatile and and another config
to indicate the initial register values after reset.
however, it looks like there is only 1 register here, so probably
not much point in that.
next prev parent reply other threads:[~2026-07-25 16:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 18:24 [PATCH 0/2] " Joshua Crofts
2026-07-21 18:24 ` [PATCH 1/2] dt-bindings: iio: dac: add support for mcp47a1 Joshua Crofts
2026-07-22 16:47 ` Conor Dooley
2026-07-24 23:04 ` Jonathan Cameron
2026-07-24 23:04 ` Jonathan Cameron
2026-07-25 8:12 ` Joshua Crofts
2026-07-25 15:41 ` David Lechner
2026-07-25 21:54 ` Jonathan Cameron
2026-07-21 18:24 ` [PATCH 2/2] iio: dac: mcp47a1: add support for new device Joshua Crofts
2026-07-21 20:47 ` Andy Shevchenko
2026-07-22 6:30 ` Joshua Crofts
2026-07-25 16:52 ` David Lechner [this message]
2026-07-24 23:14 ` Jonathan Cameron
2026-07-25 10:17 ` Joshua Crofts
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=b138904a-c095-492d-9c52-cfd5ee10a6e7@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=joshua.crofts1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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
all inboxes | Powered by JetHome®