From: mbizon@freebox.fr (Maxime Bizon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] of: DT quirks infrastructure
Date: Thu, 19 Feb 2015 19:22:54 +0100 [thread overview]
Message-ID: <1424370174.13604.18.camel@sakura.staff.proxad.net> (raw)
In-Reply-To: <20150219181218.GA5048@gradator.net>
On Thu, 2015-02-19 at 19:12 +0100, Sylvain Rochet wrote:
> Or use a 1-wire or I2C EEPROM to store your board information.
no, you don't reduce the human error probability.
eeprom needs to be preprogrammed, factory will at some point have a lot
of eeprom with different version, and will potentially equip the wrong
one.
much more error prone than them putting the resistor at the wrong place.
> 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.
I'm not a fan of schemes where not probing something is not a definitive
sign of hardware failure.
--
Maxime
next prev parent reply other threads:[~2015-02-19 18:22 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 14:59 [PATCH 0/4] Device Tree Quirks & the Beaglebone Pantelis Antoniou
2015-02-18 14:59 ` [PATCH 1/4] arm: of: Add a DT quirk method after unflattening Pantelis Antoniou
2015-02-18 14:59 ` [PATCH 2/4] of: DT quirks infrastructure Pantelis Antoniou
2015-02-18 15:41 ` Mark Rutland
2015-02-18 15:53 ` Pantelis Antoniou
2015-02-18 16:32 ` Ludovic Desroches
2015-02-18 16:39 ` Pantelis Antoniou
2015-02-18 16:47 ` Ludovic Desroches
2015-02-18 16:46 ` Matt Porter
2015-02-18 17:31 ` Mark Rutland
2015-02-18 19:32 ` Guenter Roeck
2015-02-19 14:29 ` Pantelis Antoniou
2015-02-19 16:48 ` Frank Rowand
2015-02-19 17:00 ` Pantelis Antoniou
2015-02-19 17:30 ` Frank Rowand
2015-02-19 17:38 ` Pantelis Antoniou
2015-02-19 18:01 ` Maxime Bizon
2015-02-19 18:12 ` Sylvain Rochet
2015-02-19 18:22 ` Maxime Bizon [this message]
2015-02-20 14:21 ` Peter Hurley
2015-02-20 14:35 ` Ludovic Desroches
2015-02-20 15:00 ` Peter Hurley
2015-02-20 15:02 ` Pantelis Antoniou
2015-02-20 15:24 ` Peter Hurley
2015-02-20 15:38 ` Pantelis Antoniou
2015-02-20 16:34 ` Peter Hurley
2015-02-20 16:49 ` Pantelis Antoniou
2015-02-20 17:30 ` Rob Herring
2015-02-20 17:37 ` Pantelis Antoniou
2015-02-23 7:00 ` Ludovic Desroches
2015-02-20 14:38 ` Pantelis Antoniou
2015-02-20 16:47 ` Guenter Roeck
2015-02-20 18:09 ` Peter Hurley
2015-02-20 18:48 ` Guenter Roeck
2015-02-23 7:30 ` Ludovic Desroches
2015-02-20 8:04 ` Ludovic Desroches
2015-02-19 2:08 ` Frank Rowand
2015-02-19 14:41 ` Pantelis Antoniou
2015-02-19 16:40 ` Frank Rowand
2015-02-19 16:51 ` Frank Rowand
2015-02-20 13:23 ` Peter Hurley
2015-02-19 18:01 ` Rob Herring
2015-02-19 18:12 ` Guenter Roeck
2015-02-20 8:16 ` Ludovic Desroches
2015-02-18 14:59 ` [PATCH 3/4] arm: am33xx: DT quirks for am33xx based beaglebone variants Pantelis Antoniou
2015-02-19 18:16 ` Tony Lindgren
2015-02-19 18:28 ` Pantelis Antoniou
2015-02-19 18:36 ` Tony Lindgren
2015-02-19 18:44 ` Pantelis Antoniou
2015-02-23 18:39 ` Peter Hurley
2015-02-23 18:48 ` Pantelis Antoniou
2015-02-19 18:57 ` Guenter Roeck
2015-02-20 16:13 ` Jon Hunter
2015-02-18 14:59 ` [PATCH 4/4] arm: dts: Common Black/White Beaglebone DTS using quirks Pantelis Antoniou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1424370174.13604.18.camel@sakura.staff.proxad.net \
--to=mbizon@freebox.fr \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).