Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp4518793imw; Tue, 19 Jul 2022 08:06:34 -0700 (PDT) X-Google-Smtp-Source: AGRyM1s0dhM0BnUuafhyndEXNDyiSDEXfUh30l7E5ADTJDyOuoSHOqevpbDSauxzLUozUSLxmUK5 X-Received: by 2002:a05:6870:561e:b0:10c:5fc6:cbff with SMTP id m30-20020a056870561e00b0010c5fc6cbffmr17314927oao.149.1658243193935; Tue, 19 Jul 2022 08:06:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658243193; cv=none; d=google.com; s=arc-20160816; b=vc0npj+qMWsyp2b85eBDU797s+cOkFhfx3hoYtVwTOvCF750R9znS4SuP4l37+VVsC 7oPb7T5ykR4qZ1+DAwjJolrRRuHQyKZr4Ayi2wH9GjYqPUZXiFDHr2DzGJRWicTprw5e U1GOgOh/GHdLVKUxdZGU0uer77B/uKDhYtHp/AgmTvZ5zVxbUUZSdCFe2kzMKWWwEyyu UAbeXFFLCpgJm7VFUilbCwQ24LQcw3xgiCqC0Gl82DqVOGzH6wfVc2zD7MCW7kQReldS EVUw6OuqCAobfkzdwwFGTHsi0CeR5n/1SCgiW5KuN6SHlDffVUusKxrXNT6A7z1/kfey wvtQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :feedback-id:references:in-reply-to:message-id:subject:reply-to:cc :from:to:dkim-signature:date; bh=nJjBOg+KZDuep5ju6jcUjcAcUZtT4ZszCml4jwBd4aU=; b=VPLx4w1FShl/fT/lvKkUAt54uF6Ku9a80m/Xo4L+nE/ksbFBRo5T1NUuJI6vMISEWB BAfbIrMxakX7OHL1SjvDcHHpqDZnttuawgoQAFattGPEUqRU3l7RTxxsfrjmQyEWpd72 emx0htE7gpfbgxi50DonR0KdE+JLpdw80z9ZC/ZYjXMw7yepWDpD8fyWyuI7uxANmg3r tWKiV5UHbd53zVZVkrnycpitkNiPYSulkF1NU4jvB9jfyfiK9JdPwx+R+m9/NpiVjJAV eTOYO1xzoJ+l5U4ojnSvei8d0I3jE+rfM6GcpSsFQme6Qp/xQmwzgbN5PzPC+9bDuUhZ yBQg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@protonmail.com header.s=protonmail3 header.b="Bpd0eO/b"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=protonmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id go13-20020a056870da0d00b00101f1444bd1si14294462oab.182.2022.07.19.08.06.13; Tue, 19 Jul 2022 08:06:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@protonmail.com header.s=protonmail3 header.b="Bpd0eO/b"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=protonmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238649AbiGSNtH (ORCPT + 99 others); Tue, 19 Jul 2022 09:49:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50904 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238266AbiGSNsx (ORCPT ); Tue, 19 Jul 2022 09:48:53 -0400 Received: from mail-40135.protonmail.ch (mail-40135.protonmail.ch [185.70.40.135]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 676391094C1; Tue, 19 Jul 2022 06:02:07 -0700 (PDT) Date: Tue, 19 Jul 2022 13:01:51 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1658235722; x=1658494922; bh=nJjBOg+KZDuep5ju6jcUjcAcUZtT4ZszCml4jwBd4aU=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:Feedback-ID:From:To:Cc:Date:Subject:Reply-To: Feedback-ID:Message-ID; b=Bpd0eO/bPvaeWxSiQ5tS2IdCp8LQaOEtXmV8Cj762FbvGcbYHlCcI9bHNzdRCEn+9 ITXIPWiRU5vOM+RR5MbEE6Su4YXHH18pnKMg8P+CbywHX+mFSivk9CUQ8cajjF4uNe MNaDYetuV6iIxwJwbw9fVrfhGKzum1mY0YYI9iHnaEyLa0XAF4B3Lq20fVk1hIUT6n 7TNDnD52aoDb9vbUk+mEcYpKZaAuOh3d2J6l6nMPo+rqtAT5qWErF7APYaCY7uaMV6 J5cW/TYHlk9ITOnsWGGx1qDuOsO8EZmGeSRn/Z6x26SVCHwMaNqcggD6zWZwCxiU5b 7jAGsj9axaB/A== To: devicetree@vger.kernel.org From: "Lin, Meng-Bo" Cc: Andy Gross , Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, Stephan Gerhold , Nikita Travkin , ~postmarketos/upstreaming@lists.sr.ht Reply-To: "Lin, Meng-Bo" Subject: [PATCH v3 2/4] arm64: dts: qcom: msm8916-samsung-e2015: Add initial common dtsi Message-ID: <20220719125931.54698-1-linmengbo0689@protonmail.com> In-Reply-To: <20220715102055.3844-1-linmengbo0689@protonmail.com> References: <20220715102055.3844-1-linmengbo0689@protonmail.com> Feedback-ID: 40467236:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,FREEMAIL_REPLYTO_END_DIGIT,RCVD_IN_MSPIKE_H2, SPF_HELO_PASS,SPF_PASS autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Samsung Galaxy E5, E7 and Grand Max are smartphones using the MSM8916 SoC released in 2015. e2015 and a2015 are similar, with some differences in accelerometer, MUIC and Vibrator. The common parts are shared in msm8916-samsung-a2015-common.dtsi to reduce duplication. Add a common device tree for with initial support for: - GPIO keys and vibrator - Hall sensor (except Grand Max) - SDHCI (internal and external storage) - USB Device Mode - UART (on USB connector via the SM5504 MUIC) - WCNSS (WiFi/BT) - Regulators - S3FWRN5 NFC (except Grand Max) The three devices (and all other variants of E5/E7/Grand Max released in 2015) are very similar, with some differences in display, touchscreen, sensors and NFC. The common parts are shared in msm8916-samsung-e2015-common.dtsi to reduce duplication. Unfortunately, some E5/E7/Grand Max were released with outdated 32-bit only firmware and never received any update from Samsung. Since the 32-bit TrustZone firmware is signed there seems to be no way currently to actually boot this device tree on arm64 Linux on those variants at the moment. However, it is possible to use this device tree by compiling an ARM32 kernel instead. The device tree can be easily built on ARM32 with an #include and it works really well there. To avoid confusion for others it is still better to add this device tree on arm64. Otherwise it's easy to forget to update this one when making some changes that affect all MSM8916 devices. Maybe someone finds a way to boot ARM64 Linux on those device at some point. In this case I expect that this device tree can be simply used as-is. Co-developed-by: Stephan Gerhold Signed-off-by: Stephan Gerhold Signed-off-by: Lin, Meng-Bo --- arch/arm64/boot/dts/qcom/Makefile | 3 ++ .../qcom/msm8916-samsung-e2015-common.dtsi | 39 +++++++++++++++++++ .../boot/dts/qcom/msm8916-samsung-e5.dts | 24 ++++++++++++ .../boot/dts/qcom/msm8916-samsung-e7.dts | 29 ++++++++++++++ .../dts/qcom/msm8916-samsung-grandmax.dts | 36 +++++++++++++++++ 5 files changed, 131 insertions(+) create mode 100644 arch/arm64/boot/dts/qcom/msm8916-samsung-e2015-common.d= tsi create mode 100644 arch/arm64/boot/dts/qcom/msm8916-samsung-e5.dts create mode 100644 arch/arm64/boot/dts/qcom/msm8916-samsung-e7.dts create mode 100644 arch/arm64/boot/dts/qcom/msm8916-samsung-grandmax.dts diff --git a/arch/arm64/boot/dts/qcom/Makefile b/arch/arm64/boot/dts/qcom/M= akefile index 2f8aec2cc6db..941494553b9e 100644 --- a/arch/arm64/boot/dts/qcom/Makefile +++ b/arch/arm64/boot/dts/qcom/Makefile @@ -15,6 +15,9 @@ dtb-$(CONFIG_ARCH_QCOM)=09+=3D msm8916-longcheer-l8910.dt= b dtb-$(CONFIG_ARCH_QCOM)=09+=3D msm8916-mtp.dtb dtb-$(CONFIG_ARCH_QCOM)=09+=3D msm8916-samsung-a3u-eur.dtb dtb-$(CONFIG_ARCH_QCOM)=09+=3D msm8916-samsung-a5u-eur.dtb +dtb-$(CONFIG_ARCH_QCOM)=09+=3D msm8916-samsung-e5.dtb +dtb-$(CONFIG_ARCH_QCOM)=09+=3D msm8916-samsung-e7.dtb +dtb-$(CONFIG_ARCH_QCOM)=09+=3D msm8916-samsung-grandmax.dtb dtb-$(CONFIG_ARCH_QCOM)=09+=3D msm8916-samsung-j5.dtb dtb-$(CONFIG_ARCH_QCOM)=09+=3D msm8916-samsung-serranove.dtb dtb-$(CONFIG_ARCH_QCOM)=09+=3D msm8916-wingtech-wt88047.dtb diff --git a/arch/arm64/boot/dts/qcom/msm8916-samsung-e2015-common.dtsi b/a= rch/arm64/boot/dts/qcom/msm8916-samsung-e2015-common.dtsi new file mode 100644 index 000000000000..373154ee2643 --- /dev/null +++ b/arch/arm64/boot/dts/qcom/msm8916-samsung-e2015-common.dtsi @@ -0,0 +1,39 @@ +// SPDX-License-Identifier: GPL-2.0-only + +#include "msm8916-samsung-a2015-common.dtsi" + +/ { +=09i2c-muic { +=09=09/* SM5504 MUIC instead of SM5502 */ +=09=09/delete-node/ extcon@25; + +=09=09muic: extcon@14 { +=09=09=09compatible =3D "siliconmitus,sm5504-muic"; +=09=09=09reg =3D <0x14>; + +=09=09=09interrupt-parent =3D <&msmgpio>; +=09=09=09interrupts =3D <12 IRQ_TYPE_EDGE_FALLING>; + +=09=09=09pinctrl-names =3D "default"; +=09=09=09pinctrl-0 =3D <&muic_int_default>; +=09=09}; +=09}; + +=09vibrator: vibrator { +=09=09compatible =3D "gpio-vibrator"; +=09=09enable-gpios =3D <&msmgpio 76 GPIO_ACTIVE_HIGH>; + +=09=09pinctrl-names =3D "default"; +=09=09pinctrl-0 =3D <&motor_en_default>; +=09}; +}; + +&msmgpio { +=09motor_en_default: motor-en-default { +=09=09pins =3D "gpio76"; +=09=09function =3D "gpio"; + +=09=09drive-strength =3D <2>; +=09=09bias-disable; +=09}; +}; diff --git a/arch/arm64/boot/dts/qcom/msm8916-samsung-e5.dts b/arch/arm64/b= oot/dts/qcom/msm8916-samsung-e5.dts new file mode 100644 index 000000000000..777eb934eb4b --- /dev/null +++ b/arch/arm64/boot/dts/qcom/msm8916-samsung-e5.dts @@ -0,0 +1,24 @@ +// SPDX-License-Identifier: GPL-2.0-only + +/dts-v1/; + +#include "msm8916-samsung-e2015-common.dtsi" + +/* + * NOTE: The original firmware from Samsung can only boot ARM32 kernels on= some + * variants. + * Unfortunately, the firmware is signed and cannot be replaced easily. + * There seems to be no way to boot ARM64 kernels on 32-bit devices at the + * moment, even though the hardware would support it. + * + * However, it is possible to use this device tree by compiling an ARM32 k= ernel + * instead. For clarity and build testing this device tree is maintained n= ext + * to the other MSM8916 device trees. However, it is actually used through + * arch/arm/boot/dts/qcom-msm8916-samsung-e5.dts + */ + +/ { +=09model =3D "Samsung Galaxy E5"; +=09compatible =3D "samsung,e5", "qcom,msm8916"; +=09chassis-type =3D "handset"; +}; diff --git a/arch/arm64/boot/dts/qcom/msm8916-samsung-e7.dts b/arch/arm64/b= oot/dts/qcom/msm8916-samsung-e7.dts new file mode 100644 index 000000000000..b412b61ca258 --- /dev/null +++ b/arch/arm64/boot/dts/qcom/msm8916-samsung-e7.dts @@ -0,0 +1,29 @@ +// SPDX-License-Identifier: GPL-2.0-only + +/dts-v1/; + +#include "msm8916-samsung-e2015-common.dtsi" + +/* + * NOTE: The original firmware from Samsung can only boot ARM32 kernels on= some + * variants. + * Unfortunately, the firmware is signed and cannot be replaced easily. + * There seems to be no way to boot ARM64 kernels on 32-bit devices at the + * moment, even though the hardware would support it. + * + * However, it is possible to use this device tree by compiling an ARM32 k= ernel + * instead. For clarity and build testing this device tree is maintained n= ext + * to the other MSM8916 device trees. However, it is actually used through + * arch/arm/boot/dts/qcom-msm8916-samsung-e7.dts + */ + +/ { +=09model =3D "Samsung Galaxy E7"; +=09compatible =3D "samsung,e7", "qcom,msm8916"; +=09chassis-type =3D "handset"; +}; + +&pm8916_l17 { +=09regulator-min-microvolt =3D <3000000>; +=09regulator-max-microvolt =3D <3000000>; +}; diff --git a/arch/arm64/boot/dts/qcom/msm8916-samsung-grandmax.dts b/arch/a= rm64/boot/dts/qcom/msm8916-samsung-grandmax.dts new file mode 100644 index 000000000000..41aada4bfb80 --- /dev/null +++ b/arch/arm64/boot/dts/qcom/msm8916-samsung-grandmax.dts @@ -0,0 +1,36 @@ +// SPDX-License-Identifier: GPL-2.0-only + +/dts-v1/; + +#include "msm8916-samsung-e2015-common.dtsi" + +/* + * NOTE: The original firmware from Samsung can only boot ARM32 kernels on= some + * variants. + * Unfortunately, the firmware is signed and cannot be replaced easily. + * There seems to be no way to boot ARM64 kernels on 32-bit devices at the + * moment, even though the hardware would support it. + * + * However, it is possible to use this device tree by compiling an ARM32 k= ernel + * instead. For clarity and build testing this device tree is maintained n= ext + * to the other MSM8916 device trees. However, it is actually used through + * arch/arm/boot/dts/qcom-msm8916-samsung-grandmax.dts + */ + +/ { +=09model =3D "Samsung Galaxy Grand Max"; +=09compatible =3D "samsung,grandmax", "qcom,msm8916"; +=09chassis-type =3D "handset"; + +=09/delete-node/ gpio-hall-sensor; +=09/delete-node/ i2c-nfc; +=09/delete-node/ i2c-tkey; +}; + +&vibrator { +=09enable-gpios =3D <&msmgpio 72 GPIO_ACTIVE_HIGH>; +}; + +&motor_en_default { +=09pins =3D "gpio72"; +}; -- 2.30.2