All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Ajay Kumar Gupta <ajay.gupta@ti.com>,
	linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
	felipe.balbi@nokia.com, gregkh@suse.de,
	Anand Gadiyar <gadiyar@ti.com>
Subject: Re: [PATCH 1/2] musb: Kill board specific pinmux from driver file
Date: Fri, 9 Jul 2010 12:03:32 -0700	[thread overview]
Message-ID: <20100709190332.GA29601@kroah.com> (raw)
In-Reply-To: <20100709081532.GH24913@atomide.com>

On Fri, Jul 09, 2010 at 11:15:33AM +0300, Tony Lindgren wrote:
> * Ajay Kumar Gupta <ajay.gupta@ti.com> [100708 13:59]:
> > From: Anand Gadiyar <gadiyar@ti.com>
> > 
> > This pin-muxing is best done in the board files. The driver should
> > not do this explicitly.
> > 
> > Also, this code causes a warning to be thrown when OMAP2430 and OMAP3/4
> > support are enabled in the same kernel.
> > 
> > Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
> > Acked-by: Felipe Balbi <felipe.balbi@nokia.com>
> > Signed-off-by: Ajay Kumar Gupta <ajay.gupta@ti.com>
> 
> Acked-by: Tony Lindgren <tony@atomide.com>

Thanks, I've added this to the patch.

greg k-h

> 
> > ---
> >  drivers/usb/musb/omap2430.c |    6 ------
> >  1 files changed, 0 insertions(+), 6 deletions(-)
> > 
> > diff --git a/drivers/usb/musb/omap2430.c b/drivers/usb/musb/omap2430.c
> > index e06d65e..2111a24 100644
> > --- a/drivers/usb/musb/omap2430.c
> > +++ b/drivers/usb/musb/omap2430.c
> > @@ -32,8 +32,6 @@
> >  #include <linux/clk.h>
> >  #include <linux/io.h>
> >  
> > -#include <plat/mux.h>
> > -
> >  #include "musb_core.h"
> >  #include "omap2430.h"
> >  
> > @@ -194,10 +192,6 @@ int __init musb_platform_init(struct musb *musb, void *board_data)
> >  	u32 l;
> >  	struct omap_musb_board_data *data = board_data;
> >  
> > -#if defined(CONFIG_ARCH_OMAP2430)
> > -	omap_cfg_reg(AE5_2430_USB0HS_STP);
> > -#endif
> > -
> >  	/* We require some kind of external transceiver, hooked
> >  	 * up through ULPI.  TWL4030-family PMICs include one,
> >  	 * which needs a driver, drivers aren't always needed.
> > -- 
> > 1.6.2.4
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2010-07-09 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 11:04 [patch-v2.6.36 0/2] musb patches Ajay Kumar Gupta
     [not found] ` <1278587095-16978-1-git-send-email-ajay.gupta-l0cyMroinI0@public.gmane.org>
2010-07-08 11:04   ` [PATCH 1/2] musb: Kill board specific pinmux from driver file Ajay Kumar Gupta
     [not found]     ` <1278587095-16978-2-git-send-email-ajay.gupta-l0cyMroinI0@public.gmane.org>
2010-07-08 11:04       ` [PATCH 2/2] usb: musb: do not override DMA mode in channel program Ajay Kumar Gupta
2010-07-09  8:15     ` [PATCH 1/2] musb: Kill board specific pinmux from driver file Tony Lindgren
2010-07-09 19:03       ` Greg KH [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=20100709190332.GA29601@kroah.com \
    --to=greg@kroah.com \
    --cc=ajay.gupta@ti.com \
    --cc=felipe.balbi@nokia.com \
    --cc=gadiyar@ti.com \
    --cc=gregkh@suse.de \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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 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.