linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: andy.green@linaro.org (Andy Green)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] OMAP2+: add cpu id register to MAC address helper
Date: Fri, 29 Jun 2012 17:13:27 +0800	[thread overview]
Message-ID: <4FED71B7.80308@linaro.org> (raw)
In-Reply-To: <20120629090515.GA4202@atomide.com>

On 06/29/12 17:05, the mail apparently from Tony Lindgren included:
> * Andy Green <andy.green@linaro.org> [120628 22:59]:
>>
>> Introduce a generic helper function that can generate a valid MAC
>> address using data from the OMAP unique CPU ID register.
> ...
>
>> --- a/arch/arm/mach-omap2/id.c
>> +++ b/arch/arm/mach-omap2/id.c
>> @@ -530,3 +530,42 @@ void __init omap2_set_globals_tap(struct omap_globals *omap2_globals)
>>   	else
>>   		tap_prod_id = 0x0208;
>>   }
>> +
>> +/*
>> + * this uses the unique per-cpu info from the cpu fuses set at factory to
>> + * generate a 6-byte MAC address.  Two bits in the generated code are used
>> + * to elaborate the generated address into four, so it can be used on multiple
>> + * network interfaces.
>> + */
>> +
>> +void omap2_die_id_to_ethernet_mac(u8 *mac, int subtype)
>> +{
>> +	struct omap_die_id odi;
>> +	u32 tap = read_tap_reg(OMAP_TAP_IDCODE);
>> +
>> +	omap_get_die_id(&odi);
>> +
>> +	mac[0] = odi.id_2;
>> +	mac[1] = odi.id_2 >> 8;
>> +	mac[2] = odi.id_1;
>> +	mac[3] = odi.id_1 >> 8;
>> +	mac[4] = odi.id_1 >> 16;
>> +	mac[5] = odi.id_1 >> 24;
>> +
>> +	/* XOR other chip-specific data with ID */
>> +
>> +	tap ^= odi.id_3;
>> +
>> +	mac[0] ^= tap;
>> +	mac[1] ^= tap >> 8;
>> +	mac[2] ^= tap >> 16;
>> +	mac[3] ^= tap >> 24;
>> +
>> +	/* allow four MACs from this same basic data */
>> +
>> +	mac[1] = (mac[1] & ~0xc0) | ((subtype & 3) << 6);
>> +
>> +	/* mark it as not multicast, and outside official 80211 MAC namespace */
>> +
>> +	mac[0] = (mac[0] & ~1) | 2;
>> +}
>
> Let's just make this omap_die_id_to_ethernet_mac, no need to keep the
> omap2 naming there as this should not conflict with any omap1 stuff.

Okay, will do thanks.

-Andy

-- 
Andy Green | TI Landing Team Leader
Linaro.org ? Open source software for ARM SoCs | Follow Linaro
http://facebook.com/pages/Linaro/155974581091106  - 
http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog

  reply	other threads:[~2012-06-29  9:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29  5:55 [PATCH 0/3] Add ability to set defaultless network device MAC addresses to deterministic computed locally administered values Andy Green
2012-06-29  5:55 ` [PATCH 1/3] OMAP2+: add cpu id register to MAC address helper Andy Green
2012-06-29  9:05   ` Tony Lindgren
2012-06-29  9:13     ` Andy Green [this message]
2012-06-29  5:55 ` [PATCH 2/3] OMAP2+ devices add mac address allocation register api Andy Green
2012-06-29  8:51   ` Arnd Bergmann
2012-06-29  9:03     ` Andy Green
2012-06-29  9:40   ` Tony Lindgren
2012-06-29 10:07     ` Andy Green
2012-06-29 12:03       ` Tony Lindgren
2012-06-29 13:45         ` Arnd Bergmann
2012-06-29 13:55           ` Tony Lindgren
2012-06-29 13:59             ` Andy Green
2012-06-29 14:33             ` Arnd Bergmann
2012-06-29 14:52               ` Tony Lindgren
2012-06-29 15:05                 ` Arnd Bergmann
2012-07-01  8:58                   ` Tony Lindgren
2012-07-02  7:15                     ` Arnd Bergmann
2012-07-02 10:51                       ` Tony Lindgren
2012-06-29 14:03           ` Andy Green
2012-06-29 14:38             ` Arnd Bergmann
2012-06-29  5:55 ` [PATCH 3/3] OMAP4 PANDA register ethernet and wlan for automatic mac allocation Andy Green
2012-06-29 11:55   ` Tony Lindgren
2012-06-29  8:50 ` [PATCH 0/3] Add ability to set defaultless network device MAC addresses to deterministic computed locally administered values Arnd Bergmann

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=4FED71B7.80308@linaro.org \
    --to=andy.green@linaro.org \
    --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).