From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Fabio Estevam
<fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: [RFC PATCH] mxs: i2c: Implement arbitrary clock speed derivation algorithm
Date: Sun, 10 Feb 2013 14:57:37 +0100 [thread overview]
Message-ID: <20130210135737.GB15546@nekote.pengutronix.de> (raw)
In-Reply-To: <1354297715-12201-1-git-send-email-marex-ynQEQJNshbs@public.gmane.org>
On Fri, Nov 30, 2012 at 06:48:35PM +0100, Marek Vasut wrote:
> This patch drops the i2c timing tables from this driver and instead
> derives the timing based from the requested clock sleep. The timing
> tables were completely wrong anyway when observed on a scope.
>
> This new algorithm is also only derived by using a scope, but it seems
> to produce much more accurate result.
>
> Signed-off-by: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
Since Shawn and I tested it meanwhile, I changed the printouts to
dev_warn and applied to for-next, thanks!
next prev parent reply other threads:[~2013-02-10 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 17:48 [RFC PATCH] mxs: i2c: Implement arbitrary clock speed derivation algorithm Marek Vasut
[not found] ` <1354297715-12201-1-git-send-email-marex-ynQEQJNshbs@public.gmane.org>
2013-01-08 18:14 ` Marek Vasut
2013-01-24 7:25 ` Wolfram Sang
[not found] ` <20130124072555.GD8364-8EAEigeeuNG034pCzgS/Qg7AFbiQbgqx@public.gmane.org>
2013-01-24 12:21 ` Marek Vasut
2013-01-25 6:33 ` Shawn Guo
2013-02-10 13:57 ` Wolfram Sang [this message]
[not found] ` <20130210135737.GB15546-8EAEigeeuNG034pCzgS/Qg7AFbiQbgqx@public.gmane.org>
2013-02-10 14:17 ` Marek Vasut
[not found] ` <201302101517.10571.marex-ynQEQJNshbs@public.gmane.org>
2013-02-10 14:44 ` Wolfram Sang
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=20130210135737.GB15546@nekote.pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marex-ynQEQJNshbs@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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).