From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.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 12:43:40 +0300 [thread overview]
Message-ID: <87pnnlbws3.fsf@linux.intel.com> (raw)
In-Reply-To: <9171a0e63bebaa0efaec64838f9a1c6982fc33e8.camel@infinera.com>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
Hi,
Joakim Tjernlund <Joakim.Tjernlund@infinera.com> writes:
> 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?
>
> Looking at upstream, there has not been any significant change in this
> area for a long time.
In that case, I'll let Li Yang reply.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-06-10 9:43 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 [this message]
2019-06-10 14:21 ` Greg KH
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=87pnnlbws3.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=Joakim.Tjernlund@infinera.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.