From: Yajun Deng <hidden> Date: 2021-08-26 06:04:25
pcibios_alloc_irq() will be called in pci_device_probe(), but there
hasn't pcibios_free_irq() in arm64 architecture correspond it.
pcibios_free_irq() is an empty weak function in drivers/pci/pci-driver.c.
So add pcibios_free_irq() for correspond it. This will be called
in pci_device_remove().
====================
v2: remove the change in pcibios_alloc_irq(), and modify the commit log.
====================
Signed-off-by: Yajun Deng <redacted>
---
arch/arm64/kernel/pci.c | 7 +++++++
1 file changed, 7 insertions(+)
On Thu, Aug 26, 2021 at 02:04:06PM +0800, Yajun Deng wrote:
quoted hunk
pcibios_alloc_irq() will be called in pci_device_probe(), but there
hasn't pcibios_free_irq() in arm64 architecture correspond it.
pcibios_free_irq() is an empty weak function in drivers/pci/pci-driver.c.
So add pcibios_free_irq() for correspond it. This will be called
in pci_device_remove().
====================
v2: remove the change in pcibios_alloc_irq(), and modify the commit log.
====================
Signed-off-by: Yajun Deng <redacted>
---
arch/arm64/kernel/pci.c | 7 +++++++
1 file changed, 7 insertions(+)
@@ -29,6 +29,13 @@ int pcibios_alloc_irq(struct pci_dev *dev)return0;}++voidpcibios_free_irq(structpci_dev*dev)+{+if(!acpi_disabled)+acpi_pci_irq_disable(dev);+}
For symmetry with the alloc path, this looks fine but I'd like Lorenzo
to confirm.
The other questions, what does it fix and do we need a cc stable?
Thanks.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Lorenzo Pieralisi <hidden> Date: 2021-09-21 15:47:39
On Thu, Aug 26, 2021 at 02:04:06PM +0800, Yajun Deng wrote:
pcibios_alloc_irq() will be called in pci_device_probe(), but there
hasn't pcibios_free_irq() in arm64 architecture correspond it.
pcibios_free_irq() is an empty weak function in drivers/pci/pci-driver.c.
"pcibios_alloc_irq() is a weak function called to allocate IRQs for
a device in pci_device_probe(); arm64 implements it with
ACPI specific code to enable IRQs for a device.
When a device is removed (pci_device_remove()) the pcibios_free_irq()
counterpart is called.
Current arm64 code does not implement a pcibios_free_irq() function,
and therefore, the weak empty stub is executed, which means that the
IRQ for a device are not properly disabled when a device is removed.
Add an arm64 pcibios_free_irq() to undo the actions carried out in
pcibios_alloc_irq()."
This is a stub commit log. Then you need to describe the bug you
are fixing (if any, or it is just code inspection ?)
So add pcibios_free_irq() for correspond it. This will be called
in pci_device_remove().
====================
v2: remove the change in pcibios_alloc_irq(), and modify the commit log.
====================
Don't add versioning in the commit log, it does not belong here.
I don't think we should send this to stable kernels straight away,
it is best to make sure we are not triggering any regressions first.
Lorenzo
September 21, 2021 11:47 PM, "Lorenzo Pieralisi" [off-list ref] wrote:
On Thu, Aug 26, 2021 at 02:04:06PM +0800, Yajun Deng wrote:
quoted
pcibios_alloc_irq() will be called in pci_device_probe(), but there
hasn't pcibios_free_irq() in arm64 architecture correspond it.
pcibios_free_irq() is an empty weak function in drivers/pci/pci-driver.c.
"pcibios_alloc_irq() is a weak function called to allocate IRQs for
a device in pci_device_probe(); arm64 implements it with
ACPI specific code to enable IRQs for a device.
When a device is removed (pci_device_remove()) the pcibios_free_irq()
counterpart is called.
Current arm64 code does not implement a pcibios_free_irq() function,
and therefore, the weak empty stub is executed, which means that the
IRQ for a device are not properly disabled when a device is removed.
Add an arm64 pcibios_free_irq() to undo the actions carried out in
pcibios_alloc_irq()."
This is a stub commit log. Then you need to describe the bug you
are fixing (if any, or it is just code inspection ?)
It is just code inspection.
quoted
So add pcibios_free_irq() for correspond it. This will be called
in pci_device_remove().
====================
v2: remove the change in pcibios_alloc_irq(), and modify the commit log.
====================
Don't add versioning in the commit log, it does not belong here.
I don't think we should send this to stable kernels straight away,
it is best to make sure we are not triggering any regressions first.
Lorenzo
From: Lorenzo Pieralisi <hidden> Date: 2021-09-22 16:22:09
On Wed, Sep 22, 2021 at 02:49:13AM +0000, yajun.deng@linux.dev wrote:
September 21, 2021 11:47 PM, "Lorenzo Pieralisi" [off-list ref] wrote:
quoted
On Thu, Aug 26, 2021 at 02:04:06PM +0800, Yajun Deng wrote:
quoted
pcibios_alloc_irq() will be called in pci_device_probe(), but there
hasn't pcibios_free_irq() in arm64 architecture correspond it.
pcibios_free_irq() is an empty weak function in drivers/pci/pci-driver.c.
"pcibios_alloc_irq() is a weak function called to allocate IRQs for
a device in pci_device_probe(); arm64 implements it with
ACPI specific code to enable IRQs for a device.
When a device is removed (pci_device_remove()) the pcibios_free_irq()
counterpart is called.
Current arm64 code does not implement a pcibios_free_irq() function,
and therefore, the weak empty stub is executed, which means that the
IRQ for a device are not properly disabled when a device is removed.
Add an arm64 pcibios_free_irq() to undo the actions carried out in
pcibios_alloc_irq()."
This is a stub commit log. Then you need to describe the bug you
are fixing (if any, or it is just code inspection ?)
It is just code inspection.
Before merging it it must be tested, which would prove it is needed.
Lorenzo
quoted
quoted
So add pcibios_free_irq() for correspond it. This will be called
in pci_device_remove().
====================
v2: remove the change in pcibios_alloc_irq(), and modify the commit log.
====================
Don't add versioning in the commit log, it does not belong here.
I don't think we should send this to stable kernels straight away,
it is best to make sure we are not triggering any regressions first.
Lorenzo
From: Will Deacon <will@kernel.org> Date: 2021-10-11 11:09:51
On Wed, Sep 22, 2021 at 05:22:01PM +0100, Lorenzo Pieralisi wrote:
On Wed, Sep 22, 2021 at 02:49:13AM +0000, yajun.deng@linux.dev wrote:
quoted
September 21, 2021 11:47 PM, "Lorenzo Pieralisi" [off-list ref] wrote:
quoted
On Thu, Aug 26, 2021 at 02:04:06PM +0800, Yajun Deng wrote:
quoted
pcibios_alloc_irq() will be called in pci_device_probe(), but there
hasn't pcibios_free_irq() in arm64 architecture correspond it.
pcibios_free_irq() is an empty weak function in drivers/pci/pci-driver.c.
"pcibios_alloc_irq() is a weak function called to allocate IRQs for
a device in pci_device_probe(); arm64 implements it with
ACPI specific code to enable IRQs for a device.
When a device is removed (pci_device_remove()) the pcibios_free_irq()
counterpart is called.
Current arm64 code does not implement a pcibios_free_irq() function,
and therefore, the weak empty stub is executed, which means that the
IRQ for a device are not properly disabled when a device is removed.
Add an arm64 pcibios_free_irq() to undo the actions carried out in
pcibios_alloc_irq()."
This is a stub commit log. Then you need to describe the bug you
are fixing (if any, or it is just code inspection ?)
It is just code inspection.
Before merging it it must be tested, which would prove it is needed.
Ok, I'll ignore this patch for now then. Please yell if you want me to pick
it up.
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel