Received: by 2002:ac0:da4c:0:0:0:0:0 with SMTP id a12csp1973712imi; Sun, 24 Jul 2022 03:00:18 -0700 (PDT) X-Google-Smtp-Source: AGRyM1sljMe7idHkozJ1o0wVSDPik/dMHQ7SKbYQhfHbJczPHzSExNtZrxR67gBRTRQ//2L9VuvU X-Received: by 2002:a17:902:b581:b0:16d:2d15:3a93 with SMTP id a1-20020a170902b58100b0016d2d153a93mr7309308pls.45.1658656818508; Sun, 24 Jul 2022 03:00:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658656818; cv=none; d=google.com; s=arc-20160816; b=p95HKpQ46Zu4W9gn4lgvkir+I5AChxwZuCkmUDUZeZ8AF0301OInQPi+XsiQhlZPuD CPsvZBLEFx3F11VUwl2yDx6Elmk1pDlE69y66HGcuDN3UQQix/InaXDbSd1GKiQGfNt5 9f7wqhFDP/t4IeDYUm0KEF9zoboPp7pSmSR/0QuGBPBjKWfO2qcJzrW1WkXR9WlwswMp fgVsszPIjvJme5EUGK5fDxLBtsW/Wj48vjzfH3mIH48+mYcDx9XNMCid1U7MGgliVnz3 y3w1l8n+mGqBBnhhz2oMgIxkxOQRaTloaXv+hxJ9ydddl3II4PAd2s7TTSf2G9XP3MKz 7blw== 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=G33IYnAXaeNcisAWSd3I3CheqUJ739+CZjVoPSdZkbY=; b=bKWZRuqVGNffIP7Am2J0MSGR3V9A+Q4atUWTfT17iVFTQAH8maZBRLiapFTrCSkNCw 3NFiqqOdqT5cGy/+9QdU/ap8auEx3nMvYi6cqy+8Xjg1Kv2jL/ZYY1ex6e0pyKuxae4H lgNCH5LAcqDSiEJOmruLTVXSS7qd92PLfFA696/JLJxJwl9JZIuE9C5gBSNKBzSKKoz6 LCPO1fTh163+v3EOY7PPcLxBiYeJRGe0nTVKTzPk+U+fypQCs5HmmKnO2bzirKRTyg// gsug8e4Y85itmKKTV3dY3Rsi5p/RjPEL/53XYSAAtziii5ZAq9OXJpkEB+GmbREtJTE0 OPow== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@protonmail.com header.s=protonmail3 header.b=vx2VD1ah; 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 8-20020a631348000000b0041a6c24b4b6si11124483pgt.694.2022.07.24.03.00.04; Sun, 24 Jul 2022 03:00:18 -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=vx2VD1ah; 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 S233837AbiGXJx1 (ORCPT + 99 others); Sun, 24 Jul 2022 05:53:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35094 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230273AbiGXJx0 (ORCPT ); Sun, 24 Jul 2022 05:53:26 -0400 Received: from mail-40140.protonmail.ch (mail-40140.protonmail.ch [185.70.40.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D8C899FD7 for ; Sun, 24 Jul 2022 02:53:23 -0700 (PDT) Date: Sun, 24 Jul 2022 09:53:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1658656401; x=1658915601; bh=G33IYnAXaeNcisAWSd3I3CheqUJ739+CZjVoPSdZkbY=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:Feedback-ID:From:To: Cc:Date:Subject:Reply-To:Feedback-ID:Message-ID; b=vx2VD1ahXy44r9SHT8nCxiY+59BLNhd1hBpQhoIWSPontKNJBl/V644NaraHKiqm6 xDRwTnCQA3WZJTKXnELHL0TCco/V6Y8L3mCQX5+R5CLx3cW1M2PaA+sgpV7Xqv8sW/ CjizhWhDFhKX6smh9zqWw3zJgg1Pl2yWV1msRlk+lemTBJkB3XEtg7/sfmFpYOFDWw oESWThM4bAyTL0aQJUfqnfTkK0taJ57o8QIuZSUyEvfI3IdINKJ678sw2n+s7nJVO/ +/JeYOwKppp+p3UlkgvkHjqSHLBiYH6KHJzuJnW8VQnZxSEeCeehPseB7K2aWkE++/ Sc9d171RdgdBw== 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 v7 0/5] Add Samsung Galaxy E5/E7/Grand Max device trees Message-ID: <20220724095039.13568-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,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 v7: Fix incorrectly squashed haptic patch Fix email in Acked-by tag again 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.