[patch 1/9] efikamx: read board id

[Amit Kucheria]

On 10 Oct 20, Arnaud Patard wrote:
> Amit Kucheria <amit.kucheria at linaro.org> writes:
> 
> > On 10 Oct 19, Matt Sealey wrote:
> >> On Tue, Oct 19, 2010 at 4:15 PM, Sascha Hauer <s.hauer at pengutronix.de> wrote:
> >> > On Tue, Oct 19, 2010 at 10:42:54PM +0200, Arnaud Patard wrote:
> >> >> read board id value from the GPIO3_16/17/11
> >> >>
> >> >>
> >> >> +/*   PCBID2  PCBID1 PCBID0  STATE
> >> >> +     1       1      1    ER1:rev1.1
> >> >> +     1       1      0    ER2:rev1.2
> >> >> +     1       0      1    ER3:rev1.3
> >> >> +     1       0      0    ER4:rev1.4
> >> >> +*/
> >> >> +static void __init mx51_efikamx_board_id(void)
> >> >> +{
> >> >> +     int id;
> >> >> +
> >> >> +     /* things are taking time to settle */
> >> >> +     msleep(500);
> >> >
> >> > Is it really necessary to delay the boot process such a long time?
> >> 
> >> Yes. On older boards the PCBID pins are pulled high by IOMUX settings
> >> (a pulldown on the board on newer revisions will keep it down). IOMUX
> >> and GPIO stuff takes a little while to settle in, so if you do it
> >> immediately, it will return some freakish values based on random GPIO
> >> setup (it may be high, low, or none of the above at any point before
> >> the pad setting kicks in).
> >
> > Then perhaps do this only for the older boards?
> 
> How can you detect older boards without looking at board id pins ? :)

You don't. I was suggesting a config option that doesn't penalise those with
non-buggy boards....

> >
> > So by default there is no delay, but when a (new) config option is enabled,
> > delay boot.
> 
> I don't think it's a good idea. This would mean that the same kernel
> can't run on old and new boards. Also, there's no way to easily know
> which board you have (I don't consider opening the box is an easy way)
> so it's likely that someone will get this wrong sooner or later.

...but you're right. If one has to support a variety of boards on single
kernel, this won't work.

/Amit