From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] ARM: dts: imx28-evk: Let i2c0 run at 100kHz
Date: Sat, 25 Oct 2014 20:09:12 +0800 [thread overview]
Message-ID: <20141025120910.GC3648@tiger> (raw)
In-Reply-To: <1413810481-22030-1-git-send-email-fabio.estevam@freescale.com>
On Mon, Oct 20, 2014 at 11:08:01AM -0200, Fabio Estevam wrote:
> Commit 78b81f4666fb ("ARM: dts: imx28-evk: Run I2C0 at 400kHz") caused issues
> when doing the following sequence in loop:
>
> - Boot the kernel
> - Perform audio playback
> - Reboot the system via 'reboot' command
>
> In many times the audio card cannot be probed, which causes playback to fail.
>
> After restoring to the original i2c0 frequency of 100kHz there is no such
> problem anymore.
>
> This reverts commit 78b81f4666fbb22a20b1e63e5baf197ad2e90e88.
>
> Cc: <stable@vger.kernel.org> # 3.16+
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Applied, thanks.
prev parent reply other threads:[~2014-10-25 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 13:08 [PATCH RESEND] ARM: dts: imx28-evk: Let i2c0 run at 100kHz Fabio Estevam
2014-10-25 12:09 ` Shawn Guo [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=20141025120910.GC3648@tiger \
--to=shawn.guo@linaro.org \
--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).