From: Tom Rini <trini@konsulko.com>
To: Harald Seiler <hws@denx.de>, Lokesh Vutla <lokeshvutla@ti.com>
Cc: "Matwey V. Kornilov" <matwey.kornilov@gmail.com>,
paul.barker@sancloud.com, dariobin@libero.it,
pbrobinson@gmail.com, u-boot@lists.denx.de
Subject: Re: [PATCH] am33xx: Fix USB for am335x boards
Date: Tue, 10 Aug 2021 09:23:42 -0400 [thread overview]
Message-ID: <20210810132342.GJ858@bill-the-cat> (raw)
In-Reply-To: <222aacd30ec9edd3e680f6c2ecc65e32b1c9e208.camel@denx.de>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
On Tue, Aug 10, 2021 at 12:04:23PM +0200, Harald Seiler wrote:
> Hi,
>
> On Sat, 2021-08-07 at 14:17 +0300, Matwey V. Kornilov wrote:
> > USB nodes were mistakenly disabled in
> >
> > commit 942853dd96df ("arm: dts: Resync BeagleBone device trees")
>
> To be precise, the problem is that only half of the device tree files
> were synced. am33xx.dtsi (and seemingly some more) were skipped,
> leading to the symptoms you found. I think it is likely that the
> upstream changes in am33xx.dtsi which we are missing right now will lead
> to more regressions of similar nature.
>
> So I'd say we should dig deeper into the problems you encountered while
> attempting to just sync the entirety of am33xx.dtsi. The end goal is
> that all device-tree files not ending in `-uboot` match what is in
> Linux, so it is inevitable that someone needs to look into this anyway.
Yes, there is a general need to re-sync all of the TI dts files with
upstream. It's unclear to me right now if a full resync on the am33xx
line will produce the same set of total failure that resyncing the rest
of the omap5/j6/am57xx and later families have.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-08-10 13:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 10:54 [BISECTED] arm: dts: Resync BeagleBone device trees Matwey V. Kornilov
2021-08-06 11:39 ` Harald Seiler
2021-08-06 11:44 ` Peter Robinson
2021-08-06 11:50 ` Matwey V. Kornilov
2021-08-06 12:21 ` Harald Seiler
2021-08-06 15:25 ` Matwey V. Kornilov
2021-08-07 11:17 ` [PATCH] am33xx: Fix USB for am335x boards Matwey V. Kornilov
2021-08-07 12:48 ` Paul Barker
2021-08-10 10:04 ` Harald Seiler
2021-08-10 13:23 ` Tom Rini [this message]
2021-09-11 12:16 ` 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=20210810132342.GJ858@bill-the-cat \
--to=trini@konsulko.com \
--cc=dariobin@libero.it \
--cc=hws@denx.de \
--cc=lokeshvutla@ti.com \
--cc=matwey.kornilov@gmail.com \
--cc=paul.barker@sancloud.com \
--cc=pbrobinson@gmail.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;
as well as URLs for NNTP newsgroup(s).