From: Andrew Murray <andrew.murray@arm.com> To: Xiaowei Bao <xiaowei.bao@nxp.com> Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>, Roy Zang <roy.zang@nxp.com>, "lorenzo.pieralisi@arm.co" <lorenzo.pieralisi@arm.com>, "arnd@arndb.de" <arnd@arndb.de>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>, "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>, "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Leo Li <leoyang.li@nxp.com>, "M.h. Lian" <minghuan.lian@nxp.com>, "robh+dt@kernel.org" <robh+dt@kernel.org>, "gustavo.pimentel@synopsys.com" <gustavo.pimentel@synopsys.com>, "jingoohan1@gmail.com" <jingoohan1@gmail.com>, "bhelgaas@google.com" <bhelgaas@google.com>, Kishon Vijay Abraham I <kishon@ti.com>, "shawnguo@kernel.org" <shawnguo@kernel.org>, Mingkai Hu <mingkai.hu@nxp.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH v2 06/10] PCI: layerscape: Modify the way of getting capability with different PEX Date: Mon, 2 Sep 2019 14:36:38 +0100 Message-ID: <20190902133637.GM9720@e119886-lin.cambridge.arm.com> (raw) In-Reply-To: <AM5PR04MB32995566CD6DF0AAAD1AE52EF5A40@AM5PR04MB3299.eurprd04.prod.outlook.com> On Fri, Aug 23, 2019 at 04:13:30AM +0000, Xiaowei Bao wrote: > > > > -----Original Message----- > > From: Kishon Vijay Abraham I <kishon@ti.com> > > Sent: 2019年8月23日 11:40 > > To: Xiaowei Bao <xiaowei.bao@nxp.com>; bhelgaas@google.com; > > robh+dt@kernel.org; mark.rutland@arm.com; shawnguo@kernel.org; Leo Li > > <leoyang.li@nxp.com>; lorenzo.pieralisi@arm.co > > <lorenzo.pieralisi@arm.com>; arnd@arndb.de; gregkh@linuxfoundation.org; > > M.h. Lian <minghuan.lian@nxp.com>; Mingkai Hu <mingkai.hu@nxp.com>; > > Roy Zang <roy.zang@nxp.com>; jingoohan1@gmail.com; > > gustavo.pimentel@synopsys.com; linux-pci@vger.kernel.org; > > devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; > > linux-arm-kernel@lists.infradead.org; linuxppc-dev@lists.ozlabs.org; > > andrew.murray@arm.com > > Subject: Re: [PATCH v2 06/10] PCI: layerscape: Modify the way of getting > > capability with different PEX > > > > Hi, > > > > (Fixed Lorenzo's email address. All the patches in the series have wrong email > > id) > > > > On 23/08/19 8:09 AM, Xiaowei Bao wrote: > > > > > > > > >> -----Original Message----- > > >> From: Kishon Vijay Abraham I <kishon@ti.com> > > >> Sent: 2019年8月22日 19:44 > > >> To: Xiaowei Bao <xiaowei.bao@nxp.com>; bhelgaas@google.com; > > >> robh+dt@kernel.org; mark.rutland@arm.com; shawnguo@kernel.org; Leo > > Li > > >> <leoyang.li@nxp.com>; lorenzo.pieralisi@arm.co; arnd@arndb.de; > > >> gregkh@linuxfoundation.org; M.h. Lian <minghuan.lian@nxp.com>; > > >> Mingkai Hu <mingkai.hu@nxp.com>; Roy Zang <roy.zang@nxp.com>; > > >> jingoohan1@gmail.com; gustavo.pimentel@synopsys.com; > > >> linux-pci@vger.kernel.org; devicetree@vger.kernel.org; > > >> linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org; > > >> linuxppc-dev@lists.ozlabs.org; andrew.murray@arm.com > > >> Subject: Re: [PATCH v2 06/10] PCI: layerscape: Modify the way of > > >> getting capability with different PEX > > >> > > >> Hi, > > >> > > >> On 22/08/19 4:52 PM, Xiaowei Bao wrote: > > >>> The different PCIe controller in one board may be have different > > >>> capability of MSI or MSIX, so change the way of getting the MSI > > >>> capability, make it more flexible. > > >> > > >> please use different pci_epc_features table for different boards. > > > Thanks, I think that it will be more flexible to dynamically get MSI > > > or MSIX capability, Thus, we will not need to define the pci_epc_feature for > > different boards. > > > > Is the restriction because you cannot have different compatible for different > > boards? > Sorry, I am not very clear what your mean, I think even if I use the same compatible > with different boards, each boards will enter the probe function, in there I will get > the MSI or MSIX PCIe capability of the current controller in this board. Why do I need > to define the pci_epc_feature for different boards? At present you determine how to set the [msi,msix]_capable flags of pci_epc_features based on reading the function capabilities at probe time. Instead of doing this, is it possible that you can determine the flags based on the compatible type alone? For example, is the MSI/MSIX capability the same for all fsl,ls2088a-pcie-ep devices? If it isn't *necessary* to probe for this information at probe time, then you could instead create a static pci_epc_features structure and assign it to something in your drvdata. This may provide some benefits. The dw_pcie_ep_get_features function would then look like: static const struct pci_epc_features* ls_pcie_ep_get_features(struct dw_pcie_ep *ep) { struct dw_pcie *pci = to_dw_pcie_from_pp(ep); struct ls_pcie_ep *pcie = dev_get_drvdata(pci->dev); return pcie->epc_features; } This also means you can revert "[v3,03/11] PCI: designware-ep: Move the". Is this what you had in mind Kishon? Thanks, Andrew Murray > > > > Thanks > > Kishon > > > > >> > > >> Thanks > > >> Kishon > > >>> > > >>> Signed-off-by: Xiaowei Bao <xiaowei.bao@nxp.com> > > >>> --- > > >>> v2: > > >>> - Remove the repeated assignment code. > > >>> > > >>> drivers/pci/controller/dwc/pci-layerscape-ep.c | 26 > > >>> +++++++++++++++++++------- > > >>> 1 file changed, 19 insertions(+), 7 deletions(-) > > >>> > > >>> diff --git a/drivers/pci/controller/dwc/pci-layerscape-ep.c > > >>> b/drivers/pci/controller/dwc/pci-layerscape-ep.c > > >>> index 4e92a95..8461f62 100644 > > >>> --- a/drivers/pci/controller/dwc/pci-layerscape-ep.c > > >>> +++ b/drivers/pci/controller/dwc/pci-layerscape-ep.c > > >>> @@ -22,6 +22,7 @@ > > >>> > > >>> struct ls_pcie_ep { > > >>> struct dw_pcie *pci; > > >>> + struct pci_epc_features *ls_epc; > > >>> }; > > >>> > > >>> #define to_ls_pcie_ep(x) dev_get_drvdata((x)->dev) > > >>> @@ -40,25 +41,26 @@ static const struct of_device_id > > >> ls_pcie_ep_of_match[] = { > > >>> { }, > > >>> }; > > >>> > > >>> -static const struct pci_epc_features ls_pcie_epc_features = { > > >>> - .linkup_notifier = false, > > >>> - .msi_capable = true, > > >>> - .msix_capable = false, > > >>> -}; > > >>> - > > >>> static const struct pci_epc_features* > > >>> ls_pcie_ep_get_features(struct dw_pcie_ep *ep) { > > >>> - return &ls_pcie_epc_features; > > >>> + struct dw_pcie *pci = to_dw_pcie_from_ep(ep); > > >>> + struct ls_pcie_ep *pcie = to_ls_pcie_ep(pci); > > >>> + > > >>> + return pcie->ls_epc; > > >>> } > > >>> > > >>> static void ls_pcie_ep_init(struct dw_pcie_ep *ep) { > > >>> struct dw_pcie *pci = to_dw_pcie_from_ep(ep); > > >>> + struct ls_pcie_ep *pcie = to_ls_pcie_ep(pci); > > >>> enum pci_barno bar; > > >>> > > >>> for (bar = BAR_0; bar <= BAR_5; bar++) > > >>> dw_pcie_ep_reset_bar(pci, bar); > > >>> + > > >>> + pcie->ls_epc->msi_capable = ep->msi_cap ? true : false; > > >>> + pcie->ls_epc->msix_capable = ep->msix_cap ? true : false; > > >>> } > > >>> > > >>> static int ls_pcie_ep_raise_irq(struct dw_pcie_ep *ep, u8 func_no, > > >>> @@ > > >>> -118,6 +120,7 @@ static int __init ls_pcie_ep_probe(struct > > >>> platform_device > > >> *pdev) > > >>> struct device *dev = &pdev->dev; > > >>> struct dw_pcie *pci; > > >>> struct ls_pcie_ep *pcie; > > >>> + struct pci_epc_features *ls_epc; > > >>> struct resource *dbi_base; > > >>> int ret; > > >>> > > >>> @@ -129,6 +132,10 @@ static int __init ls_pcie_ep_probe(struct > > >> platform_device *pdev) > > >>> if (!pci) > > >>> return -ENOMEM; > > >>> > > >>> + ls_epc = devm_kzalloc(dev, sizeof(*ls_epc), GFP_KERNEL); > > >>> + if (!ls_epc) > > >>> + return -ENOMEM; > > >>> + > > >>> dbi_base = platform_get_resource_byname(pdev, > > IORESOURCE_MEM, > > >> "regs"); > > >>> pci->dbi_base = devm_pci_remap_cfg_resource(dev, dbi_base); > > >>> if (IS_ERR(pci->dbi_base)) > > >>> @@ -139,6 +146,11 @@ static int __init ls_pcie_ep_probe(struct > > >> platform_device *pdev) > > >>> pci->ops = &ls_pcie_ep_ops; > > >>> pcie->pci = pci; > > >>> > > >>> + ls_epc->linkup_notifier = false, > > >>> + ls_epc->bar_fixed_64bit = (1 << BAR_2) | (1 << BAR_4), > > >>> + > > >>> + pcie->ls_epc = ls_epc; > > >>> + > > >>> platform_set_drvdata(pdev, pcie); > > >>> > > >>> ret = ls_add_pcie_ep(pcie, pdev); > > >>> _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply index Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-22 11:22 [PATCH v2 01/10] PCI: designware-ep: Add multiple PFs support for DWC Xiaowei Bao 2019-08-22 11:22 ` [PATCH v2 02/10] PCI: designware-ep: Add the doorbell mode of MSI-X in EP mode Xiaowei Bao 2019-08-23 13:35 ` Andrew Murray 2019-08-23 23:51 ` Xiaowei Bao 2019-08-22 11:22 ` [PATCH v2 03/10] PCI: designware-ep: Move the function of getting MSI capability forward Xiaowei Bao 2019-08-23 13:38 ` Andrew Murray 2019-08-24 0:20 ` Xiaowei Bao 2019-08-22 11:22 ` [PATCH v2 04/10] dt-bindings: pci: layerscape-pci: add compatible strings for ls1088a and ls2088a Xiaowei Bao 2019-08-27 22:26 ` Rob Herring 2019-08-29 9:19 ` Xiaowei Bao 2019-08-22 11:22 ` [PATCH v2 05/10] PCI: layerscape: Fix some format issue of the code Xiaowei Bao 2019-08-23 13:45 ` Andrew Murray 2019-08-24 0:00 ` Xiaowei Bao 2019-08-22 11:22 ` [PATCH v2 06/10] PCI: layerscape: Modify the way of getting capability with different PEX Xiaowei Bao 2019-08-22 11:43 ` Kishon Vijay Abraham I 2019-08-23 2:39 ` Xiaowei Bao 2019-08-23 3:39 ` Kishon Vijay Abraham I 2019-08-23 4:13 ` Xiaowei Bao 2019-09-02 13:36 ` Andrew Murray [this message] 2019-09-03 2:11 ` Xiaowei Bao 2019-08-22 11:22 ` [PATCH v2 07/10] PCI: layerscape: Modify the MSIX to the doorbell way Xiaowei Bao 2019-08-23 13:58 ` Andrew Murray 2019-08-24 0:08 ` Xiaowei Bao 2019-08-27 13:25 ` Andrew Murray 2019-08-28 2:49 ` Xiaowei Bao 2019-08-29 5:13 ` Kishon Vijay Abraham I 2019-11-05 12:37 ` Lorenzo Pieralisi 2019-11-06 9:33 ` Xiaowei Bao 2019-11-06 9:40 ` Gustavo Pimentel 2019-11-06 10:03 ` Xiaowei Bao 2019-11-06 13:39 ` Kishon Vijay Abraham I 2019-11-06 15:40 ` Gustavo Pimentel 2019-08-22 11:22 ` [PATCH v2 08/10] PCI: layerscape: Add EP mode support for ls1088a and ls2088a Xiaowei Bao 2019-08-23 14:27 ` Andrew Murray 2019-08-24 0:18 ` Xiaowei Bao 2019-08-24 6:45 ` christophe leroy 2019-08-25 3:07 ` Xiaowei Bao 2019-08-27 14:48 ` Andrew Murray 2019-08-28 3:25 ` Xiaowei Bao 2019-08-26 9:49 ` Xiaowei Bao 2019-08-27 13:34 ` Andrew Murray 2019-08-28 4:29 ` Xiaowei Bao 2019-08-28 9:01 ` Andrew Murray 2019-08-29 2:03 ` Xiaowei Bao 2019-08-22 11:22 ` [PATCH v2 09/10] arm64: dts: layerscape: Add PCIe EP node for ls1088a Xiaowei Bao 2019-08-22 11:22 ` [PATCH v2 10/10] misc: pci_endpoint_test: Add LS1088a in pci_device_id table Xiaowei Bao 2019-08-23 13:25 ` [PATCH v2 01/10] PCI: designware-ep: Add multiple PFs support for DWC Andrew Murray 2019-08-23 23:50 ` Xiaowei Bao 2019-08-27 13:10 ` Andrew Murray 2019-08-28 7:22 ` Xiaowei Bao
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=20190902133637.GM9720@e119886-lin.cambridge.arm.com \ --to=andrew.murray@arm.com \ --cc=arnd@arndb.de \ --cc=bhelgaas@google.com \ --cc=devicetree@vger.kernel.org \ --cc=gregkh@linuxfoundation.org \ --cc=gustavo.pimentel@synopsys.com \ --cc=jingoohan1@gmail.com \ --cc=kishon@ti.com \ --cc=leoyang.li@nxp.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=lorenzo.pieralisi@arm.com \ --cc=mark.rutland@arm.com \ --cc=minghuan.lian@nxp.com \ --cc=mingkai.hu@nxp.com \ --cc=robh+dt@kernel.org \ --cc=roy.zang@nxp.com \ --cc=shawnguo@kernel.org \ --cc=xiaowei.bao@nxp.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
Linux-ARM-Kernel Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-arm-kernel/0 linux-arm-kernel/git/0.git git clone --mirror https://lore.kernel.org/linux-arm-kernel/1 linux-arm-kernel/git/1.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-arm-kernel linux-arm-kernel/ https://lore.kernel.org/linux-arm-kernel \ linux-arm-kernel@lists.infradead.org public-inbox-index linux-arm-kernel Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.infradead.lists.linux-arm-kernel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git