All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Bordug <vbordug@ru.mvista.com>
To: "Charles Krinke" <ckrinke@istor.com>
Cc: Randy Brown <rbrown@istor.com>,
	Chris Carlson <ccarlson@istor.com>,
	Kevin Smith <ksmith@istor.com>,
	linuxppc-embedded@ozlabs.org
Subject: Re: I2C support for 8541
Date: Sat, 13 Oct 2007 17:52:42 +0400	[thread overview]
Message-ID: <20071013175242.040cb371@ru.mvista.com> (raw)
In-Reply-To: <9F3F0A752CAEBE4FA7E906CC2FBFF57C06A1F9@MERCURY.inside.istor.com>

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

Hello Charles,

On Mon, 30 Apr 2007 09:25:28 -0700
Charles Krinke wrote:

> Assuming I have the external IRQ's understood, the next issue is the
> hardware clock on our board with the linux-2.6.17.11 kernel. We are
> using a "DS1338U", which is an I2C RTC.
> 
> I am trying to identify the relevant source for the 8541/8555 I2C
> interface in the source base which reads/writes I2MOD, I2ADD, II2BRG,
> I2COM, I2CER & I2CMR.
> 
> I can find a few references to MPC85xx_CPM_I2C in
> ../syslib/mpc85xx_devices.c, but nothing close in drivers/i2c/...
> 
> Can someone help me understand the completeness of the I2C source in the
> 2.6.17.11 kernel, please.
> 

i2c-mpc.c is prolly responsible to care of 8xxx i2c stuff...

HTH
> Charles Krinke
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-10-13 13:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26 16:10 gcj & PPC405 Patrick Olinet
2007-04-26 18:36 ` IRQ questions & puzzles Charles Krinke
2007-04-27 15:17   ` Charles Krinke
2007-04-27 15:41   ` Jon Loeliger
2007-04-27 16:55     ` How do external irq's get mapped? Charles Krinke
2007-04-27 17:03       ` Sergei Shtylyov
2007-04-27 17:35         ` Jon Loeliger
2007-04-27 17:38         ` Charles Krinke
2007-04-27 17:46           ` Sergei Shtylyov
2007-04-27 18:05             ` Charles Krinke
2007-04-27 18:42               ` Sergei Shtylyov
2007-04-27 19:34                 ` Charles Krinke
2007-04-27 20:58                 ` Charles Krinke
2007-04-27 21:23                   ` Andy Fleming
2007-04-27 22:51                     ` Charles Krinke
2007-04-28  2:30                       ` Zhang Wei-r63237
2007-04-30 16:25                       ` I2C support for 8541 Charles Krinke
2007-05-02 10:43                         ` Clemens Koller
2007-10-13 13:52                         ` Vitaly Bordug [this message]
2007-04-30 14:32                 ` How do external irq's get mapped? Charles Krinke
2007-05-01  0:22                   ` Andy Fleming
2007-05-01 23:11                     ` Charles Krinke
2007-05-02 18:42                       ` Andy Fleming
2007-05-02 22:11                         ` Charles Krinke
2007-05-02 22:43                           ` Andy Fleming
2007-05-03 20:19                             ` Charles Krinke

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=20071013175242.040cb371@ru.mvista.com \
    --to=vbordug@ru.mvista.com \
    --cc=ccarlson@istor.com \
    --cc=ckrinke@istor.com \
    --cc=ksmith@istor.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rbrown@istor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.