From: Andrew Lunn <andrew@lunn.ch>
To: Duan Andy <fugang.duan@freescale.com>
Cc: Lothar Wa?mann <LW@KARO-electronics.de>,
"David S. Miller" <davem@davemloft.net>,
Fabio Estevam <Fabio.Estevam@freescale.com>,
Kevin Hao <haokexin@gmail.com>,
Lucas Stach <l.stach@pengutronix.de>,
Philippe Reynes <tremyfr@gmail.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Stefan Agner <stefan@agner.ch>
Subject: Re: [PATCH] net: fec: fix enet_out clock handling
Date: Sat, 28 Nov 2015 17:43:37 +0100 [thread overview]
Message-ID: <20151128164337.GF32356@lunn.ch> (raw)
In-Reply-To: <BN3PR0301MB1219C4D8E1B09F1AE27E18FAF5020@BN3PR0301MB1219.namprd03.prod.outlook.com>
> When MAC is not ready with clocks disabled, it is not necessary to
> supply clock for PHY. In fact, PHY also is not ready, why does it
> need clock ?
How about the case of the "PHY" is actually a switch? You can use the
MDIO bus separate from the MAC, you can configure the switch while the
MAC is down, etc. Packets can be flowing in and out of switch ports,
while the MAC is down. You only need the MAC up when the host wants to
send packets.
Andrew
next prev parent reply other threads:[~2015-11-28 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 13:39 [PATCH] net: fec: fix enet_out clock handling Lothar Waßmann
2015-11-27 15:16 ` Michael Heimpold
2015-11-28 13:13 ` Duan Andy
2015-11-28 16:43 ` Andrew Lunn [this message]
2015-11-30 1:46 ` Duan Andy
2015-11-30 1:58 ` Andrew Lunn
2015-11-30 6:56 ` Lothar Waßmann
2015-11-30 7:31 ` Duan Andy
2015-11-30 2:07 ` Andrew Lunn
2015-11-30 5:37 ` Lothar Waßmann
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=20151128164337.GF32356@lunn.ch \
--to=andrew@lunn.ch \
--cc=Fabio.Estevam@freescale.com \
--cc=LW@KARO-electronics.de \
--cc=davem@davemloft.net \
--cc=fugang.duan@freescale.com \
--cc=haokexin@gmail.com \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=stefan@agner.ch \
--cc=tremyfr@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).