[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250725202655.GA1826181-robh@kernel.org>
Date: Fri, 25 Jul 2025 15:26:55 -0500
From: Rob Herring <robh@...nel.org>
To: Chen-Yu Tsai <wenst@...omium.org>
Cc: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
linux-mediatek@...ts.infradead.org, herbert@...dor.apana.org.au,
davem@...emloft.net, krzk+dt@...nel.org, conor+dt@...nel.org,
chunkuang.hu@...nel.org, p.zabel@...gutronix.de, airlied@...il.com,
simona@...ll.ch, maarten.lankhorst@...ux.intel.com,
mripard@...nel.org, tzimmermann@...e.de, jassisinghbrar@...il.com,
mchehab@...nel.org, matthias.bgg@...il.com,
chunfeng.yun@...iatek.com, vkoul@...nel.org, kishon@...nel.org,
sean.wang@...nel.org, linus.walleij@...aro.org, lgirdwood@...il.com,
broonie@...nel.org, andersson@...nel.org,
mathieu.poirier@...aro.org, daniel.lezcano@...aro.org,
tglx@...utronix.de, atenart@...nel.org, jitao.shi@...iatek.com,
ck.hu@...iatek.com, houlong.wei@...iatek.com,
kyrie.wu@...iatek.corp-partner.google.com, andy.teng@...iatek.com,
tinghan.shen@...iatek.com, jiaxin.yu@...iatek.com,
shane.chien@...iatek.com, olivia.wen@...iatek.com,
granquet@...libre.com, eugen.hristev@...aro.org, arnd@...db.de,
sam.shih@...iatek.com, jieyy.yang@...iatek.com,
frank-w@...lic-files.de, mwalle@...nel.org, fparent@...libre.com,
linux-crypto@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linux-media@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-phy@...ts.infradead.org, linux-gpio@...r.kernel.org,
linux-remoteproc@...r.kernel.org, linux-sound@...r.kernel.org
Subject: Re: [PATCH 01/38] dt-bindings: display: mediatek: dpi: Allow
specifying resets
On Thu, Jul 24, 2025 at 05:16:21PM +0800, Chen-Yu Tsai wrote:
> On Thu, Jul 24, 2025 at 4:39 PM AngeloGioacchino Del Regno
> <angelogioacchino.delregno@...labora.com> wrote:
> >
> > Even though the DPI IP has a reset bit on all MediaTek SoCs, it
> > is optional, and has always been unused until MT8195; specifically:
> > on older SoCs, like MT8173, the reset bit is located in MMSYS, and
> > on newer SoCs, like MT8195, it is located in VDOSYS.
> >
> > For this reason, allow specifying the resets and reset-names on
> > all MediaTek SoCs.
> >
> > Those properties are optional because there are multiple ways to
> > reset this IP and the reset lines in MM/VDO are used only if the
> > IP cannot perform warm-reset.
> >
> > Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
> > ---
> > .../devicetree/bindings/display/mediatek/mediatek,dpi.yaml | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> > index b659d79393a8..eb4f276e8dc4 100644
> > --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> > +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> > @@ -102,6 +102,13 @@ properties:
> > - port@0
> > - port@1
> >
> > + resets:
> > + maxItems: 1
> > +
> > + reset-names:
> > + items:
> > + - const: dpi
> > +
>
> Do we really need the name if there is only one though?
Not really, but if it is already in use then easier to just fix the
binding than both the binding and dts.
Rob
Powered by blists - more mailing lists