From: Nishanth Menon <nm@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>, <linux-serial@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<nsekhar@ti.com>
Subject: Re: [PATCH] dt-bindings: serial: 8250_omap: Add compatible for UART controller on AM64 SoC
Date: Thu, 29 Oct 2020 08:26:39 -0500 [thread overview]
Message-ID: <20201029132639.xx7eoy4zrj2echi3@uphold> (raw)
In-Reply-To: <20201029065318.2437-1-vigneshr@ti.com>
On 12:23-20201029, Vignesh Raghavendra wrote:
> AM64 uses a UART controller that is compatible with AM654 UART.
> Introduce a specific compatible to help handle the differences if
> necessary.
>
> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
> ---
> Documentation/devicetree/bindings/serial/omap_serial.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/serial/omap_serial.txt b/Documentation/devicetree/bindings/serial/omap_serial.txt
> index dcba86b0a0d0..c2db8cabf2ab 100644
> --- a/Documentation/devicetree/bindings/serial/omap_serial.txt
> +++ b/Documentation/devicetree/bindings/serial/omap_serial.txt
> @@ -1,6 +1,7 @@
> OMAP UART controller
>
> Required properties:
> +- compatible : should be "ti,am64-uart", "ti,am654-uart" for AM64 controllers
> - compatible : should be "ti,j721e-uart", "ti,am654-uart" for J721E controllers
> - compatible : should be "ti,am654-uart" for AM654 controllers
> - compatible : should be "ti,omap2-uart" for OMAP2 controllers
> --
> 2.29.0
>
Thanks.
Reviewed-by: Nishanth Menon <nm@ti.com>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2020-10-29 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 6:53 [PATCH] dt-bindings: serial: 8250_omap: Add compatible for UART controller on AM64 SoC Vignesh Raghavendra
2020-10-29 13:26 ` Nishanth Menon [this message]
2020-11-04 20:54 ` 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=20201029132639.xx7eoy4zrj2echi3@uphold \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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).