public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
	Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>,
	sam@ravnborg.org, airlied@linux.ie, daniel@ffwll.ch,
	krzysztof.kozlowski+dt@linaro.org, jonathanh@nvidia.com,
	arnd@arndb.de, dri-devel@lists.freedesktop.org,
	devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 4/4] arm64: dts: smaug: Add display panel node
Date: Sat, 1 Oct 2022 11:53:12 +0200	[thread overview]
Message-ID: <a6b78a66-14ef-68bb-25df-2c2eb118a7d3@linaro.org> (raw)
In-Reply-To: <20220930211424.GA913368-robh@kernel.org>

On 30/09/2022 23:14, Rob Herring wrote:
>>>>> +		dc@54200000 {
>>>>> +			status = "okay";
>>>>
>>>> You should override by labels, not by full path.
>>>
>>> Why exactly is that? I've always stayed away from that (and asked others
>>> not to do so, at least on Tegra) because I find it impossible to parse
>>> for my human brain. Replicating the original full hierarchy makes it
>>> much more obvious to me where the changes are happening than the
>>> spaghetti-like mess that you get from overriding by label reference.
>>
>> Sure, it's entirely up to you. I forgot your preference.
>>
>> But it is a really nice way to have duplicated nodes and mistakes (which
>> happen from time to time).
> 
> We could have a schema or dtc check for that. We already warn for 
> duplicate unit-addresses which would catch some typos. Checking for a 
> node with only 'status' would probably work when that's the only 
> addition. Maybe status without a compatible would be better? We also 
> check for nodes without a specific schema, but child nodes in schemas 
> aren't handled.

Usually these are overrides of few properties and status=okay, so
looking for nodes without a compatible would work. Except for all the
cases where we do not have schema yet...

Best regards,
Krzysztof


      reply	other threads:[~2022-10-01  9:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 17:04 [PATCH 0/4] Add JDI LPM102A188A display panel support Diogo Ivo
2022-09-29 17:04 ` [PATCH 1/4] dt-bindings: display: Add bindings for JDI LPM102A188A Diogo Ivo
2022-09-30 10:49   ` Krzysztof Kozlowski
2022-10-03 17:06     ` Diogo Ivo
2022-10-04 11:05       ` Krzysztof Kozlowski
2022-10-04 16:37         ` Diogo Ivo
2022-09-29 17:05 ` [PATCH 2/4] drm/tegra: dsi: Clear enable register if powered by bootloader Diogo Ivo
2022-09-30 11:11   ` Thierry Reding
2022-10-03 18:13     ` Diogo Ivo
2022-09-29 17:05 ` [PATCH 3/4] drm/panel: Add driver for JDI LPM102A188A Diogo Ivo
2022-09-29 17:05 ` [PATCH 4/4] arm64: dts: smaug: Add display panel node Diogo Ivo
2022-09-30 10:51   ` Krzysztof Kozlowski
2022-09-30 11:15     ` Thierry Reding
2022-09-30 11:20       ` Krzysztof Kozlowski
2022-09-30 21:14         ` Rob Herring
2022-10-01  9:53           ` Krzysztof Kozlowski [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=a6b78a66-14ef-68bb-25df-2c2eb118a7d3@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=airlied@linux.ie \
    --cc=arnd@arndb.de \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=diogo.ivo@tecnico.ulisboa.pt \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sam@ravnborg.org \
    --cc=thierry.reding@gmail.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