linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap fixes against v3.17-rc2
Date: Tue, 26 Aug 2014 15:14:13 -0700	[thread overview]
Message-ID: <20140826221412.GC16006@atomide.com> (raw)

The following changes since commit 52addcf9d6669fa439387610bc65c92fa0980cef:

  Linux 3.17-rc2 (2014-08-25 15:36:20 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.17/fixes-against-rc2

for you to fetch changes up to 8fd46439e1f5a7f86d76a08733459b74debd9468:

  ARM: dts: omap54xx-clocks: Fix the l3 and l4 clock rates (2014-08-26 13:04:00 -0700)

----------------------------------------------------------------
Fixes for omaps, mostly to revert NAND back to using software ECC
by default as that's what many boards expect. Also fixes for omap5
clocks, PM wake-up events, GPIO interrupt cells for dra7, and few
other minor fixes.

----------------------------------------------------------------
Hans Wennborg (1):
      ARM: OMAP: fix %d confusingly prefixed with 0x in format string

Mark Brown (1):
      ARM: dts: Remove twl6030 clk32g "regulator"

Markus Pargmann (1):
      ARM: OMAP2+: omap_device: remove warning that clk alias already exists

Nishanth Menon (1):
      ARM: dts: DRA7: fix interrupt-cells for GPIO

Roger Quadros (4):
      mtd: nand: omap: Revert to using software ECC by default
      ARM: OMAP2+: GPMC: Support Software ECC scheme via DT
      ARM: dts: omap3430-sdp: Revert to using software ECC for NAND
      mtd: nand: omap: Fix 1-bit Hamming code scheme, omap_calculate_ecc()

Tero Kristo (1):
      ARM: dts: omap54xx-clocks: Fix the l3 and l4 clock rates

Tony Lindgren (2):
      ARM: dts: Enable UART wake-up events for beagleboard
      ARM: OMAP2+: hwmod: Rearm wake-up interrupts for DT when MUSB is idled

 Documentation/devicetree/bindings/mtd/gpmc-nand.txt |  2 +-
 arch/arm/boot/dts/dra7.dtsi                         | 16 ++++++++--------
 arch/arm/boot/dts/omap3-beagle.dts                  |  1 +
 arch/arm/boot/dts/omap3430-sdp.dts                  |  2 +-
 arch/arm/boot/dts/omap54xx-clocks.dtsi              | 16 ++++++++++------
 arch/arm/boot/dts/twl6030.dtsi                      |  4 ----
 arch/arm/mach-omap2/board-flash.c                   |  2 +-
 arch/arm/mach-omap2/gpmc-nand.c                     |  3 ++-
 arch/arm/mach-omap2/gpmc.c                          |  7 +++++--
 arch/arm/mach-omap2/id.c                            |  2 +-
 arch/arm/mach-omap2/omap_device.c                   |  2 +-
 arch/arm/mach-omap2/omap_hwmod.c                    |  4 ++++
 drivers/mtd/nand/omap2.c                            | 16 ++++++++++++----
 include/linux/platform_data/mtd-nand-omap2.h        | 13 +++++++++++--
 14 files changed, 58 insertions(+), 32 deletions(-)

             reply	other threads:[~2014-08-26 22:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 22:14 Tony Lindgren [this message]
2014-08-27 22:11 ` [GIT PULL] omap fixes against v3.17-rc2 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=20140826221412.GC16006@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).