From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP2+: a few more clock/hwmod fixes for v3.15-rc
Date: Fri, 16 May 2014 14:44:02 -0700 [thread overview]
Message-ID: <20140516214401.GN12881@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1405141850410.21921@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [140514 11:52]:
> Hi Tony,
>
> The following changes since commit c9eaa447e77efe77b7fa4c953bd62de8297fd6c5:
>
> Linux 3.15-rc1 (2014-04-13 14:18:35 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git for-v3.15-rc/omap-fixes-b
>
> for you to fetch changes up to 0f9e19ad88eee820f517b85531b555a0fa73e7e4:
>
> ARM: omap5: hwmod_data: Correct IDLEMODE for McPDM (2014-05-14 11:25:58 -0600)
>
> ----------------------------------------------------------------
> Two small OMAP fixes for v3.15-rc. One fixes "slow motion" or
> "choppy" audio playback on OMAP5. The other applies an OMAP3630 fix
> for clock rate setting for camera to other OMAP3 chips.
>
> Basic build, boot, and PM test results are available here:
>
> http://www.pwsan.com/omap/testlogs/prcm-fixes-b-v3.15-rc/20140514112639/
Thanks pulling into omap-for-v3.15/fixes-v3.
Regards,
Tony
> ----------------------------------------------------------------
> Laurent Pinchart (1):
> ARM: OMAP3: clock: Back-propagate rate change from cam_mclk to dpll4_m5 on all OMAP3 platforms
>
> Peter Ujfalusi (1):
> ARM: omap5: hwmod_data: Correct IDLEMODE for McPDM
>
> arch/arm/mach-omap2/cclock3xxx_data.c | 3 ++-
> arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 2 +-
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
prev parent reply other threads:[~2014-05-16 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 18:52 [GIT PULL] ARM: OMAP2+: a few more clock/hwmod fixes for v3.15-rc Paul Walmsley
2014-05-14 19:52 ` Tony Lindgren
2014-05-16 21:44 ` Tony Lindgren [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=20140516214401.GN12881@atomide.com \
--to=tony@atomide.com \
--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).