Re: [PATCH v3] arm64: dts: qcom: Add support for Xiaomi Poco F1 (Beryllium)

From: Amit Pundir
Date: Tue Aug 04 2020 - 03:36:25 EST

Next message: Greg KH: "Re: [PATCH] vgacon: fix out of bounds write to the scrollback buffer"
Previous message: Alex Shi: "Re: [PATCH] mm/memcg: remove useless check on page->mem_cgroup"
In reply to: Bjorn Andersson: "Re: [PATCH v3] arm64: dts: qcom: Add support for Xiaomi Poco F1 (Beryllium)"
Next in thread: Bjorn Andersson: "Re: [PATCH v3] arm64: dts: qcom: Add support for Xiaomi Poco F1 (Beryllium)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 4 Aug 2020 at 11:46, Bjorn Andersson <bjorn.andersson@xxxxxxxxxx> wrote:
>
> On Sat 01 Aug 08:55 PDT 2020, Amit Pundir wrote:
>
> > Add initial dts support for Xiaomi Poco F1 (Beryllium).
> >
> > This initial support is based on upstream Dragonboard 845c
> > (sdm845) device. With this dts, Beryllium boots AOSP up to
> > ADB shell over USB-C.
> >
> > Supported functionality includes UFS, USB-C (peripheral),
> > microSD card and Vol+/Vol-/power keys. Bluetooth should work
> > too but couldn't be verified from adb command line, it is
> > verified when enabled from UI with few WIP display patches.
> >
> > Just like initial db845c support, initializing the SMMU is
> > clearing the mapping used for the splash screen framebuffer,
> > which causes the device to hang during boot and recovery
> > needs a hard power reset. This can be worked around using:
> >
> > fastboot oem select-display-panel none
> >
> > To switch ON the display back run:
> >
> > fastboot oem select-display-panel
> >
> > But this only works on Beryllium devices running bootloader
> > version BOOT.XF.2.0-00369-SDM845LZB-1 that shipped with
> > Android-9 based release. Newer bootloader version do not
> > support switching OFF the display panel at all. So we need
> > a few additional smmu patches (under review) from here to
> > boot to shell:
> > https://github.com/pundiramit/linux/commits/beryllium-mainline
> >
> > Signed-off-by: Amit Pundir <amit.pundir@xxxxxxxxxx>
> > ---
> > v3: Added a reserved-memory region from downstream kernel to fix
> > a boot regression with recent dma-pool changes in v5.8-rc6.
> > v2: Updated machine compatible string for seemingly inevitable
> > future quirks.
> >
> > arch/arm64/boot/dts/qcom/Makefile | 1 +
> > arch/arm64/boot/dts/qcom/sdm845-beryllium.dts | 331 ++++++++++++++++++++++++++
> > 2 files changed, 332 insertions(+)
> > create mode 100644 arch/arm64/boot/dts/qcom/sdm845-beryllium.dts
> >
> > diff --git a/arch/arm64/boot/dts/qcom/Makefile b/arch/arm64/boot/dts/qcom/Makefile
> > index 0f2c33d611df..3ef1b48bc0cb 100644
> > --- a/arch/arm64/boot/dts/qcom/Makefile
> > +++ b/arch/arm64/boot/dts/qcom/Makefile
> > @@ -21,6 +21,7 @@ dtb-$(CONFIG_ARCH_QCOM) += sdm845-cheza-r1.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += sdm845-cheza-r2.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += sdm845-cheza-r3.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += sdm845-db845c.dtb
> > +dtb-$(CONFIG_ARCH_QCOM) += sdm845-beryllium.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += sdm845-mtp.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += sdm850-lenovo-yoga-c630.dtb
> > dtb-$(CONFIG_ARCH_QCOM) += sm8150-mtp.dtb
> > diff --git a/arch/arm64/boot/dts/qcom/sdm845-beryllium.dts b/arch/arm64/boot/dts/qcom/sdm845-beryllium.dts
> > new file mode 100644
> > index 000000000000..af66459712fe
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/qcom/sdm845-beryllium.dts
> > @@ -0,0 +1,331 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +
> > +/dts-v1/;
> > +
> > +#include <dt-bindings/gpio/gpio.h>
> > +#include <dt-bindings/pinctrl/qcom,pmic-gpio.h>
> > +#include <dt-bindings/regulator/qcom,rpmh-regulator.h>
> > +#include "sdm845.dtsi"
> > +#include "pm8998.dtsi"
> > +#include "pmi8998.dtsi"
> > +
> > +/ {
> > + model = "Xiaomi Technologies Inc. Beryllium";
> > + compatible = "xiaomi,beryllium", "qcom,sdm845";
> > +
> > + /* required for bootloader to select correct board */
> > + qcom,board-id = <69 0>;
> > + qcom,msm-id = <321 0x20001>;
> > +
> > + aliases {
> > + hsuart0 = &uart6;
> > + };
> > +
> > + dc12v: dc12v-regulator {
>
> This is a phone, it doesn't have a 12V DC jack. So while I don't know
> the exact power grid for this device, this node shouldn't be here.

Ack. Will remove it in next version.

>
> > + compatible = "regulator-fixed";
> > + regulator-name = "DC12V";
> > + regulator-min-microvolt = <12000000>;
> > + regulator-max-microvolt = <12000000>;
> > + regulator-always-on;
> > + };
> > +
> > + gpio_keys {
>
> y/_/-/

Ack.

>
> > + compatible = "gpio-keys";
> > + autorepeat;
> > +
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&vol_up_pin_a>;
> > +
> > + vol-up {
> > + label = "Volume Up";
> > + linux,code = <KEY_VOLUMEUP>;
> > + gpios = <&pm8998_gpio 6 GPIO_ACTIVE_LOW>;
> > + };
> > + };
> > +
> > + vbat: vbat-regulator {
> > + compatible = "regulator-fixed";
> > + regulator-name = "VBAT";
> > +
> > + vin-supply = <&dc12v>;
> > + regulator-min-microvolt = <4200000>;
> > + regulator-max-microvolt = <4200000>;
> > + regulator-always-on;
> > + };
> > +
> > + vbat_som: vbat-som-regulator {
>
> This is specific to db845c, with its power grid split between the main
> board and the SOM. Please omit.

Ack.

>
> > + compatible = "regulator-fixed";
> > + regulator-name = "VBAT_SOM";
> > +
> > + vin-supply = <&dc12v>;
> > + regulator-min-microvolt = <4200000>;
> > + regulator-max-microvolt = <4200000>;
> > + regulator-always-on;
> > + };
> > +
> > + vdc_3v3: vdc-3v3-regulator {
>
> This is probably not on the Poco and it's not referenced, please remove.

Ack.

>
> > + compatible = "regulator-fixed";
> > + regulator-name = "VDC_3V3";
> > + vin-supply = <&dc12v>;
> > + regulator-min-microvolt = <3300000>;
> > + regulator-max-microvolt = <3300000>;
> > + regulator-always-on;
> > + };
> > +
> > + vdc_5v: vdc-5v-regulator {
>
> Ditto.

Ack.

>
> > + compatible = "regulator-fixed";
> > + regulator-name = "VDC_5V";
> > +
> > + vin-supply = <&dc12v>;
> > + regulator-min-microvolt = <500000>;
> > + regulator-max-microvolt = <500000>;
> > + regulator-always-on;
> > + };
> > +
> > + vreg_s4a_1p8: vreg-s4a-1p8 {
> > + compatible = "regulator-fixed";
> > + regulator-name = "vreg_s4a_1p8";
> > +
> > + regulator-min-microvolt = <1800000>;
> > + regulator-max-microvolt = <1800000>;
> > + regulator-always-on;
> > + };
> > +};
> > +
> > +&apps_rsc {
> > + pm8998-rpmh-regulators {
> > + compatible = "qcom,pm8998-rpmh-regulators";
> > + qcom,pmic-id = "a";
> > +
> > + vreg_l1a_0p875: ldo1 {
> > + regulator-min-microvolt = <880000>;
> > + regulator-max-microvolt = <880000>;
> > + regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> > + };
> > +
> > + vreg_l7a_1p8: ldo7 {
> > + regulator-min-microvolt = <1800000>;
> > + regulator-max-microvolt = <1800000>;
> > + regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> > + };
> > +
> > + vreg_l12a_1p8: ldo12 {
> > + regulator-min-microvolt = <1800000>;
> > + regulator-max-microvolt = <1800000>;
> > + regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> > + };
> > +
> > + vreg_l13a_2p95: ldo13 {
> > + regulator-min-microvolt = <1800000>;
> > + regulator-max-microvolt = <2960000>;
> > + regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> > + };
> > +
> > + vreg_l17a_1p3: ldo17 {
> > + regulator-min-microvolt = <1304000>;
> > + regulator-max-microvolt = <1304000>;
> > + regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> > + };
> > +
> > + vreg_l20a_2p95: ldo20 {
> > + regulator-min-microvolt = <2960000>;
> > + regulator-max-microvolt = <2968000>;
> > + regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> > + };
> > +
> > + vreg_l21a_2p95: ldo21 {
> > + regulator-min-microvolt = <2960000>;
> > + regulator-max-microvolt = <2968000>;
> > + regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> > + };
> > +
> > + vreg_l24a_3p075: ldo24 {
> > + regulator-min-microvolt = <3088000>;
> > + regulator-max-microvolt = <3088000>;
> > + regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> > + };
> > +
> > + vreg_l25a_3p3: ldo25 {
> > + regulator-min-microvolt = <3300000>;
> > + regulator-max-microvolt = <3312000>;
> > + regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> > + };
> > +
> > + vreg_l26a_1p2: ldo26 {
> > + regulator-min-microvolt = <1200000>;
> > + regulator-max-microvolt = <1200000>;
> > + regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> > + };
> > + };
> > +};
> > +
> > +&gcc {
> > + protected-clocks = <GCC_QSPI_CORE_CLK>,
> > + <GCC_QSPI_CORE_CLK_SRC>,
> > + <GCC_QSPI_CNOC_PERIPH_AHB_CLK>;
> > +};
> > +
> > +/* Reserved memory changes from downstream */
> > +/ {
> > + reserved-memory {
> > + removed_region: memory@88f00000 {
>
> Do you know what these 26MB are used for? Do you think it's possible to
> give it a more appropriate label? The size happens to be the same as
> &adsp_mem from sdm845.dtsi, this is probably not a coincidence.

In downstream, this removed region is marked as removed-dma-pool
compatible, https://github.com/MiCode/Xiaomi_Kernel_OpenSource/commit/b982b6dc77ac34c184abe83dd293ac08fc607ba3,
a carved out memory region not exposed to the kernel. I honestly
didn't know what to name this region, so I kept it as it was. I can't
boot past the bootloader if I don't mark this region as reserved.

>
> That said, this overlaps at least &rmtfs_mem, &qseecom_mem and
> &camera_mem, so I would expect that you have a few warnings about this
> early in the log? Please shuffle things around to avoid this.

Sorry, I do know that it definitely overlaps with upstream &rmtfs_mem,
but I ignored that because plan was to just boot to shell with this
base dts. I was planning to submit a follow-up patch with downstream
reserved memory mappings, which do not coincide with the upstream
sdm845.dtsi mem regions you mentioned above, along with relevant
wifi/adsp/cdsp nodes. But let me take this opportunity to submit them
in the next version of this base dts.

>
> > + no-map;
> > + reg = <0 0x88f00000 0 0x1A00000>;
>
> Please lowercase the 'A'

Ack.

Regards,
Amit Pundir

>
> Regards,
> Bjorn
>
> > + };
> > + };
> > +};
> > +
> > +&pm8998_gpio {
> > + vol_up_pin_a: vol-up-active {
> > + pins = "gpio6";
> > + function = "normal";
> > + input-enable;
> > + bias-pull-up;
> > + qcom,drive-strength = <PMIC_GPIO_STRENGTH_NO>;
> > + };
> > +};
> > +
> > +&pm8998_pon {
> > + resin {
> > + compatible = "qcom,pm8941-resin";
> > + interrupts = <0x0 0x8 1 IRQ_TYPE_EDGE_BOTH>;
> > + debounce = <15625>;
> > + bias-pull-up;
> > + linux,code = <KEY_VOLUMEDOWN>;
> > + };
> > +};
> > +
> > +&qupv3_id_0 {
> > + status = "okay";
> > +};
> > +
> > +&sdhc_2 {
> > + status = "okay";
> > +
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&sdc2_default_state &sdc2_card_det_n>;
> > +
> > + vmmc-supply = <&vreg_l21a_2p95>;
> > + vqmmc-supply = <&vreg_l13a_2p95>;
> > +
> > + bus-width = <4>;
> > + cd-gpios = <&tlmm 126 GPIO_ACTIVE_HIGH>;
> > +};
> > +
> > +&tlmm {
> > + gpio-reserved-ranges = <0 4>, <81 4>;
> > +
> > + sdc2_default_state: sdc2-default {
> > + clk {
> > + pins = "sdc2_clk";
> > + bias-disable;
> > +
> > + /*
> > + * It seems that mmc_test reports errors if drive
> > + * strength is not 16 on clk, cmd, and data pins.
> > + */
> > + drive-strength = <16>;
> > + };
> > +
> > + cmd {
> > + pins = "sdc2_cmd";
> > + bias-pull-up;
> > + drive-strength = <10>;
> > + };
> > +
> > + data {
> > + pins = "sdc2_data";
> > + bias-pull-up;
> > + drive-strength = <10>;
> > + };
> > + };
> > +
> > + sdc2_card_det_n: sd-card-det-n {
> > + pins = "gpio126";
> > + function = "gpio";
> > + bias-pull-up;
> > + };
> > +};
> > +
> > +&uart6 {
> > + status = "okay";
> > +
> > + bluetooth {
> > + compatible = "qcom,wcn3990-bt";
> > +
> > + vddio-supply = <&vreg_s4a_1p8>;
> > + vddxo-supply = <&vreg_l7a_1p8>;
> > + vddrf-supply = <&vreg_l17a_1p3>;
> > + vddch0-supply = <&vreg_l25a_3p3>;
> > + max-speed = <3200000>;
> > + };
> > +};
> > +
> > +&usb_1 {
> > + status = "okay";
> > +};
> > +
> > +&usb_1_dwc3 {
> > + dr_mode = "peripheral";
> > +};
> > +
> > +&usb_1_hsphy {
> > + status = "okay";
> > +
> > + vdd-supply = <&vreg_l1a_0p875>;
> > + vdda-pll-supply = <&vreg_l12a_1p8>;
> > + vdda-phy-dpdm-supply = <&vreg_l24a_3p075>;
> > +
> > + qcom,imp-res-offset-value = <8>;
> > + qcom,hstx-trim-value = <QUSB2_V2_HSTX_TRIM_21_6_MA>;
> > + qcom,preemphasis-level = <QUSB2_V2_PREEMPHASIS_5_PERCENT>;
> > + qcom,preemphasis-width = <QUSB2_V2_PREEMPHASIS_WIDTH_HALF_BIT>;
> > +};
> > +
> > +&usb_1_qmpphy {
> > + status = "okay";
> > +
> > + vdda-phy-supply = <&vreg_l26a_1p2>;
> > + vdda-pll-supply = <&vreg_l1a_0p875>;
> > +};
> > +
> > +&ufs_mem_hc {
> > + status = "okay";
> > +
> > + reset-gpios = <&tlmm 150 GPIO_ACTIVE_LOW>;
> > +
> > + vcc-supply = <&vreg_l20a_2p95>;
> > + vcc-max-microamp = <800000>;
> > +};
> > +
> > +&ufs_mem_phy {
> > + status = "okay";
> > +
> > + vdda-phy-supply = <&vreg_l1a_0p875>;
> > + vdda-pll-supply = <&vreg_l26a_1p2>;
> > +};
> > +
> > +/* PINCTRL - additions to nodes defined in sdm845.dtsi */
> > +
> > +&qup_uart6_default {
> > + pinmux {
> > + pins = "gpio45", "gpio46", "gpio47", "gpio48";
> > + function = "qup6";
> > + };
> > +
> > + cts {
> > + pins = "gpio45";
> > + bias-disable;
> > + };
> > +
> > + rts-tx {
> > + pins = "gpio46", "gpio47";
> > + drive-strength = <2>;
> > + bias-disable;
> > + };
> > +
> > + rx {
> > + pins = "gpio48";
> > + bias-pull-up;
> > + };
> > +};
> > --
> > 2.7.4
> >

Next message: Greg KH: "Re: [PATCH] vgacon: fix out of bounds write to the scrollback buffer"
Previous message: Alex Shi: "Re: [PATCH] mm/memcg: remove useless check on page->mem_cgroup"
In reply to: Bjorn Andersson: "Re: [PATCH v3] arm64: dts: qcom: Add support for Xiaomi Poco F1 (Beryllium)"
Next in thread: Bjorn Andersson: "Re: [PATCH v3] arm64: dts: qcom: Add support for Xiaomi Poco F1 (Beryllium)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]