mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Jay Buddhabhatti <jay.buddhabhatti@amd.com>
Cc: linux-arm-kernel@lists.infradead.org, git@amd.com,
	linux-kernel@vger.kernel.org,
	Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
Subject: Re: [PATCH v2] firmware: xilinx: Request pre-allocated peripheral nodes after bulk release
Date: Wed, 4 Nov 2026 12:26:33 +0100	[thread overview]
Message-ID: <98df2f8d-14c9-44f7-b25c-b0d4cf359647@amd.com> (raw)
In-Reply-To: <20261019102110.3448932-1-jay.buddhabhatti@amd.com>



On 10/19/26 12:21, Jay Buddhabhatti wrote:
> During a kexec restart, zynqmp_clear_pm_state() releases all peripheral
> devices via PM_DEV_ALL_PERIPH. Pre-allocated nodes are then left released,
> so Linux no longer owns them and later peripheral access can fail.
> 
> Immediately re-request those nodes with zynqmp_pm_request_node(
> PM_DEV_ALL_PERIPH, ...) so Linux retains ownership. On a graceful kexec
> this runs from zynqmp_firmware_shutdown(). On a crash kernel restart it
> runs from zynqmp_firmware_probe() in the reloaded kernel.
> 
> The bulk request depends on firmware support for PM_DEV_ALL_PERIPH
> (PM_REQUEST_NODE feature check version >= PM_API_VERSION_3). On firmware
> that does not implement it, the request is skipped and a warning is
> logged. Errors are already logged inside zynqmp_clear_pm_state() and
> zynqmp_firmware_probe() does not abort if the request fails.
> 
> Also, drop the redundant ret = 0 assignments whose value is overwritten
> by the next do_feature_check_call()
> 
> Fixes: 84dbfa5519cf ("firmware: xilinx: Release all peripheral devices from firmware")
> Signed-off-by: Jay Buddhabhatti <jay.buddhabhatti@amd.com>
> Reviewed-by: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
> ---
> Changes in v2:
>    - Add Fixes tag for the bulk peripheral release commit.
>    - Add Reviewed-by from Radhey Shyam Pandey (v1 review).
> 
> Link: https://lore.kernel.org/r/20260923100343.3147243-1-jay.buddhabhatti@amd.com/
> ---
>   drivers/firmware/xilinx/zynqmp.c | 15 +++++++++++++--
>   1 file changed, 13 insertions(+), 2 deletions(-)
Applied.
M

      parent reply	other threads:[~2026-11-04 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 10:03 [PATCH] " Jay Buddhabhatti
2026-10-13 11:34 ` Pandey, Radhey Shyam
2026-10-19 10:21 ` [PATCH v2] " Jay Buddhabhatti
2026-11-02  6:25   ` Prasanna Kumar T S M
2026-11-04 11:26   ` Michal Simek [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=98df2f8d-14c9-44f7-b25c-b0d4cf359647@amd.com \
    --to=michal.simek@amd.com \
    --cc=git@amd.com \
    --cc=jay.buddhabhatti@amd.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=radhey.shyam.pandey@amd.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®