From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.225]) by ozlabs.org (Postfix) with ESMTP id 29D3CDDDF4 for ; Thu, 15 Nov 2007 04:49:14 +1100 (EST) Received: by nz-out-0506.google.com with SMTP id i1so233625nzh for ; Wed, 14 Nov 2007 09:49:13 -0800 (PST) Message-ID: Date: Wed, 14 Nov 2007 10:49:13 -0700 From: "Alan Bennett" Sender: alan@akb.net To: "Kumar Gala" Subject: Re: I2C on mpc8248 / device tree In-Reply-To: <9AADA2CE-A7F0-4C88-BFCF-08D6C8DC09E0@kernel.crashing.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1065_18226079.1195062553079" References: <9e4733910711131556r23a38780q39baf15d85c0bd85@mail.gmail.com> <9AADA2CE-A7F0-4C88-BFCF-08D6C8DC09E0@kernel.crashing.org> Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , ------=_Part_1065_18226079.1195062553079 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline ERk. So if I needed to read values from four i2c devices (raw access would be fine) and I need to get this working in a few days, how would you suggest I proceed? Kernel = 2.6.23+. Do I need to start from scratch? Start by using Jon's patch (or are the 5200 i2c and the cpm2 i2c completely incompatible?) What about other cpm2/i2c threads - Did they ever complete? 1) On Wednesday, November 23, 2005 8:01 AM Kumar Gala wrote: >* Can we rename the driver from mpc8260 -> cpm2. The driver should work* >* on any device that has a "CPM2" which includes a number of MPC82xx* >* and MPC85xx processors . So calling it and its config options, etc* >* MPC8260 is going to be confusing to users.* [PATCH] I2C: Add I2C Bus support for MPC with CPM2. On 11/14/07, Kumar Gala wrote: > > The patch is orthogonal to your issue. > > There is NOT a driver in the kernel tree for the i2c on CPM2 based > parts like the 8248 (from what I can tell). > > - k > > On Nov 14, 2007, at 9:31 AM, Alan Bennett wrote: > > > Does this patch support the cpm2 as well? > > > > I get conflicting thoughts looking over the latest postings. > > > > -Alan > > > > > > On 11/13/07, Jon Smirl < jonsmirl@gmail.com> wrote:I am working on > > a patch for i2c and device tree. I attached the current version. > > > > DTC entry looks like this. > > > > i2c@3d40 { > > compatible = "mpc5200b-i2c","mpc5200- > > i2c","fsl-i2c"; > > reg = <3d40 40>; > > interrupts = <2 10 0>; > > interrupt-parent = <&mpc5200_pic>; > > fsl5200-clocking; > > > > rtc@51f { > > compatible = "epson,rtc8564"; > > reg = <51>; > > }; > > }; > > > > > > > > -- > > Jon Smirl > > jonsmirl@gmail.com > > > > > > _______________________________________________ > > Linuxppc-dev mailing list > > Linuxppc-dev@ozlabs.org > > https://ozlabs.org/mailman/listinfo/linuxppc-dev > > ------=_Part_1065_18226079.1195062553079 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline ERk.
  So if I needed to read values from four i2c devices (raw access would be fine) and I need to get this working in a few days, how would you suggest I proceed?  Kernel = 2.6.23+. 

  Do I need to start from scratch?

  Start by using Jon's patch  (or are the 5200 i2c and the cpm2 i2c completely incompatible?) 

  What about other cpm2/i2c threads - Did they ever complete?
     1) On Wednesday, November 23, 2005 8:01 AM Kumar Gala wrote: > Can we rename the driver from mpc8260 -> cpm2. The driver should work > on any device that has a "CPM2" which includes a number of MPC82xx > and MPC85xx processors. So calling it and its config options, etc > MPC8260 is going to be confusing to users. [PATCH] I2C: Add I2C Bus support for MPC with CPM2.


 


On 11/14/07, Kumar Gala <galak@kernel.crashing.org> wrote:
The patch is orthogonal to your issue.

There is NOT a driver in the kernel tree for the i2c on CPM2 based
parts like the 8248 (from what I can tell).

- k

On Nov 14, 2007, at 9:31 AM, Alan Bennett wrote:

> Does this patch support the cpm2 as well?
>
> I get conflicting thoughts looking over the latest postings.
>
> -Alan
>
>
> On 11/13/07, Jon Smirl < jonsmirl@gmail.com> wrote:I am working on
> a patch for i2c and device tree. I attached the current version.
>
> DTC entry looks like this.
>
>                 i2c@3d40 {
>                         compatible = "mpc5200b-i2c","mpc5200-
> i2c","fsl-i2c";
>                         reg = <3d40 40>;
>                         interrupts = <2 10 0>;
>                         interrupt-parent = <&mpc5200_pic>;
>                         fsl5200-clocking;
>
>                         rtc@51f {
>                                 compatible = "epson,rtc8564";
>                                 reg = <51>;
>                         };
>                 };
>
>
>
> --
> Jon Smirl
> jonsmirl@gmail.com
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev


------=_Part_1065_18226079.1195062553079--