From: Michael Tretter <m.tretter@pengutronix.de>
To: Michal Simek <michal.simek@xilinx.com>
Cc: linux-arm-kernel@lists.infradead.org, rajan.vaja@xilinx.com,
jolly.shah@xilinx.com
Subject: Re: [PATCH v2 0/4] soc: xilinx: pm_domains: cleanup and fix PM_INIT_FINALIZE
Date: Fri, 1 Oct 2021 11:07:44 +0200 [thread overview]
Message-ID: <20211001090744.GE28226@pengutronix.de> (raw)
In-Reply-To: <36fee5a7-6c6e-9f93-0ab9-a96967b70919@xilinx.com>
Hi,
On Fri, 27 Aug 2021 10:00:59 +0200, Michal Simek wrote:
> On 8/25/21 5:03 PM, Michael Tretter wrote:
> > This is v2 of the series to cleanup and fix the zynqmp_pm_domains driver [0].
> >
> > Patch 1 of this series fixes the ZynqMP PMU FW power management
> > initialization, which was done by the wrong driver. PM_INIT_FINALIZE must be
> > called from the zynqmp_pm_domains driver, which handles power domains, instead
> > of the zynmp_power driver, which is responsible for suspend and shutdown. As a
> > side effect, PM_INIT_FINALIZE powers down all devices that have not been
> > requested, which might lead to misbehaving devices. Calling it from the
> > sync_state callback ensures that all consumers have probed and are able to
> > handle power management themselves.
> >
> > Patches 2 to 4 are various cleanup patches to improve the readability and
> > debugging experience of the zynqmp_pm_domains driver.
> >
> > Michael
> >
> > [0] https://lore.kernel.org/linux-arm-kernel/20210317160410.2097178-1-m.tretter@pengutronix.de/
> >
> > Changelog:
> >
> > v2:
> >
> > - move PM_INIT_FINALIZE to sync_state callback
> >
> > Michael Tretter (4):
> > soc: xilinx: move PM_INIT_FINALIZE to zynqmp_pm_domains driver
> > soc: xilinx: cleanup debug and error messages
> > soc: xilinx: use a properly named field instead of flags
> > soc: xilinx: add a to_zynqmp_pm_domain macro
> >
> > drivers/soc/xilinx/zynqmp_pm_domains.c | 91 +++++++++++++++-----------
> > drivers/soc/xilinx/zynqmp_power.c | 1 -
> > 2 files changed, 51 insertions(+), 41 deletions(-)
> >
>
> Rajan: Please test and ack.
>
> It looks good to me.
> Acked-by: Michal Simek <michal.simek@xilinx.com>
Gentle ping.
Michael
_______________________________________________
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:[~2021-10-01 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 15:03 [PATCH v2 0/4] soc: xilinx: pm_domains: cleanup and fix PM_INIT_FINALIZE Michael Tretter
2021-08-25 15:03 ` [PATCH v2 1/4] soc: xilinx: move PM_INIT_FINALIZE to zynqmp_pm_domains driver Michael Tretter
2021-08-25 15:03 ` [PATCH v2 2/4] soc: xilinx: cleanup debug and error messages Michael Tretter
2021-08-25 15:03 ` [PATCH v2 3/4] soc: xilinx: use a properly named field instead of flags Michael Tretter
2021-08-25 15:03 ` [PATCH v2 4/4] soc: xilinx: add a to_zynqmp_pm_domain macro Michael Tretter
2021-08-27 8:00 ` [PATCH v2 0/4] soc: xilinx: pm_domains: cleanup and fix PM_INIT_FINALIZE Michal Simek
2021-10-01 9:07 ` Michael Tretter [this message]
2021-10-01 9:22 ` Rajan Vaja
2021-09-02 6:55 ` Rajan Vaja
2021-10-18 13:09 ` Michal Simek
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=20211001090744.GE28226@pengutronix.de \
--to=m.tretter@pengutronix.de \
--cc=jolly.shah@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=michal.simek@xilinx.com \
--cc=rajan.vaja@xilinx.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