[lkml]   [2011]   [Mar]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[RFC PATCH 0/5] OMAP2+ / Panda implementation for async platform_data
The following series uses the

- proposed platform support for async platform data

- proposed usb core and usbnet use of async platform data

in order to configure onboard USB <-> Ethernet bridge wired up on
Panda boards. The same issue exists on Beagle XM boards which also
have an onboard soldered USB <-> Ethernet bridge terminating on a
normal onboard RJ45 socket.

With the above support, these patches extend platform_data led
control of onboard assets to include those probed by USB bus

In the Panda case, it uses the platform data introduced to usbnet
to enforce the selection of eth%d address since the board definition
file knows it is a permaently wired onboard connection using RJ45
jack, and to define the MAC address from unique CPU DIE ID data.


Andy Green (5):
USBNET: SMSC95XX: if mac set in platform data no need for random one
OMAP2+: Set onboard Ethernet MAC address using unique CPU ID data
OMAP2+:Common CPU DIE ID reading code reads wrong registers for OMAP4430
OMAP2+: add cpu id register to MAC address helper
OMAP2+: Panda introduce async platform data definition

drivers/net/usb/smsc95xx.c | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)


 \ /
  Last update: 2011-03-12 23:53    [W:0.103 / U:3.208 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site