From: horms+renesas@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC Fixes for v3.18
Date: Mon, 17 Nov 2014 11:45:16 +0900 [thread overview]
Message-ID: <cover.1416192055.git.horms+renesas@verge.net.au> (raw)
Hi Olof, Hi Kevin, Hi Arnd,
Please consider these Renesas ARM based SoC fixes for v3.18.
Or alternatively for v3.19 if you feel they are too late for v3.18.
* ARM: shmobile: kzm9g legacy: Set i2c clks_per_count
This problem appears to have been introduced when i2c shmobile support was
added to the sh73a0 by b028f94b76319e1b8 ("ARM: mach-shmobile: sh73a0
i2c_shmobile support.") in v2.6.37.
Without this fix i2c may not operate correctly on the sh73a0/kzm9g.
The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-soc-fixes-for-v3.18
for you to fetch changes up to b207422bb92f17f4f892a9b8737d44b37fece25b:
ARM: shmobile: kzm9g legacy: Set i2c clks_per_count to 2 (2014-11-12 10:38:30 +0900)
----------------------------------------------------------------
Renesas ARM Based SoC Fixes for v3.18
* Set i2c clks_per_count to 2 on kzm9g
----------------------------------------------------------------
Geert Uytterhoeven (1):
ARM: shmobile: kzm9g legacy: Set i2c clks_per_count to 2
arch/arm/mach-shmobile/setup-sh73a0.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
next reply other threads:[~2014-11-17 2:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 2:45 Simon Horman [this message]
2014-11-17 2:45 ` [PATCH] ARM: shmobile: kzm9g legacy: Set i2c clks_per_count to 2 Simon Horman
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=cover.1416192055.git.horms+renesas@verge.net.au \
--to=horms+renesas@verge.net.au \
--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).