From: Marc Zyngier <marc.zyngier@arm.com>
To: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
Cc: Ray Jui <rjui@broadcom.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"galak@codeaurora.org" <galak@codeaurora.org>,
Michal Simek <michals@xilinx.com>,
Soren Brinkmann <sorenb@xilinx.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"tinamdar@apm.com" <tinamdar@apm.com>,
"treding@nvidia.com" <treding@nvidia.com>,
"Minghuan.Lian@freescale.com" <Minghuan.Lian@freescale.com>,
"m-karicheri2@ti.com" <m-karicheri2@ti.com>,
"hauke@hauke-m.de" <hauke@hauke-m.de>,
"dhdang@apm.com" <dhdang@apm.com>,
"sbranden@broadcom.com" <sbranden@broadcom.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Ravikiran Gummaluri <rgummal@xilinx.com>
Subject: Re: [PATCH v8] PCI: Xilinx-NWL-PCIe: Added support for Xilinx NWL PCIe Host Controller
Date: Tue, 17 Nov 2015 09:21:00 +0000 [thread overview]
Message-ID: <20151117092100.76babf7f@arm.com> (raw)
In-Reply-To: <8520D5D51A55D047800579B0941471982585CBDA@XAP-PVEXMBX01.xlnx.xilinx.com>
On Tue, 17 Nov 2015 04:59:39 +0000
Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com> wrote:
> > On 11/16/2015 7:14 AM, Marc Zyngier wrote:
> > > On 11/11/15 06:33, Bharat Kumar Gogada wrote:
> > >> Adding PCIe Root Port driver for Xilinx PCIe NWL bridge IP.
> > >>
> > >> Signed-off-by: Bharat Kumar Gogada <bharatku@xilinx.com>
> > >> Signed-off-by: Ravi Kiran Gummaluri <rgummal@xilinx.com>
> > >> ---
> > >> Added logic to allocate contiguous hwirq in nwl_irq_domain_alloc
> > function.
> > >> Moved MSI functionality to separate functions.
> > >> Changed error return values.
> > >> ---
> > >> .../devicetree/bindings/pci/xilinx-nwl-pcie.txt | 68 ++
> > >> drivers/pci/host/Kconfig | 16 +-
> > >> drivers/pci/host/Makefile | 1 +
> > >> drivers/pci/host/pcie-xilinx-nwl.c | 1062
> > ++++++++++++++++++++
> > >> 4 files changed, 1144 insertions(+), 3 deletions(-)
> > >> create mode 100644 Documentation/devicetree/bindings/pci/xilinx-nwl-
> > pcie.txt
> > >> create mode 100644 drivers/pci/host/pcie-xilinx-nwl.c
> > >>
> > >
> > > [...]
> > >
> > >> +static int nwl_pcie_enable_msi(struct nwl_pcie *pcie, struct pci_bus
> > >> +*bus) {
> > >> + struct platform_device *pdev = to_platform_device(pcie->dev);
> > >> + struct nwl_msi *msi = &pcie->msi;
> > >> + unsigned long base;
> > >> + int ret;
> > >> +
> > >> + mutex_init(&msi->lock);
> > >> +
> > >> + /* Check for msii_present bit */
> > >> + ret = nwl_bridge_readl(pcie, I_MSII_CAPABILITIES) & MSII_PRESENT;
> > >> + if (!ret) {
> > >> + dev_err(pcie->dev, "MSI not present\n");
> > >> + ret = -EIO;
> > >> + goto err;
> > >> + }
> > >> +
> > >> + /* Enable MSII */
> > >> + nwl_bridge_writel(pcie, nwl_bridge_readl(pcie, I_MSII_CONTROL) |
> > >> + MSII_ENABLE, I_MSII_CONTROL);
> > >> +
> > >> + /* Enable MSII status */
> > >> + nwl_bridge_writel(pcie, nwl_bridge_readl(pcie, I_MSII_CONTROL) |
> > >> + MSII_STATUS_ENABLE, I_MSII_CONTROL);
> > >> +
> > >> + /* setup AFI/FPCI range */
> > >> + msi->pages = __get_free_pages(GFP_KERNEL, 0);
> > >> + base = virt_to_phys((void *)msi->pages);
> > >> + nwl_bridge_writel(pcie, lower_32_bits(base), I_MSII_BASE_LO);
> > >> + nwl_bridge_writel(pcie, upper_32_bits(base), I_MSII_BASE_HI);
> > >
> > > BTW, you still haven't answered my question as to why you need to
> > > waste a page of memory here, and why putting a device address doesn't
> > work.
> > >
> > > As this is (to the best of my knowledge) the only driver doing so, I'd
> > > really like you to explain the rational behind this.
> >
> > Might not be the only driver doing so after I start sending out patches for the
> > iProc MSI support (soon), :)
> >
> > I'm not sure how it works for the Xilinx NWL controller, which Bharat should
> > be able to help to explain. But for the iProc MSI controller, there's no device
> > I/O memory reserved for MSI posted writes in the ASIC.
> > Therefore one needs to reserve host memory for these writes.
> > >
>
> Our SoC doesn't reserve any memory for MSI, hence we need to assign a
> memory space for it out of RAM.
Question to both of you: Does the write make it to memory? Or is it
sampled by the bridge and dropped?
What happens if you replace the page in RAM with a dummy address?
Thanks,
M.
--
Jazz is not dead. It just smells funny.
WARNING: multiple messages have this Message-ID (diff)
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8] PCI: Xilinx-NWL-PCIe: Added support for Xilinx NWL PCIe Host Controller
Date: Tue, 17 Nov 2015 09:21:00 +0000 [thread overview]
Message-ID: <20151117092100.76babf7f@arm.com> (raw)
In-Reply-To: <8520D5D51A55D047800579B0941471982585CBDA@XAP-PVEXMBX01.xlnx.xilinx.com>
On Tue, 17 Nov 2015 04:59:39 +0000
Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com> wrote:
> > On 11/16/2015 7:14 AM, Marc Zyngier wrote:
> > > On 11/11/15 06:33, Bharat Kumar Gogada wrote:
> > >> Adding PCIe Root Port driver for Xilinx PCIe NWL bridge IP.
> > >>
> > >> Signed-off-by: Bharat Kumar Gogada <bharatku@xilinx.com>
> > >> Signed-off-by: Ravi Kiran Gummaluri <rgummal@xilinx.com>
> > >> ---
> > >> Added logic to allocate contiguous hwirq in nwl_irq_domain_alloc
> > function.
> > >> Moved MSI functionality to separate functions.
> > >> Changed error return values.
> > >> ---
> > >> .../devicetree/bindings/pci/xilinx-nwl-pcie.txt | 68 ++
> > >> drivers/pci/host/Kconfig | 16 +-
> > >> drivers/pci/host/Makefile | 1 +
> > >> drivers/pci/host/pcie-xilinx-nwl.c | 1062
> > ++++++++++++++++++++
> > >> 4 files changed, 1144 insertions(+), 3 deletions(-)
> > >> create mode 100644 Documentation/devicetree/bindings/pci/xilinx-nwl-
> > pcie.txt
> > >> create mode 100644 drivers/pci/host/pcie-xilinx-nwl.c
> > >>
> > >
> > > [...]
> > >
> > >> +static int nwl_pcie_enable_msi(struct nwl_pcie *pcie, struct pci_bus
> > >> +*bus) {
> > >> + struct platform_device *pdev = to_platform_device(pcie->dev);
> > >> + struct nwl_msi *msi = &pcie->msi;
> > >> + unsigned long base;
> > >> + int ret;
> > >> +
> > >> + mutex_init(&msi->lock);
> > >> +
> > >> + /* Check for msii_present bit */
> > >> + ret = nwl_bridge_readl(pcie, I_MSII_CAPABILITIES) & MSII_PRESENT;
> > >> + if (!ret) {
> > >> + dev_err(pcie->dev, "MSI not present\n");
> > >> + ret = -EIO;
> > >> + goto err;
> > >> + }
> > >> +
> > >> + /* Enable MSII */
> > >> + nwl_bridge_writel(pcie, nwl_bridge_readl(pcie, I_MSII_CONTROL) |
> > >> + MSII_ENABLE, I_MSII_CONTROL);
> > >> +
> > >> + /* Enable MSII status */
> > >> + nwl_bridge_writel(pcie, nwl_bridge_readl(pcie, I_MSII_CONTROL) |
> > >> + MSII_STATUS_ENABLE, I_MSII_CONTROL);
> > >> +
> > >> + /* setup AFI/FPCI range */
> > >> + msi->pages = __get_free_pages(GFP_KERNEL, 0);
> > >> + base = virt_to_phys((void *)msi->pages);
> > >> + nwl_bridge_writel(pcie, lower_32_bits(base), I_MSII_BASE_LO);
> > >> + nwl_bridge_writel(pcie, upper_32_bits(base), I_MSII_BASE_HI);
> > >
> > > BTW, you still haven't answered my question as to why you need to
> > > waste a page of memory here, and why putting a device address doesn't
> > work.
> > >
> > > As this is (to the best of my knowledge) the only driver doing so, I'd
> > > really like you to explain the rational behind this.
> >
> > Might not be the only driver doing so after I start sending out patches for the
> > iProc MSI support (soon), :)
> >
> > I'm not sure how it works for the Xilinx NWL controller, which Bharat should
> > be able to help to explain. But for the iProc MSI controller, there's no device
> > I/O memory reserved for MSI posted writes in the ASIC.
> > Therefore one needs to reserve host memory for these writes.
> > >
>
> Our SoC doesn't reserve any memory for MSI, hence we need to assign a
> memory space for it out of RAM.
Question to both of you: Does the write make it to memory? Or is it
sampled by the bridge and dropped?
What happens if you replace the page in RAM with a dummy address?
Thanks,
M.
--
Jazz is not dead. It just smells funny.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <marc.zyngier@arm.com>
To: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
Cc: Ray Jui <rjui@broadcom.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"galak@codeaurora.org" <galak@codeaurora.org>,
Michal Simek <michals@xilinx.com>,
Soren Brinkmann <sorenb@xilinx.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"tinamdar@apm.com" <tinamdar@apm.com>,
"treding@nvidia.com" <treding@nvidia.com>,
"Minghuan.Lian@freescale.com" <Minghuan.Lian@freescale.com>,
"m-karicheri2@ti.com" <m-karicheri2@ti.com>,
"hauke@hauke-m.de" <hauke@hauke-m.de>,
"dhdang@apm.com" <dhdang@apm.com>,
"sbranden@broadcom.com" <sbranden@broadcom.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>l
Subject: Re: [PATCH v8] PCI: Xilinx-NWL-PCIe: Added support for Xilinx NWL PCIe Host Controller
Date: Tue, 17 Nov 2015 09:21:00 +0000 [thread overview]
Message-ID: <20151117092100.76babf7f@arm.com> (raw)
In-Reply-To: <8520D5D51A55D047800579B0941471982585CBDA@XAP-PVEXMBX01.xlnx.xilinx.com>
On Tue, 17 Nov 2015 04:59:39 +0000
Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com> wrote:
> > On 11/16/2015 7:14 AM, Marc Zyngier wrote:
> > > On 11/11/15 06:33, Bharat Kumar Gogada wrote:
> > >> Adding PCIe Root Port driver for Xilinx PCIe NWL bridge IP.
> > >>
> > >> Signed-off-by: Bharat Kumar Gogada <bharatku@xilinx.com>
> > >> Signed-off-by: Ravi Kiran Gummaluri <rgummal@xilinx.com>
> > >> ---
> > >> Added logic to allocate contiguous hwirq in nwl_irq_domain_alloc
> > function.
> > >> Moved MSI functionality to separate functions.
> > >> Changed error return values.
> > >> ---
> > >> .../devicetree/bindings/pci/xilinx-nwl-pcie.txt | 68 ++
> > >> drivers/pci/host/Kconfig | 16 +-
> > >> drivers/pci/host/Makefile | 1 +
> > >> drivers/pci/host/pcie-xilinx-nwl.c | 1062
> > ++++++++++++++++++++
> > >> 4 files changed, 1144 insertions(+), 3 deletions(-)
> > >> create mode 100644 Documentation/devicetree/bindings/pci/xilinx-nwl-
> > pcie.txt
> > >> create mode 100644 drivers/pci/host/pcie-xilinx-nwl.c
> > >>
> > >
> > > [...]
> > >
> > >> +static int nwl_pcie_enable_msi(struct nwl_pcie *pcie, struct pci_bus
> > >> +*bus) {
> > >> + struct platform_device *pdev = to_platform_device(pcie->dev);
> > >> + struct nwl_msi *msi = &pcie->msi;
> > >> + unsigned long base;
> > >> + int ret;
> > >> +
> > >> + mutex_init(&msi->lock);
> > >> +
> > >> + /* Check for msii_present bit */
> > >> + ret = nwl_bridge_readl(pcie, I_MSII_CAPABILITIES) & MSII_PRESENT;
> > >> + if (!ret) {
> > >> + dev_err(pcie->dev, "MSI not present\n");
> > >> + ret = -EIO;
> > >> + goto err;
> > >> + }
> > >> +
> > >> + /* Enable MSII */
> > >> + nwl_bridge_writel(pcie, nwl_bridge_readl(pcie, I_MSII_CONTROL) |
> > >> + MSII_ENABLE, I_MSII_CONTROL);
> > >> +
> > >> + /* Enable MSII status */
> > >> + nwl_bridge_writel(pcie, nwl_bridge_readl(pcie, I_MSII_CONTROL) |
> > >> + MSII_STATUS_ENABLE, I_MSII_CONTROL);
> > >> +
> > >> + /* setup AFI/FPCI range */
> > >> + msi->pages = __get_free_pages(GFP_KERNEL, 0);
> > >> + base = virt_to_phys((void *)msi->pages);
> > >> + nwl_bridge_writel(pcie, lower_32_bits(base), I_MSII_BASE_LO);
> > >> + nwl_bridge_writel(pcie, upper_32_bits(base), I_MSII_BASE_HI);
> > >
> > > BTW, you still haven't answered my question as to why you need to
> > > waste a page of memory here, and why putting a device address doesn't
> > work.
> > >
> > > As this is (to the best of my knowledge) the only driver doing so, I'd
> > > really like you to explain the rational behind this.
> >
> > Might not be the only driver doing so after I start sending out patches for the
> > iProc MSI support (soon), :)
> >
> > I'm not sure how it works for the Xilinx NWL controller, which Bharat should
> > be able to help to explain. But for the iProc MSI controller, there's no device
> > I/O memory reserved for MSI posted writes in the ASIC.
> > Therefore one needs to reserve host memory for these writes.
> > >
>
> Our SoC doesn't reserve any memory for MSI, hence we need to assign a
> memory space for it out of RAM.
Question to both of you: Does the write make it to memory? Or is it
sampled by the bridge and dropped?
What happens if you replace the page in RAM with a dummy address?
Thanks,
M.
--
Jazz is not dead. It just smells funny.
next prev parent reply other threads:[~2015-11-17 9:21 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 6:33 [PATCH v8] PCI: Xilinx-NWL-PCIe: Added support for Xilinx NWL PCIe Host Controller Bharat Kumar Gogada
2015-11-11 6:33 ` Bharat Kumar Gogada
2015-11-11 6:33 ` Bharat Kumar Gogada
2015-11-11 17:37 ` Marc Zyngier
2015-11-11 17:37 ` Marc Zyngier
2015-11-11 17:37 ` Marc Zyngier
2015-11-17 5:06 ` Bharat Kumar Gogada
2015-11-17 5:06 ` Bharat Kumar Gogada
2015-11-17 5:06 ` Bharat Kumar Gogada
2015-11-11 20:29 ` Rob Herring
2015-11-11 20:29 ` Rob Herring
2015-11-11 20:29 ` Rob Herring
2015-11-16 10:27 ` Bharat Kumar Gogada
2015-11-16 10:27 ` Bharat Kumar Gogada
2015-11-16 10:27 ` Bharat Kumar Gogada
2015-11-16 15:14 ` Marc Zyngier
2015-11-16 15:14 ` Marc Zyngier
2015-11-16 22:01 ` Ray Jui
2015-11-16 22:01 ` Ray Jui
2015-11-16 22:01 ` Ray Jui
2015-11-17 4:59 ` Bharat Kumar Gogada
2015-11-17 4:59 ` Bharat Kumar Gogada
2015-11-17 9:21 ` Marc Zyngier [this message]
2015-11-17 9:21 ` Marc Zyngier
2015-11-17 9:21 ` Marc Zyngier
2015-11-17 13:27 ` Bharat Kumar Gogada
2015-11-17 13:27 ` Bharat Kumar Gogada
2015-11-17 13:27 ` Bharat Kumar Gogada
2015-11-17 13:55 ` Marc Zyngier
2015-11-17 13:55 ` Marc Zyngier
2015-11-17 13:55 ` Marc Zyngier
2015-11-17 16:24 ` Ray Jui
2015-11-17 16:24 ` Ray Jui
2015-11-17 16:24 ` Ray Jui
2015-11-18 6:51 ` Bharat Kumar Gogada
2015-11-18 6:51 ` Bharat Kumar Gogada
2015-11-18 6:51 ` Bharat Kumar Gogada
2015-11-16 22:16 ` Ray Jui
2015-11-16 22:16 ` Ray Jui
2015-11-16 22:16 ` Ray Jui
2015-11-17 5:01 ` Bharat Kumar Gogada
2015-11-17 5:01 ` Bharat Kumar Gogada
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=20151117092100.76babf7f@arm.com \
--to=marc.zyngier@arm.com \
--cc=Minghuan.Lian@freescale.com \
--cc=arnd@arndb.de \
--cc=bharat.kumar.gogada@xilinx.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dhdang@apm.com \
--cc=galak@codeaurora.org \
--cc=hauke@hauke-m.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=mark.rutland@arm.com \
--cc=michals@xilinx.com \
--cc=pawel.moll@arm.com \
--cc=rgummal@xilinx.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=sorenb@xilinx.com \
--cc=tinamdar@apm.com \
--cc=treding@nvidia.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.