From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: honghui.zhang@mediatek.com
Cc: bhelgaas@google.com, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, ryder.lee@mediatek.com,
ulf.hansson@linaro.org, marc.zyngier@arm.com,
matthias.bgg@gmail.com, devicetree@vger.kernel.org,
yingjoe.chen@mediatek.com, eddie.huang@mediatek.com,
youlin.pei@mediatek.com, yt.shen@mediatek.com,
sean.wang@mediatek.com
Subject: Re: [PATCH v5 1/9] PCI: mediatek: Using slot's devfn for compare to fix mtk_pcie_find_port logic
Date: Mon, 1 Oct 2018 15:36:41 +0100 [thread overview]
Message-ID: <20181001143641.GB13049@red-moon> (raw)
In-Reply-To: <1538129080-8206-2-git-send-email-honghui.zhang@mediatek.com>
On Fri, Sep 28, 2018 at 06:04:32PM +0800, honghui.zhang@mediatek.com wrote:
> From: Honghui Zhang <honghui.zhang@mediatek.com>
>
> The Mediatek's host controller has two slots, each with it's own control
> registers. The host driver need to identify which slot was connected
> in order to access the device's configuration space. There's problem
> for current host driver to find out which slot was connected to for
> a given EP device.
>
> Assuming each slot have connect with one EP device as below:
>
> host bridge
> bus 0 --> __________|_______
> | |
> | |
> slot 0 slot 1
> bus 1 -->| bus 2 --> |
> | |
> EP 0 EP 1
>
> During PCI enumeration, system software will scan all the PCI device
> starting from devfn 0. So it will get the proper port for slot0 and
> slot1 device when using PCI_SLOT(devfn) for match. But it will get
> the wrong slot for EP1: The devfn will be start from 0 when scanning
> EP1 behind slot1, it will get port0 since the PCI_SLOT(EP1) is match
> for port0's slot value. So the host driver should not using EP's devfn
> but the slot's devfn(the slot which EP was connected to) for match.
>
> This patch fix the mtk_pcie_find_port's logic by using the slot's
> devfn for match if finding device connected to the subordinate bus.
>
> Signed-off-by: Honghui Zhang <honghui.zhang@mediatek.com>
> ---
> drivers/pci/controller/pcie-mediatek.c | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pci/controller/pcie-mediatek.c b/drivers/pci/controller/pcie-mediatek.c
> index 9999dae..264e03f 100644
> --- a/drivers/pci/controller/pcie-mediatek.c
> +++ b/drivers/pci/controller/pcie-mediatek.c
> @@ -337,10 +337,25 @@ static struct mtk_pcie_port *mtk_pcie_find_port(struct pci_bus *bus,
> {
> struct mtk_pcie *pcie = bus->sysdata;
> struct mtk_pcie_port *port;
> + struct pci_dev *dev = NULL;
> +
> + /*
> + * Walk the bus hierarchy to get the devfn value
> + * of the port in the root bus.
> + */
> + while (bus && bus->number) {
> + dev = bus->self;
> + bus = dev->bus;
If you add:
devfn = dev->devfn;
here
> + }
> +
> + list_for_each_entry(port, &pcie->ports, list) {
> + /* Using slot's devfn to compare for subordinary bus. */
> + if (dev)
> + devfn = dev->devfn;
You can remove this ugly hunk altogether (and dev initialization
to NULL).
Lorenzo
> - list_for_each_entry(port, &pcie->ports, list)
> if (port->slot == PCI_SLOT(devfn))
> return port;
> + }
>
> return NULL;
> }
> --
> 2.6.4
>
next prev parent reply other threads:[~2018-10-01 14:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 10:04 [PATCH v5 0/9] PCI: mediatek: fixup find_port, enable_msi and add pm, module support honghui.zhang
2018-09-28 10:04 ` [PATCH v5 1/9] PCI: mediatek: Using slot's devfn for compare to fix mtk_pcie_find_port logic honghui.zhang
2018-10-01 14:36 ` Lorenzo Pieralisi [this message]
2018-10-02 10:59 ` Lorenzo Pieralisi
[not found] ` <20181002105945.GA27736-4tUPXFaYRHv6sAKXYmQ0tx/iLCjYCKR+VpNB7YpNyf8@public.gmane.org>
2018-10-08 3:02 ` Honghui Zhang
2018-09-28 10:04 ` [PATCH v5 2/9] PCI: mediatek: Fixup class ID for MT7622 as PCI_CLASS_BRIDGE_PCI honghui.zhang
2018-09-28 10:04 ` [PATCH v5 3/9] PCI: mediatek: Remove the redundant dev->pm_domain check honghui.zhang
2018-09-28 10:04 ` [PATCH v5 4/9] PCI: mediatek: Convert to use pci_host_probe() honghui.zhang
2018-09-28 15:41 ` Ryder Lee
2018-09-29 0:16 ` Honghui Zhang
2018-09-29 5:55 ` Ryder Lee
2018-09-28 10:04 ` [PATCH v5 5/9] PCI: mediatek: Move the mtk_pcie_startup_port_v2 function's define after mtk_pcie_setup_irq honghui.zhang
2018-09-28 10:04 ` [PATCH v5 6/9] PCI: mediatek: Enable msi after clock enabled honghui.zhang
2018-10-02 11:01 ` Lorenzo Pieralisi
2018-09-28 10:04 ` [PATCH v5 7/9] PCI: mediatek: Add system pm support for MT2712 and MT7622 honghui.zhang
2018-09-28 10:04 ` [PATCH v5 8/9] PCI: mediatek: Save the GIC IRQ in mtk_pcie_port honghui.zhang
2018-09-28 10:04 ` [PATCH v5 9/9] PCI: mediatek: Add loadable kernel module support honghui.zhang
2018-09-29 5:58 ` [PATCH v5 0/9] PCI: mediatek: fixup find_port, enable_msi and add pm, " Ryder Lee
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=20181001143641.GB13049@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=eddie.huang@mediatek.com \
--cc=honghui.zhang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=ulf.hansson@linaro.org \
--cc=yingjoe.chen@mediatek.com \
--cc=youlin.pei@mediatek.com \
--cc=yt.shen@mediatek.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).