Message ID | 20231106185736.668966-1-hugo@hugovil.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:8f47:0:b0:403:3b70:6f57 with SMTP id j7csp2862889vqu; Mon, 6 Nov 2023 10:58:16 -0800 (PST) X-Google-Smtp-Source: AGHT+IF0qBb0oNQPBQamGTv/OH2NQbtDeWtjB3/FqpeosDUHpj9/iZKnfojDWhVafitjsljzsTTv X-Received: by 2002:a05:6808:a03:b0:3a8:7f65:a96 with SMTP id n3-20020a0568080a0300b003a87f650a96mr33681530oij.33.1699297095769; Mon, 06 Nov 2023 10:58:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1699297095; cv=none; d=google.com; s=arc-20160816; b=sKifxbVKEChg5IsQetIyrU+fDJo+7F/5pGoGyfbvD4Z2W5X5fkaXI4hV6XnwotiDTq eqBe0+8mZGQP1YAn7UEdEsKPTYq0Yxp28WHuFhTq2TSd75zyEsSn/GDRQdUaIrL7gh9W Bc+fcBl+Cm4of80GlXzu4lK12CdAdMbValMfv47rKUuc0rSxu6cOKQaElfrKwBEi76B0 RNwwgbg8tnREUkQaQZORmGmWbv8fYZZWr1W5aQKa0r10KDh03gidFIF4PULgUqhZOhjA nppYZLTCIe2n/UJJn2BX/vRvCcJsvG013P/mDRzvaULEaP5NrSEDLwmAOaDVRZhEw0ME p7og== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:subject:content-transfer-encoding:mime-version :message-id:date:cc:to:from:dkim-signature; bh=x0KdJV1T5bwu5vuWgfbzxKBUcidqlaq+cthXaDBuzok=; fh=X6r1Bea5hzS19+N13jbqbcZvZbdfvOXu8EPn1uBO7NY=; b=lOOe3LPWqSns7dgWtD8uM9Vfj8HJ38IUgSYizybkPZBJIvQC6XTCXdi2wwniwS99T7 MsPCHBEqMNWsiLdeyIKdBjZPadDEaRzKCJSk6I6YoitlBntdSTMwvul4rMxg5QphqoUv hzcLSZLKa9YW5ocOGevh0l2JGg+zrvrtv+LHC6eOqglD1L+DjbnhXxFLxXzKuuaT5Ji3 x3BxFxy2LEBBsX9tu50ctjcdAJPy9+H3WdcP2dms6esEBvxkVoakbFsCyZOVHf1T6dRA 3vFsnYwAWQ1BjbP1O1PNlzNXJHvqimnJstaicJC0ED0tpK555h3dQlz/WqWG7CCGWaLB 9LeQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@hugovil.com header.s=x header.b=H1Hra38O; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:2 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from agentk.vger.email (agentk.vger.email. [2620:137:e000::3:2]) by mx.google.com with ESMTPS id ch2-20020a056a0208c200b005bd2e734ceasi307701pgb.368.2023.11.06.10.58.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 Nov 2023 10:58:15 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:2 as permitted sender) client-ip=2620:137:e000::3:2; Authentication-Results: mx.google.com; dkim=pass header.i=@hugovil.com header.s=x header.b=H1Hra38O; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:2 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by agentk.vger.email (Postfix) with ESMTP id AA9E580B816E; Mon, 6 Nov 2023 10:58:13 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at agentk.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232329AbjKFS56 (ORCPT <rfc822;lhua1029@gmail.com> + 34 others); Mon, 6 Nov 2023 13:57:58 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60562 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231801AbjKFS55 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 6 Nov 2023 13:57:57 -0500 Received: from mail.hugovil.com (mail.hugovil.com [162.243.120.170]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DB9C7BB; Mon, 6 Nov 2023 10:57:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=hugovil.com ; s=x; h=Subject:Content-Transfer-Encoding:MIME-Version:Message-Id:Date:Cc:To :From:subject:date:message-id:reply-to; bh=x0KdJV1T5bwu5vuWgfbzxKBUcidqlaq+cthXaDBuzok=; b=H1Hra38O3Zm+m9TWfOFNzqgNhY FXJ5HiNpAB0PHcU7xEe4Zc5hGuOs0fNPSpW3lYJEjU6qONoxdgM3nvJ49TnTqO8KHGvr5PJZfaxFB gvIRs4cdddEk/F29yYazWGVCGkafQij+Y8jRCLiU0f4YjkFl4sfUoRcdmOwl04XSS02I=; Received: from modemcable168.174-80-70.mc.videotron.ca ([70.80.174.168]:37940 helo=pettiford.lan) by mail.hugovil.com with esmtpa (Exim 4.92) (envelope-from <hugo@hugovil.com>) id 1r04n5-0005zO-OZ; Mon, 06 Nov 2023 13:57:40 -0500 From: Hugo Villeneuve <hugo@hugovil.com> To: Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>, Sascha Hauer <s.hauer@pengutronix.de>, Pengutronix Kernel Team <kernel@pengutronix.de>, Fabio Estevam <festevam@gmail.com>, NXP Linux Team <linux-imx@nxp.com> Cc: hugo@hugovil.com, Hugo Villeneuve <hvilleneuve@dimonoff.com>, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Date: Mon, 6 Nov 2023 13:57:36 -0500 Message-Id: <20231106185736.668966-1-hugo@hugovil.com> X-Mailer: git-send-email 2.39.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 70.80.174.168 X-SA-Exim-Mail-From: hugo@hugovil.com X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on agentk.vger.email X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 Subject: [PATCH] arm64: dts: imx8mn-var-som-symphony: add vcc supply for PCA9534 X-SA-Exim-Version: 4.2.1 (built Wed, 08 May 2019 21:11:16 +0000) X-SA-Exim-Scanned: Yes (on mail.hugovil.com) 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 (agentk.vger.email [0.0.0.0]); Mon, 06 Nov 2023 10:58:13 -0800 (PST) X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1781842151613466777 X-GMAIL-MSGID: 1781842151613466777 |
Series |
arm64: dts: imx8mn-var-som-symphony: add vcc supply for PCA9534
|
|
Commit Message
Hugo Villeneuve
Nov. 6, 2023, 6:57 p.m. UTC
From: Hugo Villeneuve <hvilleneuve@dimonoff.com> The following warning is shown when probing device: pca953x 1-0020: supply vcc not found, using dummy regulator Add fixed 3.3v regulator as vcc supply to silence the warning. Signed-off-by: Hugo Villeneuve <hvilleneuve@dimonoff.com> --- arch/arm64/boot/dts/freescale/imx8mn-var-som-symphony.dts | 1 + 1 file changed, 1 insertion(+) base-commit: d2f51b3516dade79269ff45eae2a7668ae711b25
Comments
On 06/11/2023 19:57, Hugo Villeneuve wrote: > From: Hugo Villeneuve <hvilleneuve@dimonoff.com> > > The following warning is shown when probing device: > > pca953x 1-0020: supply vcc not found, using dummy regulator > > Add fixed 3.3v regulator as vcc supply to silence the warning. > This is not really a warning. It's perfectly fine to use dummy regulator. Adding such fixed supply has sense in following cases: 1. Bindings require the supply, 2. This is in fact exactly that supply (verified on schematics). Best regards, Krzysztof
On Mon, 6 Nov 2023 21:39:42 +0100 Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote: > On 06/11/2023 19:57, Hugo Villeneuve wrote: > > From: Hugo Villeneuve <hvilleneuve@dimonoff.com> > > > > The following warning is shown when probing device: > > > > pca953x 1-0020: supply vcc not found, using dummy regulator > > > > Add fixed 3.3v regulator as vcc supply to silence the warning. > > > > This is not really a warning. It's perfectly fine to use dummy > regulator. Adding such fixed supply has sense in following cases: > 1. Bindings require the supply, > 2. This is in fact exactly that supply (verified on schematics). > > Best regards, > Krzysztof Hi Krzysztof, this is case #2, but looking more closely at the carrier board (symphony) schematics, it is not exactly the "reg_3v3_fixed" supply I mentioned in the patch, as "reg_3v3_fixed" is located on the SOM and only powers SOM components. However, "reg_3v3_fixed", which is an always-on regulator (no software enable control), is used as the enable input to a mosfet switch (Q2) on the carrier board to generate the 3.3V (label BASE_PER_3V3 on the schematics) used by all peripherals on that carrier board. I guess I could then define a new "always-on" regulator labeled as, for example, base_per_3v3, and then assign the pca953x vcc-supply property to it? Hugo.
On 06/11/2023 22:36, Hugo Villeneuve wrote: > On Mon, 6 Nov 2023 21:39:42 +0100 > Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote: > >> On 06/11/2023 19:57, Hugo Villeneuve wrote: >>> From: Hugo Villeneuve <hvilleneuve@dimonoff.com> >>> >>> The following warning is shown when probing device: >>> >>> pca953x 1-0020: supply vcc not found, using dummy regulator >>> >>> Add fixed 3.3v regulator as vcc supply to silence the warning. >>> >> >> This is not really a warning. It's perfectly fine to use dummy >> regulator. Adding such fixed supply has sense in following cases: >> 1. Bindings require the supply, >> 2. This is in fact exactly that supply (verified on schematics). >> >> Best regards, >> Krzysztof > > Hi Krzysztof, > this is case #2, but looking more closely at the carrier board > (symphony) schematics, it is not exactly the "reg_3v3_fixed" supply I > mentioned in the patch, as "reg_3v3_fixed" is located on the SOM and > only powers SOM components. > > However, "reg_3v3_fixed", which is an always-on regulator (no software > enable control), is used as the enable input to a mosfet switch (Q2) on > the carrier board to generate the 3.3V (label BASE_PER_3V3 on the > schematics) used by all peripherals on that carrier board. > > I guess I could then define a new "always-on" regulator labeled as, > for example, base_per_3v3, and then assign the pca953x vcc-supply > property to it? I guess this could be the same supply, even if this is not 100% true. However it would be good if you put above explanation in the commit msg. Best regards, Krzysztof
On Tue, 7 Nov 2023 08:14:03 +0100 Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote: > On 06/11/2023 22:36, Hugo Villeneuve wrote: > > On Mon, 6 Nov 2023 21:39:42 +0100 > > Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote: > > > >> On 06/11/2023 19:57, Hugo Villeneuve wrote: > >>> From: Hugo Villeneuve <hvilleneuve@dimonoff.com> > >>> > >>> The following warning is shown when probing device: > >>> > >>> pca953x 1-0020: supply vcc not found, using dummy regulator > >>> > >>> Add fixed 3.3v regulator as vcc supply to silence the warning. > >>> > >> > >> This is not really a warning. It's perfectly fine to use dummy > >> regulator. Adding such fixed supply has sense in following cases: > >> 1. Bindings require the supply, > >> 2. This is in fact exactly that supply (verified on schematics). > >> > >> Best regards, > >> Krzysztof > > > > Hi Krzysztof, > > this is case #2, but looking more closely at the carrier board > > (symphony) schematics, it is not exactly the "reg_3v3_fixed" supply I > > mentioned in the patch, as "reg_3v3_fixed" is located on the SOM and > > only powers SOM components. > > > > However, "reg_3v3_fixed", which is an always-on regulator (no software > > enable control), is used as the enable input to a mosfet switch (Q2) on > > the carrier board to generate the 3.3V (label BASE_PER_3V3 on the > > schematics) used by all peripherals on that carrier board. > > > > I guess I could then define a new "always-on" regulator labeled as, > > for example, base_per_3v3, and then assign the pca953x vcc-supply > > property to it? > > I guess this could be the same supply, even if this is not 100% true. > However it would be good if you put above explanation in the commit msg. Hi, I prefer to add a new supply, and with a proper label it will be more self-documenting, and I will still add part of this explanation to the updated commit message. Thank you, Hugo.
diff --git a/arch/arm64/boot/dts/freescale/imx8mn-var-som-symphony.dts b/arch/arm64/boot/dts/freescale/imx8mn-var-som-symphony.dts index a7a57442cb81..583b9859df3a 100644 --- a/arch/arm64/boot/dts/freescale/imx8mn-var-som-symphony.dts +++ b/arch/arm64/boot/dts/freescale/imx8mn-var-som-symphony.dts @@ -79,6 +79,7 @@ pca9534: gpio@20 { interrupts = <7 IRQ_TYPE_EDGE_FALLING>; #gpio-cells = <2>; wakeup-source; + vcc-supply = <®_3v3_fixed>; /* USB 3.0 OTG (usbotg1) / SATA port switch, set to USB 3.0 */ usb3-sata-sel-hog {