linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Keystone SOC updates for v3.13
Date: Tue, 8 Oct 2013 17:29:00 -0400	[thread overview]
Message-ID: <1381267740-31874-1-git-send-email-santosh.shilimkar@ti.com> (raw)

Olof,

Please pull below Keystone SOC updates for v3.13. As discussed on irc, the
pull request is build on top of v3.13-rc4 because of dependent commit
c2b9e974{dma/Kconfig: Make TI_EDMA select TI_PRIV_EDMA}. The pull request
carries Kconfig update patch {dma: Allow TI_EDMA selectable for ARCH_KEYSTONE}
with Vinod Koul's ack as per alignment on the mailing list[1]. The clock
driver support is already applied by Mike to his 3.13 clk-next [2]

The following changes since commit ef887009524c3631d804a2587ec204c4ff61a5b8:

  ARM: keystone: Enable I2C and SPI bus support (2013-10-08 15:37:41 -0400)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git tags/keystone-soc-for-arm-soc

for you to fetch changes up to ef887009524c3631d804a2587ec204c4ff61a5b8:

  ARM: keystone: Enable I2C and SPI bus support (2013-10-08 15:37:41 -0400)

----------------------------------------------------------------
SOC updates for Keystone II devices:

- Clock tree support
- Clock management support using PM core
- Keystone config update for EMDA with ack from Vinod
- Enable SPI and I2C drivers

----------------------------------------------------------------

Santosh Shilimkar (9):
  ARM: dts: keystone: Add clock tree data to devicetree
  ARM: dts: keystone: Add clock phandle to UART nodes
  ARM: keystone: Enable clock drivers
  ARM: keystone: add PM bus support for clock management
  ARM: dts: keystone: Add i2c device nodes
  ARM: dts: keystone: Add the SPI nodes
  dma: Allow TI_EDMA selectable for ARCH_KEYSTONE
  ARM: keystone: Select TI_EDMA to be able to enable SPI driver
  ARM: keystone: Enable I2C and SPI bus support

 arch/arm/boot/dts/keystone-clocks.dtsi |  821 ++++++++++++++++++++++++++++++++
 arch/arm/boot/dts/keystone.dts         |   63 ++-
 arch/arm/configs/keystone_defconfig    |    2 +
 arch/arm/mach-keystone/Kconfig         |    2 +
 drivers/bus/Makefile                   |    2 +
 drivers/bus/keystone_pm_bus.c          |   70 +++
 drivers/dma/Kconfig                    |    2 +-
 7 files changed, 959 insertions(+), 3 deletions(-)
 create mode 100644 arch/arm/boot/dts/keystone-clocks.dtsi
 create mode 100644 drivers/bus/keystone_pm_bus.c

Regards,
Santosh

[1] http://www.spinics.net/lists/arm-kernel/msg277174.html
[2] http://www.spinics.net/lists/arm-kernel/msg277924.html
-- 
1.7.9.5

             reply	other threads:[~2013-10-08 21:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 21:29 Santosh Shilimkar [this message]
2013-10-10 22:28 ` [GIT PULL] Keystone SOC updates for v3.13 Kevin Hilman
2013-10-10 23:30   ` Santosh Shilimkar
2013-10-11 19:51     ` Kevin Hilman

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=1381267740-31874-1-git-send-email-santosh.shilimkar@ti.com \
    --to=santosh.shilimkar@ti.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).