From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 0F9C6C61DA3 for ; Tue, 21 Feb 2023 22:02:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:From:References:Cc:To: Subject:MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=3gxZcwtGfUzcuTRHv6yaF2Gzlx9XjOdivHYjy9s81M4=; b=eNGc9cjzpyyFnk psOC3IHDLKnSo1LVDb/kzVMeLikLyO72K6+5slSM+iE0TWGVwiz7eA5kRlJ8P54PsCCtLgGF63oR/ i+MgECjgZvmf/sQGWhkrt9aN/dyN4UgzobMcKT+L4PojrBsXnvpP/FavJMmsYMUoD3JCijyNK6ukn XfJigFzHjnBQYr+/ru2IF6JmL1BU8x3SAb/t9+4zoV0Vx6C3y2E9Y5uR2VyhRuJcW1bpwTEpudvpg IPkfo1xgI2C0vDZKoVzhqoY6oYT7fI/KdYIPxX8b4q98izh0UV/479DlKXTsGg+gHJZVGhe1SPLfg l2+fnolj8BHfaQYiPEgg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pUahp-009uY5-Hy; Tue, 21 Feb 2023 22:01:49 +0000 Received: from esa4.hgst.iphmx.com ([216.71.154.42]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1pUahk-009uWc-1i for linux-arm-kernel@lists.infradead.org; Tue, 21 Feb 2023 22:01:48 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=wdc.com; i=@wdc.com; q=dns/txt; s=dkim.wdc.com; t=1677016904; x=1708552904; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=Qg8gwLNpEVZ/vS7KRtMF6qf8aQbtNuIsSDPzlOtBJ4E=; b=e0ym2/NzH93dGkdVBzq0aqL7dJzDqfPCCOkHCF4V9Y2aL/4ZfZ4MY0hz 1OIlqYUcxQ3rQUJb3PPMHDDeHyouLVyjmwYTHyFtVoIfUN/B5nZzqltvI C9eiKL8n/kK8O3zkBV12vLaeDHKmCm4UzL64DWWM2tMMOxakeWBYKR0Mp MZN5UQayCoMUao9f9it6xWRjV74sQGwkop3LyFZrOWdKUl/XyYloDsTEK H7Y/Qc8TLtOA9QzrqLdDFnYcpNCmy7Gr/0wiJx3HGT0DOa1ycMzfxPWla EhlZVkYqs77eaMev6NyKRTarzaUc4jyggmbLFyMEW3OV4TRfwKFAy5Jyg g==; X-IronPort-AV: E=Sophos;i="5.97,317,1669046400"; d="scan'208";a="222134355" Received: from h199-255-45-15.hgst.com (HELO uls-op-cesaep02.wdc.com) ([199.255.45.15]) by ob1.hgst.iphmx.com with ESMTP; 22 Feb 2023 06:01:42 +0800 IronPort-SDR: +xhgbUnlNNNueXwFq0OWui3UKdYEBNGpvwEmlfKo62dKiiZGqBevsu/u/OcuTlrElGerbFwENu +R5FQ8sztBSPtfgUBYYBu3qf0nIJES5tfbFjinemg/woGpzeqYVPwuJgozoVe30QxkXy3As+jT gob6rkg2pLN9Gu221ZOVX0BrhDaMK1v7bPwNSs+vNuEYwkVgpX7VAlfAdJTQO3uixgox2+X25p x36FvpXUF3ZOGvx0URoLg7O6T7euc+u3hS0OBWd92J65xRpdunjP3u5O2ayfdmdcpi8XK+iKde /AI= Received: from uls-op-cesaip02.wdc.com ([10.248.3.37]) by uls-op-cesaep02.wdc.com with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 21 Feb 2023 13:12:56 -0800 IronPort-SDR: RzN6Tsz6O2BZI2aRzOnkBCn1c2ld2ZP9XVecK/569zndj/FfkjMWLIo4ei/XxizLmVuCoSfzym Y2grxL5MPvxOTmlWfqmAfxZlCW5qk0Kl/YVkoQdKmInHupSuHtxKubH/lS1kaDo4N6DG5wygue H41kd2ce9abQntYejD/M5PH0lgzCIIGRjBb18gfWwh31tvvqtWINakpKy+ZlVnEA1QLxqMcnAx r7I6APB+uqVtonYazDQ9RR9o0e/lL47U6f1dqLhvdX7e1I/TtAnpd2xtGw6jtNeHbXv04uORem x9I= WDCIronportException: Internal Received: from usg-ed-osssrv.wdc.com ([10.3.10.180]) by uls-op-cesaip02.wdc.com with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 21 Feb 2023 14:01:42 -0800 Received: from usg-ed-osssrv.wdc.com (usg-ed-osssrv.wdc.com [127.0.0.1]) by usg-ed-osssrv.wdc.com (Postfix) with ESMTP id 4PLtY21Cwpz1RwqL for ; Tue, 21 Feb 2023 14:01:41 -0800 (PST) Authentication-Results: usg-ed-osssrv.wdc.com (amavisd-new); dkim=pass reason="pass (just generated, assumed good)" header.d=opensource.wdc.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= opensource.wdc.com; h=content-transfer-encoding:content-type :in-reply-to:organization:from:references:to:content-language :subject:user-agent:mime-version:date:message-id; s=dkim; t= 1677016898; x=1679608899; bh=Qg8gwLNpEVZ/vS7KRtMF6qf8aQbtNuIsSDP zlOtBJ4E=; b=gGgMR2vPkzdzMPMgeLlyo5S/2GKH9DnG1VxkOa//OYG6JsBXE8v UobdCeX4I2SwNGfoyzbJc3lKKSC0MiOgHBFwbRZwHD+rbPz8wEulIOZRGulr40Xd EikTsgcIRun6N7pu8sEVOSmIhVwKmbZrVsbHCn6S6k4SQHKR0kac0VNg+Eg74zxf jOua49YCHLEsdSzSqm6yHol0/VMu2imgQZzP1D1ukI32a5JFuXCN6gqTh4CD/lgv iok0pfNDhZF3UForHYcLrSrj7fnt6mBRGnOzTUKrWfC0qXdsW8gDhMYXM67EueyC fXe3UVfoxV5gMgBUke1kEYmIRDEwiIKZE6g== X-Virus-Scanned: amavisd-new at usg-ed-osssrv.wdc.com Received: from usg-ed-osssrv.wdc.com ([127.0.0.1]) by usg-ed-osssrv.wdc.com (usg-ed-osssrv.wdc.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id xYfb9LdYBTDf for ; Tue, 21 Feb 2023 14:01:38 -0800 (PST) Received: from [10.225.163.21] (unknown [10.225.163.21]) by usg-ed-osssrv.wdc.com (Postfix) with ESMTPSA id 4PLtXv6cS4z1RvLy; Tue, 21 Feb 2023 14:01:35 -0800 (PST) Message-ID: Date: Wed, 22 Feb 2023 07:01:34 +0900 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH v2 9/9] PCI: rockchip: Add parameter check for RK3399 PCIe endpoint core set_msi() Content-Language: en-US To: Rick Wertenbroek Cc: alberto.dassatti@heig-vd.ch, xxm@rock-chips.com, rick.wertenbroek@heig-vd.ch, Rob Herring , Krzysztof Kozlowski , Heiko Stuebner , Shawn Lin , Lorenzo Pieralisi , =?UTF-8?Q?Krzysztof_Wilczy=c5=84ski?= , Bjorn Helgaas , Jani Nikula , Greg Kroah-Hartman , Rodrigo Vivi , Mikko Kovanen , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org References: <20230214140858.1133292-1-rick.wertenbroek@gmail.com> <20230214140858.1133292-10-rick.wertenbroek@gmail.com> <38ae72c9-0f0b-1a94-d2e0-f4ea80e94705@opensource.wdc.com> From: Damien Le Moal Organization: Western Digital Research In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230221_140144_265514_44D3F808 X-CRM114-Status: GOOD ( 61.31 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 2/22/23 01:37, Rick Wertenbroek wrote: > On Tue, Feb 21, 2023 at 2:19 PM Rick Wertenbroek > wrote: >> >> On Tue, Feb 21, 2023 at 11:55 AM Damien Le Moal >> wrote: >>> >>> On 2/21/23 19:47, Rick Wertenbroek wrote: >>>> On Wed, Feb 15, 2023 at 2:39 AM Damien Le Moal >>>> wrote: >>>>> >>>>> On 2/14/23 23:08, Rick Wertenbroek wrote: >>>>>> The RK3399 PCIe endpoint core supports only a single PCIe physcial >>>>>> function (function number 0), therefore return -EINVAL if set_msi() is >>>>>> called with a function number greater than 0. >>>>>> The PCIe standard only allows the multi message capability (MMC) value >>>>>> to be up to 0x5 (32 messages), therefore return -EINVAL if set_msi() is >>>>>> called with a MMC value of over 0x5. >>>>>> >>>>>> Signed-off-by: Rick Wertenbroek >>>>>> --- >>>>>> drivers/pci/controller/pcie-rockchip-ep.c | 10 ++++++++++ >>>>>> 1 file changed, 10 insertions(+) >>>>>> >>>>>> diff --git a/drivers/pci/controller/pcie-rockchip-ep.c b/drivers/pci/controller/pcie-rockchip-ep.c >>>>>> index b7865a94e..80634b690 100644 >>>>>> --- a/drivers/pci/controller/pcie-rockchip-ep.c >>>>>> +++ b/drivers/pci/controller/pcie-rockchip-ep.c >>>>>> @@ -294,6 +294,16 @@ static int rockchip_pcie_ep_set_msi(struct pci_epc *epc, u8 fn, u8 vfn, >>>>>> struct rockchip_pcie *rockchip = &ep->rockchip; >>>>>> u32 flags; >>>>>> >>>>>> + if (fn) { >>>>>> + dev_err(&epc->dev, "This endpoint controller only supports a single physical function\n"); >>>>>> + return -EINVAL; >>>>>> + } >>>>> >>>>> Checking this here is late... Given that at most only one physical >>>>> function is supported, the check should be in rockchip_pcie_parse_ep_dt(). >>>>> Something like: >>>>> >>>>> err = of_property_read_u8(dev->of_node, "max-functions", >>>>> &ep->epc->max_functions); >>>>> >>>>> if (err < 0 || ep->epc->max_functions > 1) >>>>> >>>>> ep->epc->max_functions = 1; >>>>> >>>> >>>> Yes, this could be moved to the probe, thanks. >>>> >>>>> And all the macros with the (fn) argument could also be simplified >>>>> (argument fn removed) since fn will always be 0. >>>> >>>> These functions cannot be simplified because they have to follow the signature >>>> given by "pci_epc_ops" (include/linux/pci-epc.h). And this signature has the >>>> function number as a parameter. If we change the function signature we won't >>>> be able to assign these functions to the pc_epc_ops structure >>> >>> I was not suggesting to change the functions signature. I was suggesting >>> dropping the fn argument for the *macros*, e.g. >>> >>> ROCKCHIP_PCIE_EP_FUNC_BASE(fn) -> ROCKCHIP_PCIE_EP_FUNC_BASE >>> >>> since fn is always 0. >>> >>> That said, I am not entirely sure if the limit really is 1 function at most. The >>> TRM seems to be suggesting that up to 4 functions can be supported... >>> >>> [...] >>> >>>>> Another nice cleanup: define ROCKCHIP_PCIE_EP_MSI_CTRL_REG to include the >>>>> ROCKCHIP_PCIE_EP_FUNC_BASE(fn) addition so that we do not have to do it >>>>> here all the time. >>>> >>>> Yes, this could be an improvement but this is the way it is written >>>> everywhere in this >>>> driver, I chose to keep it so as to remain coherent with the rest of the driver. >>>> Cleaning this is not so important since this code will not be >>>> rewritten / changed so >>>> often. But I agree that it might be nicer. But, on the other side if >>>> at some point >>>> support for virtual functions would be added, the offsets would need >>>> to be computed >>>> based on the virtual function number and the code would be written >>>> like it is now, >>>> so I suggest keeping this the way it is for now. >>> >>> Yes, sure, this can be cleaned later. >>> >>> A more pressing problem is the lack of support for MSIX despite the fact that >>> the controller supports that *and* advertize it as a capability. That is what >>> was causing my problem with the Linux nvme driver and my prototype nvme epf >>> function driver: the host driver was seeing MSIX support (1 vector supported by >>> default), and so was allocating one MSIX for the device probe. But on the EP >>> end, it is MSI or INTX only... Working on adding that to solve this issue. >>> >> >> I have seen this too, the controller advertises the capability. However, the TRM >> (section 17.5.9) says that MSI-X is not supported (MSI / INTx only as you said). >> So the solution should be to modify the probe function of the endpoint >> controller >> so that the MSI-X capability would not be advertised, this should fix >> your problem. >> >> I wonder if one could still implement MSI-X because from the endpoint we would >> just need to implement it as a message (TLP) over PCIe (because the space for >> the vectors is allocated and written, so that part should be ok). I am >> not an expert >> on MSI-X, but the reason the endpoint cannot send them could be because MSI-X >> requires some fields in the PCIe header descriptor to be filled with values that >> cannot be set through the "desc0-3" registers of the RK3399 PCIe endpoint core. >> >> Anyways, the endpoint should not advertise the MSI-X capabilities when it cannot >> send such interrupts. Once this is fixed you should be able to have your NVMe >> function running. >> >> Regards. >> Rick >> > > It is possible to disable MSI-X by skipping the MSI-X capability > structure in the PCIe > capabilities structures linked-list. > The current linked list is MSI cap (0x90) -> MSI-X cap (0xb0) -> PCIe > Device cap (0xc0) > So we want to set MSI (0x90) -> PCIe Device cap (0xc0) > > This can be done by writing 0xc0 to bits 15-8 of 0xFDA0'0090 (MSI cap). > I tested this quickly through devmem2 before loading the endpoint > function driver > and it fixes the issue of MSI-X capabilities being advertised to the host. > > In the driver the changes would look like this; > In the probe function you can disable MSI-X as follows: > > @@ -631,6 +618,28 @@ static int rockchip_pcie_ep_probe(struct > platform_device *pdev) > > ep->irq_pci_addr = ROCKCHIP_PCIE_EP_DUMMY_IRQ_ADDR; > > + /* > + * Disable MSI-X because the controller is not capable of MSI-X > + * This requires to skip the MSI-X capabilities entry in the s/capabilities/capability > + * chain of PCIe capabilities, we get the next pointer from the > + * MSI-X entry and set that in the MSI capability entry, this way > + * the MSI-X entry is skipped (left out of the linked-list) > + */ > + cfg_msi = rockchip_pcie_read(rockchip, PCIE_EP_CONFIG_BASE + > + ROCKCHIP_PCIE_EP_MSI_CTRL_REG); > + > + cfg_msi &= ~ROCKCHIP_PCIE_EP_MSI_CP1_MASK; > + > + cfg_msix_cp = rockchip_pcie_read(rockchip, PCIE_EP_CONFIG_BASE + > + ROCKCHIP_PCIE_EP_MSIX_CAP_REG) & > ROCKCHIP_PCIE_EP_MSIX_CAP_CP_MASK; > + > + cfg_msi |= cfg_msix_cp; > + > + rockchip_pcie_write(rockchip, cfg_msi, > + PCIE_EP_CONFIG_BASE + ROCKCHIP_PCIE_EP_MSI_CTRL_REG); > + > rockchip_pcie_write(rockchip, PCIE_CLIENT_CONF_ENABLE, > PCIE_CLIENT_CONFIG); > > return 0; > err_epc_mem_exit: > pci_epc_mem_exit(epc); > > In the pcie-rockchip.h add the following #defines: > > @@ -216,21 +227,28 @@ > #define ROCKCHIP_PCIE_EP_CMD_STATUS 0x4 > #define ROCKCHIP_PCIE_EP_CMD_STATUS_IS BIT(19) > #define ROCKCHIP_PCIE_EP_MSI_CTRL_REG 0x90 > +#define ROCKCHIP_PCIE_EP_MSI_CP1_OFFSET 8 > +#define ROCKCHIP_PCIE_EP_MSI_CP1_MASK GENMASK(15, 8) > +#define ROCKCHIP_PCIE_EP_MSI_FLAGS_OFFSET 16 > #define ROCKCHIP_PCIE_EP_MSI_CTRL_MMC_OFFSET 17 > #define ROCKCHIP_PCIE_EP_MSI_CTRL_MMC_MASK GENMASK(19, 17) > #define ROCKCHIP_PCIE_EP_MSI_CTRL_MME_OFFSET 20 > #define ROCKCHIP_PCIE_EP_MSI_CTRL_MME_MASK GENMASK(22, 20) > #define ROCKCHIP_PCIE_EP_MSI_CTRL_ME BIT(16) > #define ROCKCHIP_PCIE_EP_MSI_CTRL_MASK_MSI_CAP BIT(24) > +#define ROCKCHIP_PCIE_EP_MSIX_CAP_REG 0xb0 > +#define ROCKCHIP_PCIE_EP_MSIX_CAP_CP_OFFSET 8 > +#define ROCKCHIP_PCIE_EP_MSIX_CAP_CP_MASK GENMASK(15, 8) > #define ROCKCHIP_PCIE_EP_DUMMY_IRQ_ADDR 0x1 > #define ROCKCHIP_PCIE_EP_PCI_LEGACY_IRQ_ADDR 0x3 > > I will add this to the next version of the patch set. > Thank you Damien for pointing this out ! This should solve the issues > you have with > your NVMe endpoint function regarding MSI-X interrupts. OK. I replied to your previous mail with the same idea. Looks good :) Will test that instead of my dirty hack that puts 0 in the MSIX capability ID. > > Regards > Rick > >> >>> -- >>> Damien Le Moal >>> Western Digital Research >>> -- Damien Le Moal Western Digital Research _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel