public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Rob Herring <robh@kernel.org>
Cc: krzk+dt@kernel.org, conor+dt@kernel.org, matthias.bgg@gmail.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH 1/3] dt-bindings: arm: mediatek: mmsys: Allow single vdo/mmsys endpoint
Date: Wed, 14 Jan 2026 09:27:33 +0100	[thread overview]
Message-ID: <b38823d4-1bce-496b-a063-75f2139aa3bd@collabora.com> (raw)
In-Reply-To: <20260113225346.GA367211-robh@kernel.org>

Il 13/01/26 23:53, Rob Herring ha scritto:
> On Thu, Jan 08, 2026 at 03:39:32PM +0100, AngeloGioacchino Del Regno wrote:
>> The hardware supports using just a single output while leaving all
>> of the others unconfigured (disabled), but the binding did not
>> really allow specifying a single endpoint@0, because in this case
>> one must either:
>>   - Call the subnode `endpoint` and not declare any address and/or
>>     size cells; or
>>   - Call the subnode `endpoint@0` and have at least one more other
>>     endpoint(@1 or @2), and declare address/size cells.
>>
>> Allow specifying a single `endpoint` subnode, without the `@0`
>> implicit suffix to suppress warnings happening on this kind of
>> valid usecase.
> 
> This series isn't needed. We've dropped this check from dtc. I'll do a
> sync with upstream.
> 
> In any case, it's also a W=1 warning which wouldn't be my top priority.
> 
> Rob

Oh, okay! Thanks for the feedback :D

Cheers,
Angelo


      reply	other threads:[~2026-01-14  8:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08 14:39 [PATCH 1/3] dt-bindings: arm: mediatek: mmsys: Allow single vdo/mmsys endpoint AngeloGioacchino Del Regno
2026-01-08 14:39 ` [PATCH 2/3] arm64: dts: mediatek: mt8195-cherry: Fix warnings for vdosys0 endpoint AngeloGioacchino Del Regno
2026-01-12  8:18   ` Chen-Yu Tsai
2026-01-08 14:39 ` [PATCH 3/3] arm64: dts: mediatek: mt8188-geralt: " AngeloGioacchino Del Regno
2026-01-12  8:18   ` Chen-Yu Tsai
2026-01-12  7:49 ` [PATCH 1/3] dt-bindings: arm: mediatek: mmsys: Allow single vdo/mmsys endpoint Chen-Yu Tsai
2026-01-13 22:53 ` Rob Herring
2026-01-14  8:27   ` AngeloGioacchino Del Regno [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=b38823d4-1bce-496b-a063-75f2139aa3bd@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@collabora.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh@kernel.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