From: Bin Liu <b-liu@ti.com>
To: <gregkh@linuxfoundation.org>
Cc: <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] usb: musb: da8xx: fix babble condition handling" failed to apply to 4.9-stable tree
Date: Mon, 18 Dec 2017 08:47:44 -0600 [thread overview]
Message-ID: <20171218144744.GC14090@uda0271908> (raw)
In-Reply-To: <15135972764252@kroah.com>
Hi,
On Mon, Dec 18, 2017 at 12:41:16PM +0100, gregkh@linuxfoundation.org wrote:
>
> The patch below does not apply to the 4.9-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
>
> thanks,
>
> greg k-h
>
> ------------------ original commit in Linus's tree ------------------
>
> From bd3486ded7a0c313a6575343e6c2b21d14476645 Mon Sep 17 00:00:00 2001
> From: Bin Liu <b-liu@ti.com>
> Date: Tue, 5 Dec 2017 08:45:30 -0600
> Subject: [PATCH] usb: musb: da8xx: fix babble condition handling
>
> When babble condition happens, the musb controller might automatically
> turns off VBUS. On DA8xx platform, the controller generates drvvbus
> interrupt for turning off VBUS along with the babble interrupt.
>
> In this case, we should handle the babble interrupt first and recover
> from the babble condition.
>
> This change ignores the drvvbus interrupt if babble interrupt is also
> generated at the same time, so the babble recovery routine works
> properly.
>
> Cc: stable@vger.kernel.org # v3.16+
> Signed-off-by: Bin Liu <b-liu@ti.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> diff --git a/drivers/usb/musb/da8xx.c b/drivers/usb/musb/da8xx.c
> index 0397606a211b..6c036de63272 100644
> --- a/drivers/usb/musb/da8xx.c
> +++ b/drivers/usb/musb/da8xx.c
> @@ -284,7 +284,15 @@ static irqreturn_t da8xx_musb_interrupt(int irq, void *hci)
> musb->xceiv->otg->state = OTG_STATE_A_WAIT_VRISE;
> portstate(musb->port1_status |= USB_PORT_STAT_POWER);
> del_timer(&musb->dev_timer);
This line causes the conflict. I have sent the new patch for the stable
trees.
Regards,
-Bin.
> - } else {
> + } else if (!(musb->int_usb & MUSB_INTR_BABBLE)) {
> + /*
> + * When babble condition happens, drvvbus interrupt
> + * is also generated. Ignore this drvvbus interrupt
> + * and let babble interrupt handler recovers the
> + * controller; otherwise, the host-mode flag is lost
> + * due to the MUSB_DEV_MODE() call below and babble
> + * recovery logic will not be called.
> + */
> musb->is_active = 0;
> MUSB_DEV_MODE(musb);
> otg->default_a = 0;
>
prev parent reply other threads:[~2017-12-18 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 11:41 FAILED: patch "[PATCH] usb: musb: da8xx: fix babble condition handling" failed to apply to 4.9-stable tree gregkh
2017-12-18 14:47 ` Bin Liu [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=20171218144744.GC14090@uda0271908 \
--to=b-liu@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).