From: Greg KH <gregkh@linuxfoundation.org>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
Cc: "felipe.balbi@linux.intel.com" <felipe.balbi@linux.intel.com>,
"leoyang.li@nxp.com" <leoyang.li@nxp.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: fsl_udc status?
Date: Mon, 10 Jun 2019 16:21:01 +0200 [thread overview]
Message-ID: <20190610142101.GB5937@kroah.com> (raw)
In-Reply-To: <9171a0e63bebaa0efaec64838f9a1c6982fc33e8.camel@infinera.com>
On Mon, Jun 10, 2019 at 08:33:17AM +0000, Joakim Tjernlund wrote:
> On Mon, 2019-06-10 at 10:56 +0300, Felipe Balbi wrote:
> > Hi,
> >
> > Joakim Tjernlund <Joakim.Tjernlund@infinera.com> writes:
> > > We are trying to get fsl_udc up and running on a T1042 with without success.
> > > Seems like this driver is lagging behind the corresponding host driver(mph).
> > > The mph driver has a number of USB errata workarounds while udc has none.
> > > At least erratas A007792 seems applicable for udc too.
> > >
> > > Is the fsl_udc driver functional on 4.14.x(which we use)? What is missing ?
> >
> > If you're on v4.14, then you need to ask for support from whoever gave
> > you that kernel. In this forum we treat mainline only, which currently
> > is at v5.2-rc4. Unless you can try that version of the kernel, we can't
> > really help you here.
>
> None gave me that kernel, it is the stable 4.14.x tree that Greg maintains, I would
> assume that this forum has some support for stable kernels too?
ONLY use a older LTS kernel if you already have a device up and working
properly and you need "long term" support for it. Do NOT use it for
bringing up a new device and expecting everything to work properly on it
at all. That should only be done on the latest stable release, and
sometimes, if you are using an older system, on the latest LTS release.
4.14.y is neither the latest LTS release, nor the latest stable release.
Please try either 4.19.y or 5.1 to see if Linux even works on this
device. If so, then worry about running an older kernel (but you really
do not want to do that anyway.)
> Looking at upstream, there has not been any significant change in this
> area for a long time.
There are lots and lots of changes that have happened all over the
kernel tree since 4.14.0 was released. Don't assume things are not
connected at all, they are not.
So please, try 5.1, and if that doesn't work, we will be glad to help
you out.
If you insist on using 4.14 for a device you do not even know if it
works or not, you really are on your own.
thanks,
greg k-h
next prev parent reply other threads:[~2019-06-10 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 7:51 fsl_udc status? Joakim Tjernlund
2019-06-10 7:56 ` Felipe Balbi
2019-06-10 8:33 ` Joakim Tjernlund
2019-06-10 9:43 ` Felipe Balbi
2019-06-10 14:21 ` Greg KH [this message]
2019-06-10 16:09 ` Fabio Estevam
2019-06-10 17:12 ` Leo Li
2019-06-10 17:51 ` Joakim Tjernlund
2019-06-10 18:47 ` Leo Li
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=20190610142101.GB5937@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Joakim.Tjernlund@infinera.com \
--cc=felipe.balbi@linux.intel.com \
--cc=leoyang.li@nxp.com \
--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;
as well as URLs for NNTP newsgroup(s).