From: Heiner Kallweit <hkallweit1@gmail.com>
To: "Marek Behún" <marek.behun@nic.cz>
Cc: Andrew Lunn <andrew@lunn.ch>,
netdev@vger.kernel.org,
Sebastian Reichel <sebastian.reichel@collabora.co.uk>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next v2 1/1] net: dsa: fix fixed-link port registration
Date: Sun, 11 Aug 2019 13:35:20 +0200 [thread overview]
Message-ID: <91cd70df-c856-4c7e-7ebb-c01519fb13d2@gmail.com> (raw)
In-Reply-To: <20190811033910.GL30120@lunn.ch>
On 11.08.2019 05:39, Andrew Lunn wrote:
> On Sun, Aug 11, 2019 at 05:18:57AM +0200, Marek Behún wrote:
>> Commit 88d6272acaaa ("net: phy: avoid unneeded MDIO reads in
>> genphy_read_status") broke fixed link DSA port registration in
>> dsa_port_fixed_link_register_of: the genphy_read_status does not do what
>> it is supposed to and the following adjust_link is given wrong
>> parameters.
>
> Hi Marek
>
> Which parameters are incorrect?
>
> In fixed_phy.c, __fixed_phy_register() there is:
>
> /* propagate the fixed link values to struct phy_device */
> phy->link = status->link;
> if (status->link) {
> phy->speed = status->speed;
> phy->duplex = status->duplex;
> phy->pause = status->pause;
> phy->asym_pause = status->asym_pause;
> }
>
> Are we not initialising something? Or is the initialisation done here
> getting reset sometime afterwards?
>
In addition to Andrew's question:
We talk about this DT config: armada-385-turris-omnia.dts ?
Which kernel version are you using?
> Thanks
> Andrew
>
Heiner
next prev parent reply other threads:[~2019-08-11 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-11 3:18 [PATCH net-next v2 1/1] net: dsa: fix fixed-link port registration Marek Behún
2019-08-11 3:39 ` Andrew Lunn
2019-08-11 11:35 ` Heiner Kallweit [this message]
2019-08-11 14:04 ` Marek Behun
2019-08-11 15:08 ` Marek Behun
2019-08-11 15:16 ` Vladimir Oltean
2019-08-11 16:21 ` Marek Behun
2019-08-11 15:18 ` Andrew Lunn
2019-08-11 9:54 ` Sergei Shtylyov
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=91cd70df-c856-4c7e-7ebb-c01519fb13d2@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=marek.behun@nic.cz \
--cc=netdev@vger.kernel.org \
--cc=sebastian.reichel@collabora.co.uk \
--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).