From: Conor Dooley <conor@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>,
Julien Massot <julien.massot@collabora.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH 3/5] dt-bindings: i2c: maxim,max96717: add new properties
Date: Wed, 12 Feb 2025 20:11:44 +0000 [thread overview]
Message-ID: <20250212-policy-abdominal-052bf84a7d10@spud> (raw)
In-Reply-To: <20250212174209.GA3890372-robh@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1902 bytes --]
On Wed, Feb 12, 2025 at 11:42:09AM -0600, Rob Herring wrote:
> On Tue, Feb 11, 2025 at 06:46:10PM +0000, Conor Dooley wrote:
> > On Fri, Feb 07, 2025 at 01:29:55PM +0200, Laurentiu Palcu wrote:
> > > Add 'maxim,override-mode' property to allow the user to toggle the pin
> > > configured chip operation mode and 'maxim,fsync-config' to configure the
> > > chip for relaying a frame synchronization signal, received from
> > > deserializer, to the attached sensor. The latter is needed for
> > > synchronizing the images in multi-sensor setups.
> > >
> > > Signed-off-by: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
> > > ---
> > > .../bindings/media/i2c/maxim,max96717.yaml | 28 +++++++++++++++++++
> > > 1 file changed, 28 insertions(+)
> > >
> > > diff --git a/Documentation/devicetree/bindings/media/i2c/maxim,max96717.yaml b/Documentation/devicetree/bindings/media/i2c/maxim,max96717.yaml
> > > index d1e8ba6e368ec..fae578d55fd4d 100644
> > > --- a/Documentation/devicetree/bindings/media/i2c/maxim,max96717.yaml
> > > +++ b/Documentation/devicetree/bindings/media/i2c/maxim,max96717.yaml
> > > @@ -42,10 +42,35 @@ properties:
> > > number must be in range of [0, 10].
> > >
> > > gpio-controller: true
> > > + gpio-reserved-ranges: true
> > >
> > > '#clock-cells':
> > > const: 0
> > >
> > > + maxim,override-mode:
> > > + description: Toggle the operation mode from the pin configured one.
> > > + type: boolean
> >
> > type: flag
>
> Err, no.
>
> You can do as-is or:
>
> $ref: /schemas/types.yaml#/definitions/flag
Eh, that's sloppy. I must have been rushing or distracted. Sorry.
> I am neutral as to which way. If I wasn't we'd make the meta-schema
> enforce one way or the other.
I'm biased towards flag, since I've seen confusion about setting the
boolean ones to false to disable them a bunch.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-02-12 20:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 11:29 [PATCH 0/5] media/i2c: max96717: a few changes Laurentiu Palcu
2025-02-07 11:29 ` [PATCH 3/5] dt-bindings: i2c: maxim,max96717: add new properties Laurentiu Palcu
2025-02-11 18:46 ` Conor Dooley
2025-02-12 17:42 ` Rob Herring
2025-02-12 20:11 ` Conor Dooley [this message]
2025-02-12 17:42 ` Rob Herring (Arm)
2025-02-18 13:54 ` Julien Massot
2025-03-06 8:24 ` Laurentiu Palcu
2025-03-13 7:41 ` Julien Massot
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=20250212-policy-abdominal-052bf84a7d10@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=julien.massot@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=laurentiu.palcu@oss.nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--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