From: Tony Lindgren <tony@atomide.com>
To: Koen Kooi <k.kooi@student.utwente.nl>
Cc: "linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v2] board-omap3beagle: set i2c-3 to 100kHz
Date: Fri, 20 Feb 2009 08:25:00 -0800 [thread overview]
Message-ID: <20090220162459.GL7414@atomide.com> (raw)
In-Reply-To: <20090206222255.GJ10721@atomide.com>
* Tony Lindgren <tony@atomide.com> [090206 14:56]:
> * Koen Kooi <k.kooi@student.utwente.nl> [090206 06:16]:
> >
> > Op 4 feb 2009, om 20:58 heeft Koen Kooi het volgende geschreven:
> >
> >>
> >> Op 25 jan 2009, om 13:04 heeft David Brownell het volgende geschreven:
> >>
> >>> On Sunday 25 January 2009, Koen Kooi wrote:
> >>>> From: Koen Kooi <koen@beagleboard.org>
> >>>>
> >>>> Changing it do 100kHz is needed to make more devices works
> >>>> properly. Controlling the TI DLP Pico projector[1] doesn't work
> >>>> properly at 400kHz, 100kHz and lower work fine. EDID readout is
> >>>> unaffected by this change.
> >>>>
> >>>> [1] http://focus.ti.com/dlpdmd/docs/dlpdiscovery.tsp?sectionId=60&tabId=2234
> >>>>
> >>>> Signed-off-by: Koen Kooi <koen@beagleboard.org>
> >>>
> >>> Acked-by: David Brownell <dbrownell@users.sourceforge.net>
> >>
> >> ping
> >
> > Any more changes needed before this can go in?
>
> Just few more days, I'll need to get my upstream queues ready..
> Otherwise I'll forget to apply it somewhere :)
OK, adding to omap-fixes and pushing to linux-omap.
Tony
next prev parent reply other threads:[~2009-02-20 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 8:46 [PATCH v2] board-omap3beagle: set i2c-3 to 100kHz Koen Kooi
2009-01-25 12:04 ` David Brownell
2009-02-04 19:58 ` Koen Kooi
2009-02-06 14:15 ` Koen Kooi
2009-02-06 22:23 ` Tony Lindgren
2009-02-20 16:25 ` Tony Lindgren [this message]
2009-02-20 16:59 ` Koen Kooi
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=20090220162459.GL7414@atomide.com \
--to=tony@atomide.com \
--cc=k.kooi@student.utwente.nl \
--cc=linux-omap@vger.kernel.org \
/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.