From nobody Mon May 11 04:11:55 2026 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id CB91BC433F5 for ; Thu, 14 Apr 2022 19:15:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345150AbiDNTRX (ORCPT ); Thu, 14 Apr 2022 15:17:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47544 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1343572AbiDNTRP (ORCPT ); Thu, 14 Apr 2022 15:17:15 -0400 Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9DC3B5A5AB for ; Thu, 14 Apr 2022 12:14:48 -0700 (PDT) Received: by mail-pj1-x102c.google.com with SMTP id j8-20020a17090a060800b001cd4fb60dccso6588450pjj.2 for ; Thu, 14 Apr 2022 12:14:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=t3B8R1R0UeZGzGIpSP1VsaVNrwO0rNV84syuceuTaAY=; b=b5Fs5sDOa79UhjbzPTs/JgC3ZwAG7NBgvr6aXt7bYFnhtYwh5Qhq4awyCED6jrY/ls 6kXC+XwBxlCEfJYSsKooIzN+n2k85eLJA4On2pukofnTXDJI47phHjHNzpuoqz1Z/hfA CUkxnAUQ6ExxLagh3N2auhdDGFfha9QHP7p2/1ZLM/SN9R8l0eGlJFlk0qTI607sY7nQ buU+vmnbqP0VzyEnqYwpcnJJ6VqPMt1cjurzeEvmmIRsmBNDA13xA5+n6NRTaaA7gHH5 s2eyvq89sXUs87L/lCOC1ufp8KMyH9jOxFNd/uTuundTTixrIxgw66cT4NysAjnIH7mE MLDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=t3B8R1R0UeZGzGIpSP1VsaVNrwO0rNV84syuceuTaAY=; b=gVhySQOTalFA85LZhTYrhFMh6pJBNW6tebjnnUym3k3lSkKyFGTq347Clq6ktkgOvl eNF4aHfkpzVwp9eYS9uKAi6ZOxF+nySS/Q+6283rBDVdXNOuRPRL8VC5FUExg48FXb+R /hQiyEmzJmeeWk10f8nrlInkqpI8zUDssiIQi+7pIBjsfsDjqTkElVlXhdBlVIatTYJx 3xspPD4V/XHqdsewBa/moX3uV8ePmG1B/VtDVXgzRGZtsL+qFmeH5mGrSCAVrURrDSS/ UsPC/w52FYLCUCL9KnrYEFUdQKXXJqvJOMcgUt1nBbjPMUo1KbgFV1BU/PxfqOIwhnyb IA2w== X-Gm-Message-State: AOAM5302RN7MYWw9wnn9aimsnv9t0lO1tIsNjbAwVFyPVsM65mzZ51Oi BOJxCV3VlFS+3adAm5aul20nBA== X-Google-Smtp-Source: ABdhPJyKMz9LyNs/fJ1c9/QdkmkC1o9RA5i86GWq//yvKqL0YII6HsSpPoBCxC8yJnQ9BCUWp+qP2A== X-Received: by 2002:a17:902:8304:b0:155:d594:5c04 with SMTP id bd4-20020a170902830400b00155d5945c04mr47435554plb.105.1649963688006; Thu, 14 Apr 2022 12:14:48 -0700 (PDT) Received: from x1.hsd1.or.comcast.net ([2601:1c2:1001:7090:5b60:6a76:138d:2646]) by smtp.gmail.com with ESMTPSA id e12-20020a056a001a8c00b004fab88d7de8sm614148pfv.132.2022.04.14.12.14.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 14 Apr 2022 12:14:47 -0700 (PDT) From: Drew Fustini To: Rob Herring , Krzysztof Kozlowski , Nishanth Menon , Santosh Shilimkar , Dave Gerlach , Tony Lindgren Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Drew Fustini Subject: [PATCH v2 1/2] dt-bindings: wkup-m3-ipc: Add ti,set-io-isolation property Date: Thu, 14 Apr 2022 12:12:49 -0700 Message-Id: <20220414191250.2969282-2-dfustini@baylibre.com> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20220414191250.2969282-1-dfustini@baylibre.com> References: <20220414191250.2969282-1-dfustini@baylibre.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" Add documentation for the ti,set-io-isolation DT property on the wkup_m3_ipc node which tells the wkup_m3_ipc driver to use the wkup_m3 to enable IO Isolation during low power mode transitions on am43xx platforms. Signed-off-by: Dave Gerlach [dfustini: convert to YAML, make DTS example that passes check] Signed-off-by: Drew Fustini --- Changes from v1: - correct typo of 'ti,set-io-isolation' property in subject - make 'ti,set-io-isolation' only valid for 'ti,am4372-wkup-m3-ipc' .../bindings/soc/ti/wkup-m3-ipc.yaml | 79 +++++++++++++++++-- 1 file changed, 74 insertions(+), 5 deletions(-) diff --git a/Documentation/devicetree/bindings/soc/ti/wkup-m3-ipc.yaml b/Do= cumentation/devicetree/bindings/soc/ti/wkup-m3-ipc.yaml index 7f4a75c5fcaa..97eb0faef345 100644 --- a/Documentation/devicetree/bindings/soc/ti/wkup-m3-ipc.yaml +++ b/Documentation/devicetree/bindings/soc/ti/wkup-m3-ipc.yaml @@ -24,14 +24,22 @@ description: |+ A wkup_m3_ipc device node is used to represent the IPC registers within = an SoC. =20 - Support for VTT Toggle - =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D + Support for VTT Toggle with GPIO pin + =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D On some boards like the AM335x EVM-SK and the AM437x GP EVM, a GPIO pin = is connected to the enable pin on the DDR VTT regulator. This allows the regulator to be disabled upon suspend and enabled upon resume. Please no= te that the GPIO pin must be part of the GPIO0 module as only this GPIO mod= ule is in the wakeup power domain. =20 + Support for IO Isolation + =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D + On AM437x SoCs, certain pins can be forced into an alternate state when = IO + isolation is activated. Those pins have pad control registers prefixed by + 'CTRL_CONF_' that contain DS0 (e.g. deep sleep) configuration bits that = can + override the pin's existing bias (pull-up/pull-down) and value (high/low= ) when + IO isolation is active. + properties: compatible: enum: @@ -63,6 +71,25 @@ properties: $ref: /schemas/types.yaml#/definitions/uint32 description: GPIO pin connected to enable pin on VTT regulator =20 + ti,set-io-isolation: + type: boolean + description: + If this property is present, then the wkup_m3_ipc driver will instru= ct + the CM3 firmware to activate IO isolation when suspending to deep sl= eep. + This can be leveraged by a board design to put other devices on the = board + into a low power state. + + allOf: + - if: + properties: + compatible: + not: + contains: + const: ti,am4372-wkup-m3-ipc + then: + properties: + ti,set-io-isolation: false + required: - compatible - reg @@ -74,21 +101,63 @@ additionalProperties: false =20 examples: - | + /* Example for AM335x SoC */ soc { #address-cells =3D <1>; #size-cells =3D <1>; =20 - mailbox: mailbox { + am335x_mailbox: mailbox { #mbox-cells =3D <1>; }; =20 - wkup_m3_ipc: wkup_m3_ipc@1324 { + wkup_m3_ipc@1324 { compatible =3D "ti,am3352-wkup-m3-ipc"; reg =3D <0x1324 0x24>; interrupts =3D <78>; ti,rproc =3D <&wkup_m3>; - mboxes =3D <&mailbox &mbox_wkupm3>; + mboxes =3D <&am335x_mailbox &mbox_wkupm3>; ti,vtt-gpio-pin =3D <7>; }; }; + + - | + /* + * Example for AM473x SoC: + * On the AM437x-GP-EVM board, gpio5_7 is wired to enable pin of the D= DR VTT + * regulator. The 'ddr_vtt_toggle_default' pinmux node configures gpio= 5_7 + * for pull-up during normal system operation. However, the DS0 (deep = sleep) + * state of the pin is configured for pull-down and thus the VTT regul= ator + * will be disabled to save power when IO isolation is active. Note th= at + * this method is an alternative to using the 'ti,vtt-gpio-pin' proper= ty. + */ + #include + soc { + #address-cells =3D <1>; + #size-cells =3D <1>; + + am437x_mailbox: mailbox { + #mbox-cells =3D <1>; + }; + + am43xx_pinmux { + pinctrl-names =3D "default"; + pinctrl-0 =3D <&ddr3_vtt_toggle_default>; + + ddr3_vtt_toggle_default: ddr_vtt_toggle_default { + pinctrl-single,pins =3D < + 0x25C (DS0_PULL_UP_DOWN_EN | PIN_OUTPUT_PULLUP | DS0_F= ORCE_OFF_MODE | MUX_MODE7) + >; + }; + }; + + wkup_m3_ipc@1324 { + compatible =3D "ti,am4372-wkup-m3-ipc"; + reg =3D <0x1324 0x24>; + interrupts =3D <78>; + ti,rproc =3D <&wkup_m3>; + mboxes =3D <&am437x_mailbox &mbox_wkupm3>; + ti,set-io-isolation; + }; + }; + ... --=20 2.32.0 From nobody Mon May 11 04:11:55 2026 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6C1E2C433EF for ; Thu, 14 Apr 2022 19:15:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345250AbiDNTRa (ORCPT ); Thu, 14 Apr 2022 15:17:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47550 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1343881AbiDNTRP (ORCPT ); Thu, 14 Apr 2022 15:17:15 -0400 Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 927467247C for ; Thu, 14 Apr 2022 12:14:49 -0700 (PDT) Received: by mail-pj1-x1035.google.com with SMTP id ll10so5942604pjb.5 for ; Thu, 14 Apr 2022 12:14:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=sC6zeBvAQu12F4pHcyP2yBc/sNcvkHC/U+oaZNn0uLo=; b=uOPnNAUNUQ7jwwDqzHgu4WNfYdX+MgOjquYim4Yn6+bLjo/U9mt3hsGfQRcXEeWut5 nqL/4igPajYp6EQbXgUOKztmxoV53xEfPVMXWYvPWURmBhCKUM8owh4x++rNHcV0xiOM nzlpYQ/uQZcV0eSBfQC7/sUc+0yrIzADf5be71GbD9Asgna2j14fi/Rd0Bd90m1Xc2Be aezeNYzxz19ZnqxGMpbvRLSX+br0+p7fzY3zIHVdMqNIcDkCoqVBJIAHPDL5wUApbQxC yywvJYCxIPrqSjlUMp963ymQy0bLjWocfsTWrzrMJk0H+A8Yvw5aguyCpOWlQbeNiw0C VBgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=sC6zeBvAQu12F4pHcyP2yBc/sNcvkHC/U+oaZNn0uLo=; b=Y/1a/DdzglEbdoTKWQ2WYPoLVAxRdi3HxVm+ph6TPvf1b0EVyHevWPS7MxmxIIoQm2 dhI1JFrOXb2YIy0BS+2GV12tfniNY9GNwgm763bN1rKag0xHyE/fUE9TQgY0sYmhgt1p 3cGm6Q1upaW/wINjdBzADgQcrkgMc7ARW75Lhpuq8Na11T3F97ShHcXgkC9NzpDD/Uev Zwr9oKtebDf6WOmPckIRjXHDB/IOGcbZ3p5wrSqaBHR3KZGFplO6ikL+sF3sLwG9bCCe 9pNTpcWMvfYz2oZsg4CaJ17ANAx47SYvESC1F/SmvroDcl+qUneIgNR5FvQJRBjVJm68 c9Xw== X-Gm-Message-State: AOAM532ErMEixtl2GEVW6+w2baOfeJ+8isLbd75rsWHVLZZM52jmR3Ay BAWOutu/dimV2BM5qzjhzBidmSEaGl248w== X-Google-Smtp-Source: ABdhPJyf50ZI8IugN/R07ThnGCCofq3wROK1WuuGeKtd9INnnt9Chq5pHi+VbR6o91yKZi9RNl/dvQ== X-Received: by 2002:a17:902:f68f:b0:158:4a47:5607 with SMTP id l15-20020a170902f68f00b001584a475607mr25312057plg.89.1649963689119; Thu, 14 Apr 2022 12:14:49 -0700 (PDT) Received: from x1.hsd1.or.comcast.net ([2601:1c2:1001:7090:5b60:6a76:138d:2646]) by smtp.gmail.com with ESMTPSA id e12-20020a056a001a8c00b004fab88d7de8sm614148pfv.132.2022.04.14.12.14.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 14 Apr 2022 12:14:48 -0700 (PDT) From: Drew Fustini To: Rob Herring , Krzysztof Kozlowski , Nishanth Menon , Santosh Shilimkar , Dave Gerlach , Tony Lindgren Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Drew Fustini , Keerthy Subject: [PATCH v2 2/2] soc: ti: wkup_m3_ipc: Add support for IO Isolation Date: Thu, 14 Apr 2022 12:12:50 -0700 Message-Id: <20220414191250.2969282-3-dfustini@baylibre.com> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20220414191250.2969282-1-dfustini@baylibre.com> References: <20220414191250.2969282-1-dfustini@baylibre.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" From: Dave Gerlach AM43xx support isolation of the IOs so that control is taken from the peripheral they are connected to and overridden by values present in the CTRL_CONF_* registers for the pad in the control module. The actual toggling happens from the wkup_m3, so use a DT property from the wkup_m3_ipc node to allow the PM code to communicate the necessity for placing the IOs into isolation to the firmware. Signed-off-by: Dave Gerlach Signed-off-by: Keerthy Signed-off-by: Drew Fustini --- No changes from v1 drivers/soc/ti/wkup_m3_ipc.c | 14 ++++++++++++-- include/linux/wkup_m3_ipc.h | 1 + 2 files changed, 13 insertions(+), 2 deletions(-) diff --git a/drivers/soc/ti/wkup_m3_ipc.c b/drivers/soc/ti/wkup_m3_ipc.c index 247a4b57a372..988162dd153a 100644 --- a/drivers/soc/ti/wkup_m3_ipc.c +++ b/drivers/soc/ti/wkup_m3_ipc.c @@ -46,6 +46,8 @@ #define IPC_VTT_STAT_MASK (0x1 << 3) #define IPC_VTT_GPIO_PIN_SHIFT (0x4) #define IPC_VTT_GPIO_PIN_MASK (0x3f << 4) +#define IPC_IO_ISOLATION_STAT_SHIFT (10) +#define IPC_IO_ISOLATION_STAT_MASK (0x1 << 10) =20 #define M3_STATE_UNKNOWN 0 #define M3_STATE_RESET 1 @@ -228,6 +230,11 @@ static void wkup_m3_set_vtt_gpio(struct wkup_m3_ipc *m= 3_ipc, int gpio) (gpio << IPC_VTT_GPIO_PIN_SHIFT); } =20 +static void wkup_m3_set_io_isolation(struct wkup_m3_ipc *m3_ipc) +{ + m3_ipc->isolation_conf =3D (1 << IPC_IO_ISOLATION_STAT_SHIFT); +} + /* Public functions */ /** * wkup_m3_set_mem_type - Pass wkup_m3 which type of memory is in use @@ -308,8 +315,8 @@ static int wkup_m3_prepare_low_power(struct wkup_m3_ipc= *m3_ipc, int state) wkup_m3_ctrl_ipc_write(m3_ipc, m3_ipc->resume_addr, 0); wkup_m3_ctrl_ipc_write(m3_ipc, m3_power_state, 1); wkup_m3_ctrl_ipc_write(m3_ipc, m3_ipc->mem_type | - m3_ipc->vtt_conf, 4); - + m3_ipc->vtt_conf | + m3_ipc->isolation_conf, 4); wkup_m3_ctrl_ipc_write(m3_ipc, DS_IPC_DEFAULT, 2); wkup_m3_ctrl_ipc_write(m3_ipc, DS_IPC_DEFAULT, 3); wkup_m3_ctrl_ipc_write(m3_ipc, DS_IPC_DEFAULT, 5); @@ -518,6 +525,9 @@ static int wkup_m3_ipc_probe(struct platform_device *pd= ev) dev_warn(dev, "Invalid VTT GPIO(%d) pin\n", temp); } =20 + if (of_find_property(np, "ti,set-io-isolation", NULL)) + wkup_m3_set_io_isolation(m3_ipc); + /* * Wait for firmware loading completion in a thread so we * can boot the wkup_m3 as soon as it's ready without holding diff --git a/include/linux/wkup_m3_ipc.h b/include/linux/wkup_m3_ipc.h index 2bc52c6381d5..b706eac58f92 100644 --- a/include/linux/wkup_m3_ipc.h +++ b/include/linux/wkup_m3_ipc.h @@ -34,6 +34,7 @@ struct wkup_m3_ipc { int mem_type; unsigned long resume_addr; int vtt_conf; + int isolation_conf; int state; =20 struct completion sync_complete; --=20 2.32.0