From: Marc Reilly <marc@cpdesign.com.au>
To: barebox@lists.infradead.org
Cc: Marc Reilly <marc@susedev1.rulztime>
Subject: [PATCH 3/3] mx35-3stack: fix Pad selection for CONTRAST pin.
Date: Sat, 8 May 2010 12:09:23 +1000 [thread overview]
Message-ID: <1273284563-28645-4-git-send-email-marc@cpdesign.com.au> (raw)
In-Reply-To: <1273284563-28645-3-git-send-email-marc@cpdesign.com.au>
From: Marc Reilly <marc@susedev1.rulztime>
On the Rev2 board the GPIO1_1 triggers an interrupt signal for one of the external devices (can't remember which one off the top of my head).
This change stops the endless interrupts.
---
board/freescale-mx35-3-stack/3stack.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/board/freescale-mx35-3-stack/3stack.c b/board/freescale-mx35-3-stack/3stack.c
index cee0e75..74baae0 100644
--- a/board/freescale-mx35-3-stack/3stack.c
+++ b/board/freescale-mx35-3-stack/3stack.c
@@ -325,10 +325,11 @@ static struct pad_desc f3s_pads[] = {
MX35_PAD_D3_HSYNC__IPU_DISPB_D3_HSYNC,
MX35_PAD_D3_FPSHIFT__IPU_DISPB_D3_CLK,
MX35_PAD_D3_DRDY__IPU_DISPB_D3_DRDY,
- MX35_PAD_CONTRAST__GPIO1_1,
+ MX35_PAD_CONTRAST__IPU_DISPB_CONTR,
MX35_PAD_D3_VSYNC__IPU_DISPB_D3_VSYNC,
MX35_PAD_D3_REV__IPU_DISPB_D3_REV,
MX35_PAD_D3_CLS__IPU_DISPB_D3_CLS,
+
};
static int f3s_console_init(void)
--
1.6.4.2
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-05-08 1:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 2:09 Revision boot params to kernel for ARM and mx35 3 stack fixes Marc Reilly
2010-05-08 2:09 ` [PATCH 1/3] Add passing of revision tag when booting the kernel on ARM platforms Marc Reilly
2010-05-08 2:09 ` [PATCH 2/3] Detect CPU and board revision for freescale-mx35-3-stack and add to boot parameters Marc Reilly
2010-05-08 2:09 ` Marc Reilly [this message]
2010-05-11 7:29 ` 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=1273284563-28645-4-git-send-email-marc@cpdesign.com.au \
--to=marc@cpdesign.com.au \
--cc=barebox@lists.infradead.org \
--cc=marc@susedev1.rulztime \
/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