From: Rob Herring <robh@kernel.org>
To: Pin-yen Lin <treapking@chromium.org>
Cc: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
CK Hu <ck.hu@mediatek.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, Fabien Parent <fparent@baylibre.com>,
Jitao shi <jitao.shi@mediatek.com>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 2/2] arm64: dts: mt8183: Add port node to dpi node
Date: Mon, 14 Oct 2024 12:38:53 -0500 [thread overview]
Message-ID: <CAL_JsqJM3sHECd9U1aJ+HGvTarLxmrNFkXq-k4jGU4S6h8nO3A@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqJngFLbNtT3m--xi5nNt9o7M=se8Qkhf20TxRCj-G=6dA@mail.gmail.com>
On Fri, Sep 13, 2024 at 4:37 PM Rob Herring <robh@kernel.org> wrote:
>
> On Thu, Sep 12, 2024 at 9:44 AM Pin-yen Lin <treapking@chromium.org> wrote:
> >
> > Add the port node to fix the binding schema check.
>
> The dsi node has the same issue.
This is still causing warnings in the tree. Please respin the patch.
>
> > Fixes: 009d855a26fd ("arm64: dts: mt8183: add dpi node to mt8183")
> > Signed-off-by: Pin-yen Lin <treapking@chromium.org>
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202409110843.Hm5W9upr-lkp@intel.com/
> >
> > ---
> >
> > arch/arm64/boot/dts/mediatek/mt8183.dtsi | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
> > index 266441e999f2..0a6578aacf82 100644
> > --- a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
> > +++ b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
> > @@ -1845,6 +1845,10 @@ dpi0: dpi@14015000 {
> > <&mmsys CLK_MM_DPI_MM>,
> > <&apmixedsys CLK_APMIXED_TVDPLL>;
> > clock-names = "pixel", "engine", "pll";
> > +
> > + port {
> > + dpi_out: endpoint { };
> > + };
> > };
> >
> > mutex: mutex@14016000 {
> > --
> > 2.46.0.662.g92d0881bb0-goog
> >
next prev parent reply other threads:[~2024-10-14 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 14:43 [PATCH 0/2] Fix dtcheck warnings for mediatek,dpi binding Pin-yen Lin
2024-09-12 14:43 ` [PATCH 1/2] dt-bindings: display: mediatek: dpi: Add power-domains to the bindings Pin-yen Lin
2024-09-13 21:39 ` Rob Herring
2024-09-12 14:43 ` [PATCH 2/2] arm64: dts: mt8183: Add port node to dpi node Pin-yen Lin
2024-09-13 21:37 ` Rob Herring
2024-10-14 17:38 ` Rob Herring [this message]
2024-10-02 9:33 ` (subset) [PATCH 0/2] Fix dtcheck warnings for mediatek,dpi binding AngeloGioacchino Del Regno
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=CAL_JsqJM3sHECd9U1aJ+HGvTarLxmrNFkXq-k4jGU4S6h8nO3A@mail.gmail.com \
--to=robh@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=ck.hu@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fparent@baylibre.com \
--cc=jitao.shi@mediatek.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=lkp@intel.com \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=treapking@chromium.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;
as well as URLs for NNTP newsgroup(s).