From: Tony Lindgren <tony@atomide.com>
To: Adam Ford <aford173@gmail.com>
Cc: Sekhar Nori <nsekhar@ti.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
Tero Kristo <t-kristo@ti.com>, "Liu, Bin" <b-liu@ti.com>
Subject: Re: AM3517 MUSB and CPPI
Date: Tue, 19 May 2020 08:42:50 -0700 [thread overview]
Message-ID: <20200519154250.GS37466@atomide.com> (raw)
In-Reply-To: <CAHCN7x+E3YrRFerzOHKOQHfx67g=ANESuopskKpZHX5qBx_fHQ@mail.gmail.com>
* Adam Ford <aford173@gmail.com> [200518 10:20]:
> On Mon, May 18, 2020 at 12:35 AM Sekhar Nori <nsekhar@ti.com> wrote:
> >
> > + Bin who maintains MUSB controller support
> >
> > On 5/18/20 8:17 AM, Adam Ford wrote:
> > > From what I can tell, the MUSB controller on the AM3517 hasn't worked
> > > in a very long time.
>
> Thanks for adding Bin.
>
> I can post of code patches as an RFC if interested. They don't work
> any better, but they don't work any worse either.
>
> I have modifications to the am35x glue to support cppi41, cppi41 to
> support am35, and updates to the device tree to point the musb
> controller to the am35 glue with additions for cppi41 references and
> some additional clocks.
Sorry no idea about am3517 for musb. Sounds like it's similar to the
am335x though. The USB PHY(s) is probably different though and maybe
you need a separate drivers/phy driver. Maybe check the phy drivers
we have for davinci/dm814x/dm816x, maybe it's similar to those if
not the same as on am335x.
Regards,
Tony
next prev parent reply other threads:[~2020-05-19 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 2:47 AM3517 MUSB and CPPI Adam Ford
2020-05-18 5:35 ` Sekhar Nori
2020-05-18 10:19 ` Adam Ford
2020-05-19 15:42 ` Tony Lindgren [this message]
2020-05-21 2:44 ` Bin Liu
2020-05-22 10:16 ` Adam Ford
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=20200519154250.GS37466@atomide.com \
--to=tony@atomide.com \
--cc=aford173@gmail.com \
--cc=b-liu@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=t-kristo@ti.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 NNTP newsgroup(s).