mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Colberg, Peter" <peter.colberg@intel.com>
To: "yilun.xu@linux.intel.com" <yilun.xu@linux.intel.com>
Cc: "Xu, Yilun" <yilun.xu@intel.com>,
	"linux-fpga@vger.kernel.org" <linux-fpga@vger.kernel.org>,
	"mdf@kernel.org" <mdf@kernel.org>, "Wu, Hao" <hao.wu@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"russ.weight@linux.dev" <russ.weight@linux.dev>,
	"Pagani, Marco" <marpagan@redhat.com>,
	"trix@redhat.com" <trix@redhat.com>,
	"matthew.gerlach@linux.intel.com"
	<matthew.gerlach@linux.intel.com>
Subject: Re: [PATCH v3 6/9] fpga: dfl: factor out feature data creation from build_info_commit_dev()
Date: Fri, 25 Oct 2024 22:43:28 +0000	[thread overview]
Message-ID: <2cb783bc7d3a85226d8dfbcded551ef5b93582a6.camel@intel.com> (raw)
In-Reply-To: <ZvJnC7hHISkbOo2n@yilunxu-OptiPlex-7050>

On Tue, 2024-09-24 at 15:15 +0800, Xu Yilun wrote:
> On Thu, Sep 19, 2024 at 04:34:27PM -0400, Peter Colberg wrote:
> > Add a separate function binfo_create_feature_dev_data() which allocates
> > and populates the feature platform data, and call the function from
> > build_info_commit_dev() which registers the feature platform device.
> > 
> > Signed-off-by: Peter Colberg <peter.colberg@intel.com>
> > Reviewed-by: Matthew Gerlach <matthew.gerlach@linux.intel.com>
> > ---
> >  drivers/fpga/dfl.c | 74 ++++++++++++++++++++++++++--------------------
> >  1 file changed, 42 insertions(+), 32 deletions(-)
> > 
> > diff --git a/drivers/fpga/dfl.c b/drivers/fpga/dfl.c
> > index 4c79d433d216..e644eb9fde39 100644
> > --- a/drivers/fpga/dfl.c
> > +++ b/drivers/fpga/dfl.c
> > @@ -749,12 +749,8 @@ static void dfl_fpga_cdev_add_port_data(struct dfl_fpga_cdev *cdev,
> >  	mutex_unlock(&cdev->lock);
> >  }
> >  
> > -/*
> > - * register current feature device, it is called when we need to switch to
> > - * another feature parsing or we have parsed all features on given device
> > - * feature list.
> > - */
> > -static int build_info_commit_dev(struct build_feature_devs_info *binfo)
> > +static struct dfl_feature_platform_data *
> > +binfo_create_feature_dev_data(struct build_feature_devs_info *binfo)
> >  {
> >  	struct platform_device *fdev = binfo->feature_dev;
> >  	struct dfl_feature_platform_data *pdata;
> > @@ -764,7 +760,7 @@ static int build_info_commit_dev(struct build_feature_devs_info *binfo)
> >  
> >  	type = feature_dev_id_type(fdev);
> >  	if (WARN_ON_ONCE(type >= DFL_ID_MAX))
> > -		return -EINVAL;
> > +		return ERR_PTR(-EINVAL);
> >  
> >  	/*
> >  	 * we do not need to care for the memory which is associated with
> > @@ -774,7 +770,7 @@ static int build_info_commit_dev(struct build_feature_devs_info *binfo)
> >  	 */
> >  	pdata = kzalloc(struct_size(pdata, features, binfo->feature_num), GFP_KERNEL);
> >  	if (!pdata)
> > -		return -ENOMEM;
> > +		return ERR_PTR(-ENOMEM);
> >  
> >  	pdata->dev = fdev;
> >  	pdata->num = binfo->feature_num;
> > @@ -799,7 +795,7 @@ static int build_info_commit_dev(struct build_feature_devs_info *binfo)
> >  	fdev->resource = kcalloc(binfo->feature_num, sizeof(*fdev->resource),
> >  				 GFP_KERNEL);
> >  	if (!fdev->resource)
> > -		return -ENOMEM;
> > +		return ERR_PTR(-ENOMEM);
> >  
> >  	/* fill features and resource information for feature dev */
> >  	list_for_each_entry_safe(finfo, p, &binfo->sub_features, node) {
> > @@ -818,7 +814,7 @@ static int build_info_commit_dev(struct build_feature_devs_info *binfo)
> >  						       finfo->params, finfo->param_size,
> >  						       GFP_KERNEL);
> >  			if (!feature->params)
> > -				return -ENOMEM;
> > +				return ERR_PTR(-ENOMEM);
> >  
> >  			feature->param_size = finfo->param_size;
> >  		}
> > @@ -834,8 +830,10 @@ static int build_info_commit_dev(struct build_feature_devs_info *binfo)
> >  			feature->ioaddr =
> >  				devm_ioremap_resource(binfo->dev,
> >  						      &finfo->mmio_res);
> > -			if (IS_ERR(feature->ioaddr))
> > -				return PTR_ERR(feature->ioaddr);
> > +			if (IS_ERR(feature->ioaddr)) {
> > +				ret = PTR_ERR(feature->ioaddr);
> > +				return ERR_PTR(ret);
> 
> Why change the type back and forth?
> 
>   return feature->ioaddr;
> 
> is it OK?
> 
> Thanks,
> Yilun

Yes, this has been done in the revised patch "fpga: dfl: factor out
feature data creation from build_info_commit_dev()".

Thanks,
Peter

  reply	other threads:[~2024-10-25 22:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 20:34 [PATCH v3 0/9] fpga: dfl: fix kernel warning on port release/assign for SRIOV Peter Colberg
2024-09-19 20:34 ` [PATCH v3 1/9] fpga: dfl: omit unneeded argument pdata from dfl_feature_instance_init() Peter Colberg
2024-09-19 20:34 ` [PATCH v3 2/9] fpga: dfl: omit unneeded null pointer check from {afu,fme}_open() Peter Colberg
2024-09-24  6:28   ` Xu Yilun
2024-10-25 22:39     ` Colberg, Peter
2024-09-24  6:41   ` Xu Yilun
2024-10-25 22:40     ` Colberg, Peter
2024-09-19 20:34 ` [PATCH v3 3/9] fpga: dfl: afu: use parent device to log errors on port enable/disable Peter Colberg
2024-09-19 20:34 ` [PATCH v3 4/9] fpga: dfl: afu: define local pointer to feature device Peter Colberg
2024-09-19 20:34 ` [PATCH v3 5/9] fpga: dfl: pass feature platform data instead of device as argument Peter Colberg
2024-09-19 20:34 ` [PATCH v3 6/9] fpga: dfl: factor out feature data creation from build_info_commit_dev() Peter Colberg
2024-09-24  7:15   ` Xu Yilun
2024-10-25 22:43     ` Colberg, Peter [this message]
2024-09-19 20:34 ` [PATCH v3 7/9] fpga: dfl: store FIU type in feature platform data Peter Colberg
2024-09-24  7:42   ` Xu Yilun
2024-10-25 22:46     ` Colberg, Peter
2024-09-19 20:34 ` [PATCH v3 8/9] fpga: dfl: refactor functions to take/return feature device data Peter Colberg
2024-09-19 20:34 ` [PATCH v3 9/9] fpga: dfl: fix kernel warning on port release/assign for SRIOV Peter Colberg
2024-09-24  9:01   ` Xu Yilun
2024-10-25 22:54     ` Colberg, Peter
2024-10-26  1:52       ` Colberg, Peter

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=2cb783bc7d3a85226d8dfbcded551ef5b93582a6.camel@intel.com \
    --to=peter.colberg@intel.com \
    --cc=hao.wu@intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marpagan@redhat.com \
    --cc=matthew.gerlach@linux.intel.com \
    --cc=mdf@kernel.org \
    --cc=russ.weight@linux.dev \
    --cc=trix@redhat.com \
    --cc=yilun.xu@intel.com \
    --cc=yilun.xu@linux.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

all inboxes | Powered by JetHome®