From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Chris Snook <chris.snook@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
James Hogan <jhogan@kernel.org>, Jay Cliburn <jcliburn@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Paul Burton <paul.burton@mips.com>,
Ralf Baechle <ralf@linux-mips.org>,
Rob Herring <robh+dt@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Vivien Didelot <vivien.didelot@gmail.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH v1 2/4] dt-bindings: net: dsa: qca,ar9331 switch documentation
Date: Thu, 17 Oct 2019 08:42:11 +0200 [thread overview]
Message-ID: <3944e911-8eaf-1c57-14de-0998b3245225@pengutronix.de> (raw)
In-Reply-To: <20191016202356.GM17013@lunn.ch>
On 16.10.19 22:23, Andrew Lunn wrote:
> On Mon, Oct 14, 2019 at 08:15:47AM +0200, Oleksij Rempel wrote:
>> Atheros AR9331 has built-in 5 port switch. The switch can be configured
>> to use all 5 or 4 ports. One of built-in PHYs can be used by first built-in
>> ethernet controller or to be used directly by the switch over second ethernet
>> controller.
>
> Hi Oleksij
>
> How exactly is this phy sharing controlled? I did not see anything in
> the driver. Is there a mux we need to set?
Currently it is not controlled at all, eth0 should be disabled and switch port5 enabled
(or other way around) in devicetree. If both are enabled, it will be some how brocken. I
don't know how to properly implement it.
I assume, it should not be controlled by devicetree configuration and user should be able
to do it dynamically from user space.
Ideas, suggestions?
Kind regards,
Oleksij Rempel
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2019-10-17 6:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 6:15 [PATCH v1 0/4] add dsa switch support for ar9331 Oleksij Rempel
2019-10-14 6:15 ` [PATCH v1 1/4] net: ag71xx: port to phylink Oleksij Rempel
2019-10-16 12:12 ` Andrew Lunn
2019-10-16 12:24 ` Oleksij Rempel
2019-10-16 13:32 ` Andrew Lunn
2019-10-16 17:45 ` David Miller
2019-10-14 6:15 ` [PATCH v1 2/4] dt-bindings: net: dsa: qca,ar9331 switch documentation Oleksij Rempel
2019-10-16 12:21 ` Andrew Lunn
2019-10-16 12:40 ` Oleksij Rempel
2019-10-16 20:23 ` Andrew Lunn
2019-10-17 6:42 ` Oleksij Rempel [this message]
2019-10-14 6:15 ` [PATCH v1 3/4] MIPS: ath79: ar9331: add ar9331-switch node Oleksij Rempel
2019-10-14 6:15 ` [PATCH v1 4/4] net: dsa: add support for Atheros AR9331 build-in switch Oleksij Rempel
2019-10-16 13:00 ` Andrew Lunn
2019-10-16 14:07 ` Oleksij Rempel
2019-10-16 16:20 ` Fabio Estevam
2019-10-17 18:35 ` Florian Fainelli
2019-10-18 4:52 ` Oleksij Rempel
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=3944e911-8eaf-1c57-14de-0998b3245225@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=andrew@lunn.ch \
--cc=chris.snook@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jcliburn@gmail.com \
--cc=jhogan@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.org \
--cc=vivien.didelot@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).