linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linuxppc-dev <linuxppc-dev@ozlabs.org>
Cc: Ernst Schwab <eschwab@online.de>, Anatolij Gustschin <agust@denx.de>
Subject: Please pull mpc5xxx support for -next
Date: Wed, 17 Feb 2010 23:37:44 -0700	[thread overview]
Message-ID: <fa686aa41002172237l1d3976avc7f88fd38755ca5e@mail.gmail.com> (raw)

Hi Ben,

Here's all the stuff I've got queued up for 2.6.34.  Mostly mpc5121
support, but some 5200 stuff too.  These commits have already had some
time in linux-next.

Cheers,
g.

The following changes since commit 724e6d3fe8003c3f60bf404bf22e4e331327c596:
  Linus Torvalds (1):
        Linux 2.6.33-rc8

are available in the git repository at:

  git://git.secretlab.ca/git/linux-2.6.git next

Anatolij Gustschin (10):
      powerpc/mpc5121: avoid using arch_initcall for clock init
      powerpc/mpc5121: Add machine restart support
      rtc: Add MPC5121 Real time clock driver
      powerpc/mpc5121: create and register NFC device
      powerpc/mpc5121: update mpc5121ads DTS
      powerpc/mpc5121: Add default config for MPC5121
      serial: mpc52xx_uart: re-enable mpc5121 PSC UART support
      powerpc: doc/dts-bindings: document mpc5121 psc uart dts-bindings
      powerpc/mpc5121: enable support for more PSC UARTs
      powerpc/mpc5121: correct DIU compatible property

Ernst Schwab (1):
      powerpc/of: added documentation for spi chipselects

 .../powerpc/dts-bindings/fsl/mpc5121-psc.txt       |   70 +
 Documentation/powerpc/dts-bindings/fsl/spi.txt     |    7 +
 arch/powerpc/boot/dts/mpc5121ads.dts               |   55 +-
 arch/powerpc/configs/mpc512x_defconfig             | 1694 ++++++++++++++++++++
 arch/powerpc/include/asm/mpc5121.h                 |   24 +
 arch/powerpc/include/asm/mpc52xx_psc.h             |    4 +
 arch/powerpc/platforms/512x/clock.c                |    6 +-
 arch/powerpc/platforms/512x/mpc5121_ads.c          |    3 +-
 arch/powerpc/platforms/512x/mpc5121_generic.c      |    3 +-
 arch/powerpc/platforms/512x/mpc512x.h              |    3 +
 arch/powerpc/platforms/512x/mpc512x_shared.c       |   43 +
 drivers/rtc/Kconfig                                |   10 +
 drivers/rtc/Makefile                               |    1 +
 drivers/rtc/rtc-mpc5121.c                          |  387 +++++
 drivers/serial/mpc52xx_uart.c                      |  251 +++-
 drivers/video/fsl-diu-fb.c                         |    5 +
 16 files changed, 2522 insertions(+), 44 deletions(-)
 create mode 100644 Documentation/powerpc/dts-bindings/fsl/mpc5121-psc.txt
 create mode 100644 arch/powerpc/configs/mpc512x_defconfig
 create mode 100644 arch/powerpc/include/asm/mpc5121.h
 create mode 100644 drivers/rtc/rtc-mpc5121.c


-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

             reply	other threads:[~2010-02-18  6:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18  6:37 Grant Likely [this message]
2010-02-24 15:21 ` Please pull mpc5xxx support for -next Grant Likely

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=fa686aa41002172237l1d3976avc7f88fd38755ca5e@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=agust@denx.de \
    --cc=benh@kernel.crashing.org \
    --cc=eschwab@online.de \
    --cc=linuxppc-dev@ozlabs.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).