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 8926BC61D97 for ; Tue, 21 Nov 2023 22:06:31 +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:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=8IVgL7V8sFaRGgu5kYdIs71mQzHGct459P4Wdu9XcNI=; b=GRf84doAXc6s56 dMF0SsdwktyI08b85eh23MCfmybC8pjgZmalk9+aXBogGswgtTXJEihaTWZ27BY3GZknXXTq13rSU wJII+jNuHw71kymU35Ut686dT9a8RVPjSuV5MDZSJcomMY6XgMnuE9aPSLmgUWmNNec/cQC3+eydP hq8R1+9pXQwa9dD8UMGNQnMR/wfEk6T40hESz9LaJQAxV6U2PRjwW+04f0ilbw3+dGjjLgJxxFDTb Rd84o8Bi8W2OfoyXCuwwE5xWKiAvIyuGyV8CAf8g4OZG/W5zCcE0z2nOTo/AU0AIjKEder6nLnXch vajNpFmeYliGTkXS2P/A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1r5Ysd-0009SS-2J; Tue, 21 Nov 2023 22:06:03 +0000 Received: from linux.microsoft.com ([13.77.154.182]) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1r5Ysa-0009S1-2K; Tue, 21 Nov 2023 22:06:02 +0000 Received: from skinsburskii. (unknown [131.107.159.175]) by linux.microsoft.com (Postfix) with ESMTPSA id 2EA5820B74C0; Tue, 21 Nov 2023 14:05:58 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 2EA5820B74C0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1700604358; bh=rtyIaO0ftqOt8/Ba0EA0J2h51r5MdPZqAucb2u8dkig=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=AkLb6wzbi6/WneEHAw8OZyPVFN9DnDZeBhPSjl6hw/37GifoDgNNAXT9FjM64Z/qY f/DiSNRbPU5xJxAnKZb91MqyzcqpJedgYx4oMWrlZFXXPOLFQpH3cow0Rf4jslsKDo 3E35rVsQohMzlITXkjKIJiL4RInM7/hC0sDAhkx8= Date: Tue, 21 Nov 2023 14:05:56 -0800 From: Stanislav Kinsburskii To: Bjorn Helgaas Cc: ryder.lee@mediatek.com, jianjun.wang@mediatek.com, lpieralisi@kernel.org, kw@linux.com, robh@kernel.org, bhelgaas@google.com, matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com, linux-pci@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, skinsburskii@gmail.com Subject: Re: [PATCH] PCI: mediatek: Fix sparse warning caused to virt_to_phys() prototype change Message-ID: <20231121220556.GA21969@skinsburskii.> References: <170052362584.21270.8345708191142620624.stgit@skinsburskii.> <20231121213755.GA258354@bhelgaas> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20231121213755.GA258354@bhelgaas> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231121_140600_880339_77A997EE X-CRM114-Status: GOOD ( 26.61 ) 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 Tue, Nov 21, 2023 at 03:37:55PM -0600, Bjorn Helgaas wrote: > On Mon, Nov 20, 2023 at 03:40:33PM -0800, Stanislav Kinsburskii wrote: > > Explicitly cast __iomem pointer to const void* with __force to fix the > > following warning: > > > > warning: incorrect type in argument 1 (different address spaces) > > expected void const volatile *address > > got void [noderef] __iomem * > > I have two questions about this: > > 1) There's no other use of __force in drivers/pci, so I don't know > what's special about pcie-mediatek.c. There should be a way to fix > the types so it's not needed. > __force suppreses the following sparse warning: warning: cast removes address space '__iomem' of expression > 2) virt_to_phys() is not quite right to begin with because what we > want is a *bus* address, not the CPU physical address we get from > virt_to_phys(). Obviously the current platforms that use this must > not apply any offset between bus and CPU physical addresses, but > it's not something we should rely on. > > There are only three drivers (pci-aardvark.c, pcie-xilinx.c, and > this one) that use virt_to_phys(), and they're all slightly wrong > here. > > The *_compose_msi_msg() methods could use a little more consistency > across the board. > Could you elaborate on what do you suggest? Should virt_to_phys() be simply removed? > > Signed-off-by: Stanislav Kinsburskii > > --- > > drivers/pci/controller/pcie-mediatek.c | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > diff --git a/drivers/pci/controller/pcie-mediatek.c b/drivers/pci/controller/pcie-mediatek.c > > index 66a8f73296fc..27f0f79810a1 100644 > > --- a/drivers/pci/controller/pcie-mediatek.c > > +++ b/drivers/pci/controller/pcie-mediatek.c > > @@ -397,7 +397,7 @@ static void mtk_compose_msi_msg(struct irq_data *data, struct msi_msg *msg) > > phys_addr_t addr; > > > > /* MT2712/MT7622 only support 32-bit MSI addresses */ > > - addr = virt_to_phys(port->base + PCIE_MSI_VECTOR); > > + addr = virt_to_phys((__force const void *)port->base + PCIE_MSI_VECTOR); > > msg->address_hi = 0; > > msg->address_lo = lower_32_bits(addr); > > > > @@ -520,7 +520,7 @@ static void mtk_pcie_enable_msi(struct mtk_pcie_port *port) > > u32 val; > > phys_addr_t msg_addr; > > > > - msg_addr = virt_to_phys(port->base + PCIE_MSI_VECTOR); > > + msg_addr = virt_to_phys((__force const void *)port->base + PCIE_MSI_VECTOR); > > val = lower_32_bits(msg_addr); > > writel(val, port->base + PCIE_IMSI_ADDR); > > > > > > > > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel