linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tammana, Gowtham" <g-tammana@ti.com>
To: "Anna, Suman" <s-anna@ti.com>,
	"tony@atomide.com" <tony@atomide.com>,
	"bcousson@baylibre.com" <bcousson@baylibre.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"Strashko, Grygorii" <grygorii.strashko@ti.com>,
	"Menon, Nishanth" <nm@ti.com>
Subject: RE: [PATCH v2] ARM: dts: dra7: Fix duplicate USB4 device node
Date: Wed, 26 May 2021 19:48:23 +0000	[thread overview]
Message-ID: <555c768263cc48499b299c0b595fcb94@ti.com> (raw)
In-Reply-To: <64bb0e71-dc6d-e21d-cfc0-cfeb787ca7c2@ti.com>



>-----Original Message-----
>From: Anna, Suman
>Sent: Wednesday, May 26, 2021 1:01 PM
>
>Hi Gowtham,
>
>On 5/26/21 12:20 PM, Gowtham Tammana wrote:
>> With [1] USB4 device node got defined in dra74x.dtsi file. However,
>> there was a prior defintion of the same in [2] which didn't get removed
>
>I like this approach and is more in line with the original move of USB4
>node
>into dra74x.dtsi file.
>
>Looks like you mixed up [1] and [2] or I misunderstand your terminology.

Yes, 1 and 2 got mixed up here. Will post a v3.

>Also,
>let's be precise, it is the USB4 target-module node that got duplicated in
>[2],
>USB4 node always existed but outside of ti-sysc control before [2] and did
>not
>conflict with the target-module node added in [1].
>
>> causing boot failures.
>
>on what boards? Is it affecting all of them?

I have a dra7-evm board and see failure on it. This should also affect
Dra76-evm, am572x beagle boards, am574x as they all pull in dra74x.dtsi.
Will mention these in the v3 update.

Thanks,
Gowtham 

> USB4 node is present only in DRA74x variants so
>> keeping the entry in dra74x.dtsi and removing it from the top level
>> interconnect hierarchy dra7-l4.dtsi file.
>>
>> Since USB4 is only included in DRA74x variants, remove its reference
>> for AM5718, DRA71x and DR72x boards.
>>
>> [1]: commit 549fce068a311 ("ARM: dts: dra7: Add l4 interconnect
>> hierarchy and ti-sysc data")
>> [2]: commit c7b72abca61ec ("ARM: OMAP2+: Drop legacy platform data for
>> dra7 dwc3")
>>
>> Fixes: c7b72abca61ec ("ARM: OMAP2+: Drop legacy platform data for dra7
>dwc3")
>> Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
>> ---
>> v2:

      reply	other threads:[~2021-05-26 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 17:20 [PATCH v2] ARM: dts: dra7: Fix duplicate USB4 device node Gowtham Tammana
2021-05-26 18:01 ` Suman Anna
2021-05-26 19:48   ` Tammana, Gowtham [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=555c768263cc48499b299c0b595fcb94@ti.com \
    --to=g-tammana@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --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 \
    --cc=tony@atomide.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).