public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <mike@compulab.co.il>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, mike.rapoport@gmail.com
Subject: Re: [PATCH 0/5] New mux code for 34xx
Date: Sun, 01 Nov 2009 12:29:53 +0200	[thread overview]
Message-ID: <4AED6321.7020002@compulab.co.il> (raw)
In-Reply-To: <20091029203124.11843.89983.stgit@localhost>

Hi Tony,

Tony Lindgren wrote:
> Hi all,
> 
> Here's an initial version of the new mux code to play with.
> Big thanks to Paul & Benoit for the 34xx mux data!

I've tried your patches, they seem to work just fine on CM-T35.

> To try out the new code, compile a kernel with CONFIG_OMAP_MUX
> and CONFIG_DEBUG_FS and these patches. The series is also
> availabe in the l-o git in mux branch.

[ snip ]

> 
> Comments welcome as always.

There are some comments on patches 2 (Add new style pin multiplexing code for
omap3) and 3 (Add new style pin multiplexing data for 34xx). No nitpicking for
now, but checkpatch.pl is unhappy with the patchset :)


> Regards,
> 
> Tony
> 
> 
> ---
> 
> Mike Rapoport (1):
>       omap2: mux: intoduce omap_mux_{read,write}
> 
> Tony Lindgren (4):
>       omap: mux: Add debugfs support for new mux code
>       omap: mux: Add new style init functions to omap3 board-*.c files
>       omap: mux: Add new style pin multiplexing data for 34xx
>       omap: mux: Add new style pin multiplexing code for omap3
> 
> 
>  arch/arm/mach-omap2/Makefile             |    4 
>  arch/arm/mach-omap2/board-3430sdp.c      |    9 
>  arch/arm/mach-omap2/board-cm-t35.c       |    9 
>  arch/arm/mach-omap2/board-ldp.c          |    9 
>  arch/arm/mach-omap2/board-omap3beagle.c  |    9 
>  arch/arm/mach-omap2/board-omap3evm.c     |    9 
>  arch/arm/mach-omap2/board-omap3pandora.c |    9 
>  arch/arm/mach-omap2/board-overo.c        |    8 
>  arch/arm/mach-omap2/board-rx51.c         |   10 
>  arch/arm/mach-omap2/board-zoom2.c        |    8 
>  arch/arm/mach-omap2/mux.c                |  424 ++++++++
>  arch/arm/mach-omap2/mux.h                |  127 ++
>  arch/arm/mach-omap2/mux34xx.c            | 1552 ++++++++++++++++++++++++++++++
>  arch/arm/mach-omap2/mux34xx.h            |  352 +++++++
>  14 files changed, 2533 insertions(+), 6 deletions(-)
>  create mode 100644 arch/arm/mach-omap2/mux.h
>  create mode 100644 arch/arm/mach-omap2/mux34xx.c
>  create mode 100644 arch/arm/mach-omap2/mux34xx.h
> 

-- 
Sincerely yours,
Mike.


  parent reply	other threads:[~2009-11-01 10:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29 20:35 [PATCH 0/5] New mux code for 34xx Tony Lindgren
2009-10-29 20:36 ` [PATCH 1/5] omap2: mux: intoduce omap_mux_{read,write} Tony Lindgren
2009-10-29 20:36 ` [PATCH 2/5] omap: mux: Add new style pin multiplexing code for omap3 Tony Lindgren
2009-11-01 10:30   ` Mike Rapoport
2009-11-02 18:54     ` Tony Lindgren
2009-11-03  6:56       ` Mike Rapoport
2009-10-29 20:36 ` [PATCH 3/5] omap: mux: Add new style pin multiplexing data for 34xx Tony Lindgren
2009-11-01 10:30   ` Mike Rapoport
2009-11-02 19:10     ` Tony Lindgren
2009-11-03  7:10       ` Mike Rapoport
2009-11-03 16:43         ` Tony Lindgren
2009-11-03 22:55           ` [PATCH] omap: mux: Replace omap_cfg_reg() with new style signal or gpio functions (Re: [PATCH 3/5] omap: mux: Add new style pin multiplexing data for 34xx) Tony Lindgren
2009-11-04  7:14           ` [PATCH 3/5] omap: mux: Add new style pin multiplexing data for 34xx Mike Rapoport
2009-11-10 22:37             ` Tony Lindgren
2009-11-11  8:23               ` Mike Rapoport
2009-10-29 20:36 ` [PATCH 4/5] omap: mux: Add new style init functions to omap3 board-*.c files Tony Lindgren
2009-10-29 20:36 ` [PATCH 5/5] omap: mux: Add debugfs support for new mux code Tony Lindgren
2009-10-29 21:19 ` [PATCH 0/5] New mux code for 34xx Mike Rapoport
2009-10-29 21:59   ` Tony Lindgren
2009-11-01 10:29 ` Mike Rapoport [this message]
2009-11-02 18:56   ` Tony Lindgren
2009-11-03  6:42     ` Mike Rapoport
2009-11-03 16:46       ` Tony Lindgren

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=4AED6321.7020002@compulab.co.il \
    --to=mike@compulab.co.il \
    --cc=linux-omap@vger.kernel.org \
    --cc=mike.rapoport@gmail.com \
    --cc=tony@atomide.com \
    /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