From: Liviu Dudau <liviu@dudau.co.uk>
To: Jingoo Han <jg1.han@samsung.com>
Cc: 'Liviu Dudau' <Liviu.Dudau@arm.com>,
'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>
Subject: Re: [PATCH v5 7/7] pci: Add support for creating a generic host_bridge from device tree
Date: Wed, 5 Mar 2014 08:33:12 +0000 [thread overview]
Message-ID: <20140305083311.GD13582@bart.dudau.co.uk> (raw)
In-Reply-To: <001f01cf3811$18463ed0$48d2bc70$%han@samsung.com>
On Wed, Mar 05, 2014 at 10:20:28AM +0900, Jingoo Han wrote:
> On Wednesday, March 05, 2014 12:50 AM, Liviu Dudau wrote:
> >
> > Several platforms use a rather generic version of parsing
> > the device tree to find the host bridge ranges. Move the common code
> > into the generic PCI code and use it to create a pci_host_bridge
> > structure that can be used by arch code.
> >
> > Based on early attempts by Andrew Murray to unify the code.
> > Used powerpc and microblaze PCI code as starting point.
> >
> > Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
> >
> > diff --git a/drivers/pci/host-bridge.c b/drivers/pci/host-bridge.c
> > index 8708b652..800678a 100644
> > --- a/drivers/pci/host-bridge.c
> > +++ b/drivers/pci/host-bridge.c
>
> [.....]
>
> > + res = kzalloc(sizeof(struct resource), GFP_KERNEL);
>
> It makes build error with exynos_defconfig. (ARM32)
> Thus, 'slab.h' is necessary in order to fix the build error.
>
> ./drivers/pci/host-bridge.c
> @@ -8,6 +8,7 @@
> #include <linux/module.h>
> #include <linux/of_address.h>
> #include <linux/of_pci.h>
> +#include <linux/slab.h>
Will add, thanks!
>
> #include "pci.h"
>
>
> > + if (!res) {
> > + err = -ENOMEM;
> > + goto bridge_ranges_nomem;
> > + }
> > +
> > + of_pci_range_to_resource(&range, dev, res);
> > +
> > + if (resource_type(res) == IORESOURCE_IO)
> > + *io_base = range.cpu_addr;
> > +
> > + pci_add_resource_offset(resources, res,
> > + res->start - range.pci_addr);
> > + }
> > +
> > + /* Apply architecture specific fixups for the ranges */
> > + pcibios_fixup_bridge_ranges(resources);
>
> It also makes compile problem with exynos_defconfig as below:
>
> drivers/built-in.o: In function `pci_host_bridge_of_get_ranges':
> drivers/pci/host-bridge.c:157: undefined reference to `pcibios_fixup_bridge_ranges'
Does that mean that exynos_defconfig doesn't define CONFIG_OF? How do you
compile all the .dts files then? Should CONFIG_OF not be added to the default config
file?
Other than that, your comment is correct. drivers/pci/host-bridge.c gets compiled
in regardless of CONFIG_OF and I need to provide an empty implementation for
pcibios_fixup_bridge_ranges().
Thanks!
Liviu
>
> Best regards,
> Jingoo Han
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
-------------------
.oooO
( )
\ ( Oooo.
\_) ( )
) /
(_/
One small step
for me ...
WARNING: multiple messages have this Message-ID (diff)
From: liviu@dudau.co.uk (Liviu Dudau)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 7/7] pci: Add support for creating a generic host_bridge from device tree
Date: Wed, 5 Mar 2014 08:33:12 +0000 [thread overview]
Message-ID: <20140305083311.GD13582@bart.dudau.co.uk> (raw)
In-Reply-To: <001f01cf3811$18463ed0$48d2bc70$%han@samsung.com>
On Wed, Mar 05, 2014 at 10:20:28AM +0900, Jingoo Han wrote:
> On Wednesday, March 05, 2014 12:50 AM, Liviu Dudau wrote:
> >
> > Several platforms use a rather generic version of parsing
> > the device tree to find the host bridge ranges. Move the common code
> > into the generic PCI code and use it to create a pci_host_bridge
> > structure that can be used by arch code.
> >
> > Based on early attempts by Andrew Murray to unify the code.
> > Used powerpc and microblaze PCI code as starting point.
> >
> > Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
> >
> > diff --git a/drivers/pci/host-bridge.c b/drivers/pci/host-bridge.c
> > index 8708b652..800678a 100644
> > --- a/drivers/pci/host-bridge.c
> > +++ b/drivers/pci/host-bridge.c
>
> [.....]
>
> > + res = kzalloc(sizeof(struct resource), GFP_KERNEL);
>
> It makes build error with exynos_defconfig. (ARM32)
> Thus, 'slab.h' is necessary in order to fix the build error.
>
> ./drivers/pci/host-bridge.c
> @@ -8,6 +8,7 @@
> #include <linux/module.h>
> #include <linux/of_address.h>
> #include <linux/of_pci.h>
> +#include <linux/slab.h>
Will add, thanks!
>
> #include "pci.h"
>
>
> > + if (!res) {
> > + err = -ENOMEM;
> > + goto bridge_ranges_nomem;
> > + }
> > +
> > + of_pci_range_to_resource(&range, dev, res);
> > +
> > + if (resource_type(res) == IORESOURCE_IO)
> > + *io_base = range.cpu_addr;
> > +
> > + pci_add_resource_offset(resources, res,
> > + res->start - range.pci_addr);
> > + }
> > +
> > + /* Apply architecture specific fixups for the ranges */
> > + pcibios_fixup_bridge_ranges(resources);
>
> It also makes compile problem with exynos_defconfig as below:
>
> drivers/built-in.o: In function `pci_host_bridge_of_get_ranges':
> drivers/pci/host-bridge.c:157: undefined reference to `pcibios_fixup_bridge_ranges'
Does that mean that exynos_defconfig doesn't define CONFIG_OF? How do you
compile all the .dts files then? Should CONFIG_OF not be added to the default config
file?
Other than that, your comment is correct. drivers/pci/host-bridge.c gets compiled
in regardless of CONFIG_OF and I need to provide an empty implementation for
pcibios_fixup_bridge_ranges().
Thanks!
Liviu
>
> Best regards,
> Jingoo Han
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
-------------------
.oooO
( )
\ ( Oooo.
\_) ( )
) /
(_/
One small step
for me ...
WARNING: multiple messages have this Message-ID (diff)
From: Liviu Dudau <liviu@dudau.co.uk>
To: Jingoo Han <jg1.han@samsung.com>
Cc: devicetree@vger.kernel.org,
'linaro-kernel' <linaro-kernel@lists.linaro.org>,
'Benjamin Herrenschmidt' <benh@kernel.crashing.org>,
'Arnd Bergmann' <arnd@arndb.de>,
'linux-pci' <linux-pci@vger.kernel.org>,
'Liviu Dudau' <Liviu.Dudau@arm.com>,
'LKML' <linux-kernel@vger.kernel.org>,
'Will Deacon' <Will.Deacon@arm.com>,
'Tanmay Inamdar' <tinamdar@apm.com>,
'Catalin Marinas' <Catalin.Marinas@arm.com>,
'Bjorn Helgaas' <bhelgaas@google.com>,
'LAKML' <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 7/7] pci: Add support for creating a generic host_bridge from device tree
Date: Wed, 5 Mar 2014 08:33:12 +0000 [thread overview]
Message-ID: <20140305083311.GD13582@bart.dudau.co.uk> (raw)
In-Reply-To: <001f01cf3811$18463ed0$48d2bc70$%han@samsung.com>
On Wed, Mar 05, 2014 at 10:20:28AM +0900, Jingoo Han wrote:
> On Wednesday, March 05, 2014 12:50 AM, Liviu Dudau wrote:
> >
> > Several platforms use a rather generic version of parsing
> > the device tree to find the host bridge ranges. Move the common code
> > into the generic PCI code and use it to create a pci_host_bridge
> > structure that can be used by arch code.
> >
> > Based on early attempts by Andrew Murray to unify the code.
> > Used powerpc and microblaze PCI code as starting point.
> >
> > Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
> >
> > diff --git a/drivers/pci/host-bridge.c b/drivers/pci/host-bridge.c
> > index 8708b652..800678a 100644
> > --- a/drivers/pci/host-bridge.c
> > +++ b/drivers/pci/host-bridge.c
>
> [.....]
>
> > + res = kzalloc(sizeof(struct resource), GFP_KERNEL);
>
> It makes build error with exynos_defconfig. (ARM32)
> Thus, 'slab.h' is necessary in order to fix the build error.
>
> ./drivers/pci/host-bridge.c
> @@ -8,6 +8,7 @@
> #include <linux/module.h>
> #include <linux/of_address.h>
> #include <linux/of_pci.h>
> +#include <linux/slab.h>
Will add, thanks!
>
> #include "pci.h"
>
>
> > + if (!res) {
> > + err = -ENOMEM;
> > + goto bridge_ranges_nomem;
> > + }
> > +
> > + of_pci_range_to_resource(&range, dev, res);
> > +
> > + if (resource_type(res) == IORESOURCE_IO)
> > + *io_base = range.cpu_addr;
> > +
> > + pci_add_resource_offset(resources, res,
> > + res->start - range.pci_addr);
> > + }
> > +
> > + /* Apply architecture specific fixups for the ranges */
> > + pcibios_fixup_bridge_ranges(resources);
>
> It also makes compile problem with exynos_defconfig as below:
>
> drivers/built-in.o: In function `pci_host_bridge_of_get_ranges':
> drivers/pci/host-bridge.c:157: undefined reference to `pcibios_fixup_bridge_ranges'
Does that mean that exynos_defconfig doesn't define CONFIG_OF? How do you
compile all the .dts files then? Should CONFIG_OF not be added to the default config
file?
Other than that, your comment is correct. drivers/pci/host-bridge.c gets compiled
in regardless of CONFIG_OF and I need to provide an empty implementation for
pcibios_fixup_bridge_ranges().
Thanks!
Liviu
>
> Best regards,
> Jingoo Han
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
-------------------
.oooO
( )
\ ( Oooo.
\_) ( )
) /
(_/
One small step
for me ...
next prev parent reply other threads:[~2014-03-05 8:35 UTC|newest]
Thread overview: 60+ 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 ` Liviu Dudau
2014-03-04 15:49 ` [PATCH v5 1/7] pci: Introduce pci_register_io_range() helper function Liviu Dudau
2014-03-04 15:49 ` Liviu Dudau
2014-03-04 22:30 ` Arnd Bergmann
2014-03-04 22:30 ` Arnd Bergmann
2014-03-06 16:04 ` Liviu Dudau
2014-03-06 16:04 ` Liviu Dudau
2014-03-06 16:04 ` Liviu Dudau
2014-03-07 0:24 ` Arnd Bergmann
2014-03-07 0:24 ` Arnd Bergmann
2014-03-07 0:58 ` Liviu Dudau
2014-03-07 0:58 ` Liviu Dudau
2014-03-07 0:58 ` Liviu Dudau
2014-03-10 14:45 ` Liviu Dudau
2014-03-10 14:45 ` Liviu Dudau
2014-03-10 15:57 ` Arnd Bergmann
2014-03-10 15:57 ` Arnd Bergmann
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:49 ` 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-04 15:50 ` Liviu Dudau
2014-03-05 3:48 ` Yijing Wang
2014-03-05 3:48 ` Yijing Wang
2014-03-05 4:41 ` Jingoo Han
2014-03-05 4:41 ` Jingoo Han
2014-03-05 8:19 ` Liviu Dudau
2014-03-05 8:19 ` Liviu Dudau
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 ` Liviu Dudau
2014-03-04 15:50 ` [PATCH v5 5/7] pci: Use parent domain number when allocating child busses Liviu Dudau
2014-03-04 15:50 ` Liviu Dudau
2014-03-04 15:50 ` Liviu Dudau
2014-03-05 1:49 ` Tanmay Inamdar
2014-03-05 1:49 ` Tanmay Inamdar
2014-03-05 8:16 ` Liviu Dudau
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 ` 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-04 15:50 ` Liviu Dudau
2014-03-05 1:20 ` Jingoo Han
2014-03-05 1:20 ` Jingoo Han
2014-03-05 8:33 ` Liviu Dudau [this message]
2014-03-05 8:33 ` Liviu Dudau
2014-03-05 8:33 ` Liviu Dudau
2014-03-05 8:58 ` Jingoo Han
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 1:53 ` Tanmay Inamdar
2014-03-05 8:18 ` Liviu Dudau
2014-03-05 8:18 ` Liviu Dudau
2014-03-05 17:51 ` Tanmay Inamdar
2014-03-05 17:51 ` Tanmay Inamdar
2014-03-05 11:40 ` Liviu Dudau
2014-03-05 11:40 ` Liviu Dudau
2014-03-05 17:49 ` Tanmay Inamdar
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=20140305083311.GD13582@bart.dudau.co.uk \
--to=liviu@dudau.co.uk \
--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=jg1.han@samsung.com \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.