From: Andrew Lunn <andrew@lunn.ch>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: phy: Ensure the state machine is called when phy is UP
Date: Sat, 16 Apr 2016 00:05:08 +0200 [thread overview]
Message-ID: <20160415220508.GC26665@lunn.ch> (raw)
In-Reply-To: <20160415205613.GE25196@piout.net>
> Trace without my patch:
> libphy: MACB_mii_bus: probed
> macb f8020000.ethernet eth0: Cadence GEM rev 0x00020120 at 0xf8020000 irq 27 (fc:c2:3d:0c:6e:05)
> Micrel KSZ8081 or KSZ8091 f8020000.etherne:01: attached PHY driver [Micrel KSZ8081 or KSZ8091] (mii_bus:phy_addr=f8020000.etherne:01, irq=171)
> Micrel KSZ8081 or KSZ8091 f8020000.etherne:01: PHY state change READY -> READY
> [...]
> Micrel KSZ8081 or KSZ8091 f8020000.etherne:01: PHY state change READY -> READY
Are there some state changes before this? How is it getting to state
READY? It would expect it to start in DOWN, from when the phy device
was created in phy_device_create().
Andrew
next prev parent reply other threads:[~2016-04-15 22:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 19:56 [PATCH] net: phy: Ensure the state machine is called when phy is UP Alexandre Belloni
2016-04-15 20:10 ` Florian Fainelli
2016-04-15 20:56 ` Alexandre Belloni
2016-04-15 22:05 ` Andrew Lunn [this message]
2016-04-15 22:17 ` Alexandre Belloni
2016-04-15 22:23 ` Florian Fainelli
2016-04-18 22:14 ` Alexandre Belloni
2016-04-18 22:17 ` Florian Fainelli
2016-04-18 22:42 ` Alexandre Belloni
2016-04-15 22:30 ` Andrew Lunn
2016-04-15 22:45 ` Alexandre Belloni
2016-09-19 13:15 ` Nicolas Ferre
[not found] <CALnQHM0edN=40GHHwRrOMkQEMsHk2haRoj21bwD2ySfYoLGVvA@mail.gmail.com>
2016-05-17 23:35 ` David Mosberger
2016-05-19 16:31 ` Alexandre Belloni
2016-05-19 17:17 ` David Mosberger
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=20160415220508.GC26665@lunn.ch \
--to=andrew@lunn.ch \
--cc=alexandre.belloni@free-electrons.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.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).