[RFC] two new linux-next trees (SPI and devicetree)

[RFC] two new linux-next trees (SPI and devicetree)

[Grant Likely]

Hi Stephen,

I've got two trees that I'd like to have some linux-next exposure, but
I don't want to step on any toes...

First one is a bunch of SPI patches.  I've made the offer to be SPI
co-maintainer, but I haven't received any feedback yet from either
akpm or dbrownell.  In the mean time, I still have a bunch of SPI
patches (properly signed off and everything) that should have
linux-next exposure before the merge window.  I've put them in the
tree shown in the request-pull output below.

David, akpm, please note:  I'm not intending to ask Linus to pull this
tree, but I do really need some feedback on what you want me to do.
The tree should be properly formed and signed off, so I can ask Linus
to pull from me directly if you wish.

The second one is a bunch of the device tree changes that I want to
give some linux-next exposure as soon as possible.  The tree is
properly formed, but I haven't collected a full set of acks from all
the relevant folks.  Once I get all the acks, I merge the commits into
the next-devicetree branch that you're already pulling.  Ben in
particular is very busy and hasn't had time to review.  They are in
this tree:

  git://git.secretlab.ca/git/linux-2.6 test-devicetree

So, here's the RFC.  I'd *like* to get them into linux-next before
benh gets time to ack them; but there is possibly a greater likelyhood
of breakage.  Can you add them to the end of the queue and just punt
it out if they cause grief?  Do you have any other suggestions?
Should I just put them into next-devicetree and fix it up as I get
acks?  (BTW, I have at least compile tested this tree on 32/64 bit
powerpc, 32/64 bit sparc and microblaze).

Thanks,
g.

The next-spi tree:

The following changes since commit b419148e567728f6af0c3b01965c1cc141e3e13a:
  Linus Torvalds (1):
        Linux 2.6.32-rc6

are available in the git repository at:

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

Albrecht Dreß (5):
      mpc5200/gpt: tiny fix for gpt period limitation
      mpc52xx/wdt: OF property to enable the WDT on boot
      mpc52xx/wdt: merge WDT code into the GPT driver
      mpc52xx/wdt: remove obsolete old WDT implementation

Grant Likely (4):
      spi/mpc5200: Register SPI devices described in device tree
      powerpc/5200: Add mpc5200-spi (non-PSC) device driver
      powerpc/5200: add general purpose timer API for the MPC5200
      mmc: fix missing module license declaration in of_mmc_spi.c

John Bonesio (1):
      powerpc/5200: add LocalPlus bus FIFO device driver

John Linn (1):
      Xilinx: SPI: Fix bits_per_word for transfers

Luotao Fu (3):
      mpc52xx_spi: fix clearing status register
      mpc52xx_spi: add missing mode_bits definition
      mpc52xx_spi: add gpio chipselect

Richard Röjfors (4):
      xilinx_spi: Split into of driver and generic part.
      xilinx_spi: Switch to iomem functions and support little endian.
      xilinx_spi: add support for the DS570 IP.
      xilinx_spi: add a platform driver using the xilinx_spi common module.

