devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: wuxilin123@gmail.com, Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Kees Cook <keescook@chromium.org>,
	Tony Luck <tony.luck@intel.com>,
	"Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: qcom: Add device tree for Xiaomi Mi 11 Ultra
Date: Sat, 5 Aug 2023 22:17:23 +0200	[thread overview]
Message-ID: <c32f0d5a-32c9-fd0b-822c-a8ed9238458c@linaro.org> (raw)
In-Reply-To: <20230806-xiaomi-star-v1-3-0c384e8b5737@gmail.com>

On 05/08/2023 19:03, Xilin Wu via B4 Relay wrote:
> From: Xilin Wu <wuxilin123@gmail.com>
> 
> Add support for Xiaomi Mi 11 Ultra. This commit brings support for:
> * Front and rear display panels (initialized by bootloader)
> * USB
> * UFS
> * PCIe0
> * Thermistor sensors
> * ADSP/CDSP/Modem/SLPI
> * IR Transmitter
> * RTC provided by PMK8350
> * Buttons
> 

...


> +/*
> + * Delete following upstream (sm8350.dtsi) reserved
> + * memory mappings which are different on this device.


> + */
> +/delete-node/ &pil_adsp_mem;
> +/delete-node/ &pil_slpi_mem;
> +/delete-node/ &pil_cdsp_mem;
> +/delete-node/ &pil_ipa_fw_mem;
> +/delete-node/ &pil_ipa_gsi_mem;
> +/delete-node/ &pil_gpu_mem;
> +/delete-node/ &pil_spss_mem;
> +/delete-node/ &pil_modem_mem;
> +/delete-node/ &rmtfs_mem;
> +/delete-node/ &pil_trustedvm_mem;
> +/delete-node/ &removed_mem;
> +
> +/ {
> +	model = "Xiaomi Mi 11 Ultra";
> +	compatible = "xiaomi,star", "qcom,sm8350";
> +	chassis-type = "handset";
> +
> +	chosen {
> +		#address-cells = <2>;
> +		#size-cells = <2>;
> +		ranges;
> +
> +		framebuffer0: framebuffer-front@ea600000 {

framebuffer@

> +			compatible = "simple-framebuffer";
> +			reg = <0 0xea600000 0 (1440 * 3200 * 4)>;
> +
> +			width = <1440>;
> +			height = <3200>;
> +			stride = <(1440 * 4)>;
> +			format = "a8r8g8b8";
> +		};
> +
> +		framebuffer1: framebuffer-rear@eb79c000 {

framebuffer@

> +			compatible = "simple-framebuffer";
> +			reg = <0 0xeb79c000 0 (126 * 294 * 4)>;
> +
> +			width = <126>;
> +			height = <294>;
> +			stride = <(126 * 4)>;
> +			format = "a8r8g8b8";
> +		};
> +	};
> +




> +			reg = <0 0x86100000 0 0x3900000>;
> +			no-map;
> +		};
> +
> +		pil_slpi_mem: memory@89a00000 {
> +			reg = <0 0x89a00000 0 0x2f00000>;
> +			no-map;
> +		};
> +
> +		pil_cdsp_mem: memory@8c900000 {
> +			reg = <0 0x8c900000 0 0x1e00000>;
> +			no-map;
> +		};
> +
> +		pil_ipa_fw_mem: memory@8e700000 {
> +			reg = <0 0x8e700000 0 0x10000>;
> +			no-map;
> +		};
> +
> +		pil_ipa_gsi_mem: memory@8e710000 {
> +			reg = <0 0x8e710000 0 0xa000>;
> +			no-map;
> +		};
> +

...

> +&pm8350c_gpios {
> +	gpio-line-names = "VDD_BOOST_5V_EN",
> +			  "NC",
> +			  "OTG_OVP_EN",
> +			  "WL_TXON",
> +			  "NC",
> +			  "NC",
> +			  "NC",
> +			  "NC",
> +			  "NC";
> +};
> +
> +&pmk8350_adc_tm {
> +	status = "okay";
> +
> +	pm8350-skin-therm@0 {

Hm, didn't we change the node names to generic "channel" and started
using labels? At least in next or ongoing patches? Or was it only for VADC?


> +		reg = <0>;
> +		io-channels = <&pmk8350_vadc PM8350_ADC7_AMUX_THM1_100K_PU(1)>;
> +		qcom,ratiometric;
> +		qcom,hw-settle-time-us = <200>;
> +	};

...

> +
> +&ufs_mem_hc {
> +	status = "okay";
> +
> +	reset-gpios = <&tlmm 203 GPIO_ACTIVE_LOW>;
> +
> +	vcc-supply = <&vreg_l7b_2p96>;
> +	vcc-max-microamp = <800000>;
> +	vccq-supply = <&vreg_l9b_1p2>;
> +	vccq-max-microamp = <900000>;
> +};
> +
> +&ufs_mem_phy {
> +	status = "okay";
> +
> +	vdda-phy-supply = <&vreg_l5b_0p88>;
> +	vdda-pll-supply = <&vreg_l6b_1p2>;
> +};
> +
> +&usb_1 {
> +	/* USB 2.0 only */
> +	qcom,select-utmi-as-pipe-clk;
> +	status = "okay";
> +};
> +
> +&usb_1_dwc3 {
> +	dr_mode = "otg";
> +	usb-role-switch;
> +	maximum-speed = "high-speed";
> +	/* Remove USB3 phy */
> +	phys = <&usb_1_hsphy>;
> +	phy-names = "usb2-phy";
> +};
> +
> +&usb_1_dwc3_hs {
> +	remote-endpoint = <&pmic_glink_hs_in>;
> +};
> +
> +&usb_1_hsphy {
> +	status = "okay";
> +
> +	vdda-pll-supply = <&vreg_l5b_0p88>;
> +	vdda18-supply = <&vreg_l1c_1p8>;
> +	vdda33-supply = <&vreg_l2b_3p07>;
> +};
> +

Looks like you have trailing blank line.

Best regards,
Krzysztof


  reply	other threads:[~2023-08-05 20:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-05 17:03 [PATCH 0/3] Add initial support for Xiaomi Mi 11 Ultra Xilin Wu via B4 Relay
2023-08-05 17:03 ` [PATCH 1/3] soc: qcom: pmic_glink: enable UCSI for SM8350 Xilin Wu via B4 Relay
2023-08-12 11:12   ` Konrad Dybcio
2023-08-13 10:56     ` Dmitry Baryshkov
2023-08-14  5:28       ` Sophon Wu
2023-08-05 17:03 ` [PATCH 2/3] dt-bindings: arm: qcom: Add Xiaomi Mi 11 Ultra Xilin Wu via B4 Relay
2023-08-05 20:11   ` Krzysztof Kozlowski
2023-08-10  5:26     ` Sophon Wu
2023-08-05 17:03 ` [PATCH 3/3] arm64: dts: qcom: Add device tree for " Xilin Wu via B4 Relay
2023-08-05 20:17   ` Krzysztof Kozlowski [this message]
2023-08-07 16:05   ` Konrad Dybcio
2023-08-10  5:30     ` Sophon Wu

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=c32f0d5a-32c9-fd0b-822c-a8ed9238458c@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gpiccoli@igalia.com \
    --cc=keescook@chromium.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=wuxilin123@gmail.com \
    /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).