From: Tom Rix <tom@bumblecow.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH/RFC] Better I2C support for OMAP3
Date: Sat, 31 Oct 2009 15:17:52 -0500 [thread overview]
Message-ID: <4AEC9B70.2040708@bumblecow.com> (raw)
In-Reply-To: <4AEBE94B.3090603@googlemail.com>
Dirk Behme wrote:
> Hugo Vincent wrote:
>> Hi everyone,
>>
>> This patch improves I2C support on OMAP3 platforms, including
>> supporting the second and third I2C controllers (mainline only
>> supports the first controller), and supporting writes where alen=0
>> (i.e. no register address - this was needed for some I2C devices I
>> needed to drive from u-boot).
>>
>> Tested on Gumstix Overo with several I2C devices, on I2C1 and 3.
>>
>> The multi-bus support is mostly from this patch:
>> http://www.beagleboard.org/gitweb/?p=u-boot-arm.git;a=commit;h=52eddcd07c2e7ad61d15bab2cf2d0d21466eaca2
>>
>> Best regards,
>> Hugo Vincent
>>
>> Signed-off-by: Hugo Vincent <hugo.vincent@gmail.com>
>
> Does anybody have an up to date version of this patch? Seems we need
> it for Beagle Zippy, too.
>
Thanks for the pointer.
I have cherry picked this commit and am testing it now.
I will post it once it is done, likely today.
Tom
> Thanks
>
> Dirk
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>
next prev parent reply other threads:[~2009-10-31 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 5:49 [U-Boot] [PATCH/RFC] Better I2C support for OMAP3 Hugo Vincent
2009-06-30 6:22 ` Heiko Schocher
2009-10-31 7:37 ` Dirk Behme
2009-10-31 20:17 ` Tom Rix [this message]
2009-10-31 20:29 ` Dirk Behme
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=4AEC9B70.2040708@bumblecow.com \
--to=tom@bumblecow.com \
--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.