From: Daniel Palmer <daniel@0x0f.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Corentin Labbe <clabbe.montjoie@gmail.com>,
Hans Ulli Kroll <ulli.kroll@googlemail.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: gemini: sl3516: Mainlining of NS 2502
Date: Thu, 6 May 2021 18:02:18 +0900 [thread overview]
Message-ID: <CAFr9PX=qskO+vxUiNaq5e0E7BFGGuK4xzh2sM2dEO2tEtucMtA@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdaGAiK57LE8vkEBjCGwb+HRWBzWS_C86xdNa8N51G+1PA@mail.gmail.com>
Hi Linus, Coretin
On Thu, 6 May 2021 at 08:56, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Wed, May 5, 2021 at 9:26 PM Corentin Labbe <clabbe.montjoie@gmail.com> wrote:
>
> > It seems that USB is still a bit buggy, device are detected only if plugged before boot.
>
> Yeah :/ I don't know that driver very well, only that others use it too
> so there might be some people who can help. I haven't mainlined
> that patch because there is something that seems wrong about it
> but I'm not a USB guy.
Assuming I didn't read the wrong dts this machine is using the Faraday FOTG210.
FWIW the MStar/Sigmastar ARMv7 (and earlier I think) chips use
basically the same IP for USB host (FUSBH200).
There used to be a distinct driver for the host-only version but it
got removed at some point so I added support for it to the otg driver
in my tree and it sort of works.
It seems very picky about devices being hot plugged and doesn't seem
able to enumerate low speed/full speed devices at all.
Maybe we are seeing the same issues? I have a USB bus analyzer and I
intend to debug this at some point.
Adding support for USB on the MStar stuff is pretty far off but maybe
if I find something Coretin can test to see if it helps out there too.
Thanks,
Daniel
next prev parent reply other threads:[~2021-05-06 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 18:39 gemini: sl3516: Mainlining of NS 2502 Corentin Labbe
2021-04-05 20:36 ` Andrew Lunn
2021-04-06 9:06 ` Corentin Labbe
2021-04-06 8:15 ` Linus Walleij
2021-04-06 12:05 ` Corentin Labbe
2021-04-07 9:34 ` Linus Walleij
2021-05-05 19:26 ` Corentin Labbe
2021-05-05 23:56 ` Linus Walleij
2021-05-06 9:02 ` Daniel Palmer [this message]
2021-05-12 20:14 ` Corentin Labbe
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='CAFr9PX=qskO+vxUiNaq5e0E7BFGGuK4xzh2sM2dEO2tEtucMtA@mail.gmail.com' \
--to=daniel@0x0f.com \
--cc=clabbe.montjoie@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ulli.kroll@googlemail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).