linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/10] net/fec: add mac field into platform data and consolidate fec_get_mac
Date: Wed, 29 Dec 2010 12:10:19 +0100	[thread overview]
Message-ID: <20101229111019.GA14221@pengutronix.de> (raw)
In-Reply-To: <20101229110828.GE19347@freescale.com>

Hi Shawn,

On Wed, Dec 29, 2010 at 07:08:29PM +0800, Shawn Guo wrote:
> On Wed, Dec 29, 2010 at 11:37:58AM +0100, Uwe Kleine-K?nig wrote:
> > On Wed, Dec 29, 2010 at 06:30:15PM +0800, Shawn Guo wrote:
> > > > On Tue, Dec 28, 2010 at 10:55:48PM +0800, Shawn Guo wrote:
> > > [...]
> > > > > +	/*
> > > > > +	 * try to get mac address in following order:
> > > > > +	 *
> > > > > +	 * 1) kernel command line fec_mac=xx:xx:xx...
> > > > > +	 */
> > > > > +	iap = fec_mac_default;
> > > > > +
> > > > > +	/*
> > > > > +	 * 2) from flash or fuse (via platform data)
> > > > > +	 */
> > > > 
> > > > Again, how do you handle the dual MAC case?
> > > > 
> > > For the platform data case, the following patch reads both mac
> > > addresses.
> > > 
> > > [PATCH 09/10] ARM: mx28: read fec mac address from ocotp
> > > 
> > > +static int __init mx28evk_fec_get_mac(void)
> > > +{
> > > +       int i, ret;
> > > +       u32 val;
> > > +
> > > +       /*
> > > +        * OCOTP only stores the last 4 octets for each mac address,
> > > +        * so hard-coding the first two octets as Freescale OUI (00:04:9f)
> > > +        * is needed.
> > > +        */
> > > +       for (i = 0; i < 2; i++) {
> > > +               ret = mxs_read_ocotp(0x20 + i * 0x10, 1, &val);
> > > +               if (ret)
> > > +                       goto error;
> > > +
> > > +               mx28_fec_pdata[i].mac[0] = 0x00;
> > > +               mx28_fec_pdata[i].mac[1] = 0x04;
> > > +               mx28_fec_pdata[i].mac[2] = (val >> 24) & 0xff;
> > > +               mx28_fec_pdata[i].mac[3] = (val >> 16) & 0xff;
> > > +               mx28_fec_pdata[i].mac[4] = (val >> 8) & 0xff;
> > > +               mx28_fec_pdata[i].mac[5] = (val >> 0) & 0xff;
> > uuh.  Is ((val >> 24) & 0xff) supposed to be 0x9f?  If not this might
> > have unwanted effects (practical, don't know about legal ones).
> Yes, it is 0x9f.
Then maybe hardcode that, or at least warn if it's not?

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2010-12-29 11:10 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-28 14:55 [PATCH 00/10] net/fec: add dual fec support for i.MX28 Shawn Guo
2010-12-28 14:55 ` [PATCH 01/10] net/fec: fix MMFR_OP type in fec_enet_mdio_write Shawn Guo
2010-12-28 14:55 ` [PATCH 02/10] net/fec: remove the use of "index" which is legacy Shawn Guo
2010-12-28 14:55 ` [PATCH 03/10] net/fec: add mac field into platform data and consolidate fec_get_mac Shawn Guo
2010-12-29  5:29   ` Greg Ungerer
2010-12-29  9:51     ` Shawn Guo
2010-12-29  6:53   ` Baruch Siach
2010-12-29 10:05     ` Shawn Guo
2010-12-29 10:31       ` Uwe Kleine-König
2010-12-29 11:58         ` Shawn Guo
2010-12-29 12:42           ` Uwe Kleine-König
2010-12-30  2:12             ` Shawn Guo
2010-12-30  8:04               ` Uwe Kleine-König
2010-12-30  4:29       ` Shawn Guo
2010-12-30  5:29         ` Baruch Siach
2010-12-30  7:20           ` Shawn Guo
2010-12-29 10:30     ` Shawn Guo
2010-12-29 10:37       ` Uwe Kleine-König
2010-12-29 11:08         ` Shawn Guo
2010-12-29 11:10           ` Uwe Kleine-König [this message]
2010-12-29 12:00             ` Shawn Guo
2010-12-28 14:55 ` [PATCH 04/10] net/fec: improve pm for better suspend/resume Shawn Guo
2010-12-28 14:55 ` [PATCH 05/10] net/fec: add dual fec support for mx28 Shawn Guo
2010-12-28 14:55 ` [PATCH 06/10] ARM: mx28: update clocks for dual fec support Shawn Guo
2010-12-29  6:57   ` Baruch Siach
2010-12-29  8:10     ` Uwe Kleine-König
2010-12-29 10:14       ` Shawn Guo
2010-12-29 10:28         ` Uwe Kleine-König
2010-12-28 14:55 ` [PATCH 07/10] ARM: mx28: add the second fec device registration Shawn Guo
2010-12-29 10:50   ` Uwe Kleine-König
2010-12-29 12:05     ` Shawn Guo
2010-12-28 14:55 ` [PATCH 08/10] ARM: mxs: add ocotp read function Shawn Guo
2010-12-29 10:47   ` Uwe Kleine-König
2010-12-29 12:08     ` Shawn Guo
2010-12-29 13:47       ` Uwe Kleine-König
2010-12-29 11:22   ` Uwe Kleine-König
2010-12-30  5:50     ` Shawn Guo
2010-12-30  9:15       ` Uwe Kleine-König
2010-12-31  1:43         ` Shawn Guo
2010-12-31 16:11           ` Uwe Kleine-König
2011-01-01 13:03             ` Shawn Guo
2010-12-30  8:41     ` Shawn Guo
2010-12-30  9:02       ` Uwe Kleine-König
2010-12-31  1:46         ` Shawn Guo
2010-12-28 14:55 ` [PATCH 09/10] ARM: mx28: read fec mac address from ocotp Shawn Guo
2010-12-29 10:53   ` Uwe Kleine-König
2010-12-29 12:13     ` Shawn Guo
2010-12-29 12:45       ` Uwe Kleine-König
2010-12-30  2:19         ` Shawn Guo
2010-12-30  8:33         ` Shawn Guo
2010-12-28 14:55 ` [PATCH 10/10] ARM: mxs: add initial pm support Shawn Guo
2010-12-29 10:57   ` Uwe Kleine-König
2010-12-29 12:15     ` Shawn Guo
2010-12-30  8:50     ` Shawn Guo
2010-12-29  5:26 ` [PATCH 00/10] net/fec: add dual fec support for i.MX28 Greg Ungerer

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=20101229111019.GA14221@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).