From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] I2C Register
Date: Fri, 5 Feb 2010 09:32:06 +0100 [thread overview]
Message-ID: <201002050932.06859.sr@denx.de> (raw)
In-Reply-To: <539104.18893.qm@web46114.mail.sp1.yahoo.com>
Ronny,
On Friday 05 February 2010 09:22:59 Ronny D wrote:
> My Customized ppc4xx I2C interface provides two I2C controllers. so i think
> we will have to use Hard I2C ( because i will have to modify the same in
> kernel too).
Yes, this would be best. But if you can map the I2C pins via pin multiplexing
to some GPIO pins, you could use the existing soft_i2c driver.
> Shall i used the same i2c driver from u-boot by modifying the register or
> write my own driver for it?
I have no idea, since I don't have any infos about your I2C controller. I
don't know if it is similar to any of the supported controllers. So you need
to check this yourself.
> i found the ppc4xx_i2c structure, but can i get the information about the
> each parameter or register used in that structure.
From the PPC4xx user manuals. For example the PPC440EPx. You can download
those manual from the AppliedMicro (AMCC) web site.
Cheers,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
next prev parent reply other threads:[~2010-02-05 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 14:30 [U-Boot] I2C Register Ronny D
2010-02-04 14:53 ` Stefan Roese
2010-02-05 5:43 ` Ronny D
2010-02-05 5:59 ` Stefan Roese
2010-02-05 6:41 ` Ronny D
2010-02-05 7:24 ` Stefan Roese
2010-02-05 8:22 ` Ronny D
2010-02-05 8:32 ` Stefan Roese [this message]
2010-03-02 5:50 ` [U-Boot] U-boot compilation for little endian Ronny D
2010-03-02 7:53 ` Wolfgang Denk
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=201002050932.06859.sr@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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