[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0jLms5iUM8CXDWNCPcXSQgLv9_XJzqx9RwReqGGUKFL_Q@mail.gmail.com>
Date: Wed, 20 Sep 2023 21:21:27 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>
Cc: daniel.lezcano@...aro.org, rafael@...nel.org, rui.zhang@...el.com,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH linux-next] thermal: int340x: processor_thermal: Ack all
PCI interrupts
On Wed, Sep 20, 2023 at 8:52 PM Srinivas Pandruvada
<srinivas.pandruvada@...ux.intel.com> wrote:
>
> All interrupts from the processor thermal PCI device requires ACK. This
> is done by writing 0x01 at offset 0xDC in the config space. This is
> already done for the thereshold interrupt. Extend this for the workload
> hint interrupt.
>
> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>
Is this a fix for one of the commits in linux-next? If so, which one?
> ---
> .../intel/int340x_thermal/processor_thermal_device_pci.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/thermal/intel/int340x_thermal/processor_thermal_device_pci.c b/drivers/thermal/intel/int340x_thermal/processor_thermal_device_pci.c
> index 44b179ce9bc9..3c5ced79ead0 100644
> --- a/drivers/thermal/intel/int340x_thermal/processor_thermal_device_pci.c
> +++ b/drivers/thermal/intel/int340x_thermal/processor_thermal_device_pci.c
> @@ -154,10 +154,11 @@ static irqreturn_t proc_thermal_irq_handler(int irq, void *devid)
> if (status) {
> /* Disable enable interrupt flag */
> proc_thermal_mmio_write(pci_info, PROC_THERMAL_MMIO_INT_ENABLE_0, 0);
> - pci_write_config_byte(pci_info->pdev, 0xdc, 0x01);
> pkg_thermal_schedule_work(&pci_info->work);
> }
>
> + pci_write_config_byte(pci_info->pdev, 0xdc, 0x01);
> +
> return ret;
> }
>
> --
> 2.40.1
>
Powered by blists - more mailing lists