devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Jianhua Lu <lujianhua000@gmail.com>,
	 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>,
	 Jeff Johnson <jjohnson@kernel.org>,
	linux-arm-msm@vger.kernel.org,  devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,  ath11k@lists.infradead.org
Subject: Re: [PATCH v3 2/3] arm64: dts: qcom: sm8250-xiaomi-elish: Add wifi node
Date: Fri, 11 Oct 2024 17:38:46 +0300	[thread overview]
Message-ID: <87ttdi66x5.fsf@kernel.org> (raw)
In-Reply-To: <p4j7i6fbr7htsh44vumlsziuhbl4phqok4zxnubdvyrjo2cllt@cez4iynfjayt> (Dmitry Baryshkov's message of "Fri, 11 Oct 2024 16:46:14 +0300")

Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:

> On Fri, Oct 11, 2024 at 02:08:19PM +0300, Kalle Valo wrote:
>> Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:
>> 
>> >> --- a/arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-common.dtsi
>> >> +++ b/arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-common.dtsi
>> >> @@ -680,6 +680,25 @@ &pcie0_phy {
>> >>  	status = "okay";
>> >>  };
>> >>  
>> >> +&pcieport0 {
>> >> +	wifi@0 {
>> >> +		compatible = "pci17cb,1101";
>> >> +		reg = <0x10000 0x0 0x0 0x0 0x0>;
>> >> +
>> >> +		vddrfacmn-supply = <&vreg_pmu_rfa_cmn>;
>> >> +		vddaon-supply = <&vreg_pmu_aon_0p59>;
>> >> +		vddwlcx-supply = <&vreg_pmu_wlcx_0p8>;
>> >> +		vddwlmx-supply = <&vreg_pmu_wlmx_0p85>;
>> >> +		vddrfa0p8-supply = <&vreg_pmu_rfa_0p8>;
>> >> +		vddrfa1p2-supply = <&vreg_pmu_rfa_1p2>;
>> >> +		vddrfa1p7-supply = <&vreg_pmu_rfa_1p7>;
>> >> +		vddpcie0p9-supply = <&vreg_pmu_pcie_0p9>;
>> >> +		vddpcie1p8-supply = <&vreg_pmu_pcie_1p8>;
>> >> +
>> >> +		qcom,ath11k-calibration-variant = "Xiaomi_Pad_5Pro";
>> >
>> > Let's wait for Kalle's response.
>> 
>> Sorry, I don't know what you refer to here. I have been extremly busy
>> with MLO patches so drowning with mail right now :/
>
> Just an ack for the calibration variant name.

Ah, then ack from me for the name. Thanks for following these.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2024-10-11 14:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10  7:22 [PATCH v3 1/3] arm64: dts: qcom: sm8250-xiaomi-elish: Add qca6390-pmu node Jianhua Lu
2024-10-10  7:22 ` [PATCH v3 2/3] arm64: dts: qcom: sm8250-xiaomi-elish: Add wifi node Jianhua Lu
2024-10-10 15:23   ` Dmitry Baryshkov
2024-10-11 11:08     ` Kalle Valo
2024-10-11 13:46       ` Dmitry Baryshkov
2024-10-11 14:38         ` Kalle Valo [this message]
2024-10-10  7:22 ` [PATCH v3 3/3] arm64: dts: qcom: sm8250-xiaomi-elish: Add bluetooth node Jianhua Lu

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=87ttdi66x5.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=andersson@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=jjohnson@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lujianhua000@gmail.com \
    --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).