From: Conor Dooley <conor@kernel.org>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: Nuno Sa <nuno.sa@analog.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH 5/6] dt-bindings: iio: temperature: ltc2983: document power supply
Date: Fri, 23 Feb 2024 18:43:03 +0000 [thread overview]
Message-ID: <20240223-parameter-impeach-e0dabf83a356@spud> (raw)
In-Reply-To: <8409a5bc71b995e3b738b817a074cfb131c3b2b5.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2129 bytes --]
On Fri, Feb 23, 2024 at 09:17:16AM +0100, Nuno Sá wrote:
> On Thu, 2024-02-22 at 17:54 +0000, Conor Dooley wrote:
> > On Thu, Feb 22, 2024 at 05:41:03PM +0100, Nuno Sá wrote:
> > > On Thu, 2024-02-22 at 15:40 +0000, Conor Dooley wrote:
> > > > On Thu, Feb 22, 2024 at 01:55:56PM +0100, Nuno Sa wrote:
> > > > > Add a property for the VDD power supply regulator.
> > > > >
> > > > > Signed-off-by: Nuno Sa <nuno.sa@analog.com>
> > > > > ---
> > > > > Documentation/devicetree/bindings/iio/temperature/adi,ltc2983.yaml | 2
> > > > > ++
> > > > > 1 file changed, 2 insertions(+)
> > > > >
> > > > > diff --git
> > > > > a/Documentation/devicetree/bindings/iio/temperature/adi,ltc2983.yaml
> > > > > b/Documentation/devicetree/bindings/iio/temperature/adi,ltc2983.yaml
> > > > > index dbb85135fd66..8aae867a770a 100644
> > > > > --- a/Documentation/devicetree/bindings/iio/temperature/adi,ltc2983.yaml
> > > > > +++ b/Documentation/devicetree/bindings/iio/temperature/adi,ltc2983.yaml
> > > > > @@ -57,6 +57,8 @@ properties:
> > > > > interrupts:
> > > > > maxItems: 1
> > > > >
> > > > > + vdd-supply: true
> > > >
> > > > Although technically an ABI break, should we make this supply required?
> > > > It is, at the end of the day, required by the hardware for operation.
> > > >
> > >
> > > I thought about it but then realized it could break some existing users
> > > which is
> > > never a nice thing.
> >
> > Could you explain what scenario it actually breaks a system (not
> > produces warnings with dtbs_check)?
>
> Oh, I guess I could not explain myself :). I did not meant breaking the system
> (I'm aware of the dummy regulator) but I meant exactly what you mention above
> about dtbs_check. Like, if someone already validated a devicetree against the
> current bindings, that same devicetree will fail to validate now right? And I
> had the idea that we should not allow that... If not the case, I'm perfectly
> fine in making the supply required.
I think that's fine, the system will still work which is the important
part of the ABI.
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-02-23 18:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 12:55 [PATCH 0/6] iio: temperature: ltc2983: small improvements Nuno Sa
2024-02-22 12:55 ` [PATCH 1/6] iio: temperature: ltc2983: make use of spi_get_device_match_data() Nuno Sa
2024-02-24 18:31 ` Jonathan Cameron
2024-02-22 12:55 ` [PATCH 2/6] iio: temperature: ltc2983: rename ltc2983_parse_dt() Nuno Sa
2024-02-24 18:32 ` Jonathan Cameron
2024-02-22 12:55 ` [PATCH 3/6] iio: temperature: ltc2983: convert to dev_err_probe() Nuno Sa
2024-02-24 18:44 ` Jonathan Cameron
2024-02-26 8:41 ` Nuno Sá
2024-02-22 12:55 ` [PATCH 4/6] iio: temperature: ltc2983: explicitly set the name in chip_info Nuno Sa
2024-02-24 18:47 ` Jonathan Cameron
2024-02-22 12:55 ` [PATCH 5/6] dt-bindings: iio: temperature: ltc2983: document power supply Nuno Sa
2024-02-22 15:40 ` Conor Dooley
2024-02-22 16:41 ` Nuno Sá
2024-02-22 17:54 ` Conor Dooley
2024-02-22 19:15 ` Jonathan Cameron
2024-02-23 8:17 ` Nuno Sá
2024-02-23 18:43 ` Conor Dooley [this message]
2024-02-22 12:55 ` [PATCH 6/6] iio: temperature: ltc2983: support vdd regulator Nuno Sa
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=20240223-parameter-impeach-e0dabf83a356@spud \
--to=conor@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=noname.nuno@gmail.com \
--cc=nuno.sa@analog.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.