public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: felipe.balbi@nokia.com
Cc: ext Ajay Kumar Gupta <ajay.gupta@ti.com>,
	linux-usb@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] usb: musb: fix bug in musbhsdma programming
Date: Fri, 23 Jan 2009 10:36:04 -0800	[thread overview]
Message-ID: <200901231036.04376.david-b@pacbell.net> (raw)
In-Reply-To: <20090123101812.GP9233@scadufax.research.nokia.com>

On Friday 23 January 2009, Felipe Balbi wrote:
> On Thu, Jan 08, 2009 at 06:01:36PM +0530, Ajay Kumar Gupta wrote:
> > Mode bit should be set based on function parameter "mode" of
> > configure_channel() function.
> > 
> > Signed-off-by: Ajay Kumar Gupta <ajay.gupta@ti.com>
> 
> Acked-by: Felipe Balbi <felipe.balbi@nokia.com>

NAK -- interpretation of the MODE parameter is correct
(though it's not clear to me that the callers set it right),
but this won't apply to current GIT since the code differs.

I don't know what this is *against* but it's not mainline
or the OMAP tree...

        csr |= (musb_channel->epnum << MUSB_HSDMA_ENDPOINT_SHIFT)
                | (1 << MUSB_HSDMA_ENABLE_SHIFT)
                | (1 << MUSB_HSDMA_IRQENABLE_SHIFT)
                | (musb_channel->transmit
                                ? (1 << MUSB_HSDMA_TRANSMIT_SHIFT)
                                : 0);

Ajay, if this needs to merge to mainline (e.g. so it can be
pulled down to omap-git and fix DMA there) please re-issue.

- Dave

> 
> > ---
> >  drivers/usb/musb/musbhsdma.c |    3 ++-
> >  1 files changed, 2 insertions(+), 1 deletions(-)
> > 
> > diff --git a/drivers/usb/musb/musbhsdma.c b/drivers/usb/musb/musbhsdma.c
> > index a23d005..d87c6c7 100644
> > --- a/drivers/usb/musb/musbhsdma.c
> > +++ b/drivers/usb/musb/musbhsdma.c
> > @@ -225,13 +225,14 @@ static void configure_channel(struct dma_channel *channel,
> >  			csr |= MUSB_HSDMA_BURSTMODE_INCR4;
> >  
> >  		csr |= (musb_channel->epnum << MUSB_HSDMA_ENDPOINT_SHIFT)
> > -			| MUSB_HSDMA_MODE1
> >  			| MUSB_HSDMA_ENABLE
> >  			| MUSB_HSDMA_IRQENABLE
> >  			| (musb_channel->transmit
> >  					? MUSB_HSDMA_TRANSMIT
> >  					: 0);
> >  
> > +		if (mode)
> > +			csr |= MUSB_HSDMA_MODE1;
> >  		/* address/count */
> >  		musb_write_hsdma_addr(mbase, bchannel, dma_addr);
> >  		musb_write_hsdma_count(mbase, bchannel, len);
> > -- 
> > 1.5.6
> 
> -- 
> balbi
> 
> 



  reply	other threads:[~2009-01-23 18:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 12:31 [PATCH] usb: musb: fix bug in musbhsdma programming Ajay Kumar Gupta
2009-01-23 10:18 ` Felipe Balbi
2009-01-23 18:36   ` David Brownell [this message]
     [not found]     ` <200901231036.04376.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2009-01-23 18:38       ` Felipe Balbi
2009-01-23 18:50         ` David Brownell
2009-01-24  3:04     ` Gupta, Ajay Kumar
     [not found]       ` <19F8576C6E063C45BE387C64729E739403FA6CCD3A-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2009-01-24  4:31         ` David Brownell

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=200901231036.04376.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=ajay.gupta@ti.com \
    --cc=felipe.balbi@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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