From: Rob Herring <robh@kernel.org>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: devicetree <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-serial <linux-serial@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 3/3] dt-bindings: serial: Add label property in serial.yaml
Date: Fri, 30 Apr 2021 10:21:28 -0500 [thread overview]
Message-ID: <20210430152128.GA3348522@robh.at.kernel.org> (raw)
In-Reply-To: <20210422085837.513-4-thunder.leizhen@huawei.com>
On Thu, 22 Apr 2021 16:58:37 +0800, Zhen Lei wrote:
> When there is more than one serial port present, the property 'label'
> allows a custom name to be used for briefly describe the usage or position
> of each serial port.
>
> Without this "label" property, many dtbs_check warnings similar to the
> following are reported:
> arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dt.yaml: \
> serial@ffd74000: Additional properties are not allowed ('label' was unexpected)
> From schema: Documentation/devicetree/bindings/serial/pl011.yaml
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> ---
> Documentation/devicetree/bindings/serial/serial.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2021-04-30 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 8:58 [PATCH v2 0/3] dt-bindings: serial: pl011: Fix some dtbs_check warnings Zhen Lei
2021-04-22 8:58 ` [PATCH v2 1/3] dt-bindings: serial: Normalize the node name of the serial port Zhen Lei
2021-04-30 15:18 ` Rob Herring
2021-05-06 2:08 ` Leizhen (ThunderTown)
2021-04-22 8:58 ` [PATCH v2 2/3] dt-bindings: serial: pl011: Change to reference the kernel-defined serial.yaml Zhen Lei
2021-04-30 15:21 ` Rob Herring
2021-05-06 2:44 ` Leizhen (ThunderTown)
2021-04-22 8:58 ` [PATCH v2 3/3] dt-bindings: serial: Add label property in serial.yaml Zhen Lei
2021-04-30 15:21 ` Rob Herring [this message]
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=20210430152128.GA3348522@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--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).