From: Marek Vasut <marex@denx.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
David Miller <davem@davemloft.net>
Cc: andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com,
mark.rutland@arm.com, robh+dt@kernel.org, kernel@pengutronix.de,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
david@protonic.nl, devicetree@vger.kernel.org,
linux@armlinux.org.uk, olteanv@gmail.com
Subject: Re: user space interface for configuring T1 PHY management mode (master/slave)
Date: Wed, 25 Mar 2020 11:21:10 +0100 [thread overview]
Message-ID: <e2a1877c-1cb2-e047-38e0-e3b41d941b33@denx.de> (raw)
In-Reply-To: <20200325083449.GA8404@pengutronix.de>
On 3/25/20 9:34 AM, Oleksij Rempel wrote:
> Hi all,
Hi,
> I'm working on mainlining of NXP1102 PHY (BroadR Reach/802.3bw) support.
>
> Basic functionality is working and support with mainline kernel. Now it is time
> to extend it. According to the specification, each PHY can be master or slave.
>
> The HW can be pre configured via bootstrap pins or fuses to have a default
> configuration. But in some cases we still need to be able to configure the PHY
> in a different mode:
> --------------------------------------------------------------------------------
> http://www.ieee802.org/3/1TPCESG/public/BroadR_Reach_Automotive_Spec_V3.0.pdf
>
> 6.1 MASTER-SLAVE configuration resolution
>
> All BroadR-Reach PHYs will default to configure as SLAVE upon power up or reset
> until a management system (for example, processor/microcontroller) configures
> it to be MASTER. MASTER-SLAVE assignment for each link configuration is
> necessary for establishing the timing control of each PHY.
Thanks for reminding me of this. I sent out
https://patchwork.ozlabs.org/project/netdev/list/?series=166575
maybe it helps.
prev parent reply other threads:[~2020-03-25 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 8:34 user space interface for configuring T1 PHY management mode (master/slave) Oleksij Rempel
2020-03-25 10:11 ` Russell King - ARM Linux admin
2020-03-25 10:28 ` David Jander
2020-03-25 10:21 ` Marek Vasut [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=e2a1877c-1cb2-e047-38e0-e3b41d941b33@denx.de \
--to=marex@denx.de \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=david@protonic.nl \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=robh+dt@kernel.org \
/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