mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Alain Volmat <avolmat@me.com>,
	Patrice Chotard <patrice.chotard@foss.st.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 12/14] ARM: dts: sti: addition of display nodes for stih418 platform
Date: Fri, 28 Jul 2023 09:24:03 +0200	[thread overview]
Message-ID: <0374b5b4-abc8-9aed-e49c-21287f415734@linaro.org> (raw)
In-Reply-To: <20230727215141.53910-13-avolmat@me.com>

On 27/07/2023 23:51, Alain Volmat wrote:
> Addition of a first set of nodes (compositor/tvout/hdmi/dvo) in order
> to allow graphic plane usage via HDMI or DVO on the stih418 based boards.
> 
> Signed-off-by: Alain Volmat <avolmat@me.com>
> ---
>  arch/arm/boot/dts/st/stih418-clock.dtsi |   2 +-
>  arch/arm/boot/dts/st/stih418.dtsi       | 154 ++++++++++++++++++++++++
>  2 files changed, 155 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm/boot/dts/st/stih418-clock.dtsi b/arch/arm/boot/dts/st/stih418-clock.dtsi
> index e1749e92a2e7..93641df58bf2 100644
> --- a/arch/arm/boot/dts/st/stih418-clock.dtsi
> +++ b/arch/arm/boot/dts/st/stih418-clock.dtsi
> @@ -17,7 +17,7 @@ clk_sysin: clk-sysin {
>  	clk_tmdsout_hdmi: clk-tmdsout-hdmi {
>  		#clock-cells = <0>;
>  		compatible = "fixed-clock";
> -		clock-frequency = <0>;
> +		clock-frequency = <594000000>;
>  	};
>  
>  	clocks {
> diff --git a/arch/arm/boot/dts/st/stih418.dtsi b/arch/arm/boot/dts/st/stih418.dtsi
> index b35b9b7a7ccc..b41de235fffa 100644
> --- a/arch/arm/boot/dts/st/stih418.dtsi
> +++ b/arch/arm/boot/dts/st/stih418.dtsi
> @@ -6,6 +6,7 @@
>  #include "stih418-clock.dtsi"
>  #include "stih407-family.dtsi"
>  #include "stih410-pinctrl.dtsi"
> +#include <dt-bindings/gpio/gpio.h>
>  / {
>  	cpus {
>  		#address-cells = <1>;
> @@ -114,5 +115,158 @@ thermal@91a0000 {
>  			clocks = <&clk_sysin>;
>  			interrupts = <GIC_SPI 205 IRQ_TYPE_EDGE_RISING>;
>  		};
> +
> +		sti-display-subsystem@0 {

display-subsystem@
or display-controller@

Although 0 is a bit weird address... are you sure this is correct?

> +			compatible = "st,sti-display-subsystem";
> +			#address-cells = <1>;
> +			#size-cells = <1>;
> +
> +			reg = <0 0>;
> +			assigned-clocks = <&clk_s_d2_quadfs 0>,
> +					  <&clk_s_d2_quadfs 1>,
> +					  <&clk_s_d2_flexgen CLK_TMDS_HDMI_DIV2>,
> +					  <&clk_s_d2_flexgen CLK_TMDS_HDMI>,
> +					  <&clk_s_d2_flexgen CLK_PIX_MAIN_DISP>,
> +					  <&clk_s_d2_flexgen CLK_PIX_AUX_DISP>,
> +					  <&clk_s_c0_flexgen CLK_MAIN_DISP>,
> +					  <&clk_s_c0_flexgen CLK_AUX_DISP>,
> +					  <&clk_s_c0_flexgen CLK_COMPO_DVP>,
> +					  <&clk_s_c0_flexgen CLK_PROC_MIXER>;
> +
> +			assigned-clock-parents = <0>,
> +						 <0>,
> +						 <&clk_tmdsout_hdmi>,
> +						 <&clk_tmdsout_hdmi>,
> +						 <&clk_s_d2_quadfs 0>,
> +						 <&clk_s_d2_quadfs 1>,
> +						 <&clk_s_c0_pll1 0>,
> +						 <&clk_s_c0_pll1 0>,
> +						 <&clk_s_c0_pll0 0>,
> +						 <&clk_s_c0_pll0 0>;
> +
> +			assigned-clock-rates = <297000000>,
> +					       <108000000>,
> +					       <297000000>,
> +					       <0>,
> +					       <74250000>,
> +					       <13500000>,
> +					       <400000000>,
> +					       <400000000>,
> +					       <355000000>,
> +					       <355000000>;
> +
> +			ranges;
> +
> +			sti_compo: sti-compositor@a600000 {

compositor@

> +				compatible = "st,stih418-compositor";
> +				reg = <0xa600000 0x200000>;
> +
> +				clock-names = "compo_main",
> +					      "compo_aux",
> +					      "pix_main",
> +					      "pix_aux",
> +					      "proc_mixer";
> +
> +				clocks = <&clk_s_c0_flexgen CLK_COMPO_DVP>,
> +					 <&clk_s_c0_flexgen CLK_COMPO_DVP>,
> +					 <&clk_s_d2_flexgen CLK_PIX_MAIN_DISP>,
> +					 <&clk_s_d2_flexgen CLK_PIX_AUX_DISP>,
> +					 <&clk_s_c0_flexgen CLK_PROC_MIXER>;
> +
> +				reset-names = "compo-main", "compo-aux";
> +				resets = <&softreset STIH407_COMPO_SOFTRESET>,
> +					 <&softreset STIH407_COMPO_SOFTRESET>;
> +				st,vtg = <&vtg_main>, <&vtg_aux>;
> +
> +				status = "disabled";
> +			};
> +
> +			sti_tvout: sti-tvout@a900000 {

hdmi@
or something else

> +				compatible = "st,stih418-tvout";
> +				reg = <0xa900000 0x1000>;
> +				reg-names = "tvout-reg";
> +				reset-names = "tvout";
> +				resets = <&softreset STIH407_HDTVOUT_SOFTRESET>;
> +				#address-cells = <1>;
> +				#size-cells = <1>;
> +				assigned-clocks = <&clk_s_d2_flexgen CLK_PIX_HDMI>,
> +						  <&clk_s_d2_flexgen CLK_TMDS_HDMI>,
> +						  <&clk_s_d2_flexgen CLK_REF_HDMIPHY>,
> +						  <&clk_s_d0_flexgen CLK_PCM_0>,
> +						  <&clk_s_d2_flexgen CLK_PIX_HDDAC>,
> +						  <&clk_s_d2_flexgen CLK_HDDAC>;
> +
> +				assigned-clock-parents = <&clk_s_d2_quadfs 0>,
> +							 <&clk_tmdsout_hdmi>,
> +							 <&clk_s_d2_quadfs 0>,
> +							 <&clk_s_d0_quadfs 0>,
> +							 <&clk_s_d2_quadfs 0>,
> +							 <&clk_s_d2_quadfs 0>;
> +				assigned-clock-rates = <74250000>,
> +						       <0>,
> +						       <74250000>,
> +						       <0>,
> +						       <74250000>,
> +						       <148500000>;
> +
> +				status = "disabled";
> +			};
> +
> +			sti_dvo: sti-dvo@a800400 {

I don't know, but definitely sti is not a generic name.

> +				compatible = "st,stih407-dvo";
> +				reg = <0xa800400 0x200>;
> +				reg-names = "dvo-reg";
> +				clock-names = "dvo_pix", "dvo",
> +					      "main_parent", "aux_parent";
> +				clocks = <&clk_s_d2_flexgen CLK_PIX_DVO>,
> +					 <&clk_s_d2_flexgen CLK_DVO>,
> +					 <&clk_s_d2_quadfs 0>, <&clk_s_d2_quadfs 1>;
> +				status = "disabled";
> +			};
> +
> +			sti_hdmi: sti-hdmi@a804000 {

hdmi@

> +				compatible = "st,stih418-hdmi";
> +				reg = <0xa804000 0x1000>;
> +				reg-names = "hdmi-reg";
> +				#sound-dai-cells = <0>;
> +				interrupts = <GIC_SPI 106 IRQ_TYPE_LEVEL_HIGH>;
> +				interrupt-names = "irq";
> +				clock-names = "pix",
> +					      "tmds",
> +					      "phy",
> +					      "audio",
> +					      "main_parent",
> +					      "aux_parent";
> +
> +				clocks = <&clk_s_d2_flexgen CLK_PIX_HDMI>,
> +					 <&clk_s_d2_flexgen CLK_TMDS_HDMI>,
> +					 <&clk_s_d2_flexgen CLK_REF_HDMIPHY>,
> +					 <&clk_s_d0_flexgen CLK_PCM_0>,
> +					 <&clk_s_d2_quadfs 0>,
> +					 <&clk_s_d2_quadfs 1>;
> +
> +				hdmi,hpd-gpio = <&pio5 3 GPIO_ACTIVE_LOW>;
> +				reset-names = "hdmi";
> +				resets = <&softreset STIH407_HDMI_TX_PHY_SOFTRESET>;
> +
> +				status = "disabled";
> +			};
> +		};
Best regards,
Krzysztof


  reply	other threads:[~2023-07-28  7:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27 21:51 [PATCH 00/14] drm/sti: add display support on stih418 family Alain Volmat
2023-07-27 21:51 ` [PATCH 01/14] drm/sti: add hdmi tx6g0c28 phy for STi platform Alain Volmat
2023-07-27 21:51 ` [PATCH 02/14] dt-bindings: display: add st,stih418-vtg compatible for sti vtg Alain Volmat
2023-07-28  7:22   ` Krzysztof Kozlowski
2023-07-27 21:51 ` [PATCH 03/14] drm/sti: add support for VTG on the stih418 platform Alain Volmat
2023-07-27 21:51 ` [PATCH 04/14] drm/sti: add STih418 platform support in sti mixer Alain Volmat
2023-07-27 21:51 ` [PATCH 05/14] drm/sti: add support for stih418 in tvout Alain Volmat
2023-07-27 21:51 ` [PATCH 06/14] drm/sti: remove VTG_SYNC_ID_HDMI from sti_vtg.h Alain Volmat
2023-07-27 21:51 ` [PATCH 07/14] drm/sti: add more possible GDP / VID planes entries in sti_plane Alain Volmat
2023-07-27 21:51 ` [PATCH 08/14] drm/sti: add more planes supports in sti_mixer Alain Volmat
2023-07-27 21:51 ` [PATCH 09/14] drm/sti: add support for GDPPLUS / stih418 GDPs Alain Volmat
2023-07-27 21:51 ` [PATCH 10/14] drm/sti: add compositor support for stih418 platform Alain Volmat
2023-07-27 21:51 ` [PATCH 11/14] ARM: dts: sti: move vtg_main / vtg_aux into stih407/stih410 dtsi Alain Volmat
2023-07-27 21:51 ` [PATCH 12/14] ARM: dts: sti: addition of display nodes for stih418 platform Alain Volmat
2023-07-28  7:24   ` Krzysztof Kozlowski [this message]
2023-07-27 21:51 ` [PATCH 13/14] ARM: dts: sti: add the gpu node for the MALI-400 on stih418.dtsi Alain Volmat
2023-07-27 21:51 ` [PATCH 14/14] ARM: dts: sti: enable basic display on stih418-b2264 board Alain Volmat
2023-07-28  7:24   ` Krzysztof Kozlowski

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=0374b5b4-abc8-9aed-e49c-21287f415734@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=avolmat@me.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrice.chotard@foss.st.com \
    --cc=robh+dt@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

all inboxes | Powered by JetHome®