devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Rob Herring <robh@kernel.org>
Cc: <devicetree@vger.kernel.org>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	<linux-kernel@vger.kernel.org>, Sinthu Raja <sinthu.raja@ti.com>,
	Sinthu Raja <sinthu.raja@mistralsolutions.com>,
	<linux-arm-kernel@lists.infradead.org>,
	Hari Nagalla <hnagalla@ti.com>
Subject: Re: [PATCH V2 2/4] dt-bindings: arm: ti: am642/am654: Allow for SoC only compatibles
Date: Tue, 5 Oct 2021 13:31:17 -0500	[thread overview]
Message-ID: <20211005183117.fndcsfjdfhjmidib@lantern> (raw)
In-Reply-To: <20211004185920.26iyyq3xz7vjam5i@gentile>

On 13:59-20211004, Nishanth Menon wrote:
> On 12:54-20211004, Rob Herring wrote:
> > On Sat, Sep 25, 2021 at 03:14:28PM -0500, Nishanth Menon wrote:
> > > Maintain consistency in K3 SoCs by allowing AM654 and AM642 platforms
> > > just state SoC compatibles without specific board specific compatibles
> > > aligned with what we have done for J721E/J7200 platforms as well.
> > 
> > This is the wrong direction IMO. Why do you want this other than 
> > alignment?
> 
> Many downstream boards tend not to have an specific compatible at least
> during initial phase and I would like folks to start using checks to
> make sure that the easy to catch issues via match against bindings are
> already handled.
> 
> I am curious as to why you think this is wrong - because we permit an
> alternative option that allows the board files to be less specific?


Thinking again, I get the rationale. We are attempting to be specific,
and this patch reverses the direction. Agreed. Will drop applying this
patch. Also, for future SoCs, will insist on being specific compatible.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

  reply	other threads:[~2021-10-05 18:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-25 20:14 [PATCH V2 0/4] arm64: dts: ti: k3-j721e/j7200: Introduce EVM compatible Nishanth Menon
2021-09-25 20:14 ` [PATCH V2 1/4] dt-bindings: arm: ti: Add missing compatibles for j721e/j7200 evms Nishanth Menon
2021-09-27 14:24   ` Suman Anna
2021-10-04 17:52   ` Rob Herring
2021-09-25 20:14 ` [PATCH V2 2/4] dt-bindings: arm: ti: am642/am654: Allow for SoC only compatibles Nishanth Menon
2021-09-27 14:26   ` Suman Anna
2021-10-04 17:54   ` Rob Herring
2021-10-04 18:59     ` Nishanth Menon
2021-10-05 18:31       ` Nishanth Menon [this message]
2021-09-25 20:14 ` [PATCH V2 3/4] arm64: dts: ti: k3-j721e-common-proc-board: Add j721e-evm compatible Nishanth Menon
2021-09-27 14:27   ` Suman Anna
2021-09-25 20:14 ` [PATCH V2 4/4] arm64: dts: ti: k3-j7200-common-proc-board: Add j7200-evm compatible Nishanth Menon
2021-09-27 14:27   ` Suman Anna
2021-10-05 22:56 ` (subset) [PATCH V2 0/4] arm64: dts: ti: k3-j721e/j7200: Introduce EVM compatible Nishanth Menon

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=20211005183117.fndcsfjdfhjmidib@lantern \
    --to=nm@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hnagalla@ti.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sinthu.raja@mistralsolutions.com \
    --cc=sinthu.raja@ti.com \
    --cc=vigneshr@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).