From: David Brownell <david-b@pacbell.net>
To: Jason Kridner <jkridner@beagleboard.org>
Cc: Koen Kooi <koen@beagleboard.org>,
"linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>,
Beagle Board <beagleboard@googlegroups.com>
Subject: Re: [PATCH] ARM: OMAP: board-omap3beagle: set i2c-3 to 100kHz
Date: Sat, 24 Jan 2009 12:30:34 -0800 [thread overview]
Message-ID: <200901241230.34735.david-b@pacbell.net> (raw)
In-Reply-To: <A73F0912-41CB-43F7-BE84-A4B91183B66B@beagleboard.org>
On Saturday 24 January 2009, Jason Kridner wrote:
>
> Given that this port is only used on the DVI port for the BeagleBoard,
> I believe it is appropriate to set it to 100kHz as Koen has done.
That's what I meant to say (kHz not MHZ!) ... except, also add a
comment saying why the (un-obvious) restriction is being made.
Though I did note that since it's a nice level-shifted I2C, some
folk may want to use it for non-DDC purposes [1], where a 100 KHz
limit might not always be wanted.
- Dave
[1] http://www.paintyourdragon.com/uc/i2c/index.html
next prev parent reply other threads:[~2009-01-24 20:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 19:30 [PATCH] ARM: OMAP: board-omap3beagle: set i2c-3 to 100kHz Koen Kooi
2009-01-15 19:54 ` Koen Kooi
2009-01-23 8:00 ` Koen Kooi
2009-01-23 9:52 ` David Brownell
2009-01-23 10:48 ` Koen Kooi
2009-01-24 15:06 ` Jason Kridner
2009-01-24 20:30 ` David Brownell [this message]
2009-01-24 21:09 ` Koen Kooi
2009-01-24 22:33 ` David Brownell
[not found] ` <bd7b27490901250616q2363c5b4wf422d32831bd3638@mail.gmail.com>
2009-01-27 9:18 ` No audio support for BeagleBoard in Latest GIT tree? ndno72-omap
2009-01-27 9:38 ` Peter Ujfalusi
2009-01-27 10:35 ` ndno72-omap
2009-01-27 10:51 ` Peter Ujfalusi
2009-01-27 11:08 ` Arun KS
2009-01-27 9:55 ` Jarkko Nikula
2009-01-27 10:37 ` ndno72-omap
-- strict thread matches above, loose matches on Subject: below --
2009-01-15 19:34 [PATCH] ARM: OMAP: board-omap3beagle: set i2c-3 to 100kHz Koen Kooi
2009-01-15 19:43 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=200901241230.34735.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=beagleboard@googlegroups.com \
--cc=jkridner@beagleboard.org \
--cc=koen@beagleboard.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox