All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Mike Rapoport <mike.rapoport@gmail.com>
Cc: Mike Rapoport <mike@compulab.co.il>, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/5] New mux code for 34xx
Date: Tue, 3 Nov 2009 08:46:46 -0800	[thread overview]
Message-ID: <20091103164646.GF8981@atomide.com> (raw)
In-Reply-To: <f870da180911022242p2ddbd8f8j94da3fb466966d20@mail.gmail.com>

* Mike Rapoport <mike.rapoport@gmail.com> [091102 22:42]:
> On Mon, Nov 2, 2009 at 8:56 PM, Tony Lindgren <tony@atomide.com> wrote:
> > * Mike Rapoport <mike@compulab.co.il> [091101 02:29]:
> >> 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.
> >
> > OK cool.
> >
> >> > 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 :)
> >
> > OK, will run checkpatch.pl --strict on them. Thanks for the
> > comments!
> 
> While on it, can you please update board-cm-t35.c to use CUS package?

OK, will do.

FYI, currently working on converting the old style omap_cfg_reg()
calls so we can remove the old code for 34xx. It will be probably
few days before I get around posting updated patches because of
some meetings over next few days.

Regards,

Tony

      reply	other threads:[~2009-11-03 16:46 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
2009-11-02 18:56   ` Tony Lindgren
2009-11-03  6:42     ` Mike Rapoport
2009-11-03 16:46       ` Tony Lindgren [this message]

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=20091103164646.GF8981@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mike.rapoport@gmail.com \
    --cc=mike@compulab.co.il \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.