From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sandor Yu <sandor.yu@nxp.com>
Cc: "dmitry.baryshkov@linaro.org" <dmitry.baryshkov@linaro.org>,
"andrzej.hajda@intel.com" <andrzej.hajda@intel.com>,
"neil.armstrong@linaro.org" <neil.armstrong@linaro.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
"jonas@kwiboo.se" <jonas@kwiboo.se>,
"jernej.skrabec@gmail.com" <jernej.skrabec@gmail.com>,
"airlied@gmail.com" <airlied@gmail.com>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"vkoul@kernel.org" <vkoul@kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
"mripard@kernel.org" <mripard@kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
dl-linux-imx <linux-imx@nxp.com>,
Oliver Brown <oliver.brown@nxp.com>,
"alexander.stein@ew.tq-group.com"
<alexander.stein@ew.tq-group.com>,
"sam@ravnborg.org" <sam@ravnborg.org>
Subject: Re: [EXT] Re: [PATCH v18 3/8] dt-bindings: display: bridge: Add Cadence MHDP8501
Date: Tue, 29 Oct 2024 08:21:04 +0100 [thread overview]
Message-ID: <c0b9157c-48cd-41a7-ab38-c0334f1e5af7@kernel.org> (raw)
In-Reply-To: <PAXPR04MB9448D20D5EDE86DEF060222CF44B2@PAXPR04MB9448.eurprd04.prod.outlook.com>
On 29/10/2024 08:17, Sandor Yu wrote:
>>
>> On Tue, Oct 29, 2024 at 02:02:11PM +0800, Sandor Yu wrote:
>>> + interrupts:
>>> + items:
>>> + - description: Hotplug cable plugin.
>>> + - description: Hotplug cable plugout.
>>> +
>>> + interrupt-names:
>>> + items:
>>> + - const: plug_in
>>> + - const: plug_out
>>> +
>>> + data-lanes:
>>> + $ref: /schemas/media/video-interfaces.yaml#/properties/data-lanes
>>> + minItems: 4
>>> + maxItems: 4
>>> + description: Lane reordering for HDMI or DisplayPort interface.
>>
>> Please look how existing bindings do it. data-lanes is a property of port.
>> Otherwise why would you like this to be applied to the input?
>
> 'lane reordering' is a feature of the MHDP IP, and different boards have different mappings.
Yeah, and?
>
> Benjamin comments in v16, the imx8mq-zii-ultra board's lane mapping differs from the default in my driver,
> so we need to treat it as an input.
But HDMI is not your input port. At least that's what few lines below!
This is confusing.
>
> As data-lanes is a property of port, so there is no exist property could be reused,
data-lanes, really, what is the problem here?
> How about revert 'data-lanes' back to my previous implementation of 'lane-mapping'?
No.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-29 7:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 6:02 [PATCH v18 0/8] Initial support Cadence MHDP8501(HDMI/DP) for i.MX8MQ Sandor Yu
2024-10-29 6:02 ` [PATCH v18 1/8] drm: bridge: Cadence: Create MHDP helper driver Sandor Yu
2024-10-31 19:51 ` Dmitry Baryshkov
2024-11-05 14:05 ` Sandor Yu
2024-10-29 6:02 ` [PATCH v18 2/8] phy: Add HDMI configuration options Sandor Yu
2024-12-04 13:46 ` Vinod Koul
2024-10-29 6:02 ` [PATCH v18 3/8] dt-bindings: display: bridge: Add Cadence MHDP8501 Sandor Yu
2024-10-29 6:57 ` Krzysztof Kozlowski
2024-10-29 7:17 ` [EXT] " Sandor Yu
2024-10-29 7:21 ` Krzysztof Kozlowski [this message]
2024-10-29 9:47 ` Sandor Yu
2024-10-31 19:55 ` Dmitry Baryshkov
2024-10-31 20:56 ` Dmitry Baryshkov
2024-11-05 14:05 ` Sandor Yu
2024-10-29 6:02 ` [PATCH v18 4/8] drm: bridge: Cadence: Add MHDP8501 DP/HDMI driver Sandor Yu
2024-10-29 6:02 ` [PATCH v18 5/8] dt-bindings: phy: Add Freescale iMX8MQ DP and HDMI PHY Sandor Yu
2024-10-29 6:02 ` [PATCH v18 6/8] phy: freescale: Add DisplayPort/HDMI Combo-PHY driver for i.MX8MQ Sandor Yu
2024-10-31 21:15 ` Dmitry Baryshkov
2024-11-05 14:05 ` Sandor Yu
2024-11-06 9:29 ` Dmitry Baryshkov
2024-11-26 14:12 ` Sandor Yu
2024-11-30 8:28 ` Dmitry Baryshkov
2024-11-07 13:43 ` Dmitry Baryshkov
2024-11-26 14:12 ` [EXT] " Sandor Yu
2024-11-30 8:29 ` Dmitry Baryshkov
2024-12-09 8:16 ` Sandor Yu
2024-12-09 10:13 ` Dmitry Baryshkov
2024-10-29 6:02 ` [PATCH v18 7/8] arm64: dts: imx8mq: Add DCSS + HDMI/DP display pipeline Sandor Yu
2024-10-29 6:02 ` [PATCH v18 8/8] arm64: dts: imx8mq: tqma8mq-mba8mx: Enable HDMI support Sandor Yu
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=c0b9157c-48cd-41a7-ab38-c0334f1e5af7@kernel.org \
--to=krzk@kernel.org \
--cc=airlied@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=oliver.brown@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sam@ravnborg.org \
--cc=sandor.yu@nxp.com \
--cc=shawnguo@kernel.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).