Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>,
	Paul Cercueil <paul@crapouillou.net>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memory: jz4780-nemc: publish drvdata before creating children
Date: Tue, 30 Jun 2026 19:22:51 +0200	[thread overview]
Message-ID: <fca00776-1a15-42ab-9c0d-dab0911788ef@kernel.org> (raw)
In-Reply-To: <20260616005713.10474-1-pengpeng@iscas.ac.cn>

On 16/06/2026 02:57, Pengpeng Hou wrote:
> The NEMC child drivers can call exported helpers that fetch the parent
> controller state with dev_get_drvdata(dev->parent).  jz4780_nemc_probe()
> currently creates child platform devices before storing the controller
> pointer in the parent drvdata, so a child that probes immediately can
> observe a NULL parent drvdata pointer.
> 
> Store the controller pointer before creating child devices.  Also

"Also" is indication you mix up two independent commits.

> depopulate child devices during remove before disabling the controller
> clock so child teardown still runs while the parent resources are
> available.
> 
> Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
> ---
>  drivers/memory/jz4780-nemc.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/memory/jz4780-nemc.c b/drivers/memory/jz4780-nemc.c
> index 1a8161514d03..1c1d1d019f77 100644
> --- a/drivers/memory/jz4780-nemc.c
> +++ b/drivers/memory/jz4780-nemc.c
> @@ -331,6 +331,8 @@ static int jz4780_nemc_probe(struct platform_device *pdev)
>  		return -EINVAL;
>  	}
>  
> +	platform_set_drvdata(pdev, nemc);
> +
>  	/*
>  	 * Iterate over child devices, check that they do not conflict with
>  	 * each other, and register child devices for them. If a child device
> @@ -379,7 +381,6 @@ static int jz4780_nemc_probe(struct platform_device *pdev)
>  		}
>  	}
>  
> -	platform_set_drvdata(pdev, nemc);
>  	dev_info(dev, "JZ4780 NEMC initialised\n");
>  	return 0;
>  }
> @@ -388,6 +389,7 @@ static void jz4780_nemc_remove(struct platform_device *pdev)
>  {
>  	struct jz4780_nemc *nemc = platform_get_drvdata(pdev);
>  
> +	of_platform_depopulate(&pdev->dev);

This should be separate commit. Another problem is that driver does not
populate the bus, so calling of_platform_depopulate() feels not only
heavily confusing but actually wrong. Commit msg should explain why it
is correct, in your opinion. IMO, it might be not right since we never
set the OF_POPULATED_BUS flag.

How did you test it?


Best regards,
Krzysztof

      reply	other threads:[~2026-06-30 17:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16  0:57 [PATCH] memory: jz4780-nemc: publish drvdata before creating children Pengpeng Hou
2026-06-30 17:22 ` Krzysztof Kozlowski [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=fca00776-1a15-42ab-9c0d-dab0911788ef@kernel.org \
    --to=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paul@crapouillou.net \
    --cc=pengpeng@iscas.ac.cn \
    /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