From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 2/4] omap3_beagle: Disable USB support
Date: Tue, 30 Jun 2020 14:48:47 -0400 [thread overview]
Message-ID: <20200630184847.GY1306@bill-the-cat> (raw)
In-Reply-To: <CAHCN7xJ9YHmJG+cZBO_U4R3BvR_TFK+gJBGH1Rh1Crg-AB8uLw@mail.gmail.com>
On Tue, Jun 30, 2020 at 12:35:31PM -0500, Adam Ford wrote:
> On Tue, Jun 30, 2020 at 12:14 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > On Tue, Jun 30, 2020 at 12:07:51PM -0500, Adam Ford wrote:
> > > On Tue, Jun 30, 2020 at 11:56 AM Tom Rini <trini@konsulko.com> wrote:
> > > >
> > > > Disable USB support for now. There is non-trivial work required to
> > > > fully move the OMAP3 platforms to DM. While this work is in-progress,
> > > > disable USB support for now as we've gone well past the migration
> > > > deadline.
> > > >
> > > > Cc: Adam Ford <aford173@gmail.com>
> > > > Signed-off-by: Tom Rini <trini@konsulko.com>
> > > > ---
> > >
> > > I don't have a beagle, but I have DM_USB working on two different
> > > OMAP3 boards. I am curious to know what's left or what's not working.
> >
> > Oh? I thought when we talked last there was still more to do to fully
> > migrate things over. Where should I check again to see what I need to
> > do on beagle to convert it over? Thanks!
>
> With [1], the DM support for the EHCI controller was added. There is
> still some work to be done to make it better, because there are still
> some #defines that need to assign the reset GPIO's. Ideally we'd get
> rid of the GPIO defines and use the device tree to address the reset.
> It isn't perfect, but it's better than having no USB at all. The
> am3517_evm and omap3_logic_somlv have them working. Make sure the
> board files have the legacy USB stuff removed [2]
>
> [1] - https://gitlab.denx.de/u-boot/u-boot/-/commit/94ed66194f150c308d1713965a28abce3ac6e200
> [2] - https://gitlab.denx.de/u-boot/u-boot/-/commit/76f6d52e61a1968702af69d6cea463b9d9332a96
>
> Let me know if there is anything I can do to help.
Hunh, thanks. I thought I had tried this much before but had things
blow up. With [2] it's a quick conversion and passing basic sanity
checks. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200630/5c616ad8/attachment.sig>
next prev parent reply other threads:[~2020-06-30 18:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 16:56 [PATCH 1/4] am335x: Update list of defconfigs Tom Rini
2020-06-30 16:56 ` [PATCH 2/4] omap3_beagle: Disable USB support Tom Rini
2020-06-30 17:07 ` Adam Ford
2020-06-30 17:14 ` Tom Rini
2020-06-30 17:35 ` Adam Ford
2020-06-30 18:48 ` Tom Rini [this message]
2020-06-30 18:49 ` Tom Rini
2020-06-30 16:56 ` [PATCH 3/4] ti816x_evm: Enable DM_MMC Tom Rini
2020-06-30 21:15 ` Tom Rini
2020-06-30 16:56 ` [PATCH 4/4] ti814x: Remove platform Tom Rini
2020-06-30 21:15 ` Tom Rini
2020-06-30 21:15 ` [PATCH 1/4] am335x: Update list of defconfigs Tom Rini
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=20200630184847.GY1306@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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