From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Rob Herring <robh@kernel.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ulrich Hecht <uli+renesas@fpond.eu>,
Chris Brandt <chris.brandt@renesas.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: serial: sh-sci: Convert to json-schema
Date: Mon, 23 Mar 2020 15:38:40 +0100 [thread overview]
Message-ID: <CAMuHMdWoRSE7VQ5o575Ocjfh+y1yH-ciFE1BUqqPVO9oukwgNw@mail.gmail.com> (raw)
In-Reply-To: <20200312200523.GA17854@bogus>
Hi Rob,
Thanks a lot for your comments!
On Thu, Mar 12, 2020 at 9:05 PM Rob Herring <robh@kernel.org> wrote:
> On Fri, Mar 06, 2020 at 10:07:20AM +0100, Geert Uytterhoeven wrote:
> > Convert the Renesas Serial Communication Interface ((H)SCI(F)(A|B))
> > Device Tree binding documentation to json-schema.
> >
> > Split the bindings in 5 files, one per major type, to ease expressing
> > constraints.
> >
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/serial/renesas,sci.yaml
> > +properties:
> > + compatible:
> > + oneOf:
> > + - items:
> > + - const: renesas,sci
>
> Do you plan to add to this? It can be simplified to just
Not really. I just used the same construct for consistency with the other
SCI variants.
> 'const: renesas,sci'.
OK. I guess no other H8 and SuperH variants will pop up anytime soon.
Oops, RZ/A1 has SCI, and RZ/A2 has SCIg (they keep on inventing new
names, to be seen how compatible).
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/serial/renesas,scif.yaml
> > @@ -0,0 +1,168 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: "http://devicetree.org/schemas/serial/renesas,scif.yaml#"
> > +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> > +
> > +title: Renesas Serial Communication Interface with FIFO (SCIF)
> > +
> > +maintainers:
> > + - Geert Uytterhoeven <geert+renesas@glider.be>
> > +
> > +description:
> > + Each enabled UART may have an optional "serialN" alias in the "aliases" node,
> > + where N is the port number (non-negative decimal integer) as printed on the
> > + label next to the physical port.
>
> That's every serial port...
So you suggest to just remove this paragraph from all files?
Shall I add it to serial.yaml instead?
> > + interrupts:
> > + description: |
> > + Must contain one or more interrupt-specifiers for the serial interface.
> > + If a single interrupt is expressed, then all events are
> > + multiplexed into this single interrupt.
> > +
> > + If multiple interrupts are provided by the hardware, the order
> > + in which the interrupts are listed must match order below. Note
> > + that some HW interrupt events may be muxed together resulting
> > + in duplicate entries.
> > + minItems: 1
> > + maxItems: 6
>
> This allows 2, 3, 4, or 5 interrupts. Is that valid? If not, then you
1, 4, and 6 are valid.
> should do something like this:
>
> oneOf:
> - items:
> description: A combined interrupt
> - items:
> - description: Error interrupt
> - ...
So I tried:
interrupts:
oneOf:
- items:
description: A combined interrupt
- items:
- description: Error interrupt
- description: Receive buffer full interrupt
- description: Transmit buffer empty interrupt
- description: Transmit End interrupt
- items:
- description: Error interrupt
- description: Receive buffer full interrupt
- description: Transmit buffer empty interrupt
- description: Break interrupt
- description: Data Ready interrupt
- description: Transmit End interrupt
That fails for devices with 4 or 6 interrupts, e.g.:
arch/arm/boot/dts/r7s9210-rza2mevb.dt.yaml: serial@e8007000:
interrupts: [[0, 265, 4], [0, 266, 4], [0, 267, 4], [0, 265, 4], [0,
268, 4], [0, 268, 4]] is valid under each of {'additionalItems':
False, 'items': [{}, {}, {}, {}, {}, {}], 'maxItems': 6, 'minItems':
6, 'type': 'array'}, {'items': {}, 'type': 'array'}
Note that initially I forgot to cater for the 4-interrupt case used in
arch/arm/boot/dts/r7s72100.dtsi, and "make dtbs_check" did not complain.
> > +
> > + interrupt-names:
> > + minItems: 1
> > + maxItems: 6
> > + items:
> > + enum:
> > + - eri # Error
> > + - rxi # Receive buffer full
> > + - txi # Transmit buffer empty
> > + - bri # Break
> > + - dri # Data Ready
> > + - tei # Transmit End
>
> Based on above, you probably want 'items' to be a list, not a
> dict(schema).
Like
interrupt-names:
oneOf:
- items:
- const: eri
- const: rxi
- const: txi
- const: tei
- items:
- const: eri
- const: rxi
- const: txi
- const: bri
- const: dri
- const: tei
?
Seems to work, but needs the duplication as the 4-interrupt case is not
just the 4 first entries of the 6-interrupt case (tei is always last).
> > +
> > + clocks:
> > + minItems: 1
> > + maxItems: 4
> > +
> > + clock-names:
> > + minItems: 1
> > + maxItems: 4
> > + items:
> > + enum:
> > + - fck # UART functional clock
> > + - sck # optional external clock input
> > + - brg_int # optional internal clock source for BRG frequency divider
> > + - scif_clk # optional external clock source for BRG frequency divider
>
> Same issue again...
The order is not fixed for the three optional clocks, as they may or
may not be wired (for sck and scif_clk), or the BRG may not be present.
Hence unlike for interrupts, I cannot drop the "enum", IIUIC?
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-23 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 9:07 [PATCH] dt-bindings: serial: sh-sci: Convert to json-schema Geert Uytterhoeven
2020-03-12 20:05 ` Rob Herring
2020-03-23 14:38 ` Geert Uytterhoeven [this message]
2020-03-23 16:41 ` Rob Herring
2020-03-24 8:10 ` Geert Uytterhoeven
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=CAMuHMdWoRSE7VQ5o575Ocjfh+y1yH-ciFE1BUqqPVO9oukwgNw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=chris.brandt@renesas.com \
--cc=dalias@libc.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=robh@kernel.org \
--cc=uli+renesas@fpond.eu \
--cc=ysato@users.sourceforge.jp \
/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).