From: Kendall Willis <k-willis@ti.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@kernel.org>, <d-gole@ti.com>,
<vishalm@ti.com>, <sebin.francis@ti.com>, <msp@baylibre.com>,
<khilman@baylibre.com>, <a-kaur@ti.com>, <s-kochidanadu@ti.com>,
<linux-kernel@vger.kernel.org>, <linux-serial@vger.kernel.org>
Subject: Re: [PATCH] serial: 8250: omap: set out-of-band wakeup if wakeup pinctrl exists
Date: Fri, 16 Jan 2026 09:37:44 -0600 [thread overview]
Message-ID: <f7a2e47b-a37e-4735-91ea-4fcac3217186@ti.com> (raw)
In-Reply-To: <2026011620-clause-gecko-2cb0@gregkh>
On 1/16/26 07:16, Greg Kroah-Hartman wrote:
> On Tue, Dec 30, 2025 at 03:24:51PM -0600, Kendall Willis wrote:
>> In TI K3 SoCs, I/O daisy chaining is used to allow wakeup from UART when
>> the UART controller is off. Set UART device as wakeup capable using
>> out-of-band wakeup if the 'wakeup' pinctrl state exists and the device may
>> wakeup.
>>
>> Signed-off-by: Kendall Willis <k-willis@ti.com>
>> ---
>> Implementation
>> --------------
>> This patch is intended to be implemented along with the following
>> series. This patch has no dependencies on any of the other series:
>>
>> 1. "pmdomain: ti_sci: handle wakeup constraint for out-of-band wakeup":
>> Skips setting constraints for wakeup sources that have out-of-band
>> wakeup capability.
>> https://github.com/kwillis01/linux/commits/v6.19/uart-daisy-chain/pmdomain
>>
>> 2. "serial: 8250: omap: set out-of-band wakeup if wakeup pinctrl exists"
>> (this patch): Implements out-of-band wakeup from the UARTs for TI K3
>> SoCs
>> https://github.com/kwillis01/linux/tree/v6.19/uart-daisy-chain/uart-wakeup
>>
>> 3. "arm64: dts: ti: k3-am62: Support Main UART wakeup": Implements the
>> functionality to wakeup the system from the Main UART
>> https://github.com/kwillis01/linux/tree/b4/uart-daisy-chain-dts
>
> How am I to pull any of this into the mainline kernel tree? If this is
> dependant on those out-of-tree stuff, there's no need for me to take
> this now, please submit this all together properly.
This patch has no dependencies on the listed series. I listed them so
that there was a full picture of the feature implementation. The
"pmdomain: ti_sci: handle wakeup constraint for out-of-band wakeup"
patch has been merged already [1]. The "arm64: dts: ti: k3-am62: Support
Main UART wakeup" series is posted [2] and has a dependency on this
patch. Sorry for the confusion with the GitHub links, in the future I
either won't add them or will add lore links instead.
[1] https://lore.kernel.org/all/20251230-pmdomain-v1-1-3a009d1ff72e@ti.com/
[2]
https://lore.kernel.org/all/20260106-b4-uart-daisy-chain-dts-v3-0-398a66258f2c@ti.com/
Best,
Kendall Willis <k-willis@ti.com>
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2026-01-16 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 21:24 Kendall Willis
2026-01-16 5:40 ` Dhruva Gole
2026-01-16 13:16 ` Greg Kroah-Hartman
2026-01-16 15:37 ` Kendall Willis [this message]
2026-01-16 15:47 ` Greg Kroah-Hartman
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=f7a2e47b-a37e-4735-91ea-4fcac3217186@ti.com \
--to=k-willis@ti.com \
--cc=a-kaur@ti.com \
--cc=d-gole@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=s-kochidanadu@ti.com \
--cc=sebin.francis@ti.com \
--cc=vishalm@ti.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
all inboxes | Powered by JetHome®