linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ux500: bump i2c bus speed to 400kHz
Date: Mon, 18 Jun 2012 13:28:34 +0200	[thread overview]
Message-ID: <201206181328.34644.marek.vasut@gmail.com> (raw)
In-Reply-To: <CACRpkdZENi8PCdjmr-Ypey95HjDmEZmpJtqEC49SbwPBCfqr7Q@mail.gmail.com>

Dear Linus Walleij,

> On Mon, Jun 18, 2012 at 1:06 AM, Marek Vasut <marek.vasut@gmail.com> wrote:
> >> From: Linus Walleij <linus.walleij@linaro.org>
> >> 
> >> Some recent discussion revealed inconsistency in the board file
> >> for the MOP500 family. The board can very well do 400kHz on
> >> the I2C busses, so make it do that.
> > 
> > Shouldn't this be controlled by DT?
> 
> They can be controlled by Device Tree after Lee's patch I think.
> 
> > Some of the i2c devices can't do 400kHz.
> 
> Which ones? This works find on the MOP500/HREF board, are you referring
> to Snowball devices?

I had issues with some omnivision cameras, but they were indeed quite old. My 
rant was rather about not closing the door for 100kHz if it was ever needed. But 
like you said above, if it can be changed after applying the aforementioned 
patch, that's ok.

Thanks for clearing this up, sorry for pestering you.

> Yours,
> Linus Walleij

Best regards,
Marek Vasut

      reply	other threads:[~2012-06-18 11:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17 17:57 [PATCH] ARM: ux500: bump i2c bus speed to 400kHz Linus Walleij
2012-06-17 23:06 ` Marek Vasut
2012-06-18  6:01   ` Linus Walleij
2012-06-18 11:28     ` Marek Vasut [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=201206181328.34644.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).