Message ID | 20230928085537.3246669-2-wenst@chromium.org |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:cae8:0:b0:403:3b70:6f57 with SMTP id r8csp3355815vqu; Thu, 28 Sep 2023 07:31:16 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFwBxExgXNhA3Cf+dg1Y/SBVkDAod33cQA4VXlFuddPItHDyImo0IMXQf750v3faTWZlPRI X-Received: by 2002:a17:902:7048:b0:1c5:9d28:b2bb with SMTP id h8-20020a170902704800b001c59d28b2bbmr1102248plt.33.1695911476078; Thu, 28 Sep 2023 07:31:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1695911476; cv=none; d=google.com; s=arc-20160816; b=LXZhDOI5SMVgf1NMed1ez4O5BhBcDLOJy+z1WnOSa/KVOCnbXReuonlEjF+s+QB+V9 gC7ZiDON/fkqbvlSsORwebnNsq6ejMdsKHBvjNNj8/gc/RXR/VEungVykYiQVAW0ShMK rCuTLrxTlJvS0mXZL/1+MzDhP+X0k6sgSdwEzQAhXNlxyJovL5u8g2FyUzH9wIwkIQWn +s2OXXUPMiNyrUMM7NF3XwnOxLciPOPK7MFuukCUVokmhBEEu44spr4qpkaosz/F8Sil wvrGW0mhLyIv7aV96bLS63Q+NyRm0Gb5S0rmHeuOd4m/Qnx6f200hZnnVPPyKwnnPWCt YQDA== 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 :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=FRtfnBP9AwX73M7WqRrv6j9K/SzoRky3umOfoZElyY0=; fh=1VO4H82VDv9wq1mVoOWtG3wZpf9vPmQRrFvco4/uLOY=; b=jlI/SD5nRQCsEHbUbtM7a342L+oTz1hGk6jm94EReqv1QlEBA7+wtW80f/IFiZHH48 lvyltbvrElpsG9qsM/I6a30KaZoHUafoUsWBlPbUGICiGepf7rj8Er5YXd1bCZTaC7dA ZVzeklzZZQGCOM/Orm42rxKLn2nQSMf3bX5+m5TtEhJPx7UIW9Ra0Hw837YAHJK2Vqxu jAUjt/CTmekZaqIpg6p4Vih6MR6pnMwVZQC8F2eYCs72lOxqrK8fQH8LALc1MFaNWV/j UgWkwLBDdRTmmOBw3yQaGrntZdgrK7RWCcUeiCzB6KMmaKYh3RBNK1OFOZlFtek5tIJD iBOw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=nNu2oiDE; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.36 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: from pete.vger.email (pete.vger.email. [23.128.96.36]) by mx.google.com with ESMTPS id d3-20020a170902f14300b001c62b659fa0si8078403plb.122.2023.09.28.07.31.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Sep 2023 07:31:16 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.36 as permitted sender) client-ip=23.128.96.36; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=nNu2oiDE; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.36 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by pete.vger.email (Postfix) with ESMTP id C005C809BE57; Thu, 28 Sep 2023 01:56:29 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at pete.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231405AbjI1I4B (ORCPT <rfc822;pwkd43@gmail.com> + 21 others); Thu, 28 Sep 2023 04:56:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49176 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231435AbjI1Iz6 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Thu, 28 Sep 2023 04:55:58 -0400 Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B3C17B7 for <linux-kernel@vger.kernel.org>; Thu, 28 Sep 2023 01:55:56 -0700 (PDT) Received: by mail-pf1-x432.google.com with SMTP id d2e1a72fcca58-690f7bf73ddso9960519b3a.2 for <linux-kernel@vger.kernel.org>; Thu, 28 Sep 2023 01:55:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; t=1695891356; x=1696496156; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=FRtfnBP9AwX73M7WqRrv6j9K/SzoRky3umOfoZElyY0=; b=nNu2oiDEcLtwMa4eozythgdjGBLmTpyIMJiqGEu9HRwKm41Ei2jLNZB/flOmvyI9KF afrontNqpyZVw3LiICXDgOUNkhiIq5JgG8NENQIlpH1FcFOOLwKZkZM+JOEWszqR8QMh /D3u9jRvluIq0wZ6925OrG5nmSsOp/BhDuR2Q= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695891356; x=1696496156; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=FRtfnBP9AwX73M7WqRrv6j9K/SzoRky3umOfoZElyY0=; b=A9kdvPBGc0shv49gBVnH9PVGw5dCIzRvG70lutirf7YR6yOtkEJHuFR8uOk8UVMgpr GfX9gINS2AMZRtZmB4UM7pFyEmBMViXZuC0fnsnLuHxHhZx56q3oWUEw6T33ZJwsxGnt 43H5ICM6p7khNe/EGdxjOZhirTYc6f/fcyNxpriI0cT2GGGrY/jy9UPTZkDo+hfPizAy BeoVkrLb0Caakiw4fc/W8Dr03tGaZ139a5OwOVMiYH6iBu2nrVIjN7nQwFz3wUloR5vD whVuR3pd6uXDKD5UKiUtWWpD/w2HiP7bjIjUdCVnaYpCESeD9zauNjahqww7a3VlLvnG p7MA== X-Gm-Message-State: AOJu0YzvndTwgF6wONiAUcv7wa3qvLVZmGX0iLnbRAlvPHpN9xzZ/dS1 VJeHCN7f4iGl2pBWD0lem2Mhkw== X-Received: by 2002:a05:6a00:14c9:b0:693:3783:4a29 with SMTP id w9-20020a056a0014c900b0069337834a29mr619701pfu.20.1695891356126; Thu, 28 Sep 2023 01:55:56 -0700 (PDT) Received: from wenstp920.tpe.corp.google.com ([2401:fa00:1:10:6747:c12a:dbfd:2cc7]) by smtp.gmail.com with ESMTPSA id y7-20020aa78047000000b006879493aca0sm1754016pfm.26.2023.09.28.01.55.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Sep 2023 01:55:55 -0700 (PDT) From: Chen-Yu Tsai <wenst@chromium.org> To: Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>, Matthias Brugger <matthias.bgg@gmail.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Mark Brown <broonie@kernel.org> Cc: Chen-Yu Tsai <wenst@chromium.org>, Lee Jones <lee@kernel.org>, Zhiyong Tao <zhiyong.tao@mediatek.com>, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Subject: [PATCH v4 01/12] dt-bindings: mfd: mt6397: Split out compatible for MediaTek MT6366 PMIC Date: Thu, 28 Sep 2023 16:55:24 +0800 Message-ID: <20230928085537.3246669-2-wenst@chromium.org> X-Mailer: git-send-email 2.42.0.582.g8ccd20d70d-goog In-Reply-To: <20230928085537.3246669-1-wenst@chromium.org> References: <20230928085537.3246669-1-wenst@chromium.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on pete.vger.email Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (pete.vger.email [0.0.0.0]); Thu, 28 Sep 2023 01:56:29 -0700 (PDT) X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1778284789674729903 X-GMAIL-MSGID: 1778292072037784213 |
Series |
regulator: mt6366: Split out of MT6358 and cleanup
|
|
Commit Message
Chen-Yu Tsai
Sept. 28, 2023, 8:55 a.m. UTC
The MT6366 PMIC is mostly, but not fully, compatible with MT6358. It has a different set of regulators. Specifically, it lacks the camera related VCAM* LDOs and VLDO28, but has additional VM18, VMDDR, and VSRAM_CORE LDOs. The PMICs contain a chip ID register that can be used to detect which exact model is preset, so it is possible to share a common base compatible string. Add a separate compatible for the MT6366 PMIC, with a fallback to the MT6358 PMIC. Fixes: 49be16305587 ("dt-bindings: mfd: Add compatible for the MediaTek MT6366 PMIC") Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> --- Documentation/devicetree/bindings/mfd/mt6397.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
Comments
Il 28/09/23 10:55, Chen-Yu Tsai ha scritto: > The MT6366 PMIC is mostly, but not fully, compatible with MT6358. It has > a different set of regulators. Specifically, it lacks the camera related > VCAM* LDOs and VLDO28, but has additional VM18, VMDDR, and VSRAM_CORE LDOs. > > The PMICs contain a chip ID register that can be used to detect which > exact model is preset, so it is possible to share a common base > compatible string. > > Add a separate compatible for the MT6366 PMIC, with a fallback to the > MT6358 PMIC. > > Fixes: 49be16305587 ("dt-bindings: mfd: Add compatible for the MediaTek MT6366 PMIC") > Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
On Thu, 28 Sep 2023 16:55:24 +0800, Chen-Yu Tsai wrote: > The MT6366 PMIC is mostly, but not fully, compatible with MT6358. It has > a different set of regulators. Specifically, it lacks the camera related > VCAM* LDOs and VLDO28, but has additional VM18, VMDDR, and VSRAM_CORE LDOs. > > The PMICs contain a chip ID register that can be used to detect which > exact model is preset, so it is possible to share a common base > compatible string. > > [...] Applied, thanks! [01/12] dt-bindings: mfd: mt6397: Split out compatible for MediaTek MT6366 PMIC commit: 9e2a2fd1ca0555bd0c278cd4061cc4bd9c8d0f7f -- Lee Jones [李琼斯]
diff --git a/Documentation/devicetree/bindings/mfd/mt6397.txt b/Documentation/devicetree/bindings/mfd/mt6397.txt index 294693a8906c..10540aa7afa1 100644 --- a/Documentation/devicetree/bindings/mfd/mt6397.txt +++ b/Documentation/devicetree/bindings/mfd/mt6397.txt @@ -22,8 +22,9 @@ compatible: "mediatek,mt6323" for PMIC MT6323 "mediatek,mt6331" for PMIC MT6331 and MT6332 "mediatek,mt6357" for PMIC MT6357 - "mediatek,mt6358" for PMIC MT6358 and MT6366 + "mediatek,mt6358" for PMIC MT6358 "mediatek,mt6359" for PMIC MT6359 + "mediatek,mt6366", "mediatek,mt6358" for PMIC MT6366 "mediatek,mt6397" for PMIC MT6397 Optional subnodes: @@ -40,6 +41,7 @@ Optional subnodes: - compatible: "mediatek,mt6323-regulator" see ../regulator/mt6323-regulator.txt - compatible: "mediatek,mt6358-regulator" + - compatible: "mediatek,mt6366-regulator", "mediatek-mt6358-regulator" see ../regulator/mt6358-regulator.txt - compatible: "mediatek,mt6397-regulator" see ../regulator/mt6397-regulator.txt