From: Vladimir Oltean <olteanv@gmail.com>
To: Bhadram Varka <vbhadram@nvidia.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Russell King <linux@armlinux.org.uk>,
Andrew Lunn <andrew@lunn.ch>,
Revanth Kumar Uppala <ruppala@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v4 RESEND] stmmac: tegra: Add MGBE support
Date: Fri, 18 Nov 2022 15:02:16 +0200 [thread overview]
Message-ID: <20221118130216.hxes7yucdl6hn2kl@skbuf> (raw)
In-Reply-To: <LV2PR12MB5727354F4A1EDE7B08FBC5A5AF229@LV2PR12MB5727.namprd12.prod.outlook.com>
Hi Bhadram,
On Wed, Oct 12, 2022 at 04:56:52AM +0000, Bhadram Varka wrote:
> > You should be modeling this as a proper PCS driver and have a 'pcs-handle'
> > property pointing to it in your Device Tree.
> >
> > The configuration you are doing here is probably working the first time you
> > bring-up the network device but I doubt it works across system
> > suspend/resume states where power to the GMAC and PCS is lost, it also
> > begs the question of which mediums this was tested with and whether
> > dynamic switching of speeds and so on is working?
> > --
>
> For Tegra234, there is UPHY lanes control logic inside XPCS IP which is memory-mapped IP (not part of the MAC IP).
> mgbe_uphy_lane_bringup performs UPHY lane bring up here. Here MGBE/XPCS works in XFI mode.
>
> Agree that lane bring down logic is not present interface down/suspend paths. Will update the changes accordingly.
> One more thing is that UPHY lane bring should happen only after the line side link is up. This also will make the changes.
> Please let me know if I miss anything here.
What about the non-UPHY part of the XPCS IP, how does the dwmac-tegra.c
driver control it/see the status it reports?
next prev parent reply other threads:[~2022-11-18 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 11:49 [PATCH net-next v4 RESEND] stmmac: tegra: Add MGBE support Thierry Reding
2022-09-27 9:29 ` Paolo Abeni
2022-09-27 15:33 ` Thierry Reding
2022-09-27 17:23 ` Florian Fainelli
2022-10-12 4:56 ` Bhadram Varka
2022-11-18 9:23 ` Jon Hunter
2022-11-18 13:02 ` Vladimir Oltean [this message]
2022-11-22 7:05 ` Bhadram Varka
2022-11-22 13:26 ` Vladimir Oltean
2022-11-25 4:14 ` Bhadram Varka
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=20221118130216.hxes7yucdl6hn2kl@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ruppala@nvidia.com \
--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