From: Tony Lindgren <tony@atomide.com>
To: Roger Quadros <rogerq@ti.com>
Cc: robh+dt@kernel.org, s-anna@ti.com, nm@ti.com, lokeshvutla@ti.com,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] ARM: dts: dra7: Separate AM57 dtsi files
Date: Fri, 12 Apr 2019 09:57:33 -0700 [thread overview]
Message-ID: <20190412165733.GA2839@atomide.com> (raw)
In-Reply-To: <20190408094249.29894-1-rogerq@ti.com>
* Roger Quadros <rogerq@ti.com> [190408 09:43]:
> AM5 and DRA7 SoC families have different set of modules
> in them so the SoC sepecific dtsi files need to be separated.
>
> e.g. Some of the major differences between AM576 and DRA76
>
> DRA76x AM576x
>
> USB3 x
> USB4 x
> ATL x
> VCP x
> MLB x
> ISS x
> PRU-ICSS1 x
> PRU-ICSS2 x
>
> This patch only deals with disabling USB3, USB4 and ATL for
> AM57 variants.
>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
> Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
> ---
>
> Changelog:
>
> v2:
> - fix am57xx-beagle-x15-common.dtsi
Thanks applying this into omap-for-v5.2/dt.
Regards,
Tony
prev parent reply other threads:[~2019-04-12 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 13:28 [PATCH 0/2] ARM: dts: dra7: Introduce AM57 dtsi files Roger Quadros
2019-04-05 13:28 ` [PATCH 1/2] dt-binding: arm: omap: Add information for AM5748 Roger Quadros
2019-04-12 16:56 ` Tony Lindgren
2019-04-05 13:28 ` [PATCH 2/2] ARM: dts: dra7: Separate AM57 dtsi files Roger Quadros
2019-04-06 10:10 ` Lokesh Vutla
2019-04-08 9:28 ` Roger Quadros
2019-04-08 9:42 ` [PATCH v2 1/1] " Roger Quadros
2019-04-12 16:57 ` 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=20190412165733.GA2839@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
--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).