From: Kumar Gala <kumar.gala@freescale.com>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: [PATCH][RFC] OCP support for MPC107 and relatives
Date: Mon, 14 Jun 2004 08:43:55 -0500 [thread overview]
Message-ID: <E1775B59-BE08-11D8-8344-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <1087207803.7360.83.camel@newt>
On Jun 14, 2004, at 5:10 AM, Adrian Cox wrote:
> The attached patch is a start at adding the internal peripherals of the
> MPC107/MPC8240/MPC8245 to the OCP bus. I've used thus in the 2.6 port
> of
> my MPC107 I2C driver, which follows shortly. I intend to use this for
> the DMA controller later, once I decide what device ID to give it.
> I'm a little uncertain about OCP device IDs. Should there be a separate
> I2C device ID for each different I2C programming interface from the
> same
> vendor? Motorola have already given us two separate implementations on
> PowerPC.
Take a look at the driver i2c-mpc.c in
bk://ppc.bkbits.net/linuxppc-2.4. We have been trying to write a
single driver to handle as many variations of one device as possible.
Our expectation is that one driver should hopefully be able to handle
10x, 824x, 85xx. (and some future device families 83xx & 86xx).
I've also pushed support for 85xx infrastructure into linuxppc-2.5
which includes support for some config options for Motorola/Freescale
OCP. These changes are expected to make it into linux-2.5 after 2.6.7
is released.
We are looking at adding OCP support for 824x as well for the I2C
driver.
I will make sure to look over the code and provide any feedback I've
got.
- kumar
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-14 13:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 10:10 [PATCH][RFC] OCP support for MPC107 and relatives Adrian Cox
2004-06-14 10:23 ` [PATCH][RFC] I2C " Adrian Cox
2004-06-14 11:01 ` Stefan Nickl
2004-06-14 11:37 ` Adrian Cox
2004-06-14 13:01 ` Stefan Nickl
2004-06-14 13:24 ` Adrian Cox
2004-06-14 13:39 ` Kumar Gala
2004-06-14 14:38 ` Pantelis Antoniou
2004-06-14 13:43 ` Kumar Gala [this message]
2004-06-14 13:59 ` [PATCH][RFC] OCP " Kumar Gala
2004-06-14 14:47 ` Adrian Cox
2004-06-14 15:46 ` Matt Porter
2004-06-15 0:38 ` Kumar Gala
2004-06-14 17:05 ` Mark A. Greer
2004-06-15 8:10 ` Adrian Cox
2004-06-15 17:33 ` Mark A. Greer
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=E1775B59-BE08-11D8-8344-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=adrian@humboldt.co.uk \
--cc=linuxppc-embedded@lists.linuxppc.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).