From: Petre Rodan <petre.rodan@subdimension.ro>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH 1/2] dt-bindings: iio: pressure: honeywell,mprls0025pa
Date: Wed, 20 Dec 2023 19:25:25 +0200 [thread overview]
Message-ID: <ZYMjhfAbWfw9vUdd@sunspire> (raw)
In-Reply-To: <20231220151645.16ada807@jic23-huawei>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
hi Jonathan,
On Wed, Dec 20, 2023 at 03:16:45PM +0000, Jonathan Cameron wrote:
> On Tue, 19 Dec 2023 15:02:20 +0200
> Petre Rodan <petre.rodan@subdimension.ro> wrote:
> > honeywell,pmin-pascal:
> > description:
> > Minimum pressure value the sensor can measure in pascal.
> > + To be specified only if honeywell,pressure-triplet is set to "NA".
> That just added a backwards compatibility break. It would be fine
> if there was a default: NA for honeywell,pressure-triplet or a check that either
> one or the other was supplied (which I'd prefer). Thus old bindings will work
> and new ones also supported.
ok, I see your reasoning. but in this second scenario that you prefer how can we
propery define the 'required:' block? an equivalent to
required:
- compatible
- reg
- (honeywell,pmin-pascal && honeywell,pmax-pascal) || honeywell,pressure-triplet
- honeywell,transfer-function
thanks,
peter
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-20 17:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231219130230.32584-1-petre.rodan@subdimension.ro>
2023-12-19 13:02 ` [PATCH 1/2] dt-bindings: iio: pressure: honeywell,mprls0025pa Petre Rodan
2023-12-20 15:16 ` Jonathan Cameron
2023-12-20 17:25 ` Petre Rodan [this message]
2023-12-21 11:04 ` Jonathan Cameron
2023-12-22 15:27 ` Conor Dooley
2023-12-23 11:28 ` Petre Rodan
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=ZYMjhfAbWfw9vUdd@sunspire \
--to=petre.rodan@subdimension.ro \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).