From: "Raghavendra, Vignesh" <vigneshr@ti.com>
To: Nishanth Menon <nm@ti.com>, Tony Lindgren <tony@atomide.com>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Dhruva Gole <d-gole@ti.com>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62-wakeup: Configure ti-sysc for wkup_uart0
Date: Wed, 27 Dec 2023 20:52:04 +0530 [thread overview]
Message-ID: <e28a4f16-f9a8-499a-a6a3-7acef0e0aa10@ti.com> (raw)
In-Reply-To: <170368552643.1332094.7883858507182654481.b4-ty@ti.com>
On 12/27/2023 7:29 PM, Vignesh Raghavendra wrote:
>
> On Tue, 12 Sep 2023 14:12:15 +0300, Tony Lindgren wrote:
>> The devices in the wkup domain are capable of waking up the system from
>> suspend. We can configure the wkup domain devices in a generic way using
>> the ti-sysc interconnect target module driver like we have done with the
>> earlier TI SoCs.
>>
>> As ti-sysc manages the SYSCONFIG related registers independent of the
>> child hardware device, the wake-up configuration is also set even if
>> wkup_uart0 is reserved by sysfw.
>>
>> [...]
>
> Applied, thanks!
>
> [1/1] arm64: dts: ti: k3-am62-wakeup: Configure ti-sysc for wkup_uart0
> commit: 86224524b52a8efba26f920736d08c8bfdd22d87
>
Please ignore above. I meant to pick v4. Sorry for the noise!
Regards
Vignesh
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-12-27 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 11:12 [PATCH] arm64: dts: ti: k3-am62-wakeup: Configure ti-sysc for wkup_uart0 Tony Lindgren
2023-09-12 15:38 ` Dhruva Gole
2023-12-27 13:59 ` Vignesh Raghavendra
2023-12-27 15:22 ` Raghavendra, Vignesh [this message]
2024-02-13 8:56 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2023-12-18 7:38 Tony Lindgren
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=e28a4f16-f9a8-499a-a6a3-7acef0e0aa10@ti.com \
--to=vigneshr@ti.com \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nm@ti.com \
--cc=tony@atomide.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