Devicetree
 help / color / mirror / Atom feed
From: Xu Yilun <yilun.xu@linux.intel.com>
To: Mahesh Rao <mahesh.rao@intel.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
	dinguyen@kernel.org, hao.wu@intel.com, krzk+dt@kernel.org,
	krzysztof.kozlowski@linaro.org, linux-fpga@vger.kernel.org,
	linux-kernel@vger.kernel.org, mahesh.rao@altera.com,
	mdf@kernel.org, robh@kernel.org, trix@redhat.com,
	yilun.xu@intel.com
Subject: Re: [PATCH 3/3] firmware: stratix10-svc: Add of_platform_default_populate()
Date: Thu, 6 Feb 2025 14:23:16 +0800	[thread overview]
Message-ID: <Z6RVVGriTgZIM22k@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <20250129180113.17219-1-mahesh.rao@intel.com>

On Thu, Jan 30, 2025 at 02:01:13AM +0800, Mahesh Rao wrote:
> Hi Yilun,
> Thanks for reviewing the patch.
> 
> On Sun, 26 Jan 2025 16:28:55 +0800, Xu Yilun wrote:
> > > Add of_platform_default_populate() to stratix10-svc driver as the
> > > firmware/svc node was moved out of soc.
> > > This fixes the failed probing of child drivers of svc node.
> > >
> > > Fixes: 23c3ebed382a ("arm64: dts: socfpga: agilex: move firmware out
> > > of soc node")
> 
> > > +	ret = of_platform_default_populate(dev_of_node(dev), NULL, dev);
> > > +	if (ret < 0) {
> > 
> > 	if (ret)  is just fine.
> 
> ok ,I will make the change.
> 
> > 
> > > +		of_platform_depopulate(dev);
> > > +		goto err_unregister_fcs_dev;
> > 
> > You wanna destroy everything even if some child drivers work?
> 
> Currently, there is no requirement to retain the driver if a child component fails.
> we will handle it if it is needed in the future.

Does the previous "soc" style population did the same way?

Thanks,
Yilun

> 
> > And do we need to do depopulation on driver remove?
> 
> I think yes , I have missed this. I will add depopulate in the remove callback().
> 
> > I'm actually a little confused how to handle populate() fail and depopulate().
> 
> I think this was a mistake on my side. I will make the change in next revision.
> 
> Best Regards,
> Mahesh Rao

      reply	other threads:[~2025-02-06  6:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22  5:58 [PATCH 0/3] stratix10: miscellaneous changes and fix for child driver probing Mahesh Rao
2025-01-22  5:58 ` [PATCH 1/3] dt-bindings: fpga: stratix10: Convert to json-schema Mahesh Rao
2025-01-22 18:35   ` Conor Dooley
2025-01-27 16:31     ` Mahesh Rao
2025-01-22  5:58 ` [PATCH 2/3] dt-bindings: firmware: " Mahesh Rao
2025-01-22  7:42   ` kernel test robot
2025-01-22 18:40   ` Conor Dooley
2025-01-27 17:07     ` Mahesh Rao
2025-01-27 17:50       ` Conor Dooley
2025-01-22  5:58 ` [PATCH 3/3] firmware: stratix10-svc: Add of_platform_default_populate() Mahesh Rao
2025-01-23  7:26   ` Krzysztof Kozlowski
2025-01-29  8:27     ` Mahesh Rao
2025-01-26  8:28   ` Xu Yilun
2025-01-29 18:01     ` Mahesh Rao
2025-02-06  6:23       ` Xu Yilun [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=Z6RVVGriTgZIM22k@yilunxu-OptiPlex-7050 \
    --to=yilun.xu@linux.intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=hao.wu@intel.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mahesh.rao@altera.com \
    --cc=mahesh.rao@intel.com \
    --cc=mdf@kernel.org \
    --cc=robh@kernel.org \
    --cc=trix@redhat.com \
    --cc=yilun.xu@intel.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