From: Tony Lindgren <tony@atomide.com>
To: arm@kernel.org
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes against v4.5-rc3
Date: Fri, 12 Feb 2016 14:50:18 -0800 [thread overview]
Message-ID: <20160212225018.GA3500@atomide.com> (raw)
The following changes since commit 388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95:
Linux 4.5-rc3 (2016-02-07 15:38:30 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.5/fixes-rc3-v2
for you to fetch changes up to cf26f1137333251f3515dea31f95775b99df0fd5:
ARM: OMAP2+: Fix omap_device for module reload on PM runtime forbid (2016-02-12 08:56:52 -0800)
----------------------------------------------------------------
Few fixes for omaps against v4.5-rc3:
- Improve omap_device error message to tell driver writers what is
wrong after commit 5de85b9d57ab ("PM / runtime: Re-init runtime PM
states at probe error and driver unbind"). There will be also a
handful of driver related fixes also queued separately. But adding
this error message makes it easy to fix any omap_device using
drivers suffering from this issue so I think it's important to
have.
- Also related to commit 5de85b9d57ab discussion, let's fix a bug
where disabling PM runtime via sysfs will also cause the hardware
state to be different from PM runtime state.
- Fix audio clocks for beagle-x15.
- Use wakeup-source instead of gpio-key,wakeup for the new entries
that sneaked in during the merge window.
- Fix a legacy booting vs device tree based booting regression for
n900 where the legacy user space expects to have the device
revision available in /proc/atags also when booted with device
tree.
----------------------------------------------------------------
Ivaylo Dimitrov (1):
ARM: OMAP2+: Set system_rev from ATAGS for n900
Peter Ujfalusi (1):
ARM: DTS: am57xx-beagle-x15: Select SYS_CLK2 for audio clocks
Sudeep Holla (1):
ARM: dts: am335x/am57xx: replace gpio-key,wakeup with wakeup-source property
Tony Lindgren (2):
ARM: OMAP2+: Improve omap_device error for driver writers
ARM: OMAP2+: Fix omap_device for module reload on PM runtime forbid
arch/arm/boot/dts/am335x-shc.dts | 4 ++--
arch/arm/boot/dts/am57xx-beagle-x15.dts | 4 ++++
arch/arm/boot/dts/am57xx-cl-som-am57x.dts | 2 +-
arch/arm/mach-omap2/board-generic.c | 22 +++++++++++++++++++++-
arch/arm/mach-omap2/omap_device.c | 14 +++++++++++++-
5 files changed, 41 insertions(+), 5 deletions(-)
next reply other threads:[~2016-02-12 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 22:50 Tony Lindgren [this message]
2016-02-24 8:05 ` [GIT PULL] omap fixes against v4.5-rc3 Olof Johansson
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=20160212225018.GA3500@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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).