Wolfram Sang (3):
      spi/mpc52xx-psc-spi: check for valid PSC
      spi/mpc52xx: replace printk with dev_err
      spi/mpc52xx-spi: minor cleanups

 Documentation/powerpc/dts-bindings/fsl/mpc5200.txt |   17 +-
 arch/powerpc/include/asm/mpc52xx.h                 |   47 ++
 arch/powerpc/kernel/io.c                           |    4 +-
 arch/powerpc/platforms/52xx/Kconfig                |    5 +
 arch/powerpc/platforms/52xx/Makefile               |    1 +
 arch/powerpc/platforms/52xx/mpc52xx_gpt.c          |  428 ++++++++++++++-
 arch/powerpc/platforms/52xx/mpc52xx_lpbfifo.c      |  560 +++++++++++++++++++
 drivers/mmc/host/of_mmc_spi.c                      |    2 +
 drivers/spi/Kconfig                                |   28 +-
 drivers/spi/Makefile                               |    3 +
 drivers/spi/mpc52xx_psc_spi.c                      |   25 +-
 drivers/spi/mpc52xx_spi.c                          |  578 ++++++++++++++++++++
 drivers/spi/xilinx_spi.c                           |  358 ++++++-------
 drivers/spi/xilinx_spi.h                           |   32 ++
 drivers/spi/xilinx_spi_of.c                        |  134 +++++
 drivers/spi/xilinx_spi_pltfm.c                     |  102 ++++
 drivers/watchdog/Kconfig                           |    4 +-
 drivers/watchdog/Makefile                          |    1 -
 drivers/watchdog/mpc5200_wdt.c                     |  293 ----------
 include/linux/spi/xilinx_spi.h                     |   20 +
 20 files changed, 2136 insertions(+), 506 deletions(-)
 create mode 100644 arch/powerpc/platforms/52xx/mpc52xx_lpbfifo.c
 create mode 100644 drivers/spi/mpc52xx_spi.c
 create mode 100644 drivers/spi/xilinx_spi.h
 create mode 100644 drivers/spi/xilinx_spi_of.c
 create mode 100644 drivers/spi/xilinx_spi_pltfm.c
 delete mode 100644 drivers/watchdog/mpc5200_wdt.c
 create mode 100644 include/linux/spi/xilinx_spi.h


On Fri, Nov 20, 2009 at 11:01 AM, Grant Likely
<grant.likely@secretlab.ca> wrote:
> Ping?  Any comments on this?
>
> If I don't hear anything, then I think I'm going to go ahead and push
> out a tree with all the SPI changes I've signed off on and ask sfr to
> add it to his list, just so that I'm sure that they get some
> linux-next exposure before Linus opens the merge window.  I won't
> necessarily ask LInus to pull it, I just want the testing.
>
> Cheers.
> g.
>
> On Fri, Nov 13, 2009 at 5:25 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
>> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
>> ---
>>
>> Hi David, Andrew.
>>
>> David, I know that you haven't had enough time lately to keep on top
>> of the pending SPI patches, so I was wondering if you would like some
>> help?  If you are interested, I'm willing to act as co-maintainer of
>> for the SPI subsystem.
>>
>> Here's what I'm thinking.  Right now all SPI patches are going through
>> the -mm tree and just adding to akpm's burden.  I'd be more than happy
>> to take over the task of actually collecting the acked patches into a
>> git tree, getting them some exposure on linux-next, and asking Linus
>> to pull it during the merge window.  If you ack them, then I'll merge
>> them.
>>
>> I'm also be willing to take responsibility for all powerpc-specific
>> SPI patches so that you don't need to look at them.
>>
>> How does this sound to you?
>>
>> Cheers,
>> g.
>>
>>  MAINTAINERS |    1 +
>>  1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index a1a2ace..2b697cb 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -4937,6 +4937,7 @@ F:        drivers/char/specialix*
>>
>>  SPI SUBSYSTEM
>>  M:     David Brownell <dbrownell@users.sourceforge.net>
>> +M:     Grant Likely <grant.likely@secretlab.ca>
>>  L:     spi-devel-general@lists.sourceforge.net
>>  S:     Maintained
>>  F:     Documentation/spi/
>>
>>
>
>
>
> --
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
>



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

Re: [RFC] two new linux-next trees (SPI and devicetree)

[Andrew Morton]

On Tue, 24 Nov 2009 17:54:27 -0700
Grant Likely <grant.likely@secretlab.ca> wrote:

> I've made the offer to be SPI
> co-maintainer,

OK by me.  Don't break anything.

My current stash:


atmel_spi-fix-dma-addr-calculation-for-len-buffer_size.patch
spi-controller-driver-for-designware-spi-core.patch
spi-add-pci-interface-driver-for-designware-spi-core.patch
spi-add-pci-interface-driver-for-designware-spi-core-fix.patch
spi-controller-driver-for-designware-spi-core-fix.patch
spidev-add-proper-section-markers.patch
spidev-use-declare_bitmap-instead-of-declaring-the-array.patch
spidev-use-declare_bitmap-instead-of-declaring-the-array-checkpatch-fixes.patch
spi-drain-mxc-spi-transfer-buffer-when-probing-device.patch
spi_s3c24xx-add-fiq-pseudo-dma-support.patch


