From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 V2] MXS: Set I2C timing registers for mxs-i2c
Date: Tue, 10 Jul 2012 17:13:31 +0200 [thread overview]
Message-ID: <201207101713.31498.marex@denx.de> (raw)
In-Reply-To: <20120710140911.GK20456@pengutronix.de>
Dear Robert Schwebel,
> On Mon, Jul 09, 2012 at 05:58:22PM +0200, Marek Vasut wrote:
> > > The kernel should work for all users, not only for the majority, so:
> > > Better safe than sorry.
> > >
> > > Also, defaults should make the system work. Tuning can be done later by
> > > somebody who understands what is needed.
> > >
> > > And frankly, this attitude which made you add a potential regression is
> > > worrisome. I'd suggest to give stability a higher priority.
> >
> > I believe you misunderstood my intention. Setting it to 400kHz was done
> > because it's what most people will use, therefore avoiding duplication
> > (most of the board files will override this setting now). All right,
> > your sane defaults here can be applied, I won't argue.
>
> I think all I2C chips support 100 kHz, but only selected ones support
> 400 kHz.
Yes, this is correct. And I never argued about this.
But anyway, V3 patch is out, let's cut this discussion short.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-07-10 15:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 6:09 [PATCH 1/2 V2] MXS: Set I2C timing registers for mxs-i2c Marek Vasut
2012-07-06 6:09 ` [PATCH 2/2 V2] MXS: Implement DMA support into mxs-i2c Marek Vasut
2012-07-09 10:53 ` [PATCH 1/2 V2] MXS: Set I2C timing registers for mxs-i2c Wolfram Sang
2012-07-09 11:07 ` Marek Vasut
2012-07-09 12:05 ` Wolfram Sang
2012-07-09 15:58 ` Marek Vasut
2012-07-10 14:09 ` Robert Schwebel
2012-07-10 15:13 ` Marek Vasut [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-08 18:54 Marek Vasut
2012-06-09 4:15 ` Shubhrajyoti Datta
2012-06-09 10:34 ` Marek Vasut
2012-06-09 10:53 ` Sascha Hauer
2012-06-09 11:11 ` Marek Vasut
2012-06-09 11:25 ` Sascha Hauer
2012-06-09 11:40 ` Marek Vasut
2012-06-09 12:46 ` Shubhrajyoti Datta
2012-06-09 13:10 ` Marek Vasut
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=201207101713.31498.marex@denx.de \
--to=marex@denx.de \
--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).