From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Jeremy Kerr <jk@codeconstruct.com.au>,
Joel Stanley <joel@jms.id.au>,
Billy Tsai <billy_tsai@aspeedtech.com>,
Aniket <aniketmaurya@google.com>
Cc: linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
vamshigajjela@google.com
Subject: Re: [PATCH 0/3] i3c: dw: Add support for power management
Date: Mon, 15 Jul 2024 23:47:53 +0200 [thread overview]
Message-ID: <172108005329.1453338.15447064873136258175.b4-ty@bootlin.com> (raw)
In-Reply-To: <20240708062103.3296587-1-aniketmaurya@google.com>
On Mon, 08 Jul 2024 06:21:00 +0000, Aniket wrote:
> These patches add pm support for the dw i3c controller.
> Controller registers that can be lost are saved and restored during resume.
> Clocks, resets and pads are put in their relevant state during suspend and resume.
> For runtime pm, power is resumed and later suspended for the xfer/IBI APIs.
>
> Aniket (3):
> i3c: dw: Save timing registers and other values
> i3c: dw: Add some functions for reusability
> i3c: dw: Add power management support
>
> [...]
Applied, thanks!
[1/3] i3c: dw: Save timing registers and other values
https://git.kernel.org/abelloni/c/e88def6d757d
[2/3] i3c: dw: Add some functions for reusability
https://git.kernel.org/abelloni/c/2ab158e0ab28
[3/3] i3c: dw: Add power management support
https://git.kernel.org/abelloni/c/56e697d7dc6d
Best regards,
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2024-07-15 21:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 6:21 Aniket
2024-07-08 6:21 ` [PATCH 1/3] i3c: dw: Save timing registers and other values Aniket
2024-07-08 6:21 ` [PATCH 2/3] i3c: dw: Add some functions for reusability Aniket
2024-07-08 6:21 ` [PATCH 3/3] i3c: dw: Add power management support Aniket
2024-07-15 21:47 ` Alexandre Belloni [this message]
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=172108005329.1453338.15447064873136258175.b4-ty@bootlin.com \
--to=alexandre.belloni@bootlin.com \
--cc=aniketmaurya@google.com \
--cc=billy_tsai@aspeedtech.com \
--cc=jk@codeconstruct.com.au \
--cc=joel@jms.id.au \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vamshigajjela@google.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®