From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot twsi i2c driver
Date: Mon, 06 Jul 2009 08:55:15 +0200 [thread overview]
Message-ID: <4A519FD3.1000806@denx.de> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E202DD54D8BF@SC-VEXCH1.marvell.com>
Hello Prafulla,
Prafulla Wadaskar wrote:
>> -----Original Message-----
>> From: Heiko Schocher [mailto:hs at denx.de]
>> Sent: Monday, July 06, 2009 12:05 PM
>> To: Prafulla Wadaskar
>> Cc: Stefan Roese; Detlev Zundel; Brunck, Holger; U-Boot user list
>> Subject: u-boot twsi i2c driver
>>
>> Hello Prafulla,
>>
>> I have here a ARM926EJS (CPU Core Version FEROCEON_88FR131
>> SOC Family: KIRKWOOD,
>> KW88F6281) based board, with a basic u-boot support, see:
>>
>> http://git.denx.de/?p=u-boot/u-boot-testing.git;a=shortlog;h=r
>> efs/heads/keymile-suen3
>>
>> and we need i2c support for it. I thought to port the Linux
>> driver to u-boot, but Stefan Roese pointed out, that this
>> driver is maybe @marvell in work. So my question is, has
>> marvell such a i2c driver, and if yes, are there any plans to
>> push this driver to mainline?
> Dear Heiko
> Certainly there are plans to develop and push kirkwood i2c driver.
> But the i2c driver is lowest priority for me since it is not blocking any board support.
> There is no active work done so far for this driver?
OK, thanks for this info, so I have to do it.
>> I can help here of course (testing, finishing, pushing to mainline)
> You are most welcomed for this activity, even development too :o)
Ok, if I develop it and have some questions, maybe you get a EMail
from me ;-)
bye
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
prev parent reply other threads:[~2009-07-06 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 6:35 [U-Boot] u-boot twsi i2c driver Heiko Schocher
2009-07-06 6:54 ` Prafulla Wadaskar
2009-07-06 6:55 ` Heiko Schocher [this message]
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=4A519FD3.1000806@denx.de \
--to=hs@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 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.