From: "Heiko Stübner" <heiko@sntech.de>
To: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Sandy Huang <hjc@rock-chips.com>,
Andy Yan <andy.yan@rock-chips.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Mark Yao <markyao0591@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
kernel@collabora.com, Alexandre ARNOUD <aarnoud@me.com>,
Luis de Arquer <ldearquer@gmail.com>
Subject: Re: [PATCH v5 1/4] dt-bindings: display: bridge: Add schema for Synopsys DW HDMI QP TX IP
Date: Sat, 31 Aug 2024 15:58:31 +0200 [thread overview]
Message-ID: <10210346.L8ug28u51p@diego> (raw)
In-Reply-To: <57wj2vwjv7eehlix2bmvbm3z4agv5fsyp6vmwwqzotkdsadx7n@azqg2kkaeuxz>
Hi,
Am Samstag, 31. August 2024, 08:16:26 CEST schrieb Krzysztof Kozlowski:
> On Sat, Aug 31, 2024 at 12:55:29AM +0300, Cristian Ciocaltea wrote:
> > + clocks:
> > + minItems: 4
> > + maxItems: 6
> > + items:
> > + - description: Peripheral/APB bus clock
> > + - description: EARC RX biphase clock
> > + - description: Reference clock
> > + - description: Audio interface clock
> > + additionalItems: true
>
> What is the usefulness of all this? How can you even be sure that each
> implementation of this core will have exactly these clocks?
>
> > +
> > + clock-names:
> > + minItems: 4
> > + maxItems: 6
> > + items:
> > + - const: pclk
> > + - const: earc
> > + - const: ref
> > + - const: aud
> > + additionalItems: true
> > +
> > + interrupts:
> > + minItems: 4
> > + maxItems: 5
> > + items:
> > + - description: AVP Unit interrupt
> > + - description: CEC interrupt
> > + - description: eARC RX interrupt
> > + - description: Main Unit interrupt
>
> If these are real pins, then this seems more possible, but
> additionalItems does not make me happy.
So while not "pins", the interrupts are separately specified in the
SoC's list of interrupts in the GIC:
RK3588 has:
201 irq_hdmitx0_oavp
202 irq_hdmitx0_ocec
203 irq_hdmitx0_oearcrx
204 irq_hdmitx0_omain
392 irq_hdmitx0_hpd
and another set of all of them for hdmitx1
and RK3576 using the same hdmi IP has:
370 irq_hdmitx_oavp
371 irq_hdmitx_ocec
372 irq_hdmitx_oearcrx
373 irq_hdmitx_omain
399 irq_hdmitx_hpd
so I guess the fifth interrupt is meant to be the hotplug?
Though I guess this should be specificed in the name-list too.
From the SoC's manual it looks like the controller is set up from
different modules.
Like AVP is the audio-video-packet-module, there is a Main and CEC Module
as well as a eARC RX controller inside. I'd guess it might be possible
other SoC vendors could leave out specific modules?
TL;DR I think those clocks and interrupts are dependent on how the
IP core was synthesized, so for now I'd think we can only guarantee
that they are true for rk3588 and rk3576.
So I guess they should move to the rockchip-specific part of the binding
until we have more hdmi-qp controllers in the field?
Heiko
next prev parent reply other threads:[~2024-08-31 13:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 21:55 [PATCH v5 0/4] Add initial support for the Rockchip RK3588 HDMI TX Controller Cristian Ciocaltea
2024-08-30 21:55 ` [PATCH v5 1/4] dt-bindings: display: bridge: Add schema for Synopsys DW HDMI QP TX IP Cristian Ciocaltea
2024-08-31 6:16 ` Krzysztof Kozlowski
2024-08-31 13:58 ` Heiko Stübner [this message]
[not found] ` <aee7b364-39df-4eb4-a823-4e734f104982@collabora.com>
2024-09-01 6:40 ` Andy Yan
2024-09-01 10:23 ` Krzysztof Kozlowski
2024-08-30 21:55 ` [PATCH v5 2/4] drm/bridge: synopsys: Add DW HDMI QP TX Controller support library Cristian Ciocaltea
2024-09-08 9:11 ` Markus Elfring
2024-09-10 15:52 ` Cristian Ciocaltea
2024-08-30 21:55 ` [PATCH v5 3/4] dt-bindings: display: rockchip: Add schema for RK3588 HDMI TX Controller Cristian Ciocaltea
2024-08-31 6:13 ` Krzysztof Kozlowski
2024-08-30 21:55 ` [PATCH v5 4/4] drm/rockchip: Add basic RK3588 HDMI output support Cristian Ciocaltea
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=10210346.L8ug28u51p@diego \
--to=heiko@sntech.de \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=aarnoud@me.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hjc@rock-chips.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=ldearquer@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=markyao0591@gmail.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=tzimmermann@suse.de \
/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