From: Anders Darander <anders.darander@datarespons.se>
To: Jiri Pirko <jpirko@redhat.com>
Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>,
"David S. Miller" <davem@davemloft.net>,
Erik Waling <erik.waling@konftel.com>,
Patrick McHardy <kaber@trash.net>,
Grant Likely <grant.likely@secretlab.ca>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MACB: Set PHY address in kernel parameters
Date: Wed, 31 Mar 2010 12:11:20 +0200 [thread overview]
Message-ID: <20100331101120.GJ4837@datarespons.se> (raw)
In-Reply-To: <20100331100313.GA4053@psychotron.lab.eng.brq.redhat.com>
* Jiri Pirko <jpirko@redhat.com> [100331 12:03]:
> Wed, Mar 31, 2010 at 09:51:42AM CEST, anders.darander@gmail.com wrote:
> >
> >- phydev = phy_find_first(bp->mii_bus);
> >+ if (phy_addr >= PHY_MAX_ADDRESS)
> >+ phydev = phy_find_first(bp->mii_bus);
> >+ else
> >+ phydev = bp->mii_bus->phy_map[phy_addr];
> >+
> > if (!phydev) {
> > printk (KERN_ERR "%s: no PHY found\n", dev->name);
> > return -1;
>
> This is really ugly :( Should be done differently, more general. I've been
> thinking about this for a while. Maybe the solution is to integrate the switch
> into DSA subsystem. See net/dsa. Not sure though...
A more general solution is always welcome...
However, although I've not tested it, I think that Marc Kleine-Budde
came up with the correct solution. That was using phy_mask, and set it
up in the *eth_data structure in the board setup code.
Thus, it seems that the needed functionality is readily available.
(Working in the embedded field, I've no problem with defining HW-related
things in the board setup code, as opposite of having it dynamically
defined).
Regards,
Anders
prev parent reply other threads:[~2010-03-31 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 7:51 [PATCH] MACB: Set PHY address in kernel parameters Anders Darander
2010-03-31 8:28 ` Patrick McHardy
2010-03-31 8:50 ` Anders Darander
2010-03-31 10:03 ` Jiri Pirko
2010-03-31 10:11 ` Anders Darander [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=20100331101120.GJ4837@datarespons.se \
--to=anders.darander@datarespons.se \
--cc=davem@davemloft.net \
--cc=erik.waling@konftel.com \
--cc=grant.likely@secretlab.ca \
--cc=hskinnemoen@atmel.com \
--cc=jpirko@redhat.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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