From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] ARM: dts: AM43x-epos-evm: Add AM438x compatible string for epos
Date: Mon, 19 Oct 2015 09:06:07 -0700 [thread overview]
Message-ID: <20151019160606.GC22043@atomide.com> (raw)
In-Reply-To: <1444885808-6306-3-git-send-email-j-keerthy@ti.com>
* Keerthy <j-keerthy@ti.com> [151014 22:14]:
> Add AM438x compatible property to identify the SoCs on epos evms.
>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> ---
>
> Changes in v2:
>
> * Rebased to latest 4.3-rc5
>
> Documentation/devicetree/bindings/arm/omap/omap.txt | 5 ++++-
> arch/arm/boot/dts/am43x-epos-evm.dts | 2 +-
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/arm/omap/omap.txt b/Documentation/devicetree/bindings/arm/omap/omap.txt
> index 9f4e513..dc3b5f2 100644
> --- a/Documentation/devicetree/bindings/arm/omap/omap.txt
> +++ b/Documentation/devicetree/bindings/arm/omap/omap.txt
> @@ -100,6 +100,9 @@ SoCs:
> - AM4372
> compatible = "ti,am4372", "ti,am43"
>
> +- AM438x
> + compatible = "ti,am438x", "ti,am43"
> +
The compatible strings should not have x, this should be
"ti,am438" instead. But my guess is that we are better off
adding proper SoC detection to avoid needing a separate dts
file for each SoC revision. Ideally booting with "ti,am43"
should be enough and we can initialize the rest during
runtime.
Regards,
Tony
next prev parent reply other threads:[~2015-10-19 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 5:10 [PATCH v2 0/3] ARM: OMAP2+: Optimize soc_is calls Keerthy
2015-10-15 5:10 ` [PATCH v2 1/3] ARM: OMAP2: DRA7: Modify optimize string comparisons in " Keerthy
2015-10-16 19:09 ` Tony Lindgren
2015-10-15 5:10 ` [PATCH v2 2/3] ARM: dts: AM43x-epos-evm: Add AM438x compatible string for epos Keerthy
2015-10-19 16:06 ` Tony Lindgren [this message]
2015-10-15 5:10 ` [PATCH v2 3/3] ARM: OMAP2: AM43XX: Modify optimize string comparisons in soc_is calls Keerthy
2015-10-16 19:11 ` Tony Lindgren
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=20151019160606.GC22043@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).