From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from comal.ext.ti.com ([198.47.26.152]:41386 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751107AbbJBTVE (ORCPT ); Fri, 2 Oct 2015 15:21:04 -0400 Date: Fri, 2 Oct 2015 14:21:01 -0500 From: Felipe Balbi To: John Youn , Greg KH CC: "balbi@ti.com" , "linux-usb@vger.kernel.org" , "david.fisher1@synopsys.com" , "stable@vger.kernel.org" Subject: Re: [PATCH 1/6] usb: dwc3: Support Synopsys USB 3.1 IP Message-ID: <20151002192101.GF5552@saruman.tx.rr.com> Reply-To: References: <20151002020355.GB2534@saruman.tx.rr.com> <2B3535C5ECE8B5419E3ECBE30077290901DC384A94@US01WEMBX2.internal.synopsys.com> <20151002140502.GC5552@saruman.tx.rr.com> <2B3535C5ECE8B5419E3ECBE30077290901DC385371@US01WEMBX2.internal.synopsys.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BqNvIJgrK1/MQy2W" Content-Disposition: inline In-Reply-To: <2B3535C5ECE8B5419E3ECBE30077290901DC385371@US01WEMBX2.internal.synopsys.com> Sender: stable-owner@vger.kernel.org List-ID: --BqNvIJgrK1/MQy2W Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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: # v3.18+ > >>> > >>> I really fail to how any of these patches in this series apply for st= able. 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? > >=20 > > I have a feeling the answer to that will be that you will need to backp= ort your > > own patches :-( Or upgrade to the latest kernel around once your patche= s get > > merged. > >=20 > > Would you care to explain why upgrading the kernel is so complex for th= is > > prototyping solution ? I suppose you're not using HAPS as a PCIe card o= n a > > common desktop PC, then ? >=20 > 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. >=20 > We're trying to avoid the situation where where we have to ship > patches or maintain a separate kernel tree. >=20 > Do you have any objections to these going into stable? I'm not the one you need to convince. That would be Greg :-) -- balbi --BqNvIJgrK1/MQy2W Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJWDtkcAAoJEIaOsuA1yqRESeMP/0533sHVCk7rkuwJ2vLROClK 1LKz9SXOCUY4aEVc6td8zFpmbHPydP8pEJDH51mz1njoaRmVpsbmFwyVChkgnk6u E0SSGsPmcnYsxK+9sdSO2zVpvBFarRdDCiClAzGMxCpeZcny6qdJfd5yzyXeN2B9 u2EmdslReX1zDNZXQjf6aQ0JqjLko52fJZIk7hQpgX8ruTwMh/I86etQ+2ShlCPs V2SrA+FAEzSahfCcZ/4HUUyH+Q8ZtjzCAzDBI8V2jlcf6go09fDhMtXFw2Bab3vT QUQlycL/1pykPvZfKYIc28TWsLCRITn6ZkHGAO0Ywbd61mr5/y6OuUSjpaFBKooq Nct82Hy5JTzT4dB7CQOan6Iu7+tS8cY+ZU13GPA1wJqpmYdqvWBnATN1L03+eNmw 3rRAcb3Nn3iJNEgl5EDdXKKgOfoHBsYQDa2N4Fe7TvenIZCytxe3h4+EnSg6c63/ 0zEpK45N37ahN8hH/FAMnftdZASXhtMW0KFdTzXoI3ObsBfhanBThE7qkCTC8RbN ZN+qvM5HBvUbYJSAd/Zgwnd9H6Ixx9fZYvLQiRrrtNEUyjFdMSAML8QQTjXPgAhJ GH7tv+pGCWacbhOEEIWiXE2+Lw6v8QDF1yM7+VggAzOYlmJC2RUISsTIIzq83ykC YJdE6BoYsz/H52O3eI7i =zr7Q -----END PGP SIGNATURE----- --BqNvIJgrK1/MQy2W--