From: Rob Herring <robh@kernel.org>
To: Markus Schneider-Pargmann <msp@baylibre.com>
Cc: devicetree@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
linux-mediatek@lists.infradead.org, Vinod Koul <vkoul@kernel.org>,
dri-devel@lists.freedesktop.org, linux-phy@lists.infradead.org
Subject: Re: [PATCH v5 1/7] dt-bindings: mediatek,dpi: Add DP_INTF compatible
Date: Thu, 21 Oct 2021 08:30:05 -0500 [thread overview]
Message-ID: <1634823005.130125.353182.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20211021092707.3562523-2-msp@baylibre.com>
On Thu, 21 Oct 2021 11:27:01 +0200, Markus Schneider-Pargmann wrote:
> DP_INTF is similar to DPI but does not have the exact same feature set
> or register layouts.
>
> DP_INTF is the sink of the display pipeline that is connected to the
> DisplayPort controller and encoder unit. It takes the same clocks as
> DPI.
>
> Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
> ---
>
> Notes:
> Changes v4 -> v5:
> - Newly created patch after realizing that the specific clocks for dpintf were
> the same as engine and pixel clocks.
>
> .../bindings/display/mediatek/mediatek,dpi.yaml | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
Running 'make dtbs_check' with the schema in this patch gives the
following warnings. Consider if they are expected or the schema is
incorrect. These may not be new warnings.
Note that it is not yet a requirement to have 0 warnings for dtbs_check.
This will change in the future.
Full log is available here: https://patchwork.ozlabs.org/patch/1544237
dpi@14014000: Additional properties are not allowed ('ports' was unexpected)
arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dt.yaml
arch/arm/boot/dts/mt7623n-rfb-emmc.dt.yaml
dpi@14014000: compatible: Additional items are not allowed ('mediatek,mt2701-dpi' was unexpected)
arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dt.yaml
arch/arm/boot/dts/mt7623n-rfb-emmc.dt.yaml
dpi@14014000: compatible: ['mediatek,mt7623-dpi', 'mediatek,mt2701-dpi'] is too long
arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dt.yaml
arch/arm/boot/dts/mt7623n-rfb-emmc.dt.yaml
dpi@14014000: 'port' is a required property
arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dt.yaml
arch/arm/boot/dts/mt7623n-rfb-emmc.dt.yaml
dpi@1401d000: Additional properties are not allowed ('power-domains' was unexpected)
arch/arm64/boot/dts/mediatek/mt8173-elm.dt.yaml
arch/arm64/boot/dts/mediatek/mt8173-elm-hana.dt.yaml
arch/arm64/boot/dts/mediatek/mt8173-elm-hana-rev7.dt.yaml
arch/arm64/boot/dts/mediatek/mt8173-evb.dt.yaml
next prev parent reply other threads:[~2021-10-21 13:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 9:27 [PATCH v5 0/7] drm/mediatek: Add mt8195 DisplayPort driver Markus Schneider-Pargmann
2021-10-21 9:27 ` [PATCH v5 1/7] dt-bindings: mediatek,dpi: Add DP_INTF compatible Markus Schneider-Pargmann
2021-10-21 13:30 ` Rob Herring [this message]
2021-10-27 20:32 ` Rob Herring
2021-10-21 9:27 ` [PATCH v5 2/7] dt-bindings: mediatek,dp: Add Display Port binding Markus Schneider-Pargmann
2021-10-21 13:30 ` Rob Herring
2021-10-22 23:19 ` Rob Herring
2021-10-24 15:36 ` Markus Schneider-Pargmann
2021-10-21 9:27 ` [PATCH v5 3/7] drm/edid: Add cea_sad helpers for freq/length Markus Schneider-Pargmann
2021-10-21 9:27 ` [PATCH v5 4/7] video/hdmi: Add audio_infoframe packing for DP Markus Schneider-Pargmann
2021-10-21 9:27 ` [PATCH v5 5/7] drm/mediatek: dpi: Add dpintf support Markus Schneider-Pargmann
2021-10-21 9:27 ` [PATCH v5 6/7] phy: phy-mtk-dp: Add driver for DP phy Markus Schneider-Pargmann
2021-10-22 5:12 ` Vinod Koul
2021-10-22 13:06 ` Markus Schneider-Pargmann
2021-10-25 7:20 ` Vinod Koul
2021-10-21 9:27 ` [PATCH v5 7/7] drm/mediatek: Add mt8195 DisplayPort driver Markus Schneider-Pargmann
2021-10-31 5:17 ` kernel test robot
2021-11-06 16:33 ` kernel test robot
2021-11-12 1:29 ` kernel test robot
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=1634823005.130125.353182.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=chunkuang.hu@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=msp@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).