linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] ath9k: use unmanaged PCI functions in ath9k_pci_owl_loader
@ 2024-04-01 15:30 Heiner Kallweit
  2024-04-03 21:23 ` Toke Høiland-Jørgensen
  0 siblings, 1 reply; 3+ messages in thread
From: Heiner Kallweit @ 2024-04-01 15:30 UTC (permalink / raw)
  To: Toke Høiland-Jørgensen, Kalle Valo, Andreas Färber,
	Manivannan Sadhasivam, Martin Blumenstingl
  Cc: linux-wireless, linux-arm-kernel@lists.infradead.org,
	linux-actions, linux-pci@vger.kernel.org

Using the device-managed versions has no benefit here, because
resources are released as part of the asynchronous fw loading.

Actual reason why I got here is that I was looking for places with
dubious use of pcim_pin_device().

Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
---
 drivers/net/wireless/ath/ath9k/ath9k_pci_owl_loader.c | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/drivers/net/wireless/ath/ath9k/ath9k_pci_owl_loader.c b/drivers/net/wireless/ath/ath9k/ath9k_pci_owl_loader.c
index a5eb43f30..bc93ca075 100644
--- a/drivers/net/wireless/ath/ath9k/ath9k_pci_owl_loader.c
+++ b/drivers/net/wireless/ath/ath9k/ath9k_pci_owl_loader.c
@@ -65,7 +65,7 @@ static int ath9k_pci_fixup(struct pci_dev *pdev, const u16 *cal_data,
 
 	dev_info(&pdev->dev, "fixup device configuration\n");
 
-	mem = pcim_iomap(pdev, 0, 0);
+	mem = pci_iomap(pdev, 0, 0);
 	if (!mem) {
 		dev_err(&pdev->dev, "ioremap error\n");
 		return -EINVAL;
@@ -103,7 +103,7 @@ static int ath9k_pci_fixup(struct pci_dev *pdev, const u16 *cal_data,
 	pci_write_config_word(pdev, PCI_COMMAND, cmd);
 
 	pci_write_config_dword(pdev, PCI_BASE_ADDRESS_0, bar0);
-	pcim_iounmap(pdev, mem);
+	pci_iounmap(pdev, mem);
 
 	pci_disable_device(pdev);
 
@@ -200,11 +200,9 @@ static int owl_probe(struct pci_dev *pdev,
 	const char *eeprom_name;
 	int err = 0;
 
-	if (pcim_enable_device(pdev))
+	if (pci_enable_device(pdev))
 		return -EIO;
 
-	pcim_pin_device(pdev);
-
 	ctx = devm_kzalloc(&pdev->dev, sizeof(*ctx), GFP_KERNEL);
 	if (!ctx)
 		return -ENOMEM;
-- 
2.44.0


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] ath9k: use unmanaged PCI functions in ath9k_pci_owl_loader
  2024-04-01 15:30 [PATCH] ath9k: use unmanaged PCI functions in ath9k_pci_owl_loader Heiner Kallweit
@ 2024-04-03 21:23 ` Toke Høiland-Jørgensen
  2024-04-04 21:07   ` Heiner Kallweit
  0 siblings, 1 reply; 3+ messages in thread
From: Toke Høiland-Jørgensen @ 2024-04-03 21:23 UTC (permalink / raw)
  To: Heiner Kallweit, Kalle Valo, Andreas Färber,
	Manivannan Sadhasivam, Martin Blumenstingl
  Cc: linux-wireless, linux-arm-kernel@lists.infradead.org,
	linux-actions, linux-pci@vger.kernel.org

Heiner Kallweit <hkallweit1@gmail.com> writes:

> Using the device-managed versions has no benefit here, because
> resources are released as part of the asynchronous fw loading.
>
> Actual reason why I got here is that I was looking for places with
> dubious use of pcim_pin_device().

Could you please expand the commit message to explain what this means in
a bit more detail? That will be helpful to someone who wants to
understand what the difference between these versions is and why this
change makes sense, but who is not that familiar with how these internal
bits are really supposed to work. Someone like myself, in other words :)

-Toke

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] ath9k: use unmanaged PCI functions in ath9k_pci_owl_loader
  2024-04-03 21:23 ` Toke Høiland-Jørgensen
@ 2024-04-04 21:07   ` Heiner Kallweit
  0 siblings, 0 replies; 3+ messages in thread
From: Heiner Kallweit @ 2024-04-04 21:07 UTC (permalink / raw)
  To: Toke Høiland-Jørgensen, Kalle Valo, Andreas Färber,
	Manivannan Sadhasivam, Martin Blumenstingl
  Cc: linux-wireless, linux-arm-kernel@lists.infradead.org,
	linux-actions, linux-pci@vger.kernel.org

On 03.04.2024 23:23, Toke Høiland-Jørgensen wrote:
> Heiner Kallweit <hkallweit1@gmail.com> writes:
> 
>> Using the device-managed versions has no benefit here, because
>> resources are released as part of the asynchronous fw loading.
>>
>> Actual reason why I got here is that I was looking for places with
>> dubious use of pcim_pin_device().
> 
> Could you please expand the commit message to explain what this means in
> a bit more detail? That will be helpful to someone who wants to
> understand what the difference between these versions is and why this
> change makes sense, but who is not that familiar with how these internal
> bits are really supposed to work. Someone like myself, in other words :)
> 
Sure. I'll add some more context in a v2.

> -Toke
Heiner

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2024-04-04 21:07 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-04-01 15:30 [PATCH] ath9k: use unmanaged PCI functions in ath9k_pci_owl_loader Heiner Kallweit
2024-04-03 21:23 ` Toke Høiland-Jørgensen
2024-04-04 21:07   ` Heiner Kallweit

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).