From: David Lechner <dlechner@baylibre.com>
To: "Nuno Sá" <noname.nuno@gmail.com>,
"Ariana Lazar" <ariana.lazar@microchip.com>,
"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>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: dac: adding support for Microchip MCP47FEB02
Date: Mon, 22 Sep 2025 17:15:29 -0500 [thread overview]
Message-ID: <3457c119-2f49-43a3-b96b-736b8f5de99b@baylibre.com> (raw)
In-Reply-To: <859d8472a8f9e8d28b890ad565f9d3ce11e162d5.camel@gmail.com>
On 9/22/25 3:10 PM, Nuno Sá wrote:
> Hi Ariana,
>
> Thanks for your patches. Some initial comments from me...
>
> On Mon, 2025-09-22 at 14:30 +0300, Ariana Lazar wrote:
...
>> +static IIO_DEVICE_ATTR(store_eeprom, 0200, NULL, mcp47feb02_store_eeprom, 0);
>> +static struct attribute *mcp47feb02_attributes[] = {
>> + &iio_dev_attr_store_eeprom.dev_attr.attr,
>> + NULL,
>> +};
>> +
>
> Not going to argue about the ABI for now but I don't think this is a standard one? So
> if acceptable you need an ABI doc.
>
Here's a random idea. (I would wait for Jonathan to weigh in first before
assuming it is an acceptable idea though :-p)
The config registers are pretty much going to be a one-time deal. So those
could be written to only if they need it during probe.
For the voltage output registers, we could add extra out_voltageY channels
that are the power-on output state channels. So writing to out_voltageY_raw
wouldn't change any real output but would just be written to EEPROM. This
way these voltages could be controlled independently from the real outputs
and it uses existing ABI.
In any case, it would be interesting to hear more about how this chips are
actually used to better understand this EEPROM feature.
next prev parent reply other threads:[~2025-09-22 22:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 11:30 [PATCH 0/2] Adding " Ariana Lazar
2025-09-22 11:30 ` [PATCH 1/2] dt-bindings: iio: dac: adding " Ariana Lazar
2025-09-22 16:38 ` Rob Herring (Arm)
2025-09-22 21:59 ` David Lechner
2025-09-27 17:00 ` Jonathan Cameron
2025-09-22 22:00 ` Rob Herring
2025-09-22 11:30 ` [PATCH 2/2] " Ariana Lazar
2025-09-22 20:10 ` Nuno Sá
2025-09-22 22:15 ` David Lechner [this message]
2025-09-23 8:21 ` Nuno Sá
2025-09-27 17:13 ` Jonathan Cameron
2025-09-29 5:44 ` Nuno Sá
2025-09-26 15:38 ` Dan Carpenter
2025-09-27 17:53 ` Jonathan Cameron
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=3457c119-2f49-43a3-b96b-736b8f5de99b@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andy@kernel.org \
--cc=ariana.lazar@microchip.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noname.nuno@gmail.com \
--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®