[PATCHv2 3/9] macb: unify at91 and avr32 platform data
Jamie Iles
jamie at jamieiles.com
Thu Mar 17 05:34:03 EDT 2011
On Thu, Mar 17, 2011 at 10:22:53AM +0100, Peter Korsgaard wrote:
> >>>>> "Russell" == Russell King <- ARM Linux <linux at arm.linux.org.uk>> writes:
>
> Hi,
>
> >> That should probably be cleaned up as well then. Sharing platform_data
> >> structures between unrelated drivers seems like quite a mess to me.
>
> Russell> Why should every driver have a separate platform data structure?
> Russell> Is it right to end up with thousands of unique data structures each
> Russell> specific to a particular driver? To me, that sounds like a headache
> Russell> waiting to happen.
>
> Well, the point of the platform data is to provide driver specific
> (E.G. not generic) data to the driver, so in general it will be
> different for different hardware.
>
> The current situation with 2 different structure defination depending on
> arch, macro magic and 1 of these structures also used for a 2nd driver
> isn't optimal.
>
> But ok, I don't feel strongly about struct macb_platform_data also being
> used for the old at91_ether driver, but it shouldn't be called
> eth_platform_data as it isn't really a generic structure.
Ok, I'll rename to macb_platform_data and update at91_ether to use that
with a comment describing that we're sharing the platform data with
macb. At least that gets rid of the preprocessor stuff in board.h for
at91 too.
Jamie
More information about the linux-arm-kernel
mailing list