[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150219181218.GA5048@gradator.net>
Date: Thu, 19 Feb 2015 19:12:18 +0100
From: Sylvain Rochet <gradator@...dator.net>
To: Maxime Bizon <mbizon@...ebox.fr>
Cc: Pantelis Antoniou <pantelis.antoniou@...sulko.com>,
Mark Rutland <mark.rutland@....com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Tony Lindgren <tony@...mide.com>,
Koen Kooi <koen@...inion.thruhere.net>,
Nicolas Ferre <nicolas.ferre@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Grant Likely <grant.likely@...retlab.ca>,
Ludovic Desroches <ludovic.desroches@...el.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Matt Porter <matt.porter@...aro.org>, frowand.list@...il.com,
Guenter Roeck <linux@...ck-us.net>
Subject: Re: [PATCH 2/4] of: DT quirks infrastructure
Hello,
On Thu, Feb 19, 2015 at 07:01:59PM +0100, Maxime Bizon wrote:
> On Thu, 2015-02-19 at 19:38 +0200, Pantelis Antoniou wrote:
>
> > Having to boot and tweak the bootloader settings to select the correct
> > dtb (even if it’s present on the flash medium) takes time and is
> > error-prone.
>
> Dedicate a set of GPIO for board/PCB revision detection (it only costs a
> few resistors connected to VCC or GND), then use that information to
> choose the correct DTB.
Or use a 1-wire or I2C EEPROM to store your board information.
Or, even better, if you have an I2C device, just chose a different
address on each board for this device and then probe I2C devices in your
boot loader until you found one you are looking for, this way, you don't
need spare GPIO at all. You don't even need to populate the same I2C
device on all boards, you can actually probe anything.
Sylvain
Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists