From: Xulei <B33228-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
Xulei <B33228-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Subject: [PATCH] I2C: Add support for 64bit system.
Date: Mon, 20 Dec 2010 15:37:34 +0800 [thread overview]
Message-ID: <1292830654-7056-1-git-send-email-B33228@freescale.com> (raw)
Currently I2C_MPC supports 32bit system only, then this
modification makes it support 32bit and 64bit system both.
Signed-off-by: Xulei <B33228-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
---
drivers/i2c/busses/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
index 9c6170c..3392f4b 100644
--- a/drivers/i2c/busses/Kconfig
+++ b/drivers/i2c/busses/Kconfig
@@ -422,7 +422,7 @@ config I2C_IXP2000
config I2C_MPC
tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
- depends on PPC32
+ depends on PPC32 || PPC64
help
If you say yes to this option, support will be included for the
built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
--
1.7.0.4
next reply other threads:[~2010-12-20 7:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 7:37 Xulei [this message]
[not found] ` <1292830654-7056-1-git-send-email-B33228-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2010-12-20 14:59 ` [PATCH] I2C: Add support for 64bit system Ben Dooks
[not found] ` <20101220145954.GA1126-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2010-12-21 7:32 ` xulei
2011-03-15 15:44 ` Kumar Gala
[not found] ` <D9BF0938-44B1-4BB8-BF3C-0A9CB44B9CC5-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2011-03-15 15:56 ` Timur Tabi
[not found] ` <AANLkTim0_ttjDPJvx71B-=Ze5dRTrKXfpavx7gxvYr5p-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-15 16:00 ` Kumar Gala
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=1292830654-7056-1-git-send-email-B33228@freescale.com \
--to=b33228-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.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).