From: Jonathan Cameron <jic23@kernel.org>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"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 00:14:17 +0100 [thread overview]
Message-ID: <20260725001417.159653b8@jic23-huawei> (raw)
In-Reply-To: <20260721-mcp47a1-add-support-v1-2-da045a2567e3@gmail.com>
On Tue, 21 Jul 2026 20:24:39 +0200
Joshua Crofts <joshua.crofts1@gmail.com> wrote:
> The Microchip MCP47A1 is a 6-bit volatile Digital-to-Analog converted
> which communicates via I2C.
>
> Signed-off-by: Joshua Crofts <joshua.crofts1@gmail.com>
A few really small comments inline. Nice little driver.
Given the really small number of registers, regmap does seem like
it might be overkill
> diff --git a/drivers/iio/dac/mcp47a1.c b/drivers/iio/dac/mcp47a1.c
> new file mode 100644
> index 000000000000..251c2281634f
> --- /dev/null
> +++ b/drivers/iio/dac/mcp47a1.c
> @@ -0,0 +1,193 @@
...
> +static int mcp47a1_probe(struct i2c_client *client)
> +{
...
> + /*
> + * This is a volatile DAC which doesn't have an ID register, instead
> + * the value register is set to 0x20 every Power-on-Reset (table 4-1).
> + * Any other read value at startup could indicate that the device is
> + * damaged etc.
or some earlier software wrote it and the all the regulators are stubs
provided as they can't be turned off by software.
I'd drop this test - it is a bit too flakey as a way to tell the chip
is there and working.
> + */
> + ret = regmap_read(data->regmap, MCP47A1_CMD_CODE, ®_val);
> + if (ret)
> + return dev_err_probe(dev, ret,
> + "Failed to read register on startup\n");
> +
> + if (reg_val != 0x20)
> + dev_info(dev, "Read value 0x%02x at startup\n", reg_val);
> +
> + indio_dev->name = "mcp47a1";
> + indio_dev->modes = INDIO_DIRECT_MODE;
> + indio_dev->info = &mcp47a1_info;
> + indio_dev->channels = mcp47a1_channels;
> + indio_dev->num_channels = ARRAY_SIZE(mcp47a1_channels);
> +
> + return devm_iio_device_register(dev, indio_dev);
> +}
next prev parent reply other threads:[~2026-07-24 23:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 18:24 [PATCH 0/2] iio: dac: mcp47a1: add support for new device Joshua Crofts
2026-07-21 18:24 ` [PATCH 1/2] dt-bindings: iio: dac: add support for mcp47a1 Joshua Crofts
2026-07-21 18:33 ` sashiko-bot
2026-07-21 18:37 ` 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 19:20 ` sashiko-bot
2026-07-21 20:47 ` Andy Shevchenko
2026-07-22 6:30 ` Joshua Crofts
2026-07-25 16:52 ` David Lechner
2026-07-24 23:14 ` Jonathan Cameron [this message]
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=20260725001417.159653b8@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--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