[U-Boot] [PATCH 3/3] omap4: splitting padconfs into common, 4430 and 4460

[Aneesh V <aneesh@ti.com>]

Hi Ricardo,

On Thursday 22 September 2011 01:47 AM, Ricardo Salveti de Araujo wrote:
> Not all padconfs are the same between 4430 and 4460, so instead of
> working around this with an if, we should have an specific padconf
> structure for both chips (like handling the differences between the LEDs
> GPIOs and TPS).

I was actually wondering whether I was right in keeping some mux data
in the SoC directory and was thinking of moving it back to the board
dir. Strictly speaking mux data is board specific and I have already
encountered a customer board that uses a different UART for traces. So
essential, non_essential etc completely depends on the boards not SoCs.
So, I am inclined to move it back to the board directories, because
that will be more maintainable when more and more boards get added with
conflicting mux definitions.

So, the arrays should be rather padconf_panda_common,
padconf_4460panda, padconf_4430panda etc. and they should be all in
their respective board directories.

What do you think?

br,
Aneesh