From: Heiko Schocher <hs@denx.de>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, vbordug@ru.mvista.com, akpm@osdl.org,
jeff@garzik.org, wd@denx.de
Subject: Re: [PATCH] net, fixed phy: make BUSID configurable
Date: Mon, 05 Dec 2011 11:21:09 +0100 [thread overview]
Message-ID: <4EDC9B15.8020302@denx.de> (raw)
In-Reply-To: <20111204.132321.9566486322084069.davem@davemloft.net>
Hello David,
David Miller wrote:
> From: Heiko Schocher <hs@denx.de>
> Date: Sun, 4 Dec 2011 10:37:24 +0100
>
>> Signed-off-by: Heiko Schocher <hs@denx.de>
>
> Give me a break.
>
> You can't submit a change like this with essentially an
> empty commit message.
Uh, yes, sorry!
> Why in the world does this ever need to be configurable?
> Are there alternative (and much better) ways to deal with
> whatever problem this patch solves?
>
> You've presented no information about why you need to make this
> change, and more importantly why no viable alternatives exist
> to solve your problem.
On a am1808 based board porting to current kernel, I have connected
a KSZ8864RMN switch and using the drivers/net/ethernet/ti/davinci_emac.c
driver. To the switch I have always 100/FULL connection and so
I decided to use the fixed PHY driver. But the busid 0 is used
from the drivers/net/ethernet/ti/davinci_emac.c driver, and the
fixed PHY driver is fix at busid 0 ...
Looking in the drivers/net/ethernet/ti/davinci_emac.c in emac_dev_open()
there is the possibility if no priv->phy_id is defined through
plattform code, to use a fixed 100/FULL speed and duplex settings ...
which would fix my needs ...
But code did not reach this, because first a:
if (!priv->phy_id) {
struct device *phy;
phy = bus_find_device(&mdio_bus_type, NULL, NULL,
match_first_device);
if (phy)
priv->phy_id = dev_name(phy);
}
is checked ... maybe it is better to fix this here by removing this
"if (!priv->phy_id) {" and do not use the fixed PHY driver?
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
prev parent reply other threads:[~2011-12-05 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 9:37 [PATCH] net, fixed phy: make BUSID configurable Heiko Schocher
2011-12-04 18:23 ` David Miller
2011-12-05 10:21 ` Heiko Schocher [this message]
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=4EDC9B15.8020302@denx.de \
--to=hs@denx.de \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=vbordug@ru.mvista.com \
--cc=wd@denx.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).