public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan Gerhold <stephan.gerhold@linaro.org>
To: jens.glathe@oldschoolsolutions.biz
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v8 2/3] arm64: dts: qcom: x1-hp-x14: Unify HP Omnibook X14 device tree structure
Date: Sun, 14 Sep 2025 15:20:58 +0200	[thread overview]
Message-ID: <aMbBOgNc-382vwMY@linaro.org> (raw)
In-Reply-To: <20250909-hp-x14-x1p-v8-2-8082ab069911@oldschoolsolutions.biz>

On Tue, Sep 09, 2025 at 07:02:34PM +0200, Jens Glathe via B4 Relay wrote:
> From: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
> 
> Extract common elements into a shared .dtsi file for HP Omnibook X14 to
> support both Hamoa (x1e*/x1p6*) and Purwa (x1p4*/x1*) variants.
> Required because the device trees are not compatible.
> 
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
> ---
>  ...hp-omnibook-x14.dts => x1-hp-omnibook-x14.dtsi} |   48 +-
>  .../boot/dts/qcom/x1e80100-hp-omnibook-x14.dts     | 1606 +-------------------
>  2 files changed, 48 insertions(+), 1606 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/qcom/x1e80100-hp-omnibook-x14.dts b/arch/arm64/boot/dts/qcom/x1-hp-omnibook-x14.dtsi
> similarity index 97%
> copy from arch/arm64/boot/dts/qcom/x1e80100-hp-omnibook-x14.dts
> copy to arch/arm64/boot/dts/qcom/x1-hp-omnibook-x14.dtsi
> index 716205b437df55489cfb7d29846cdaf8e403cf72..e6851dbaba121029bde926310616169e319cf5e3 100644
> --- a/arch/arm64/boot/dts/qcom/x1e80100-hp-omnibook-x14.dts
> +++ b/arch/arm64/boot/dts/qcom/x1-hp-omnibook-x14.dtsi
> [...]
> @@ -1028,6 +1015,7 @@ &mdss_dp0 {
>  };
>  
>  &mdss_dp0_out {
> +	data-lanes = <0 1>;
>  	link-frequencies = /bits/ 64 <1620000000 2700000000 5400000000 8100000000>;
>  };
>  
> @@ -1036,15 +1024,13 @@ &mdss_dp1 {
>  };
>  
>  &mdss_dp1_out {
> +	data-lanes = <0 1>;
>  	link-frequencies = /bits/ 64 <1620000000 2700000000 5400000000 8100000000>;
>  };
>  
>  &mdss_dp3 {
>  	/delete-property/ #sound-dai-cells;
>  
> -	pinctrl-0 = <&edp0_hpd_default>;
> -	pinctrl-names = "default";
> -
>  	status = "okay";
>  
>  	aux-bus {
> @@ -1061,13 +1047,19 @@ edp_panel_in: endpoint {
>  			};
>  		};
>  	};
> -};
>  
> -&mdss_dp3_out {
> -	data-lanes = <0 1 2 3>;
> -	link-frequencies = /bits/ 64 <1620000000 2700000000 5400000000 8100000000>;
> +	ports {
> +		port@1 {
> +			reg = <1>;
> +
> +			mdss_dp3_out: endpoint {
> +				data-lanes = <0 1 2 3>;
> +				link-frequencies = /bits/ 64 <1620000000 2700000000 5400000000 8100000000>;
>  
> -	remote-endpoint = <&edp_panel_in>;
> +				remote-endpoint = <&edp_panel_in>;
> +			};
> +		};
> +	};
>  };
>  
>  &mdss_dp3_phy {

Please review the resulting diff carefully when you rebase changes with
conflicts. You're reverting other changes (4 lane DP, eDP HPD pinctrl)
here. :-)

Thanks,
Stephan

  reply	other threads:[~2025-09-14 13:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09 17:02 [PATCH v8 0/3] arm64: dts: qcom: x1-hp-x14: Add support for X1P42100 HP Omnibook X14 Jens Glathe via B4 Relay
2025-09-09 17:02 ` [PATCH v8 1/3] dt-bindings: arm: qcom: Add HP Omnibook X14 AI X1P4200 variant Jens Glathe via B4 Relay
2025-09-09 17:02 ` [PATCH v8 2/3] arm64: dts: qcom: x1-hp-x14: Unify HP Omnibook X14 device tree structure Jens Glathe via B4 Relay
2025-09-14 13:20   ` Stephan Gerhold [this message]
2025-09-14 13:23     ` Jens Glathe
2025-09-15  7:39       ` Jens Glathe
2025-09-09 17:02 ` [PATCH v8 3/3] arm64: dts: qcom: x1-hp-x14: Add support for X1P42100 HP Omnibook X14 Jens Glathe via B4 Relay

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=aMbBOgNc-382vwMY@linaro.org \
    --to=stephan.gerhold@linaro.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jens.glathe@oldschoolsolutions.biz \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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