From: Bjorn Helgaas <bhelgaas@google.com>
To: Ray Jui <rjui@broadcom.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>, Arnd Bergmann <arnd@arndb.de>,
Mark Rutland <mark.rutland@arm.com>,
Hauke Mehrtens <hauke@hauke-m.de>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 1/4] PCI: iproc: enable arm64 support for iProc PCIe
Date: Tue, 21 Jul 2015 17:02:59 -0500 [thread overview]
Message-ID: <20150721220259.GK21967@google.com> (raw)
In-Reply-To: <55AEB094.1090601@broadcom.com>
On Tue, Jul 21, 2015 at 01:50:28PM -0700, Ray Jui wrote:
>
>
> On 7/21/2015 1:30 PM, Bjorn Helgaas wrote:
> > On Wed, Jul 15, 2015 at 09:39:20PM -0700, Ray Jui wrote:
> >> This patch enables arm64 support to the iProc PCIe driver
> >
> > This needs a little more explanation: ARM has a common struct pci_sys_data
> > but ARM64 does not,
>
> Correct, and according to Arnd, there's already work in process of
> removing the need for pci_sys_data on arm32. Before that is done, we
> need this in the driver for it to work on both arm32 and arm64.
>
> and ARM needs pci_fixup_irqs() but ARM64 does not (why
> > not?),
>
> under arch/arm64/kernel/pci.c:
>
> 41 /*
> 42 * Try to assign the IRQ number from DT when adding a new device
> 43 */
> 44 int pcibios_add_device(struct pci_dev *dev)
> 45 {
> 46 dev->irq = of_irq_parse_and_map_pci(dev, 0, 0);
> 47
> 48 return 0;
> 49 }
>
> interrupt is automatically parsed and mapped when adding a new device
> for arm64.
>
> ARM uses the common pci_sys_data for the PCI sysdata while ARM64
> > uses a driver-specific sysdata, etc.
>
> Correct. pci_sys_data for arm32 will eventually be removed, so all arm32
> based PCie host should only need to carry driver specific sysdata.
That all makes sense. I'm just looking for a condensed version of it in
the changelog because it takes some digging to figure it out, and in a
couple months even the implicit context of "somebody's working to combine
arm32 and arm64" will be gone. So we need a changelog that motivates this
patch as it is.
> >> Signed-off-by: Ray Jui <rjui@broadcom.com>
> >> Reviewed-by: Scott Branden <sbranden@broadcom.com>
> >> ---
> >> drivers/pci/host/pcie-iproc.c | 15 ++++-----------
> >> drivers/pci/host/pcie-iproc.h | 8 ++++++--
> >> 2 files changed, 10 insertions(+), 13 deletions(-)
> >>
> >> diff --git a/drivers/pci/host/pcie-iproc.c b/drivers/pci/host/pcie-iproc.c
> >> index d77481e..8a556d5 100644
> >> --- a/drivers/pci/host/pcie-iproc.c
> >> +++ b/drivers/pci/host/pcie-iproc.c
> >> @@ -58,11 +58,6 @@
> >> #define SYS_RC_INTX_EN 0x330
> >> #define SYS_RC_INTX_MASK 0xf
> >>
> >> -static inline struct iproc_pcie *sys_to_pcie(struct pci_sys_data *sys)
> >> -{
> >> - return sys->private_data;
> >> -}
> >> -
> >> /**
> >> * Note access to the configuration registers are protected at the higher layer
> >> * by 'pci_lock' in drivers/pci/access.c
> >> @@ -71,8 +66,7 @@ static void __iomem *iproc_pcie_map_cfg_bus(struct pci_bus *bus,
> >> unsigned int devfn,
> >> int where)
> >> {
> >> - struct pci_sys_data *sys = bus->sysdata;
> >> - struct iproc_pcie *pcie = sys_to_pcie(sys);
> >> + struct iproc_pcie *pcie = bus->sysdata;
> >> unsigned slot = PCI_SLOT(devfn);
> >> unsigned fn = PCI_FUNC(devfn);
> >> unsigned busno = bus->number;
> >> @@ -208,10 +202,7 @@ int iproc_pcie_setup(struct iproc_pcie *pcie, struct list_head *res)
> >>
> >> iproc_pcie_reset(pcie);
> >>
> >> - pcie->sysdata.private_data = pcie;
> >> -
> >> - bus = pci_create_root_bus(pcie->dev, 0, &iproc_pcie_ops,
> >> - &pcie->sysdata, res);
> >> + bus = pci_create_root_bus(pcie->dev, 0, &iproc_pcie_ops, pcie, res);
> >> if (!bus) {
> >> dev_err(pcie->dev, "unable to create PCI root bus\n");
> >> ret = -ENOMEM;
> >> @@ -229,7 +220,9 @@ int iproc_pcie_setup(struct iproc_pcie *pcie, struct list_head *res)
> >>
> >> pci_scan_child_bus(bus);
> >> pci_assign_unassigned_bus_resources(bus);
> >> +#ifdef CONFIG_ARM
> >> pci_fixup_irqs(pci_common_swizzle, pcie->map_irq);
> >> +#endif
> >> pci_bus_add_devices(bus);
> >>
> >> return 0;
> >> diff --git a/drivers/pci/host/pcie-iproc.h b/drivers/pci/host/pcie-iproc.h
> >> index ba0a108..0ee9673 100644
> >> --- a/drivers/pci/host/pcie-iproc.h
> >> +++ b/drivers/pci/host/pcie-iproc.h
> >> @@ -18,18 +18,22 @@
> >>
> >> /**
> >> * iProc PCIe device
> >> + * @sysdata: Per PCI controller data. This needs to be kept at the beginning of
> >> + * struct iproc_pcie, to enable support of both ARM32 and ARM64 platforms with
> >> + * minimal changes in the iProc PCIe core driver
> >> * @dev: pointer to device data structure
> >> * @base: PCIe host controller I/O register base
> >> * @resources: linked list of all PCI resources
> >> - * @sysdata: Per PCI controller data
> >> * @root_bus: pointer to root bus
> >> * @phy: optional PHY device that controls the Serdes
> >> * @irqs: interrupt IDs
> >> */
> >> struct iproc_pcie {
> >> +#ifdef CONFIG_ARM
> >> + struct pci_sys_data sysdata;
> >> +#endif
> >
> > I'm OK with adding #ifdefs to make this work on both ARM and ARM64. We can
> > at least see the ifdefs and know what needs to be fixed. I'm a little more
> > hesitant about adding code that depends on the position of sysdata within
> > struct iproc_pcie. I'd rather have something ugly and robust that cries
> > out for fixing than something minimal and fragile.
>
> Yes that was my original code and that was a bit ugly. Arnd proposed
> this and it does indeed make the look a lot cleaner. But yeah, it now
> depends on the location of struct pci_sys_data in memory and I see your
> concern. In fact, I asked exactly the same question to Arnd.
>
> Are you okay with living with this for a little while until struct
> pci_sys_data is eventually removed from arm32?
>
> > I see that your v1 patch added #ifdef CONFIG_ARM around sysdata at its
> > original location below, and you mentioned that you took Arnd's advice to
> > move sysdata to the beginning of the structure, but I don't see Arnd's
> > email on the list.
>
> Sorry maybe you need to elaborate here. Am I supposed to add Arnd's name
> in the commit message? Other than that, Arnd is on this email thread.
No, I wasn't looking for Arnd's name in the changelog; I was just hoping to
read that discussion because it could save me from the embarrassment of
suggesting something different than Arnd did :)
Personally I'd rather have ugly ifdefs because they make it obvious where
the potholes are. But again, I'm sure Arnd has very good reasons if he
thinks this is better.
> >> struct device *dev;
> >> void __iomem *base;
> >> - struct pci_sys_data sysdata;
> >> struct pci_bus *root_bus;
> >> struct phy *phy;
> >> int irqs[IPROC_PCIE_MAX_NUM_IRQS];
> >> --
> >> 1.7.9.5
> >>
next prev parent reply other threads:[~2015-07-21 22:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 4:39 [PATCH v3 0/4] Add Broadcom North Star 2 support Ray Jui
2015-07-16 4:39 ` [PATCH v3 1/4] PCI: iproc: enable arm64 support for iProc PCIe Ray Jui
2015-07-21 20:30 ` Bjorn Helgaas
2015-07-21 20:50 ` Ray Jui
2015-07-21 21:04 ` Ray Jui
2015-07-21 22:02 ` Bjorn Helgaas [this message]
2015-07-22 0:01 ` Ray Jui
2015-07-16 4:39 ` [PATCH v3 2/4] PCI: iproc: Fix ARM64 dependency in Kconfig Ray Jui
2015-07-16 4:39 ` [PATCH v3 3/4] arm64: Add Broadcom iProc family support Ray Jui
2015-07-16 4:39 ` [PATCH v3 4/4] arm64: dts: Add Broadcom North Star 2 support Ray Jui
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=20150721220259.GK21967@google.com \
--to=bhelgaas@google.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rjui@broadcom.com \
--cc=will.deacon@arm.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