Received: by 2002:ac0:da4c:0:0:0:0:0 with SMTP id a12csp1659351imi; Sat, 23 Jul 2022 12:56:03 -0700 (PDT) X-Google-Smtp-Source: AGRyM1t9ADND5PAHvMkt0QlGVaxhpjD4YdTAjF6wOCqqNm7ngLlYlYcbIuftNW2o9XvtDietZQ5Q X-Received: by 2002:a17:907:2c59:b0:72b:8ea2:5128 with SMTP id hf25-20020a1709072c5900b0072b8ea25128mr4422754ejc.590.1658606163299; Sat, 23 Jul 2022 12:56:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658606163; cv=none; d=google.com; s=arc-20160816; b=u+7L8m9gZjB1klCMu8eNHoWUplU6c5mpHOU/0OLqKgmYIMRCleDS5FMlWxxVqjQDFa C0LqjLmuL30JMuFgkbr2BW9EirToATH5aW66kzCE7aMR+NR2aHZe0Bqh9b19gFYc/2Tj JrjAzqdyHoaT+faNWdIVsw8L6vbHPAX3uRf0Z107w0k2AgzsD8Ic8TquyB8uX74Sdr2E LJnFa0Fz7UGcHKpBX7qWLDy9WRqXugSJGl4XnhQi1FWPQeo0UyXBanA3Wjx4lwa9JLzI IlXX4iSVHQ8dgc3uZeRXOupzZaPqRcGLvQrS/bAApbkdMdSNdsEVIAmnHJj8x+plGpjV yF7g== 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:message-id:subject:reply-to:cc:from:to:dkim-signature :date; bh=m8R1HiRlIp9Imo0Yj9VIVGVtSUHR6cnW7lkME/XSDRo=; b=N7dAFahsQUlnXUfL9BJL0swZs1Sp5fIxuLNBO4C3xf6TkEq5zdGm6AbCBNGZ/U56Bt Hfosanlm4pig1LwPU3iHQ8I4MMd4XT4Mas4E4p6cDnVz9Z+3qjBoHhDtPDcrItESuxbH sK92CCXBOZWDV5K0CkyjP6hWXm54R6JfoAGfbAHKlz9eEVlqS0Syy6TO2OkSWFHFkp1b SMiV7dNLI8snkAIF3+jeWwldd7JKJlsvu/mc+IPFFyK6OM2Gc7cPRAnND52t2batrqrB z3okVC8GvTuheciovxZeLMlVElzog9fCmpeXjiUs7UI+fFGxWaX0hMyty9I5mCELRSjI rQVg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@protonmail.com header.s=protonmail3 header.b=DV1+t+qX; 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 m11-20020a1709066d0b00b00722dcffcce0si8019064ejr.434.2022.07.23.12.55.11; Sat, 23 Jul 2022 12:56:03 -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=DV1+t+qX; 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 S238466AbiGWS56 (ORCPT + 99 others); Sat, 23 Jul 2022 14:57:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56580 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232490AbiGWS5y (ORCPT ); Sat, 23 Jul 2022 14:57:54 -0400 Received: from mail-4027.protonmail.ch (mail-4027.protonmail.ch [185.70.40.27]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 973AF1658B; Sat, 23 Jul 2022 11:57:52 -0700 (PDT) Date: Sat, 23 Jul 2022 18:57:33 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1658602670; x=1658861870; bh=m8R1HiRlIp9Imo0Yj9VIVGVtSUHR6cnW7lkME/XSDRo=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:Feedback-ID:From:To: Cc:Date:Subject:Reply-To:Feedback-ID:Message-ID; b=DV1+t+qXdVU50nQIMWc8T6Jzh7S0g5g4U6/w2tstnOE0yWj0+gO4mUgAZHgbLumCm Tj7VQIEGCSUQpVaHYbvJrDeC7U47ys9bUWPmuhknp9na6TxYdidKXfADa6/WdZJ9OO IPrqMoBTp1X6w4LqvUs47dXuQC46qA/sI4g42aKvnGDmGLzb9umN/Ognsk3qj8Y/yO V16VQdCPmDKDw9g05rqSc9l7vORyn5fhG/RlQ3xjaurmu0rTO8ktXdMbXlUkXeV6vH yAwbe0lTpwIJsg35k/zBNCdGCcNXO8dcgXfbcC5f3J3GL56PWqs89+fzK5pG9OheEE jqJDV7PbKhxaQ== To: devicetree@vger.kernel.org From: "Lin, Meng-Bo" Cc: Andy Gross , Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , Arnd Bergmann , Olof Johansson , Stephen Boyd , Stephan Gerhold , Nikita Travkin , soc@kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, ~postmarketos/upstreaming@lists.sr.ht Reply-To: "Lin, Meng-Bo" Subject: [PATCH v6 0/5] Add Samsung Galaxy E5/E7/Grand Max device trees Message-ID: <20220723185424.203340-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 v6: Rename touchscreen analog regulator for a2015 Use regulator haptic instead of GPIO vibrator Fix email in Acked-by tag v5: Fix Error: arch/arm64/boot/dts/qcom/msm8916-samsung-e2015-common.dtsi:36.2-22 Properti= es must precede subnodes Restore Acked-by tag in the dt-bindings patch v4: Disable i2c2 until lis2hh12 accelerometer is fixed. Add GPIO LEDs for Grand Max. v3: Add a cover letter and changelog v2: Add dt-bindings documentation 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. 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.