From: Kendall Willis <k-willis@ti.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-serial@vger.kernel.org>,
<devicetree@vger.kernel.org>, <d-gole@ti.com>, <vishalm@ti.com>,
<sebin.francis@ti.com>, <msp@baylibre.com>,
<khilman@baylibre.com>, <a-kaur@ti.com>,
<andriy.shevchenko@linux.intel.com>, <yujiaoliang@vivo.com>,
<b-liu@ti.com>, <u.kleine-koenig@baylibre.com>,
Kendall Willis <k-willis@ti.com>
Subject: [PATCH v2 1/2] dt-bindings: serial: 8250_omap: Add wakeup pinctrl state
Date: Wed, 10 Sep 2025 16:23:31 -0500 [thread overview]
Message-ID: <20250910-uart-daisy-chain-8250-omap-v2-1-e90d44c1a9ac@ti.com> (raw)
In-Reply-To: <20250910-uart-daisy-chain-8250-omap-v2-0-e90d44c1a9ac@ti.com>
From: Markus Schneider-Pargmann <msp@baylibre.com>
Pins associated with the 8250 omap unit can be the source of a wakeup in
deep sleep states. To be able to wakeup, these pins have to be
configured in a special way. To support this configuration add the
default and wakeup pinctrl states.
Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
Signed-off-by: Kendall Willis <k-willis@ti.com>
---
Documentation/devicetree/bindings/serial/8250_omap.yaml | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/Documentation/devicetree/bindings/serial/8250_omap.yaml b/Documentation/devicetree/bindings/serial/8250_omap.yaml
index 1859f71297ff297141e5cd455574fa9ccd9dd11c..aabacca2b2fa6a7740173e6c415656360b5df4e4 100644
--- a/Documentation/devicetree/bindings/serial/8250_omap.yaml
+++ b/Documentation/devicetree/bindings/serial/8250_omap.yaml
@@ -71,6 +71,22 @@ properties:
overrun-throttle-ms: true
wakeup-source: true
+ pinctrl-0:
+ description: Default pinctrl state
+
+ pinctrl-1:
+ description: Wakeup pinctrl state
+
+ pinctrl-names:
+ description:
+ When present should contain at least "default" describing the default pin
+ states. The second state called "wakeup" describes the pins in their
+ wakeup configuration required to exit sleep states.
+ minItems: 1
+ items:
+ - const: default
+ - const: wakeup
+
required:
- compatible
- reg
--
2.34.1
next prev parent reply other threads:[~2025-09-10 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 21:23 [PATCH v2 0/2] serial: 8250: omap: Add wakeup support Kendall Willis
2025-09-10 21:23 ` Kendall Willis [this message]
2025-09-15 0:26 ` [PATCH v2 1/2] dt-bindings: serial: 8250_omap: Add wakeup pinctrl state Rob Herring (Arm)
2025-09-15 5:21 ` Dhruva Gole
2025-09-10 21:23 ` [PATCH v2 2/2] serial: 8250: omap: Support wakeup pinctrl state on suspend Kendall Willis
2025-09-15 5:33 ` Dhruva Gole
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250910-uart-daisy-chain-8250-omap-v2-1-e90d44c1a9ac@ti.com \
--to=k-willis@ti.com \
--cc=a-kaur@ti.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=b-liu@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=robh@kernel.org \
--cc=sebin.francis@ti.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=vigneshr@ti.com \
--cc=vishalm@ti.com \
--cc=yujiaoliang@vivo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox