From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: David Bauer <mail@david-bauer.net>, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Landen Chao <Landen.Chao@mediatek.com>,
DENG Qingfang <dqfext@gmail.com>,
Sean Wang <sean.wang@mediatek.com>,
Daniel Golle <daniel@makrotopia.org>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 2/2] dt-bindings: net: dsa: mediatek,mt7530: document MDIO-bus
Date: Sun, 30 Apr 2023 15:53:00 +0300 [thread overview]
Message-ID: <fd6651a8-64e4-4f22-349f-b7f796ecffcc@arinc9.com> (raw)
In-Reply-To: <20230430112834.11520-2-mail@david-bauer.net>
On 30.04.2023 14:28, David Bauer wrote:
> Document the ability to add nodes for the MDIO bus connecting the
> switch-internal PHYs.
>
> Signed-off-by: David Bauer <mail@david-bauer.net>
> ---
> .../devicetree/bindings/net/dsa/mediatek,mt7530.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/dsa/mediatek,mt7530.yaml b/Documentation/devicetree/bindings/net/dsa/mediatek,mt7530.yaml
> index e532c6b795f4..50f8f83cc440 100644
> --- a/Documentation/devicetree/bindings/net/dsa/mediatek,mt7530.yaml
> +++ b/Documentation/devicetree/bindings/net/dsa/mediatek,mt7530.yaml
> @@ -128,6 +128,12 @@ properties:
> See Documentation/devicetree/bindings/regulator/mt6323-regulator.txt for
> details for the regulator setup on these boards.
>
> + mdio:
> + $ref: /schemas/net/mdio.yaml#
> + unevaluatedProperties: false
> + description:
> + Node for the internal MDIO bus connected to the embedded ethernet-PHYs.
Maybe saying "connected to the internal switch PHYs" would better
explain this.
Arınç
prev parent reply other threads:[~2023-04-30 12:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230430112834.11520-1-mail@david-bauer.net>
2023-04-30 11:28 ` [PATCH 2/2] dt-bindings: net: dsa: mediatek,mt7530: document MDIO-bus David Bauer
2023-04-30 12:34 ` Arınç ÜNAL
2023-04-30 12:44 ` Daniel Golle
2023-04-30 12:52 ` Arınç ÜNAL
2023-04-30 16:17 ` Arınç ÜNAL
2023-04-30 17:18 ` Andrew Lunn
2023-04-30 18:28 ` Arınç ÜNAL
2023-04-30 18:48 ` Andrew Lunn
2023-04-30 19:54 ` Arınç ÜNAL
2023-04-30 20:41 ` Andrew Lunn
2023-05-01 9:22 ` David Bauer
2023-05-01 9:28 ` Arınç ÜNAL
2023-04-30 12:53 ` Arınç ÜNAL [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=fd6651a8-64e4-4f22-349f-b7f796ecffcc@arinc9.com \
--to=arinc.unal@arinc9.com \
--cc=Landen.Chao@mediatek.com \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mail@david-bauer.net \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.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