linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Felipe Balbi <balbi@ti.com>, Greg KH <greg@kroah.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Daniel Mack <zonque@gmail.com>
Subject: linux-next: manual merge of the usb-gadget tree with the usb.current tree
Date: Fri, 4 Jul 2014 14:51:27 +1000	[thread overview]
Message-ID: <20140704145127.30008370@canb.auug.org.au> (raw)

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

Hi Felipe,

Today's linux-next merge of the usb-gadget tree got a conflict in
drivers/usb/musb/musb_cppi41.c between commit c58d80f523ff ("usb: musb:
Ensure that cppi41 timer gets armed on premature DMA TX irq") from the
usb.current tree and commit 50aea6fca771 ("usb: musb: cppi41: fire
hrtimer according to programmed channel length") from the usb-gadget
tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

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

diff --cc drivers/usb/musb/musb_cppi41.c
index 5341bb223b7c,adfffe884891..000000000000
--- a/drivers/usb/musb/musb_cppi41.c
+++ b/drivers/usb/musb/musb_cppi41.c
@@@ -312,15 -271,13 +271,13 @@@ static void cppi41_dma_callback(void *p
  				goto out;
  			}
  		}
- 		if (is_isoc(hw_ep, 0)) {
- 			schedule_work(&cppi41_channel->dma_completion);
- 			goto out;
- 		}
  		list_add_tail(&cppi41_channel->tx_check,
  				&controller->early_tx_list);
 -		if (!hrtimer_active(&controller->early_tx)) {
 +		if (!hrtimer_is_queued(&controller->early_tx)) {
+ 			unsigned long usecs = cppi41_channel->total_len / 10;
+ 
  			hrtimer_start_range_ns(&controller->early_tx,
- 				ktime_set(0, 140 * NSEC_PER_USEC),
+ 				ktime_set(0, usecs * NSEC_PER_USEC),
  				40 * NSEC_PER_USEC,
  				HRTIMER_MODE_REL);
  		}

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2014-07-04  4:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-04  4:51 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-05-28  8:36 linux-next: manual merge of the usb-gadget tree with the usb.current tree Stephen Rothwell
2015-01-16  6:23 Stephen Rothwell
2015-01-16  9:56 ` Kaukab, Yousaf
2015-01-13  4:06 Stephen Rothwell
2015-01-13  4:02 Stephen Rothwell
2014-09-08  7:09 Stephen Rothwell
2014-09-08  7:02 Stephen Rothwell
2014-09-08 13:27 ` Felipe Balbi
2013-12-18  6:09 Stephen Rothwell
2013-07-30  4:08 Stephen Rothwell
2013-07-30  5:50 ` Felipe Balbi
2013-03-22  3:31 Stephen Rothwell
2013-03-22  6:28 ` Felipe Balbi
2013-03-22  3:28 Stephen Rothwell
2013-03-22  6:28 ` Felipe Balbi

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=20140704145127.30008370@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=balbi@ti.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=zonque@gmail.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;
as well as URLs for NNTP newsgroup(s).