From: Jingoo Han <jg1.han@samsung.com>
To: 'Yijing Wang' <wangyijing@huawei.com>,
'Liviu Dudau' <Liviu.Dudau@arm.com>
Cc: 'linux-pci' <linux-pci@vger.kernel.org>,
'Bjorn Helgaas' <bhelgaas@google.com>,
'Catalin Marinas' <Catalin.Marinas@arm.com>,
'Will Deacon' <Will.Deacon@arm.com>,
'linaro-kernel' <linaro-kernel@lists.linaro.org>,
'Benjamin Herrenschmidt' <benh@kernel.crashing.org>,
'LKML' <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org,
'LAKML' <linux-arm-kernel@lists.infradead.org>,
'Tanmay Inamdar' <tinamdar@apm.com>,
'Arnd Bergmann' <arnd@arndb.de>,
'Jingoo Han' <jg1.han@samsung.com>
Subject: Re: [PATCH v5 3/7] pci: Create pci_host_bridge before its associated bus in pci_create_root_bus.
Date: Wed, 05 Mar 2014 13:41:35 +0900 [thread overview]
Message-ID: <002401cf382d$3062aa50$9127fef0$%han@samsung.com> (raw)
In-Reply-To: <53169E86.1090609@huawei.com>
On Wednesday, March 05, 2014 12:48 PM, Yijing Wang wrote:
> On 2014/3/4 23:50, Liviu Dudau wrote:
> > Before commit 7b5436635800 the pci_host_bridge was created before the root bus.
> > As that commit has added a needless dependency on the bus for pci_alloc_host_bridge()
> > the creation order has been changed for no good reason. Revert the order of
> > creation as we are going to depend on the pci_host_bridge structure to retrieve the
> > domain number of the root bus.
> >
> > Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
> >
> > diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> > index 6e34498..78ccba0 100644
> > --- a/drivers/pci/probe.c
> > +++ b/drivers/pci/probe.c
> > @@ -505,7 +505,7 @@ static void pci_release_host_bridge_dev(struct device *dev)
> > kfree(bridge);
> > }
> >
> > -static struct pci_host_bridge *pci_alloc_host_bridge(struct pci_bus *b)
> > +static struct pci_host_bridge *pci_alloc_host_bridge(void)
> > {
> > struct pci_host_bridge *bridge;
> >
> > @@ -514,7 +514,6 @@ static struct pci_host_bridge *pci_alloc_host_bridge(struct pci_bus *b)
> > return NULL;
> >
> > INIT_LIST_HEAD(&bridge->windows);
> > - bridge->bus = b;
> > return bridge;
> > }
> >
> > @@ -1727,9 +1726,21 @@ struct pci_bus *pci_create_root_bus(struct device *parent, int bus,
> > char bus_addr[64];
> > char *fmt;
> >
> > + bridge = pci_alloc_host_bridge();
> > + if (!bridge)
> > + return NULL;
> > +
> > + bridge->dev.parent = parent;
> > + bridge->dev.release = pci_release_host_bridge_dev;
> > + error = pcibios_root_bridge_prepare(bridge);
> > + if (error) {
> > + kfree(bridge);
> > + return NULL;
>
> What about use goto err_out?
+1
I agree with your opinion.
It makes the code simpler.
Best regards,
Jingoo Han
>
> > + }
> > +
> > b = pci_alloc_bus();
> > if (!b)
> > - return NULL;
> > + goto err_out;
> >
> > b->sysdata = sysdata;
> > b->ops = ops;
> > @@ -1738,26 +1749,15 @@ struct pci_bus *pci_create_root_bus(struct device *parent, int bus,
> > if (b2) {
> > /* If we already got to this bus through a different bridge, ignore it */
> > dev_dbg(&b2->dev, "bus already known\n");
> > - goto err_out;
> > + goto err_bus_out;
> > }
> >
> > - bridge = pci_alloc_host_bridge(b);
> > - if (!bridge)
> > - goto err_out;
> > -
> > - bridge->dev.parent = parent;
> > - bridge->dev.release = pci_release_host_bridge_dev;
> > + bridge->bus = b;
> > dev_set_name(&bridge->dev, "pci%04x:%02x", pci_domain_nr(b), bus);
> > - error = pcibios_root_bridge_prepare(bridge);
> > - if (error) {
> > - kfree(bridge);
> > - goto err_out;
> > - }
> > -
> > error = device_register(&bridge->dev);
> > if (error) {
> > put_device(&bridge->dev);
> > - goto err_out;
> > + goto err_bus_out;
> > }
> > b->bridge = get_device(&bridge->dev);
> > device_enable_async_suspend(b->bridge);
> > @@ -1814,8 +1814,10 @@ struct pci_bus *pci_create_root_bus(struct device *parent, int bus,
> > class_dev_reg_err:
> > put_device(&bridge->dev);
> > device_unregister(&bridge->dev);
> > -err_out:
> > +err_bus_out:
> > kfree(b);
> > +err_out:
> > + kfree(bridge);
> > return NULL;
> > }
> >
> >
next prev parent reply other threads:[~2014-03-05 4:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 15:49 [PATCH v5 0/7] [RFC] Support for creating generic host_bridge from device tree Liviu Dudau
2014-03-04 15:49 ` [PATCH v5 1/7] pci: Introduce pci_register_io_range() helper function Liviu Dudau
2014-03-04 22:30 ` Arnd Bergmann
[not found] ` <201403042330.09607.arnd-r2nGTMty4D4@public.gmane.org>
2014-03-06 16:04 ` Liviu Dudau
2014-03-07 0:24 ` Arnd Bergmann
2014-03-07 0:58 ` Liviu Dudau
2014-03-10 14:45 ` Liviu Dudau
2014-03-10 15:57 ` Arnd Bergmann
2014-03-04 15:49 ` [PATCH v5 2/7] pci: OF: Fix the conversion of IO ranges into IO resources Liviu Dudau
2014-03-04 15:50 ` [PATCH v5 3/7] pci: Create pci_host_bridge before its associated bus in pci_create_root_bus Liviu Dudau
2014-03-05 3:48 ` Yijing Wang
2014-03-05 4:41 ` Jingoo Han [this message]
[not found] ` <002401cf382d$3062aa50$9127fef0$%han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-03-05 8:19 ` Liviu Dudau
2014-03-04 15:50 ` [PATCH v5 4/7] pci: Introduce a domain number for pci_host_bridge Liviu Dudau
2014-03-04 15:50 ` [PATCH v5 5/7] pci: Use parent domain number when allocating child busses Liviu Dudau
2014-03-05 1:49 ` Tanmay Inamdar
2014-03-05 8:16 ` Liviu Dudau
2014-03-04 15:50 ` [PATCH v5 6/7] pci: Export find_pci_host_bridge() function Liviu Dudau
2014-03-04 15:50 ` [PATCH v5 7/7] pci: Add support for creating a generic host_bridge from device tree Liviu Dudau
2014-03-05 1:20 ` Jingoo Han
2014-03-05 8:33 ` Liviu Dudau
2014-03-05 8:58 ` Jingoo Han
2014-03-05 1:53 ` [PATCH v5 0/7] [RFC] Support for creating " Tanmay Inamdar
2014-03-05 8:18 ` Liviu Dudau
2014-03-05 17:51 ` Tanmay Inamdar
2014-03-05 11:40 ` Liviu Dudau
2014-03-05 17:49 ` Tanmay Inamdar
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='002401cf382d$3062aa50$9127fef0$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=Catalin.Marinas@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=Will.Deacon@arm.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tinamdar@apm.com \
--cc=wangyijing@huawei.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;
as well as URLs for NNTP newsgroup(s).