All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/2] omap4: panda: convert to device model
Date: Mon, 15 Jun 2020 10:57:59 -0400	[thread overview]
Message-ID: <20200615145759.GC24893@bill-the-cat> (raw)
In-Reply-To: <3dc2d11d-77f3-f87e-0464-73ec9b2b5cb8@ti.com>

On Mon, Jun 15, 2020 at 05:53:39PM +0300, Tero Kristo wrote:
> On 15/06/2020 17:48, Vignesh Raghavendra wrote:
> > 
> > 
> > On 15/06/20 11:49 am, Tero Kristo wrote:
> > > On 14/06/2020 16:49, Lokesh Vutla wrote:
> > > > Hi Tero,
> > > > 
> > > > On 02/06/20 4:49 pm, Tero Kristo wrote:
> > > > > Hi,
> > > > > 
> > > > > As there is looming death to OMAP4 Panda board u-boot support, I decided
> > > > > to take a shot and convert it to device model myself. With these patches
> > > > > it boots up fine, and there are no DM_SPL conversion complaints during
> > > > > compile time anymore. I think USB ethernet does not work anymore with
> > > > > this, but its better than dropping the support for the board completely.
> > > > > USB itself appears working, so it should be relatively easy for someone
> > > > > to fix the networking support if they need it.
> > > > 
> > > > I see the below warning with these patches:
> > > > 
> > > > board/ti/panda/panda.c:329:35: warning: ?struct ehci_hcor? declared
> > > > inside parameter list will not be visible outside of this definition
> > > > or declaration
> > > >  ?? 329 |?? struct ehci_hccr **hccr, struct ehci_hcor **hcor)
> > > >  ?????? |?????????????????????????????????? ^~~~~~~~~
> > > > board/ti/panda/panda.c:329:10: warning: ?struct ehci_hccr? declared
> > > > inside parameter list will not be visible outside of this definition
> > > > or declaration
> > > >  ?? 329 |?? struct ehci_hccr **hccr, struct ehci_hcor **hcor)
> > > >  ?????? |????????? ^~~~~~~~~
> > > > board/ti/panda/panda.c: In function ?ehci_hcd_init?:
> > > > board/ti/panda/panda.c:339:8: warning: implicit declaration of
> > > > function ?omap_ehci_hcd_init?; did you mean ?ehci_hcd_init??
> > > > [-Wimplicit-function-declaration]
> > > >  ?? 339 |? ret = omap_ehci_hcd_init(index, &usbhs_bdata, hccr, hcor);
> > > >  ?????? |??????? ^~~~~~~~~~~~~~~~~~
> > > >  ?????? |??????? ehci_hcd_init
> > > > board/ti/panda/panda.c: In function ?ehci_hcd_stop?:
> > > > board/ti/panda/panda.c:348:9: warning: implicit declaration of
> > > > function ?omap_ehci_hcd_stop?; did you mean ?ehci_hcd_stop??
> > > > [-Wimplicit-function-declaration]
> > > >  ?? 348 |? return omap_ehci_hcd_stop();
> > > >  ?????? |???????? ^~~~~~~~~~~~~~~~~~
> > > >  ?????? |???????? ehci_hcd_stop
> > > 
> > > Yeah, I actually see these also. I think we could maybe drop all the
> > > offending code as I did later with the omap5-uevm. On omap5, USB seemed
> > > to work even without these.
> > > 
> > > Maybe some USB expert can comment on these (Vignesh)?
> > > 
> > 
> > 
> > Offending code won't compile with DM_USB enabled. I suggest to drop them
> > for now in order to avoid entire board support from being dropped. USB
> > can be added back later if needed...
> > 
> > Or you would have to disable DM_USB give this a try..
> 
> Yeah, dropping DM_USB USB stops working completely I believe. And, USB
> appears working (at least partially: usb start, usb info provides some sane
> data) with these two patches, just the compiler warnings are there.
> 
> However, I eliminated the offending code in v2 I posted today, and USB still
> appears functional as far as I can see. Trying to compile mass storage
> support in to test USB mass storage devices causes a mayhem so I left that
> for someone more experienced with USB.

Please note that DM_USB migration also has a deadline of almost a year
ago so this is another area to fix or remove-now-readd-later.  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/20200615/17e6c322/attachment.sig>

  reply	other threads:[~2020-06-15 14:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 11:19 [PATCH 0/2] omap4: panda: convert to device model Tero Kristo
2020-06-02 11:19 ` [PATCH 1/2] omap4: Copy device tree from Linux 5.7.y Tero Kristo
2020-06-02 11:19 ` [PATCH 2/2] omap4: panda: convert to device model Tero Kristo
2020-06-11 18:10   ` Jagan Teki
2020-06-06  7:49 ` [PATCH 0/2] " Jonathan Gray
2020-06-14 13:49 ` Lokesh Vutla
2020-06-15  6:19   ` Tero Kristo
2020-06-15 14:48     ` Vignesh Raghavendra
2020-06-15 14:53       ` Tero Kristo
2020-06-15 14:57         ` Tom Rini [this message]
2020-06-15 15:01           ` Tero Kristo
2020-06-15 15:06             ` Tom Rini
2020-06-15 15:02         ` 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=20200615145759.GC24893@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 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.