From: Tony Lindgren <tony@atomide.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Gowtham Tammana <g-tammana@ti.com>, Suman Anna <s-anna@ti.com>,
bcousson@baylibre.com, robh+dt@kernel.org,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Nisanth Menon <nm@ti.com>
Subject: Re: [PATCH v4] ARM: dts: dra7: Fix duplicate USB4 target module node
Date: Fri, 11 Jun 2021 08:33:50 +0300 [thread overview]
Message-ID: <YML1vuROPftMR+j6@atomide.com> (raw)
In-Reply-To: <c140f39c-9fe1-f7e1-3da5-fc5fff604714@ti.com>
* Grygorii Strashko <grygorii.strashko@ti.com> [210608 10:40]:
> On 03/06/2021 01:04, Gowtham Tammana wrote:
> > With [1] USB4 target-module node got defined in dra74x.dtsi file.
> > However, the earlier definition in [2] was not removed, and this
> > duplication of the target module is causing boot failure on dra74
> > variant boards - dra7-evm, dra76-evm.
> >
> > USB4 is only present in DRA74x variants, so keeping the entry in
> > dra74x.dtsi and removing it from the top level interconnect hierarchy
> > dra7-l4.dtsi file. This change makes the USB4 target module no longer
> > visible to AM5718, DRA71x and DRA72x so removing references to it in
> > their respective dts files.
> >
> > [1]: commit c7b72abca61ec ("ARM: OMAP2+: Drop legacy platform data for
> > dra7 dwc3")
> > [2]: commit 549fce068a311 ("ARM: dts: dra7: Add l4 interconnect
> > hierarchy and ti-sysc data")
> >
> > Fixes: c7b72abca61ec ("ARM: OMAP2+: Drop legacy platform data for dra7 dwc3")
> > Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
...
> Thank you.
> Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>
Thanks applying into fixes.
Tony
prev parent reply other threads:[~2021-06-11 5:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 22:04 [PATCH v4] ARM: dts: dra7: Fix duplicate USB4 target module node Gowtham Tammana
2021-06-08 10:40 ` Grygorii Strashko
2021-06-11 5:33 ` Tony Lindgren [this message]
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=YML1vuROPftMR+j6@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=g-tammana@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@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).