From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: barebox@lists.infradead.org
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>,
Brian Lilly <brian@crystalfontz.com>
Subject: [PATCH] ARM: cfa10036: Add more board ID for boot time detection
Date: Thu, 23 May 2013 16:53:07 +0200 [thread overview]
Message-ID: <1369320787-29172-1-git-send-email-maxime.ripard@free-electrons.com> (raw)
From: Brian Lilly <brian@crystalfontz.com>
As new breakout boards are being developped, we need to add their IDs in
the device detection code, otherwise they will be treated as regular
CFA-10036.
Signed-off-by: Brian Lilly <brian@crystalfontz.com>
Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
---
arch/arm/boards/crystalfontz-cfa10036/hwdetect.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/arch/arm/boards/crystalfontz-cfa10036/hwdetect.c b/arch/arm/boards/crystalfontz-cfa10036/hwdetect.c
index 5eb3ca4..21199d6 100644
--- a/arch/arm/boards/crystalfontz-cfa10036/hwdetect.c
+++ b/arch/arm/boards/crystalfontz-cfa10036/hwdetect.c
@@ -29,6 +29,10 @@ enum board_type {
BOARD_ID_CFA10036 = 0,
BOARD_ID_CFA10037 = 1,
BOARD_ID_CFA10049 = 2,
+ BOARD_ID_CFA10055 = 3,
+ BOARD_ID_CFA10056 = 4,
+ BOARD_ID_CFA10057 = 5,
+ BOARD_ID_CFA10058 = 6,
};
struct cfa_eeprom_info {
@@ -83,6 +87,18 @@ void cfa10036_detect_hw(void)
case BOARD_ID_CFA10049:
board_name = "cfa10049";
break;
+ case BOARD_ID_CFA10055:
+ board_name = "cfa10055";
+ break;
+ case BOARD_ID_CFA10056:
+ board_name = "cfa10056";
+ break;
+ case BOARD_ID_CFA10057:
+ board_name = "cfa10057";
+ break;
+ case BOARD_ID_CFA10058:
+ board_name = "cfa10058";
+ break;
default:
pr_err("Board ID not supported\n");
return;
--
1.8.1.2
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2013-05-23 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 14:53 Maxime Ripard [this message]
2013-05-24 6:34 ` Sascha Hauer
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=1369320787-29172-1-git-send-email-maxime.ripard@free-electrons.com \
--to=maxime.ripard@free-electrons.com \
--cc=barebox@lists.infradead.org \
--cc=brian@crystalfontz.com \
/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