Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Guangshuo Li" <lgs201920130244@gmail.com>
Cc: imx@lists.linux.dev, Frank.Li@kernel.org
Subject: Re: [PATCH v2] pmdomain: imx: gpc: remove all initialized power domains
Date: Thu, 24 Sep 2026 14:31:49 +0000	[thread overview]
Message-ID: <20260924143150.1CD721F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260924142520.1594149-1-lgs201920130244@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] imx_gpc_remove: syntax error due to missing closing brace
--

commit 8c74b27165f06b794b40a774855d31374a0b317d
Author: Guangshuo Li <lgs201920130244@gmail.com>

pmdomain: imx: gpc: remove all initialized power domains

This commit updates imx_gpc_remove() to use match data to iterate
and remove all initialized power domains in reverse order. It also
ensures the PU clocks are released when the PU domain is removed.

> diff --git a/drivers/pmdomain/imx/gpc.c b/drivers/pmdomain/imx/gpc.c
> index abca5f449a226..d83fb37e22974 100644
> --- a/drivers/pmdomain/imx/gpc.c
> +++ b/drivers/pmdomain/imx/gpc.c

[ ... ]

> @@ -519,20 +521,23 @@ static void imx_gpc_remove(struct platform_device *pdev)
>  	if (!pgc_node) {
>  		of_genpd_del_provider(pdev->dev.of_node);

[ ... ]

> +		num_domains = of_id_data->num_domains;
> +		while (num_domains--) {
> +			ret = pm_genpd_remove(&imx_gpc_domains[num_domains].base);
> +			if (ret) {
> +				dev_err(&pdev->dev,
> +					"Failed to remove %s power domain (%pe)\n",
> +					imx_gpc_domains[num_domains].base.name,
> +					ERR_PTR(ret));
> +				return;
> +			}
> +
> +		if (num_domains == GPC_PGC_DOMAIN_PU)
> +			imx_pgc_put_clocks(&imx_gpc_domains[num_domains]);
>  	}

[Severity: Low]
Is this while loop missing a closing brace?

Because there is no closing brace added for the new while loop, it appears
the closing brace at the end of this block will close the while loop instead
of the outer if (!pgc_node) statement. Will this cause unbalanced braces
and a build failure?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260924142520.1594149-1-lgs201920130244@gmail.com?part=1

      reply	other threads:[~2026-09-24 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 14:25 [PATCH v2] pmdomain: imx: gpc: remove all initialized power domains Guangshuo Li
2026-09-24 14:31 ` sashiko-bot [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=20260924143150.1CD721F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=lgs201920130244@gmail.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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