From: Andreas Kemnade <andreas@kemnade.info>
To: Andrew Davis <afd@ti.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
"Colin Foster" <colin.foster@in-advantage.com>,
"Olof Johansson" <olof@lixom.net>,
"Arnd Bergmann" <arnd@arndb.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 1/2] ARM: dts: omap: Drop ti,omap36xx compatible
Date: Mon, 27 Mar 2023 21:18:38 +0200 [thread overview]
Message-ID: <20230327211838.580af7a9@aktux> (raw)
In-Reply-To: <20230216153339.19987-2-afd@ti.com>
On Thu, 16 Feb 2023 09:33:38 -0600
Andrew Davis <afd@ti.com> wrote:
> This was not matched anywhere and provides no additional information.
>
> Signed-off-by: Andrew Davis <afd@ti.com>
> ---
> arch/arm/boot/dts/omap3-beagle-xm.dts | 2 +-
> arch/arm/boot/dts/omap3-cm-t3730.dts | 2 +-
> arch/arm/boot/dts/omap3-igep0020-rev-f.dts | 2 +-
> arch/arm/boot/dts/omap3-igep0020.dts | 2 +-
> arch/arm/boot/dts/omap3-igep0030-rev-g.dts | 2 +-
> arch/arm/boot/dts/omap3-igep0030.dts | 2 +-
> arch/arm/boot/dts/omap3-lilly-dbb056.dts | 2 +-
> arch/arm/boot/dts/omap3-n9.dts | 2 +-
> arch/arm/boot/dts/omap3-n950.dts | 2 +-
> arch/arm/boot/dts/omap3-overo-storm-alto35.dts | 2 +-
> arch/arm/boot/dts/omap3-overo-storm-chestnut43.dts | 2 +-
> arch/arm/boot/dts/omap3-overo-storm-gallop43.dts | 2 +-
> arch/arm/boot/dts/omap3-overo-storm-palo35.dts | 2 +-
> arch/arm/boot/dts/omap3-overo-storm-palo43.dts | 2 +-
> arch/arm/boot/dts/omap3-overo-storm-summit.dts | 2 +-
> arch/arm/boot/dts/omap3-overo-storm-tobi.dts | 2 +-
> arch/arm/boot/dts/omap3-overo-storm-tobiduo.dts | 2 +-
> arch/arm/boot/dts/omap3-pandora-1ghz.dts | 2 +-
> arch/arm/boot/dts/omap3-sbc-t3730.dts | 2 +-
> arch/arm/boot/dts/omap3-sniper.dts | 2 +-
> arch/arm/boot/dts/omap3-zoom3.dts | 2 +-
> 21 files changed, 21 insertions(+), 21 deletions(-)
>
hmm, we have
drivers/clk/ti/dpll.c: of_machine_is_compatible("ti,omap36xx"))
but that is more completely
if ((of_machine_is_compatible("ti,omap3630") ||
of_machine_is_compatible("ti,omap36xx")) &&
so missing omap36xx will not harm if 3630 is there. SO this should
be probably ok.
Regards,
Andreas
next prev parent reply other threads:[~2023-03-27 19:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 15:33 [RFC 0/2] Convert omap.txt to DT schema Andrew Davis
2023-02-16 15:33 ` [RFC 1/2] ARM: dts: omap: Drop ti,omap36xx compatible Andrew Davis
2023-03-27 19:18 ` Andreas Kemnade [this message]
2023-03-28 5:01 ` Tony Lindgren
2023-03-28 7:06 ` Andreas Kemnade
2023-03-28 7:08 ` Tony Lindgren
2023-03-28 7:27 ` Tony Lindgren
2023-02-16 15:33 ` [RFC 2/2] WIP: dt-bindings: omap: Convert omap.txt to yaml Andrew Davis
2023-02-16 16:08 ` H. Nikolaus Schaller
2023-02-16 16:19 ` Andrew Davis
2023-02-16 16:43 ` H. Nikolaus Schaller
2023-02-16 16:41 ` Rob Herring
2023-02-16 17:30 ` Andrew Davis
2023-02-17 5:48 ` [RFC 0/2] Convert omap.txt to DT schema 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=20230327211838.580af7a9@aktux \
--to=andreas@kemnade.info \
--cc=afd@ti.com \
--cc=arnd@arndb.de \
--cc=bcousson@baylibre.com \
--cc=colin.foster@in-advantage.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--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).