From: Conor Dooley <conor@kernel.org>
To: "Paller, Kim Seer" <KimSeer.Paller@analog.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Dimitri Fedrau" <dima.fedrau@gmail.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
"Nuno Sá" <noname.nuno@gmail.com>
Subject: Re: [PATCH v4 4/5] dt-bindings: iio: dac: Add adi,ltc2672.yaml
Date: Mon, 24 Jun 2024 18:00:24 +0100 [thread overview]
Message-ID: <20240624-untracked-molasses-31e8769dddd3@spud> (raw)
In-Reply-To: <PH0PR03MB71419D55571B07479B4F4FB8F9D42@PH0PR03MB7141.namprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2710 bytes --]
On Mon, Jun 24, 2024 at 03:26:26PM +0000, Paller, Kim Seer wrote:
>
>
> > -----Original Message-----
> > From: Jonathan Cameron <jic23@kernel.org>
> > Sent: Sunday, June 23, 2024 9:44 PM
> > To: Conor Dooley <conor@kernel.org>
> > Cc: Paller, Kim Seer <KimSeer.Paller@analog.com>; linux-
> > kernel@vger.kernel.org; linux-iio@vger.kernel.org; devicetree@vger.kernel.org;
> > David Lechner <dlechner@baylibre.com>; Lars-Peter Clausen
> > <lars@metafoo.de>; Liam Girdwood <lgirdwood@gmail.com>; Mark Brown
> > <broonie@kernel.org>; Dimitri Fedrau <dima.fedrau@gmail.com>; Krzysztof
> > Kozlowski <krzk+dt@kernel.org>; Rob Herring <robh@kernel.org>; Conor
> > Dooley <conor+dt@kernel.org>; Hennerich, Michael
> > <Michael.Hennerich@analog.com>; Nuno Sá <noname.nuno@gmail.com>
> > Subject: Re: [PATCH v4 4/5] dt-bindings: iio: dac: Add adi,ltc2672.yaml
> >
> > [External]
> >
> > On Wed, 19 Jun 2024 18:57:59 +0100
> > Conor Dooley <conor@kernel.org> wrote:
> >
> > > On Wed, Jun 19, 2024 at 02:49:03PM +0800, Kim Seer Paller wrote:
> > > > +patternProperties:
> > > > + "^channel@[0-4]$":
> > > > + type: object
> > > > + additionalProperties: false
> > > > +
> > > > + properties:
> > > > + reg:
> > > > + description: The channel number representing the DAC output
> > channel.
> > > > + maximum: 4
> > > > +
> > > > + adi,toggle-mode:
> > > > + description:
> > > > + Set the channel as a toggle enabled channel. Toggle operation
> > enables
> > > > + fast switching of a DAC output between two different DAC codes
> > without
> > > > + any SPI transaction.
> > > > + type: boolean
> > > > +
> > > > + adi,output-range-microamp:
> > > > + description: Specify the channel output full scale range.
> > > > + enum: [3125000, 6250000, 12500000, 25000000, 50000000,
> > 100000000,
> > > > + 200000000, 300000000]
> > >
> > > IIO folks, is this sort of thing common/likely to exist on other DACs?
> >
> > Fair point. It is probably time to conclude this is at least moderately common
> > and generalize it - which will need a dac.yaml similar to the one we have for
> > ADCs in adc/adc.yaml. That will need to make this a per channel node property
> > (same as the adc ones).
>
> Should I proceed with generalizing common DAC properties in this series and does
I think so, yes.
> this mean somehow removing these common properties from existing DAC bindings?
I think that that one is up to Jonathan.
> > I'd also expect it to always take 2 values. In many cases the first will be 0 but
> > that is fine.
> >
> > Jonathan
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-06-24 17:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 6:48 [PATCH v4 0/5] Add driver for LTC2664 and LTC2672 Kim Seer Paller
2024-06-19 6:49 ` [PATCH v4 1/5] iio: ABI: Generalize ABI documentation for DAC Kim Seer Paller
2024-06-19 6:49 ` [PATCH v4 2/5] iio: ABI: add DAC 42kohm_to_gnd powerdown mode Kim Seer Paller
2024-06-19 6:49 ` [PATCH v4 3/5] dt-bindings: iio: dac: Add adi,ltc2664.yaml Kim Seer Paller
2024-06-19 17:56 ` Conor Dooley
2024-06-24 15:13 ` Paller, Kim Seer
2024-06-24 16:13 ` Conor Dooley
2024-06-24 16:48 ` David Lechner
2024-06-25 15:41 ` Paller, Kim Seer
2024-06-19 6:49 ` [PATCH v4 4/5] dt-bindings: iio: dac: Add adi,ltc2672.yaml Kim Seer Paller
2024-06-19 17:57 ` Conor Dooley
2024-06-23 13:43 ` Jonathan Cameron
2024-06-23 14:03 ` Conor Dooley
2024-06-23 16:20 ` Jonathan Cameron
2024-06-24 15:26 ` Paller, Kim Seer
2024-06-24 17:00 ` Conor Dooley [this message]
2024-06-24 17:37 ` Jonathan Cameron
2024-06-25 15:51 ` Paller, Kim Seer
2024-06-25 16:20 ` Conor Dooley
2024-06-28 19:02 ` Jonathan Cameron
2024-06-19 6:49 ` [PATCH v4 5/5] iio: dac: ltc2664: Add driver for LTC2664 and LTC2672 Kim Seer Paller
2024-06-20 0:00 ` Paller, Kim Seer
2024-06-23 13:50 ` Jonathan Cameron
2024-06-26 11:14 ` Nuno Sá
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=20240624-untracked-molasses-31e8769dddd3@spud \
--to=conor@kernel.org \
--cc=KimSeer.Paller@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dima.fedrau@gmail.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noname.nuno@gmail.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