From: Rob Herring <robh@kernel.org>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial <linux-serial@vger.kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
linux-stm32 <linux-stm32@st-md-mailman.stormreply.com>,
Rob Herring <robh+dt@kernel.org>, Al Cooper <alcooperx@gmail.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
devicetree <devicetree@vger.kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: serial: Change to reference the kernel-defined serial.yaml
Date: Thu, 6 May 2021 20:14:49 -0500 [thread overview]
Message-ID: <20210507011449.GA1126886@robh.at.kernel.org> (raw)
In-Reply-To: <20210506132049.1513-2-thunder.leizhen@huawei.com>
On Thu, 06 May 2021 21:20:48 +0800, Zhen Lei wrote:
> The /schemas/serial.yaml from dt-schema only has the property $nodename,
> whereas the kernel-defined /schemas/serial/serial.yaml contains more
> useful properties, support for more complex application scenarios.
>
> For example:
> 1) The property "current-speed" in fsl-lx2160a.dtsi
> 2) The subnode "bluetooth" in hi3660-hikey960.dts
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> ---
> Documentation/devicetree/bindings/serial/8250.yaml | 2 +-
> .../devicetree/bindings/serial/brcm,bcm7271-uart.yaml | 2 +-
> Documentation/devicetree/bindings/serial/ingenic,uart.yaml | 2 +-
> Documentation/devicetree/bindings/serial/pl011.yaml | 4 ++--
> Documentation/devicetree/bindings/serial/qca,ar9330-uart.yaml | 4 ++--
> Documentation/devicetree/bindings/serial/renesas,em-uart.yaml | 2 +-
> Documentation/devicetree/bindings/serial/samsung_uart.yaml | 2 +-
> Documentation/devicetree/bindings/serial/sifive-serial.yaml | 4 ++--
> .../devicetree/bindings/serial/snps-dw-apb-uart.yaml | 2 +-
> Documentation/devicetree/bindings/serial/st,stm32-uart.yaml | 3 +--
> 10 files changed, 13 insertions(+), 14 deletions(-)
>
Thanks for doing this!
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-05-07 1:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 13:20 [PATCH v3 0/2] dt-bindings: serial: Change to reference the kernel-defined serial.yaml Zhen Lei
2021-05-06 13:20 ` [PATCH v3 1/2] " Zhen Lei
2021-05-07 1:14 ` Rob Herring [this message]
2021-05-06 13:20 ` [PATCH v3 2/2] dt-bindings: serial: Add label property in serial.yaml Zhen Lei
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=20210507011449.GA1126886@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alcooperx@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=thunder.leizhen@huawei.com \
/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).