From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3]: arm:kirkwood Define kirkwood phy address magic number
Date: Thu, 20 Aug 2009 13:47:07 +0200 [thread overview]
Message-ID: <20090820134707.7ab2dbbb@marrow.netinsight.se> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E202E39159B4@SC-VEXCH1.marvell.com>
On Thu, 20 Aug 2009 02:40:48 -0700
Prafulla Wadaskar <prafulla@marvell.com> wrote:
> >
> > +#define KIRKWOOD_PHY_ADR_REQUEST 0xee
> define this in header file
>
> Basically this is needed in drivers/net/phy/mv88e61xx.c for multi chip support
> in this case we need to define this in include/miiphy.h.
> which conflicts with other phy address definition, that's why not done earlier
>
> It makes more sense to add APIs miiphy_read/write_phyadr to miiutils
But is this really general functionality? miiphy.h is something I
suppose should be generic between phys and not contain device-specific
things like this.
Perhaps we should revive the patches that move out the phy
initialization from sheevaplug.c and place the define and some
implementation there?
// Simon
next prev parent reply other threads:[~2009-08-20 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 8:11 [U-Boot] [PATCH 0/3]: arm:Kirkwood network driver fixes Simon Kagstrom
2009-08-20 8:12 ` [U-Boot] [PATCH 1/3]: arm:kirkwood Define kirkwood phy address magic number Simon Kagstrom
2009-08-20 9:40 ` Prafulla Wadaskar
2009-08-20 11:47 ` Simon Kagstrom [this message]
2009-08-21 3:20 ` Prafulla Wadaskar
2009-08-21 8:52 ` Simon Kagstrom
2009-08-21 16:59 ` Ben Warren
2009-08-20 8:13 ` [U-Boot] [PATCH 2/3]: Wait for the link to come up on kirkwood network init Simon Kagstrom
2009-08-20 8:14 ` [U-Boot] [PATCH 3/3] [repost]: arm: kirkwood: See to it that sent data is 8-byte aligned Simon Kagstrom
2009-08-20 9:25 ` Prafulla Wadaskar
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=20090820134707.7ab2dbbb@marrow.netinsight.se \
--to=simon.kagstrom@netinsight.net \
--cc=u-boot@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.