> but I haven't received any feedback yet from either
> akpm or dbrownell.

I haven't heard anything from David in over a month.

Re: [RFC] two new linux-next trees (SPI and devicetree)

[Grant Likely]

On Tue, Nov 24, 2009 at 6:04 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Tue, 24 Nov 2009 17:54:27 -0700
> Grant Likely <grant.likely@secretlab.ca> wrote:
>
>> I've made the offer to be SPI
>> co-maintainer,
>
> OK by me.  Don't break anything.

I'll do my best.

> My current stash:
>
>
> atmel_spi-fix-dma-addr-calculation-for-len-buffer_size.patch
> spi-controller-driver-for-designware-spi-core.patch
> spi-add-pci-interface-driver-for-designware-spi-core.patch
> spi-add-pci-interface-driver-for-designware-spi-core-fix.patch
> spi-controller-driver-for-designware-spi-core-fix.patch
> spidev-add-proper-section-markers.patch
> spidev-use-declare_bitmap-instead-of-declaring-the-array.patch
> spidev-use-declare_bitmap-instead-of-declaring-the-array-checkpatch-fixes.patch
> spi-drain-mxc-spi-transfer-buffer-when-probing-device.patch
> spi_s3c24xx-add-fiq-pseudo-dma-support.patch

Since they're already in your tree, do you mind continuing to shepherd
these (either merge or drop)?  I've gotten a patchwork project set up
on kernel.org for the spi mailing list, so I can easily track things
from this point on.  My gameplan at this point is to try and stay on
top of the things that I'm familiar with (mostly powerpc) and depend
on other people to ack the rest.  I'll pick up anything that a)
doesn't look ugly, b) isn't contested, and c) applies.  :-)

>> but I haven't received any feedback yet from either
>> akpm or dbrownell.
>
> I haven't heard anything from David in over a month.

Okay, shall I go ahead and merge my change to MAINTAINERS through my
tree too then?

g.


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

Re: [RFC] two new linux-next trees (SPI and devicetree)

[Andrew Morton]

On Tue, 24 Nov 2009 18:53:21 -0700 Grant Likely <grant.likely@secretlab.ca> wrote:

> > My current stash:
> >
> >
> > atmel_spi-fix-dma-addr-calculation-for-len-buffer_size.patch
> > spi-controller-driver-for-designware-spi-core.patch
> > spi-add-pci-interface-driver-for-designware-spi-core.patch
> > spi-add-pci-interface-driver-for-designware-spi-core-fix.patch
> > spi-controller-driver-for-designware-spi-core-fix.patch
> > spidev-add-proper-section-markers.patch
> > spidev-use-declare_bitmap-instead-of-declaring-the-array.patch
> > spidev-use-declare_bitmap-instead-of-declaring-the-array-checkpatch-fixes.patch
> > spi-drain-mxc-spi-transfer-buffer-when-probing-device.patch
> > spi_s3c24xx-add-fiq-pseudo-dma-support.patch
> 
> Since they're already in your tree, do you mind continuing to shepherd
> these (either merge or drop)?

Sure.

> > I haven't heard anything from David in over a month.
> 
> Okay, shall I go ahead and merge my change to MAINTAINERS through my
> tree too then?

OK by me.

Re: [RFC] two new linux-next trees (SPI and devicetree)

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 2401 bytes --]

Hi Grant,

On Tue, 24 Nov 2009 17:54:27 -0700 Grant Likely <grant.likely@secretlab.ca> wrote:
>
> First one is a bunch of SPI patches.  I've made the offer to be SPI
> co-maintainer, but I haven't received any feedback yet from either
> akpm or dbrownell.  In the mean time, I still have a bunch of SPI
> patches (properly signed off and everything) that should have
> linux-next exposure before the merge window.  I've put them in the
> tree shown in the request-pull output below.
> 
> David, akpm, please note:  I'm not intending to ask Linus to pull this
> tree, but I do really need some feedback on what you want me to do.
> The tree should be properly formed and signed off, so I can ask Linus
> to pull from me directly if you wish.
> 
>   git://git.secretlab.ca/git/linux-2.6 next-spi

I have added this to linux-next from today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
	Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]