stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: John Youn <John.Youn@synopsys.com>, Greg KH <gregkh@linuxfoundation.org>
Cc: "balbi@ti.com" <balbi@ti.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"david.fisher1@synopsys.com" <david.fisher1@synopsys.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 1/6] usb: dwc3: Support Synopsys USB 3.1 IP
Date: Fri, 2 Oct 2015 14:21:01 -0500	[thread overview]
Message-ID: <20151002192101.GF5552@saruman.tx.rr.com> (raw)
In-Reply-To: <2B3535C5ECE8B5419E3ECBE30077290901DC385371@US01WEMBX2.internal.synopsys.com>

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

Hi,

On Fri, Oct 02, 2015 at 07:16:05PM +0000, John Youn wrote:
> >>>> From now, any check based on a revision (for STARS, workarounds, and
> >>>> new features) should take into consideration how it applies to both
> >>>> the 3.1/3.0 IP and make the check accordingly.
> >>>>
> >>>> Cc: <stable@vger.kernel.org> # v3.18+
> >>>
> >>> I really fail to how any of these patches in this series apply for stable. Care
> >>> to explain ?
> >>
> >> We have some prototyping products that are stuck on 3.18 stable
> >> kernels and will continue to ship with that for some time. We'd
> >> like to run the USB 3.1 controller on those platforms. Without
> >> these version id and version number updates dwc3 will not work
> >> with the USB 3.1 IP.
> >>
> >> I think the plan is to update those platforms to 4.2 eventually.
> >> So even then it will still need this patch.
> >>
> >> Also it will help out any customers stuck on earlier kernels.
> >>
> >> How would you advise we handle this, with the version id and
> >> number changes?
> > 
> > I have a feeling the answer to that will be that you will need to backport your
> > own patches :-( Or upgrade to the latest kernel around once your patches get
> > merged.
> > 
> > Would you care to explain why upgrading the kernel is so complex for this
> > prototyping solution ? I suppose you're not using HAPS as a PCIe card on a
> > common desktop PC, then ?
> 
> I don't know the technical reasons why. One platform is ARM based
> and using the 3.18 Linaro stable kernel. Another uses our ARC
> platform which is also on 3.18.
> 
> We're trying to avoid the situation where where we have to ship
> patches or maintain a separate kernel tree.
> 
> Do you have any objections to these going into stable?

I'm not the one you need to convince. That would be Greg :-)

--
balbi

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

  reply	other threads:[~2015-10-02 19:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02  1:14 [PATCH 0/6] usb: dwc3: Various updates for Synopsys platforms John Youn
2015-08-07 18:04 ` [PATCH 2/6] usb: dwc3: pci: Add the Synopsys HAPS AXI Product ID John Youn
2015-08-07 18:47 ` [PATCH 3/6] usb: dwc3: pci: Add the PCI Product ID for Synopsys USB 3.1 John Youn
2015-09-05  2:15 ` [PATCH 1/6] usb: dwc3: Support Synopsys USB 3.1 IP John Youn
2015-10-02  2:03   ` Felipe Balbi
2015-10-02  3:09     ` John Youn
2015-10-02 14:05       ` Felipe Balbi
2015-10-02 19:16         ` John Youn
2015-10-02 19:21           ` Felipe Balbi [this message]
2015-10-02 22:02             ` Greg KH
2015-10-03  0:33               ` Felipe Balbi
2015-10-03  1:14                 ` John Youn
2015-10-03  5:54                   ` Greg KH
2015-10-02 19:47       ` John Youn
2015-10-02 19:55         ` Felipe Balbi
2015-09-26  6:47 ` [PATCH 6/6] usb: dwc3: pci: trivial: Formatting John Youn
2015-09-26  7:11 ` [PATCH 4/6] usb: dwc3: pci: Add platform data for Synopsys HAPS John Youn
2015-09-26  7:31 ` [PATCH 5/6] usb: dwc3: Add dis_enblslpm_quirk John Youn
2015-10-02  2:06   ` 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=20151002192101.GF5552@saruman.tx.rr.com \
    --to=balbi@ti.com \
    --cc=John.Youn@synopsys.com \
    --cc=david.fisher1@synopsys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.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).