From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Valentin Longchamp
<valentin.longchamp-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
Cc: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Subject: Re: [PATCH] i2c: mpc: assign the correct prescaler from SVR
Date: Sun, 15 Mar 2015 11:08:14 +0100 [thread overview]
Message-ID: <20150315100813.GH6770@katana> (raw)
In-Reply-To: <1423583193-28450-1-git-send-email-valentin.longchamp-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
On Tue, Feb 10, 2015 at 04:46:33PM +0100, Valentin Longchamp wrote:
> For the 85xx platforms, the source clock for the i2c-mpc can change from
> one SoC to another. This is documented in the AN2919 "Determining the
> I2C Frequency Divider Ratio for SCL" by Freescale. Not taking this into
> account can lead to the output SCL frequency to by off by an offset. It
> was observed on the P2041 from the QorIQ family.
>
> This patch fixes this problem by setting the prescaler value to the
> appropriate value when required. The SoCs that required a different
> prescaler than 1 are identified by reading out the SVR as discussed in
> http://thread.gmane.org/gmane.linux.drivers.devicetree/94247/focus=20556
>
> Signed-off-by: Valentin Longchamp <valentin.longchamp-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
>
Applied to for-next, thanks!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-03-15 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 15:46 [PATCH] i2c: mpc: assign the correct prescaler from SVR Valentin Longchamp
[not found] ` <1423583193-28450-1-git-send-email-valentin.longchamp-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2015-03-15 10:08 ` Wolfram Sang [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=20150315100813.GH6770@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=valentin.longchamp-SkAbAL50j+5BDgjK7y7TUQ@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).