From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: linuxppc-embedded@ozlabs.org
Cc: Daniel Ng <daniel_ng11@lycos.com>
Subject: Re: i2c support for MPC 8247
Date: Thu, 4 Dec 2008 09:58:28 +0100 [thread overview]
Message-ID: <200812040958.28687.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <loom.20081204T014044-850@post.gmane.org>
Hi Daniel,
On Thursday 04 December 2008 02:49:45 Daniel Ng wrote:
> Hi,
>
> We were successfully using drivers/i2c/busses/i2c-mpc8260.c for I2C support
> on a MPC8247 in Linux 2.6.14.
>
> Now, we are wanting to upgrade our embedded system to Linux 2.6.24.
>
> However, in 2.6.24, the file i2c-mpc8260.c doesn't exist. There is a
> i2c-mpc.c but this doesn't seem to handle the MPC8247. This is because I
> get the following message when I try to access the I2C device:
>
> "/dev/i2c-0: No such device"
>
> Perhaps the i2c-mpc.c driver uses a different device node? There is nothing
> in the i2c-mpc.c file which specifies a particular dev node.
>
> Is I2C supported on the MPC8247 in Linux 2.6.24?
>
> If so, what is the appropriate driver file?
The MPC8247 I2C controller is supported by the i2c-cpm driver, introduced in
2.6.27. It shouldn't be difficult to backport the driver to 2.6.24. Please
note that the driver only supports the powerpc architecture and won't work on
ppc kernels.
Alternatively, you could port the i2c-mpc8260 driver to 2.6.24.
Best regards,
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussee de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
F +32 (2) 387 42 75
next prev parent reply other threads:[~2008-12-04 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 1:49 i2c support for MPC 8247 Daniel Ng
2008-12-04 8:58 ` Laurent Pinchart [this message]
2008-12-07 23:31 ` Daniel Ng
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=200812040958.28687.laurentp@cse-semaphore.com \
--to=laurentp@cse-semaphore.com \
--cc=daniel_ng11@lycos.com \
--cc=linuxppc-embedded@ozlabs.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).