From: "Rafał Miłecki" <zajec5@gmail.com> To: Hauke Mehrtens <hauke@hauke-m.de> Cc: Ray Jui <rjui@broadcom.com>, Bjorn Helgaas <bhelgaas@google.com>, Arnd Bergmann <arnd@arndb.de>, Linux PCI <linux-pci@vger.kernel.org>, Scott Branden <sbranden@broadcom.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com> Subject: Re: [PATCH 2/2] PCI: iproc: add bcma pcie driver Date: Wed, 13 May 2015 08:27:47 +0200 [thread overview] Message-ID: <CACna6rxVpJ-4b_5jG91JN62jQHh8u=QaLpO+_7J9mFr+_ScPaA@mail.gmail.com> (raw) In-Reply-To: <1431465781-10753-3-git-send-email-hauke@hauke-m.de> On 12 May 2015 at 23:23, Hauke Mehrtens <hauke@hauke-m.de> wrote: > This driver adds support for the PCIe 2.0 controller found on the bcma > bus. This controller can be found on (mostly) all Broadcom BCM470X / > BCM5301X ARM SoCs. > > The driver found in the Broadcom SDK does some more stuff, like setting > up some DMA memory areas, chaining MPS and MRRS to 512 and also some > PHY changes like "improving" the PCIe jitter and doing some special > initializations for the 3rd PCIe port. > > This was tested on a bcm4708 board with 2 PCIe ports and wireless cards > connected to them. > > PCI_DOMAINS is needed by this driver, because normally there is more > than one PCIe controller and without PCI_DOMAINS only the first > controller gets registered. > This controller gets 6 IRQs, the last one is trigged by all IRQ events. > > Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Acked-by: Rafał Miłecki <zajec5@gmail.com> > +static int iproc_pcie_bcma_probe(struct bcma_device *bdev) > +{ > + struct iproc_pcie *pcie; > + LIST_HEAD(res); > + struct resource res_mem; > + int ret; > + > + pcie = devm_kzalloc(&bdev->dev, sizeof(*pcie), GFP_KERNEL); > + if (!pcie) > + return -ENOMEM; > + > + pcie->dev = &bdev->dev; > + bcma_set_drvdata(bdev, pcie); > + > + pcie->base = bdev->io_addr; > + > + res_mem.start = bdev->addr_s[0]; > + res_mem.end = bdev->addr_s[0] + SZ_128M - 1; > + res_mem.name = "PCIe MEM space"; > + res_mem.flags = IORESOURCE_MEM; > + pci_add_resource(&res, &res_mem); > + > + pcie->resources = &res; > + > + pcie->map_irq = iproc_pcie_bcma_map_irq; > + > + ret = iproc_pcie_setup(pcie); I think I don't like this part of iproc design. It lefts pcie->resources pointing to some random memory after the setup/probe are done. Guess it should be a separated parameter or sth. The patch is still OK, I just refer to generic iproc possible issue.
WARNING: multiple messages have this Message-ID (diff)
From: zajec5@gmail.com (Rafał Miłecki) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 2/2] PCI: iproc: add bcma pcie driver Date: Wed, 13 May 2015 08:27:47 +0200 [thread overview] Message-ID: <CACna6rxVpJ-4b_5jG91JN62jQHh8u=QaLpO+_7J9mFr+_ScPaA@mail.gmail.com> (raw) In-Reply-To: <1431465781-10753-3-git-send-email-hauke@hauke-m.de> On 12 May 2015 at 23:23, Hauke Mehrtens <hauke@hauke-m.de> wrote: > This driver adds support for the PCIe 2.0 controller found on the bcma > bus. This controller can be found on (mostly) all Broadcom BCM470X / > BCM5301X ARM SoCs. > > The driver found in the Broadcom SDK does some more stuff, like setting > up some DMA memory areas, chaining MPS and MRRS to 512 and also some > PHY changes like "improving" the PCIe jitter and doing some special > initializations for the 3rd PCIe port. > > This was tested on a bcm4708 board with 2 PCIe ports and wireless cards > connected to them. > > PCI_DOMAINS is needed by this driver, because normally there is more > than one PCIe controller and without PCI_DOMAINS only the first > controller gets registered. > This controller gets 6 IRQs, the last one is trigged by all IRQ events. > > Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Acked-by: Rafa? Mi?ecki <zajec5@gmail.com> > +static int iproc_pcie_bcma_probe(struct bcma_device *bdev) > +{ > + struct iproc_pcie *pcie; > + LIST_HEAD(res); > + struct resource res_mem; > + int ret; > + > + pcie = devm_kzalloc(&bdev->dev, sizeof(*pcie), GFP_KERNEL); > + if (!pcie) > + return -ENOMEM; > + > + pcie->dev = &bdev->dev; > + bcma_set_drvdata(bdev, pcie); > + > + pcie->base = bdev->io_addr; > + > + res_mem.start = bdev->addr_s[0]; > + res_mem.end = bdev->addr_s[0] + SZ_128M - 1; > + res_mem.name = "PCIe MEM space"; > + res_mem.flags = IORESOURCE_MEM; > + pci_add_resource(&res, &res_mem); > + > + pcie->resources = &res; > + > + pcie->map_irq = iproc_pcie_bcma_map_irq; > + > + ret = iproc_pcie_setup(pcie); I think I don't like this part of iproc design. It lefts pcie->resources pointing to some random memory after the setup/probe are done. Guess it should be a separated parameter or sth. The patch is still OK, I just refer to generic iproc possible issue.
next prev parent reply other threads:[~2015-05-13 6:27 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-12 21:22 [PATCH 0/2] PCI: iproc: add bcma PCIe 2.0 controller Hauke Mehrtens 2015-05-12 21:22 ` Hauke Mehrtens 2015-05-12 21:23 ` [PATCH 1/2] PCI: iproc: make of_irq_parse_and_map_pci() configurable Hauke Mehrtens 2015-05-12 21:23 ` Hauke Mehrtens 2015-05-12 22:14 ` Ray Jui 2015-05-12 22:14 ` Ray Jui 2015-05-12 21:23 ` [PATCH 2/2] PCI: iproc: add bcma pcie driver Hauke Mehrtens 2015-05-12 21:23 ` Hauke Mehrtens 2015-05-12 22:18 ` Ray Jui 2015-05-12 22:18 ` Ray Jui 2015-05-13 6:27 ` Rafał Miłecki [this message] 2015-05-13 6:27 ` Rafał Miłecki 2015-05-13 15:56 ` Ray Jui 2015-05-13 15:56 ` Ray Jui 2015-05-13 16:19 ` Rafał Miłecki 2015-05-13 16:19 ` Rafał Miłecki 2015-05-13 16:30 ` Ray Jui 2015-05-13 16:30 ` Ray Jui 2015-05-13 18:43 ` Hauke Mehrtens 2015-05-13 18:43 ` Hauke Mehrtens 2015-05-19 23:14 ` Bjorn Helgaas 2015-05-19 23:14 ` Bjorn Helgaas 2015-05-19 23:17 ` Ray Jui 2015-05-19 23:17 ` Ray Jui 2015-05-20 5:27 ` Rafał Miłecki 2015-05-20 5:27 ` Rafał Miłecki 2015-05-12 22:05 ` [PATCH 0/2] PCI: iproc: add bcma PCIe 2.0 controller Ray Jui 2015-05-12 22:05 ` Ray Jui 2015-05-20 14:52 ` Bjorn Helgaas 2015-05-20 14:52 ` Bjorn Helgaas
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='CACna6rxVpJ-4b_5jG91JN62jQHh8u=QaLpO+_7J9mFr+_ScPaA@mail.gmail.com' \ --to=zajec5@gmail.com \ --cc=arnd@arndb.de \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=bhelgaas@google.com \ --cc=hauke@hauke-m.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-pci@vger.kernel.org \ --cc=rjui@broadcom.com \ --cc=sbranden@broadcom.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: linkBe 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.