From: Wenrui Li <wenrui.li@rock-chips.com>
To: Arnd Bergmann <arnd@arndb.de>, Shawn Lin <shawn.lin@rock-chips.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Doug Anderson <dianders@chromium.org>,
linux-pci@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] pci: Add PCIe driver for Rockchip Soc
Date: Fri, 27 May 2016 14:48:41 +0800 [thread overview]
Message-ID: <5747EDC9.2080603@rock-chips.com> (raw)
In-Reply-To: <9836736.6VjP1ug4kE@wuerfel>
Hi,
On 2016/5/24 21:03, Arnd Bergmann wrote:
> On Friday, May 20, 2016 6:29:16 PM CEST Shawn Lin wrote:
>
>> +static int rockchip_pcie_wr_own_conf(struct rockchip_pcie_port *pp,
>> + int where, int size, u32 val)
>> +{
>> + u32 tmp;
>> + int offset;
>> +
>> + offset = (where & (~0x3));
>> + tmp = readl(pp->apb_base + PCIE_RC_CONFIG_BASE + offset);
>> + if (size == 4) {
>> + writel(val, pp->apb_base + PCIE_RC_CONFIG_BASE + where);
>> + } else if (size == 2) {
>> + if (where & 0x2)
>> + tmp = ((tmp & 0xffff) | (val << 16));
>> + else
>> + tmp = ((tmp & 0xffff0000) | val);
>> +
>> + writel(tmp, pp->apb_base + PCIE_RC_CONFIG_BASE + offset);
>> + } else if (size == 1) {
>> + if ((where & 0x3) == 0)
>> + tmp = ((tmp & (~0xff)) | val);
>> + else if ((where & 0x3) == 1)
>> + tmp = ((tmp & (~0xff00)) | (val << 8));
>> + else if ((where & 0x3) == 2)
>> + tmp = ((tmp & (~0xff0000)) | (val << 16));
>> + else if ((where & 0x3) == 3)
>> + tmp = ((tmp & (~0xff000000)) | (val << 24));
>> +
>> + writel(tmp, pp->apb_base + PCIE_RC_CONFIG_BASE + offset);
>> + } else {
>> + return PCIBIOS_BAD_REGISTER_NUMBER;
>> + }
>> + return PCIBIOS_SUCCESSFUL;
>> +}
>
> Why can't you access the individual sub-word registers here?
Our soc not support byte and word write in these region. so we have to
use writel() to write these registers.
>
>> +
>> +static int rockchip_pcie_rd_other_conf(struct rockchip_pcie_port *pp,
>> + struct pci_bus *bus, u32 devfn,
>> + int where, int size, u32 *val)
>> +{
>> + u32 busdev;
>> +
>> + busdev = PCIE_ECAM_ADDR(bus->number, PCI_SLOT(devfn),
>> + PCI_FUNC(devfn), where);
>> +
>> + if (busdev & (size - 1)) {
>> + *val = 0;
>> + return PCIBIOS_BAD_REGISTER_NUMBER;
>> + }
>> +
>> + if (size == 4) {
>> + *val = readl(pp->reg_base + busdev);
>> + } else if (size == 2) {
>> + *val = readw(pp->reg_base + busdev);
>> + } else if (size == 1) {
>> + *val = readb(pp->reg_base + busdev);
>> + } else {
>> + *val = 0;
>> + return PCIBIOS_BAD_REGISTER_NUMBER;
>> + }
>> + return PCIBIOS_SUCCESSFUL;
>> +}
>> +
>
> This looks like the normal ECAM operations, you could just call those.
I read ECAM reference code, I found it not support ioremap config space
for each bus individually on 64-bit systems. Our soc is 64-bit system,
and bus0 config space base address is 0xfda00000, bus1 base address is
0xf8100000. So I think it is not normal ECAM operations, I do not know
if I have understood correctly?
>
>> + while (time_before(jiffies, timeout)) {
>> + regmap_read(port->grf, port->pcie_status, &status);
>> + if ((status & (1 << 9))) {
>> + dev_info(port->dev, "pll locked!\n");
>> + err = 0;
>> + break;
>> + }
>> + }
>
> Maybe add an msleep(1) here to avoid busy-looping?
Yeah, its a good suggestion.
>
>
>> + for (reg_no = 0; reg_no < (port->mem_size >> 20); reg_no++) {
>> + err = rockchip_pcie_prog_ob_atu(port, reg_no + 1,
>> + AXI_WRAPPER_MEM_WRITE,
>> + 20 - 1,
>> + port->mem_bus_addr +
>> + (reg_no << 20),
>> + 0);
>> + if (err) {
>> + dev_err(dev, "Program RC outbound atu failed\n");
>> + return err;
>> + }
>> + }
>
> What if there is more than one outbound memory window, e.g. prefetchable
> and non-prefetchable?
>
> Where do you set the I/O window?
Yeah, our soc support these outbound windows, we will support these
windows next patch.
>
>> + err = rockchip_pcie_prog_ib_atu(port, 2, 32 - 1, 0x0, 0);
>> + if (err) {
>> + dev_err(dev, "Program RC inbound atu failed\n");
>> + return err;
>> + }
>
> And this doesn't seem to reflect the DMA ranges.
Our soc support all the ram region use as DMA zone. SO I set all the 32
bits bypass for the inbound ATS.
>
>> +
>> + port->root_bus_nr = port->busn->start;
>> + if (IS_ENABLED(CONFIG_PCI_MSI)) {
>> + bus = pci_scan_root_bus_msi(port->dev, port->root_bus_nr,
>> + &rockchip_pcie_ops, port, &res,
>> + port->msi);
>> + } else {
>> + bus = pci_scan_root_bus(&pdev->dev, 0,
>> + &rockchip_pcie_ops, port, &res);
>
>
> PCI_MSI is selected unconditionally from Kconfig for this driver, so no
> need for the compile-time check here.
Yeah, we will delete the compile-time check in next patch.
>
>> +
>> +static int rockchip_pcie_remove(struct platform_device *pdev)
>> +{
>> + struct rockchip_pcie_port *port = platform_get_drvdata(pdev);
>> +
>> + clk_disable_unprepare(port->hclk_pcie);
>> + clk_disable_unprepare(port->aclk_perf_pcie);
>> + clk_disable_unprepare(port->aclk_pcie);
>> + clk_disable_unprepare(port->clk_pciephy_ref);
>> +
>> + return 0;
>> +}
>
> You don't seem to remove the child devices here. Have you tried unloading the module?
>
I don't seem the remove function in other pcie host driver. I think this
function could be deleted.
> Arnd
>
>
>
>
>
Best Regards
Wenrui Li
next prev parent reply other threads:[~2016-05-27 6:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 10:28 [PATCH 0/2] Add Rockchip PCIe RC controller support Shawn Lin
2016-05-20 10:29 ` [PATCH 1/2] Documentation: add binding description of Rockchip PCIe controller Shawn Lin
2016-05-20 11:20 ` Heiko Stuebner
2016-05-21 3:55 ` Shawn Lin
2016-05-23 19:53 ` Heiko Stuebner
2016-05-24 1:42 ` Shawn Lin
[not found] ` <1463740146-7106-1-git-send-email-shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-05-30 11:08 ` Marc Zyngier
[not found] ` <20160530120836.290f0d16-5wv7dgnIgG8@public.gmane.org>
2016-05-31 9:48 ` Shawn Lin
[not found] ` <c6fa65a1-58bd-520a-42a1-d6edf576840a-NgiFYW8Wbx6Ta72+1OMJgUB+6BGkLq7r@public.gmane.org>
2016-05-31 10:09 ` Marc Zyngier
2016-05-20 10:29 ` [PATCH 2/2] pci: Add PCIe driver for Rockchip Soc Shawn Lin
2016-05-20 21:13 ` Heiko Stuebner
2016-05-23 0:48 ` Shawn Lin
2016-05-23 3:27 ` Shawn Lin
2016-05-23 15:15 ` Bharat Kumar Gogada
2016-05-24 1:28 ` Shawn Lin
[not found] ` <1463740156-7148-1-git-send-email-shawn.lin-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-05-24 13:03 ` Arnd Bergmann
2016-05-27 6:48 ` Wenrui Li [this message]
[not found] ` <5747EDC9.2080603-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-05-27 7:13 ` Bharat Kumar Gogada
2016-05-27 10:31 ` Wenrui Li
[not found] ` <57482200.9090008-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-01 8:24 ` Arnd Bergmann
2016-06-01 9:57 ` Shawn Lin
[not found] ` <edd7ae48-fb73-41dd-51b7-6d61d1e92ae7-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-01 12:24 ` Arnd Bergmann
2016-05-26 19:00 ` [2/2] " Rajat Jain
2016-05-27 12:25 ` [PATCH 2/2] " Marc Zyngier
[not found] ` <57483CAA.8000005-5wv7dgnIgG8@public.gmane.org>
2016-06-01 2:56 ` Wenrui Li
2016-06-01 8:34 ` Marc Zyngier
[not found] ` <574E9E27.9070702-5wv7dgnIgG8@public.gmane.org>
2016-06-01 9:52 ` Wenrui Li
2016-06-03 8:55 ` Lorenzo Pieralisi
2016-06-03 9:01 ` Marc Zyngier
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=5747EDC9.2080603@rock-chips.com \
--to=wenrui.li@rock-chips.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=shawn.lin@rock-chips.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).