From: Markus Schneider-Pargmann <msp@baylibre.com>
To: Rob Herring <robh@kernel.org>
Cc: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Vinod Koul <vkoul@kernel.org>, Sam Ravnborg <sam@ravnborg.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/7] dt-bindings: mediatek, dp: Add Display Port binding
Date: Wed, 20 Oct 2021 21:34:07 +0200 [thread overview]
Message-ID: <20211020193407.meektqms4psltg34@blmsp> (raw)
In-Reply-To: <CAL_Jsq+QwEPNEztD+yg-UO8gWf_X=E-n0_HMYJsGxteZAZparg@mail.gmail.com>
Hi Rob,
On Mon, Oct 18, 2021 at 02:38:33PM -0500, Rob Herring wrote:
> On Mon, Oct 18, 2021 at 9:19 AM Markus Schneider-Pargmann
> <msp@baylibre.com> wrote:
> >
> > Hi Rob,
> >
> > On Mon, Oct 11, 2021 at 07:43:16PM -0500, Rob Herring wrote:
> > > On Mon, Oct 11, 2021 at 11:46:19AM +0200, Markus Schneider-Pargmann wrote:
> > > > This controller is present on several mediatek hardware. Currently
> > > > mt8195 and mt8395 have this controller without a functional difference,
> > > > so only one compatible field is added.
> > > >
> > > > The controller can have two forms, as a normal display port and as an
> > > > embedded display port.
> > > >
> > > > Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
> > > > ---
> > > > .../display/mediatek/mediatek,dp.yaml | 89 +++++++++++++++++++
> > > > 1 file changed, 89 insertions(+)
> > > > create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,dp.yaml
> > > >
> > > > diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dp.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,dp.yaml
> > > > new file mode 100644
> > > > index 000000000000..f7a35962c23b
> > > > --- /dev/null
> > > > +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dp.yaml
> > > > @@ -0,0 +1,89 @@
> > > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > > > +%YAML 1.2
> > > > +---
> > > > +$id: http://devicetree.org/schemas/display/mediatek/mediatek,dp.yaml#
> > > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > > +
> > > > +title: Mediatek Display Port Controller
> > > > +
> > > > +maintainers:
> > > > + - CK Hu <ck.hu@mediatek.com>
> > > > + - Jitao shi <jitao.shi@mediatek.com>
> > > > +
> > > > +description: |
> > > > + Device tree bindings for the Mediatek (embedded) Display Port controller
> > > > + present on some Mediatek SoCs.
> > > > +
> > > > +properties:
> > > > + compatible:
> > > > + enum:
> > > > + - mediatek,mt8195-edp_tx
> > > > + - mediatek,mt8195-dp_tx
> > >
> > > Are these blocks different?
> >
> > Good point, the registers of these blocks are described in its own
> > chapter each. Also I do need to distinguish between both in the driver.
> > Would you suggest making this distinction differently or keep it as two
> > compatibles?
>
> If the registers are all the same, then it should be the same
> compatible. If you still need to distinguish, then you should have a
> panel or connector node that will let you do that.
Thank you. Good idea to check with the connector node, I have changed it
as you suggested.
>
> Also, s/_/-/ in the compatible string.
Done.
Thanks,
Markus
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2021-10-20 19:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 9:46 [PATCH v4 0/7] drm/mediatek: Add mt8195 DisplayPort driver Markus Schneider-Pargmann
2021-10-11 9:46 ` [PATCH v4 1/7] dt-bindings: mediatek,dpintf: Add DP_INTF binding Markus Schneider-Pargmann
2021-10-11 13:36 ` Rob Herring
2021-10-11 13:43 ` Markus Schneider-Pargmann
2021-10-11 18:41 ` Rob Herring
2021-10-11 23:44 ` Rob Herring
2021-10-20 19:13 ` Markus Schneider-Pargmann
2021-10-11 9:46 ` [PATCH v4 2/7] dt-bindings: mediatek,dp: Add Display Port binding Markus Schneider-Pargmann
2021-10-11 13:36 ` [PATCH v4 2/7] dt-bindings: mediatek, dp: " Rob Herring
2021-10-11 13:44 ` Markus Schneider-Pargmann
2021-10-12 0:43 ` Rob Herring
2021-10-18 14:19 ` Markus Schneider-Pargmann
2021-10-18 19:38 ` Rob Herring
2021-10-20 19:34 ` Markus Schneider-Pargmann [this message]
2021-10-11 9:46 ` [PATCH v4 3/7] drm/edid: Add cea_sad helpers for freq/length Markus Schneider-Pargmann
2021-10-11 9:46 ` [PATCH v4 4/7] video/hdmi: Add audio_infoframe packing for DP Markus Schneider-Pargmann
2021-10-11 9:46 ` [PATCH v4 5/7] drm/mediatek: dpi: Add dpintf support Markus Schneider-Pargmann
2021-10-11 9:46 ` [PATCH v4 6/7] phy: phy-mtk-dp: Add driver for DP phy Markus Schneider-Pargmann
2021-10-11 9:46 ` [PATCH v4 7/7] drm/mediatek: Add mt8195 DisplayPort driver Markus Schneider-Pargmann
2021-10-11 21:10 ` kernel test robot
2021-10-11 21:45 ` kernel test robot
2021-10-11 23:57 ` 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=20211020193407.meektqms4psltg34@blmsp \
--to=msp@baylibre.com \
--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=p.zabel@pengutronix.de \
--cc=robh@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).