From: Linus Walleij <linus.walleij@linaro.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Michal Miroslaw <mirq-linux@rere.qmqm.pl>,
Florian Fainelli <f.fainelli@gmail.com>,
Paulius Zaleckas <paulius.zaleckas@gmail.com>,
Hans Ulli Kroll <ulli.kroll@googlemail.com>,
Janos Laube <janos.dev@gmail.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH net-next 2/5 v2] net: gemini: Improve connection prints
Date: Sun, 8 Jul 2018 22:47:07 +0200 [thread overview]
Message-ID: <CACRpkdaZ_SgiiHj24EfB55pHNW+siU_n-wofckj-GUHkY_NMqw@mail.gmail.com> (raw)
In-Reply-To: <20180704204047.GD23469@lunn.ch>
On Wed, Jul 4, 2018 at 10:40 PM Andrew Lunn <andrew@lunn.ch> wrote:
> On Wed, Jul 04, 2018 at 08:33:21PM +0200, Linus Walleij wrote:
> > @@ -300,23 +305,26 @@ static void gmac_speed_set(struct net_device *netdev)
> > status.bits.speed = GMAC_SPEED_1000;
> > if (phydev->interface == PHY_INTERFACE_MODE_RGMII)
> > status.bits.mii_rmii = GMAC_PHY_RGMII_1000;
> > - netdev_info(netdev, "connect to RGMII @ 1Gbit\n");
> > + netdev_dbg(netdev, "connect %s to RGMII @ 1Gbit\n",
> > + phydev_name(phydev));
>
> Hi Linus
>
> Since these are netdev_dbg, they will generally never be seen. So
> could you add a call to phy_print_status() at the end of this
> function. That is what most MAC drivers do.
It does:
if (netif_msg_link(port)) {
phy_print_status(phydev);
netdev_info(netdev, "link flow control: %s\n",
phydev->pause
? (phydev->asym_pause ? "tx" : "both")
: (phydev->asym_pause ? "rx" : "none")
);
}
Just not visible in the patch since it was there all the time :D
My new module parameter however, makes that
phy_print_status() actually show up-
I can mention it in the commit message so it's clear.
> > - netdev_info(netdev, "connected to PHY \"%s\"\n",
> > - phydev_name(phy));
> > - phy_attached_print(phy, "phy_id=0x%.8lx, phy_mode=%s\n",
> > - (unsigned long)phy->phy_id,
> > - phy_modes(phy->interface));
> > + netdev_dbg(netdev, "connected to PHY \"%s\"\n",
> > + phydev_name(phy));
> >
>
> It would be nice to call phy_attached_info(), as most other MAC
> drivers do.
OK adding it!
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-07-08 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 18:33 [PATCH net-next 1/5 v2] net: gemini: Look up L3 maxlen from table Linus Walleij
2018-07-04 18:33 ` [PATCH net-next 2/5 v2] net: gemini: Improve connection prints Linus Walleij
2018-07-04 20:40 ` Andrew Lunn
2018-07-08 20:47 ` Linus Walleij [this message]
2018-07-04 18:33 ` [PATCH net-next 3/5 v2] net: gemini: Allow multiple ports to instantiate Linus Walleij
2018-07-04 18:33 ` [PATCH net-next 4/5 v2] net: gemini: Move main init to port Linus Walleij
2018-07-04 18:33 ` [PATCH net-next 5/5 v2] net: gemini: Indicate that we can handle jumboframes Linus Walleij
2018-07-04 20:35 ` Andrew Lunn
2018-07-11 19:10 ` Linus Walleij
2018-07-07 16:14 ` [PATCH net-next 1/5 v2] net: gemini: Look up L3 maxlen from table Michał Mirosław
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=CACRpkdaZ_SgiiHj24EfB55pHNW+siU_n-wofckj-GUHkY_NMqw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=janos.dev@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=netdev@vger.kernel.org \
--cc=paulius.zaleckas@gmail.com \
--cc=ulli.kroll@googlemail.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).