From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/5] non-urgent omap fixes for v4.11 merge window
Date: Tue, 24 Jan 2017 10:05:14 -0800 [thread overview]
Message-ID: <pull-1485274191-192300> (raw)
The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77:
Linux 4.10-rc1 (2016-12-25 16:13:08 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.11/fixes-not-urgent-signed
for you to fetch changes up to 631af44c10f9430163296626c6134db16a4f51fb:
ARM: OMAP3: Fix SoC detection of OMAP36/37 Family (2017-01-20 10:13:06 -0800)
----------------------------------------------------------------
Non-urgent fixes for omaps for v4.11 merge window. These all are
fixes for things that have never worked or have been broken for
a long time and nobody noticed:
- Fix omap3 off mode pull defines
- Allow multiple pdata quirks instead of just one
- Fix am335x and dm814x scm syscon to probe children too
- Fix compatible for ti81xx to allow use with 8250_omap as well
- Fix 8250_omap on omap5 by adding HWMOD_SWSUP_SIDLE_ACT flag
- Fix SoC detection for omap36/37 SoCs
----------------------------------------------------------------
Adam Ford (1):
ARM: OMAP3: Fix SoC detection of OMAP36/37 Family
Tony Lindgren (4):
ARM: dts: Fix omap3 off mode pull defines
ARM: OMAP2+: Fix init for multiple quirks for the same SoC
ARM: dts: Fix am335x and dm814x scm syscon to probe children
ARM: dts: Fix compatible for ti81xx uarts for 8250
Vignesh R (1):
ARM: OMAP5: Add HWMOD_SWSUP_SIDLE_ACT flag for UART
arch/arm/boot/dts/am33xx.dtsi | 3 ++-
arch/arm/boot/dts/dm814x.dtsi | 9 +++++----
arch/arm/boot/dts/dm816x.dtsi | 6 +++---
arch/arm/mach-omap2/id.c | 10 +++++++++-
arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 8 ++++++--
arch/arm/mach-omap2/pdata-quirks.c | 1 -
include/dt-bindings/pinctrl/omap.h | 4 ++--
7 files changed, 27 insertions(+), 14 deletions(-)
next reply other threads:[~2017-01-24 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 18:05 Tony Lindgren [this message]
2017-01-24 18:05 ` [GIT PULL 2/5] omap soc changes for v4.11 merge window Tony Lindgren
2017-01-24 18:05 ` [GIT PULL 3/5] omap wkup_m3_ipc driver " Tony Lindgren
2017-01-24 18:05 ` [GIT PULL 4/5] omap device tree " Tony Lindgren
2017-01-24 18:05 ` [GIT PULL 5/5] omap defconfig " Tony Lindgren
[not found] ` <58879774.9c41620a.96bae.6ba2SMTPIN_ADDED_BROKEN@mx.google.com>
2017-01-30 1:15 ` [GIT PULL 2/5] omap soc " Olof Johansson
[not found] ` <58879775.06c9620a.ef45c.5d29SMTPIN_ADDED_BROKEN@mx.google.com>
2017-01-30 1:16 ` [GIT PULL 3/5] omap wkup_m3_ipc driver " Olof Johansson
[not found] ` <58879776.d8cc620a.90442.3f64SMTPIN_ADDED_BROKEN@mx.google.com>
2017-01-30 1:17 ` [GIT PULL 4/5] omap device tree " Olof Johansson
[not found] ` <58879776.0ada620a.ff7f0.43b9SMTPIN_ADDED_BROKEN@mx.google.com>
2017-01-30 1:18 ` [GIT PULL 5/5] omap defconfig " Olof Johansson
[not found] <58879773.4111630a.b973d.9b1cSMTPIN_ADDED_BROKEN@mx.google.com>
2017-01-30 1:15 ` [GIT PULL 1/5] non-urgent omap fixes " 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=pull-1485274191-192300 \
--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).