LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Alan Bennett" <embedded@akb.net>
To: "Scott Wood" <scottwood@freescale.com>, linuxppc-dev@ozlabs.org
Subject: I2C on mpc8248 / device tree
Date: Tue, 13 Nov 2007 16:39:05 -0700	[thread overview]
Message-ID: <bfa0697f0711131539n228f9f21q7b2acc896499b80d@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]

I've got four devices on i2c that I need to read.  Simple thermal and
voltage monitors.  I2c works fine in uboot, and now I'm trying to get things
to work in linux.

In the kernel .config I enable
  I2C
and
  I2C_MPC

During the platform boot code:
I init the IO ports for i2c, (same as ep8248e code)
    {3, 14, CPM_PIN_INPUT | CPM_PIN_SECONDARY},
    {3, 15, CPM_PIN_INPUT | CPM_PIN_SECONDARY},

__Do I need to configure a brg for the i2c along with the other devices ?
i.e. cpm2_clk_setup ?


Next, I'm sure my device tree needs work, but my first stab adds i2c onto
the SOC @ 11860  (immr+11860= I2c mode register) and interrupt 1.
       soc@e0000000 {
               ...
               cpm@119c0 {
               ...
               i2c@11860 {
                   device_type = "i2c";
                   compatible = "fsl-i2c";
                   reg = <11860 18>;
                   interrupts = <1 3>;
                   interrupt-parent = <&PIC>;
               };

After Cleaning up these routines and descriptions, would I be expected to
continue using the /dev/i2c- entries?

-Alan

[-- Attachment #2: Type: text/html, Size: 2054 bytes --]

             reply	other threads:[~2007-11-13 23:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 23:39 Alan Bennett [this message]
2007-11-13 23:56 ` I2C on mpc8248 / device tree Jon Smirl
2007-11-14 15:31   ` Alan Bennett
2007-11-14 16:20     ` Kumar Gala
2007-11-14 17:49       ` Alan Bennett
2007-11-14 17:56         ` Scott Wood
2007-11-14 19:26           ` Jon Smirl
2007-11-14 20:21             ` Kumar Gala
2007-11-14  7:17 ` 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=bfa0697f0711131539n228f9f21q7b2acc896499b80d@mail.gmail.com \
    --to=embedded@akb.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    /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