From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: serial: Convert generic bindings to json-schema
Date: Wed, 4 Mar 2020 15:44:28 +0100 [thread overview]
Message-ID: <CAMuHMdUh-NBSDhO7A_HU54S7X920PUj8ScAZUWh8uMqZnjE2xA@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqL7x-XevypLxUUksOCyezbn8=NpL9rMfo0rCQyYzrUxmw@mail.gmail.com>
Hi Rob,
On Wed, Mar 4, 2020 at 3:03 PM Rob Herring <robh+dt@kernel.org> wrote:
> On Tue, Mar 3, 2020 at 7:43 AM Geert Uytterhoeven
> <geert+renesas@glider.be> wrote:
> > Convert the generic serial interface Device Tree binding documentation
> > to json-schema.
> >
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > + cts-gpios:
> > + description:
> > + Must contain a GPIO specifier, referring to the GPIO pin to be used as
> > + the UART's CTS line.
> > + rts-gpios:
> > + description:
> > + Must contain a GPIO specifier, referring to the GPIO pin to be used as
> > + the UART's RTS line.
> > +
> > + uart-has-rtscts:
> > + $ref: /schemas/types.yaml#/definitions/flag
> > + description:
> > + The presence of this property indicates that the UART has dedicated lines
> > + for RTS/CTS hardware flow control, and that they are available for use
> > + (wired and enabled by pinmux configuration). This depends on both the
> > + UART hardware and the board wiring.
> > + Note that this property is mutually-exclusive with "cts-gpios" and
> > + "rts-gpios" above, unless support is provided to switch between modes
> > + dynamically.
>
> This can be expressed as:
>
> oneOf:
> - {} # None of the properties present
> - required:
> - uart-has-rtscts
> - anyOf:
> - required:
> - cts-gpios
> - required:
> - rts-gpios
>
> Or probably more clearly:
>
> if:
> required:
> - uart-has-rtscts
> then:
> properties:
> rts-gpios: false
> cts-gpios: false
>
> (Untested)
Thanks. Note that when adding this, the note above must be removed.
>
> > +
> > +examples:
>
> Personally, I'd just drop examples from schemas that aren't complete.
OK.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2020-03-04 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 13:43 [PATCH 0/2] dt-bindings: serial: Convert generic and slave bindings to json-schema Geert Uytterhoeven
2020-03-03 13:43 ` [PATCH 1/2] dt-bindings: serial: Convert generic " Geert Uytterhoeven
2020-03-03 15:09 ` Geert Uytterhoeven
2020-03-04 14:03 ` Rob Herring
2020-03-04 14:44 ` Geert Uytterhoeven [this message]
2020-03-03 13:43 ` [PATCH 2/2] dt-bindings: serial: Convert slave-device " Geert Uytterhoeven
2020-03-03 15:10 ` Geert Uytterhoeven
2020-03-04 14:44 ` Rob Herring
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=CAMuHMdUh-NBSDhO7A_HU54S7X920PUj8ScAZUWh8uMqZnjE2xA@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@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).