public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Koen Kooi <koen@beagleboard.org>
Cc: "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: Fri, 23 Jan 2009 01:52:16 -0800	[thread overview]
Message-ID: <200901230152.17239.david-b@pacbell.net> (raw)
In-Reply-To: <A11F15D6-F171-4D62-ADB9-1508B57037E4@beagleboard.org>

On Friday 23 January 2009, Koen Kooi wrote:
> 
> Op 15 jan 2009, om 20:30 heeft Koen Kooi het volgende geschreven:
> 
> > From: Koen Kooi <koen@beagleboard.org>
> >
> > Changing it to 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>
> 
> Any comments on this patch?

I2C-3 is only used for talking on DVI, right?
Which means EDID ... and maybe DLP/Pico, unless
someone uses it as an I2C adapter.  (Which some
folk hack together on PCs...)

Seems harmless to me, but I'd add a comment
explaining why just 100 MHz.  (The Pico manual
says 400 KHz should work.)

- Dave


> 
> regards,
> 
> Koen
> 
> 
> 
> 
> >
> > ---
> > arch/arm/mach-omap2/board-omap3beagle.c |    2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach- 
> > omap2/board-omap3beagle.c
> > index fe97bab..f279404 100644
> > --- a/arch/arm/mach-omap2/board-omap3beagle.c
> > +++ b/arch/arm/mach-omap2/board-omap3beagle.c
> > @@ -227,7 +227,7 @@ static int __init omap3_beagle_i2c_init(void)
> > #ifdef CONFIG_I2C2_OMAP_BEAGLE
> > 	omap_register_i2c_bus(2, 400, NULL, 0);
> > #endif
> > -	omap_register_i2c_bus(3, 400, NULL, 0);
> > +	omap_register_i2c_bus(3, 100, NULL, 0);
> > 	return 0;
> > }
> >
> > -- 
> > 1.5.6.3

  reply	other threads:[~2009-01-23  9:52 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 [this message]
2009-01-23 10:48     ` Koen Kooi
2009-01-24 15:06       ` Jason Kridner
2009-01-24 20:30         ` David Brownell
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=200901230152.17239.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=beagleboard@googlegroups.com \
    --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