From: Juergen Beisert <jbe@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH/master] ARM/MXS: pull-up and bitkeeper must be handled differently
Date: Fri, 20 Jul 2012 15:34:49 +0200 [thread overview]
Message-ID: <201207201534.50481.jbe@pengutronix.de> (raw)
Since commit 2f6b1f7690640f571f8e72fc2f2564acb2e13778 the pull-up and
bitkeeper handling for i.MX23/28 is correct. But now it is important to
distinguish these pin features as their programmed bit values are different.
With this patch the bitkeeper and pull-up enable/disable bits are now handled
separately.
Signed-off-by: Juergen Beisert <jbe@pengutronix.de>
diff --git a/arch/arm/mach-mxs/include/mach/iomux-imx23.h b/arch/arm/mach-mxs/include/mach/iomux-imx23.h
index 7b2883c..82362d7 100644
--- a/arch/arm/mach-mxs/include/mach/iomux-imx23.h
+++ b/arch/arm/mach-mxs/include/mach/iomux-imx23.h
@@ -22,13 +22,14 @@
* ^^^^____ Bit offset
* ^^________ Function
* ^__________ Drive strength feature present
- * ^___________ Pull up / bit keeper present
+ * ^___________ Pull up present
* ^^____________ Drive strength setting
* ^______________ Pull up / bit keeper setting
* ^_______________ Voltage select present
* ^________________ Voltage selection
* ^____________________ direction if enabled as GPIO (1 = output)
* ^_____________________ initial output value if enabled as GPIO and configured as output
+ * ^______________________ Bit keeper present
*/
#ifndef __ASM_MACH_IOMUX_H
#define __ASM_MACH_IOMUX_H
@@ -63,7 +64,7 @@
/* control pad's pull up / bit keeper feature */
#define PE (1 << 10)
-#define BK (1 << 11) /* FIXME useful to distinguish? */
+#define BK (1 << 21)
#define PE_PRESENT(x) (!!((x) & PE))
#define BK_PRESENT(x) (!!((x) & BK))
#define PULLUP(x) ((x) << 13)
diff --git a/arch/arm/mach-mxs/include/mach/iomux-imx28.h b/arch/arm/mach-mxs/include/mach/iomux-imx28.h
index ea1c3d8..82918cf 100644
--- a/arch/arm/mach-mxs/include/mach/iomux-imx28.h
+++ b/arch/arm/mach-mxs/include/mach/iomux-imx28.h
@@ -16,7 +16,7 @@
* ^^^______ Register Number
* ^^_________ Function
* ^___________ Drive strength feature present
- * ^____________ Pull up / bit keeper present
+ * ^____________ Pull up present
* ^^_____________ Drive strength setting
* ^_______________ Pull up / bit keeper setting
* ^________________ Voltage select present
@@ -24,6 +24,7 @@
* ^_____________________ direction if enabled as GPIO (1 = output)
* ^______________________ initial output value if enabled as GPIO
* and configured as output
+ * ^_______________________ Bit keeper present
*/
#ifndef __MACH_IOMUX_IMX28_H
#define __MACH_IOMUX_IMX28_H
@@ -57,7 +58,7 @@
/* control pad's pull up / bit keeper feature */
#define PE (1 << 11)
-#define BK (1 << 11) /* FIXME useful to distinguish? */
+#define BK (1 << 22)
#define PE_PRESENT(x) (!!((x) & PE))
#define BK_PRESENT(x) (!!((x) & BK))
#define PULLUP(x) ((x) << 14)
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2012-07-20 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 13:34 Juergen Beisert [this message]
2012-07-23 20:11 ` 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=201207201534.50481.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=barebox@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