From: Vladimir Oltean <olteanv@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Christian Marangi <ansuelsmth@gmail.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 2/6] dt-bindings: marvell: Add Marvell MV88E6060 DSA schema
Date: Mon, 16 Oct 2023 14:52:08 +0300 [thread overview]
Message-ID: <20231016115208.434cpmke4q3g3lwu@skbuf> (raw)
In-Reply-To: <20231016-marvell-88e6152-wan-led-v3-2-38cd449dfb15@linaro.org>
On Mon, Oct 16, 2023 at 11:12:55AM +0200, Linus Walleij wrote:
> +description:
> + The Marvell MV88E6060 switch has been produced and sold by Marvell
> + since at least 2010. The switch has one pin ADDR4 that controls the
> + MDIO address of the switch to be 0x10 or 0x00, and on the MDIO bus
> + connected to the switch, the PHY:s inside the switch appear as
PHYs without :, I guess
> + independent devices on address 0x00-0x04 or 0x10-0x14, so in difference
> + from many other DSA switches this switch does not have an internal
> + MDIO bus for the PHY devices.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Oltean <olteanv@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Christian Marangi <ansuelsmth@gmail.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 2/6] dt-bindings: marvell: Add Marvell MV88E6060 DSA schema
Date: Mon, 16 Oct 2023 14:52:08 +0300 [thread overview]
Message-ID: <20231016115208.434cpmke4q3g3lwu@skbuf> (raw)
In-Reply-To: <20231016-marvell-88e6152-wan-led-v3-2-38cd449dfb15@linaro.org>
On Mon, Oct 16, 2023 at 11:12:55AM +0200, Linus Walleij wrote:
> +description:
> + The Marvell MV88E6060 switch has been produced and sold by Marvell
> + since at least 2010. The switch has one pin ADDR4 that controls the
> + MDIO address of the switch to be 0x10 or 0x00, and on the MDIO bus
> + connected to the switch, the PHY:s inside the switch appear as
PHYs without :, I guess
> + independent devices on address 0x00-0x04 or 0x10-0x14, so in difference
> + from many other DSA switches this switch does not have an internal
> + MDIO bus for the PHY devices.
next prev parent reply other threads:[~2023-10-16 11:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 9:12 [PATCH net-next v3 0/6] Create a binding for the Marvell MV88E6xxx DSA switches Linus Walleij
2023-10-16 9:12 ` Linus Walleij
2023-10-16 9:12 ` [PATCH net-next v3 1/6] dt-bindings: marvell: Rewrite MV88E6xxx in schema Linus Walleij
2023-10-16 9:12 ` Linus Walleij
2023-10-16 10:20 ` Rob Herring
2023-10-16 10:20 ` Rob Herring
2023-10-16 11:08 ` Vladimir Oltean
2023-10-16 11:08 ` Vladimir Oltean
2023-10-16 12:59 ` Rob Herring
2023-10-16 12:59 ` Rob Herring
2023-10-16 11:52 ` Vladimir Oltean
2023-10-16 11:52 ` Vladimir Oltean
2023-10-16 12:57 ` Rob Herring
2023-10-16 12:57 ` Rob Herring
2023-10-16 9:12 ` [PATCH net-next v3 2/6] dt-bindings: marvell: Add Marvell MV88E6060 DSA schema Linus Walleij
2023-10-16 9:12 ` Linus Walleij
2023-10-16 11:52 ` Vladimir Oltean [this message]
2023-10-16 11:52 ` Vladimir Oltean
2023-10-16 9:12 ` [PATCH net-next v3 3/6] dt-bindings: net: mvusb: Fix up DSA example Linus Walleij
2023-10-16 9:12 ` Linus Walleij
2023-10-16 12:03 ` Vladimir Oltean
2023-10-16 12:03 ` Vladimir Oltean
2023-10-16 9:12 ` [PATCH net-next v3 4/6] ARM: dts: marvell: Fix some common switch mistakes Linus Walleij
2023-10-16 9:12 ` Linus Walleij
2023-10-16 9:12 ` [PATCH net-next v3 5/6] ARM: dts: nxp: " Linus Walleij
2023-10-16 9:12 ` Linus Walleij
2023-10-16 9:12 ` [PATCH net-next v3 6/6] ARM64: dts: marvell: " Linus Walleij
2023-10-16 9:12 ` Linus Walleij
2023-10-16 10:47 ` Vladimir Oltean
2023-10-16 10:47 ` Vladimir Oltean
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=20231016115208.434cpmke4q3g3lwu@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.