From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Jon Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: serial: tegra-tcu: Document "reg" property
Date: Sat, 27 Mar 2021 12:49:25 -0600 [thread overview]
Message-ID: <20210327184925.GA367052@robh.at.kernel.org> (raw)
In-Reply-To: <20210326174641.1612738-3-thierry.reding@gmail.com>
On Fri, Mar 26, 2021 at 06:46:40PM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> In order to support early console support with the Tegra TCU, add an
> optional "reg" property that points to the TX mailbox.
This will mean the same address in in DT twice which we try to avoid,
right? I guess it's fine, we could drop it if we ever enforce that. I'm
sure there's worse abuses with duplicates than this.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../devicetree/bindings/serial/nvidia,tegra194-tcu.yaml | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/serial/nvidia,tegra194-tcu.yaml b/Documentation/devicetree/bindings/serial/nvidia,tegra194-tcu.yaml
> index 0a321658ccb5..8c9ed7cfaa52 100644
> --- a/Documentation/devicetree/bindings/serial/nvidia,tegra194-tcu.yaml
> +++ b/Documentation/devicetree/bindings/serial/nvidia,tegra194-tcu.yaml
> @@ -24,6 +24,9 @@ properties:
> compatible:
> const: nvidia,tegra194-tcu
>
> + reg:
> + maxItems: 1
> +
> mbox-names:
> items:
> - const: rx
> @@ -48,8 +51,9 @@ examples:
> - |
> #include <dt-bindings/mailbox/tegra186-hsp.h>
>
> - tcu: tcu {
> + tcu: tcu@c168000 {
While you're here:
serial@...
> compatible = "nvidia,tegra194-tcu";
> + reg = <0x0c168000 0x4>;
> mboxes = <&hsp_top0 TEGRA_HSP_MBOX_TYPE_SM 0>,
> <&hsp_aon TEGRA_HSP_MBOX_TYPE_SM 1>;
> mbox-names = "rx", "tx";
> --
> 2.30.2
>
next prev parent reply other threads:[~2021-03-27 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 17:46 [PATCH 0/3] arm64: tegra: Add earlycon support on Tegra194 Thierry Reding
2021-03-26 17:46 ` [PATCH 1/3] dt-bindings: serial: tegra-tcu: Convert to json-schema Thierry Reding
2021-03-27 18:41 ` Rob Herring
2021-03-26 17:46 ` [PATCH 2/3] dt-bindings: serial: tegra-tcu: Document "reg" property Thierry Reding
2021-03-27 18:49 ` Rob Herring [this message]
2021-03-29 7:23 ` Thierry Reding
2021-03-29 7:26 ` Thierry Reding
2021-03-26 17:46 ` [PATCH 3/3] arm64: tegra: Add "reg" property for TCU on Tegra194 Thierry Reding
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=20210327184925.GA367052@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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).