devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tessolveupstream@gmail.com
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	andersson@kernel.org, konradybcio@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 2/2] arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board
Date: Mon, 15 Dec 2025 19:00:31 +0530	[thread overview]
Message-ID: <2fa1ed49-4051-4ecc-a38c-de2c7b97dc03@gmail.com> (raw)
In-Reply-To: <846a5cc1-fa0b-4952-ab40-852a07607eb7@oss.qualcomm.com>



On 05-12-2025 16:22, Konrad Dybcio wrote:
> On 12/1/25 6:22 PM, Sudarshan Shetty wrote:
>> Add the device tree for the QCS615-based Talos EVK platform. The
>> platform is composed of a System-on-Module following the SMARC
>> standard, and a Carrier Board.
> 
> [...]
> 
>> +	hdmi-out {
> 
> You must refer to existing nodes by &label references - let's call
> this one hdmi_connector: hdmi-out {}
> 

Okay, will update in v10 patch.
> [...]
> 
>> +&i2c1 {
>> +	clock-frequency = <400000>;
>> +
>> +	status = "okay";
>> +
>> +	bridge@3d {
>> +		status = "disabled";
>> +	};
> 
> Similarly here - hdmi_bridge: bridge@3d {}
> 

Okay.
>> +
>> +	bridge: bridge@2c {
> 
> lvds_bridge:
>

Okay, got it. > [...]
> 
> +
>> +				sn65dsi84_in: endpoint {
>> +				data-lanes = <0 1 2 3>;
>> +				remote-endpoint = <&mdss_dsi0_out>;
> 
> The formatting fell apart a little here - please give it a touch-up
>

Okay, will update in v10 patch.
> [...]
> >> +&tlmm {
>> +	pcie_default_state: pcie-default-state {
>> +		clkreq-pins {
>> +			pins = "gpio90";
>> +			function = "pcie_clk_req";
>> +			drive-strength = <2>;
>> +			bias-pull-up;
>> +		};
>> +
>> +		perst-pins {
>> +			pins = "gpio101";
>> +			function = "gpio";
>> +			drive-strength = <2>;
>> +			bias-pull-down;
> 
> bias-disable - this pin is active-low
> 

Okay, got it. Will update in next patch
> [...]
> 
>> +&i2c1 {
>> +	clock-frequency = <400000>;
>> +	status = "okay";
>> +	bridge: bridge@3d {
> 
> This really needs a \n above

Okay.
>> +		compatible = "adi,adv7535";
>> +		reg = <0x3d>;
>> +		avdd-supply = <&vreg_v1p8_out>;
>> +		dvdd-supply = <&vreg_v1p8_out>;
>> +		pvdd-supply = <&vreg_v1p8_out>;
>> +		a2vdd-supply = <&vreg_v1p8_out>;
>> +		v3p3-supply = <&vreg_v3p3_out>;
>> +		interrupts-extended = <&tlmm 26 IRQ_TYPE_LEVEL_LOW>;
>> +		adi,dsi-lanes = <4>;
>> +		ports {
> 
> And here

Understood, will take care in v10 patch.

> 
> Konrad


  reply	other threads:[~2025-12-15 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01 17:22 [PATCH v9 0/2] Add Qualcomm Technologies, Inc. Talos EVK SMARC support Sudarshan Shetty
2025-12-01 17:22 ` [PATCH v9 1/2] dt-bindings: arm: qcom: talos-evk: Add QCS615 Talos EVK SMARC platform Sudarshan Shetty
2025-12-01 17:22 ` [PATCH v9 2/2] arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board Sudarshan Shetty
2025-12-05 10:52   ` Konrad Dybcio
2025-12-15 13:30     ` tessolveupstream [this message]
2025-12-05 23:21   ` Dmitry Baryshkov

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=2fa1ed49-4051-4ecc-a38c-de2c7b97dc03@gmail.com \
    --to=tessolveupstream@gmail.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).