From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Bhadram Varka <vbhadram@nvidia.com>,
Paolo Abeni <pabeni@redhat.com>,
devicetree@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jon Hunter <jonathanh@nvidia.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-tegra@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v4 5/9] dt-bindings: net: Add Tegra234 MGBE
Date: Mon, 11 Jul 2022 13:09:47 -0600 [thread overview]
Message-ID: <20220711190947.GA108998-robh@kernel.org> (raw)
In-Reply-To: <20220707074818.1481776-6-thierry.reding@gmail.com>
On Thu, 07 Jul 2022 09:48:14 +0200, Thierry Reding wrote:
> From: Bhadram Varka <vbhadram@nvidia.com>
>
> Add device-tree binding documentation for the Multi-Gigabit Ethernet
> (MGBE) controller found on NVIDIA Tegra234 SoCs.
>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> Signed-off-by: Bhadram Varka <vbhadram@nvidia.com>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> Changes in v4:
> - uses fixed lists of items for clock-names and reset-names
> - add missing maxItems to interrupts property
> - drop minItems where it equals maxItems
> - drop unnecessary blank lines
> - drop redundant comment
>
> Changes in v3:
> - add macsec and macsec-ns interrupt names
> - improve mdio bus node description
> - drop power-domains description
> - improve bindings title
>
> Changes in v2:
> - add supported PHY modes
> - change to dual license
>
> .../bindings/net/nvidia,tegra234-mgbe.yaml | 162 ++++++++++++++++++
> 1 file changed, 162 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/nvidia,tegra234-mgbe.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-07-11 19:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 7:48 [PATCH v4 0/9] tegra: Add support for MGBE controller Thierry Reding
2022-07-07 7:48 ` [PATCH v4 1/9] dt-bindings: power: Add Tegra234 MGBE power domains Thierry Reding
2022-07-07 7:48 ` [PATCH v4 2/9] dt-bindings: Add Tegra234 MGBE clocks and resets Thierry Reding
2022-07-07 7:48 ` [PATCH v4 3/9] dt-bindings: memory: Add Tegra234 MGBE memory clients Thierry Reding
2022-07-07 7:48 ` [PATCH v4 4/9] memory: tegra: Add MGBE memory clients for Tegra234 Thierry Reding
2022-07-07 7:48 ` [PATCH v4 5/9] dt-bindings: net: Add Tegra234 MGBE Thierry Reding
2022-07-08 16:26 ` Thierry Reding
2022-07-11 19:09 ` Rob Herring [this message]
2022-07-07 7:48 ` [PATCH v4 6/9] arm64: tegra: Add MGBE nodes on Tegra234 Thierry Reding
2022-07-07 7:48 ` [PATCH v4 7/9] arm64: tegra: Enable MGBE on Jetson AGX Orin Developer Kit Thierry Reding
2022-07-07 7:48 ` [PATCH v4 8/9] arm64: defconfig: Enable Tegra MGBE driver Thierry Reding
2022-07-07 7:48 ` [PATCH net-next v4 9/9] stmmac: tegra: Add MGBE support Thierry Reding
2022-09-07 16:36 ` Thierry Reding
2022-09-22 15:05 ` Jon Hunter
2022-09-22 15:34 ` Jakub Kicinski
2022-09-23 12:39 ` Thierry Reding
2022-09-23 12:52 ` Jakub Kicinski
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=20220711190947.GA108998-robh@kernel.org \
--to=robh@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vbhadram@nvidia.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).