mbox series

[0/4] Backport intel thermal driver patches to 5.15-stable

Message ID 20220211093437.8713-1-sumeet.r.pawnikar@intel.com
Headers show
Series Backport intel thermal driver patches to 5.15-stable | expand

Message

Sumeet Pawnikar Feb. 11, 2022, 9:34 a.m. UTC
We need to apply 2685c77b80a8 ("thermal/drivers/int340x: Fix RFIM mailbox write commands")
to the 5.15-stable tree but it does not apply. This patch fix the write
operation for mailbox command for RFIM (cmd = 0x08) which is ignored.
This results in failing to store RFI restriction.

To apply this fix, we need to backport below set of three patches on
5.15-stable tree because this fix depended on these three patches.
Without these three dependent patches, we cannot directly apply
fix (fourth) patch.

Backport three patches:
 [1] c4fcf1ada4ae ("thermal/drivers/int340x: Improve the tcc offset saving for suspend/resume")
 [2] 994a04a20b03 ("thermal: int340x: Limit Kconfig to 64-bit")
 [3] aeb58c860dc5 ("thermal/drivers/int340x: processor_thermal: Suppot 64 bit RFIM responses")

Fix RFIM patch:
 [4] 2685c77b80a8 ("thermal/drivers/int340x: Fix RFIM mailbox write commands")


*** BLURB HERE ***

Antoine Tenart (1):
  thermal/drivers/int340x: Improve the tcc offset saving for
    suspend/resume

Arnd Bergmann (1):
  thermal: int340x: Limit Kconfig to 64-bit

Srinivas Pandruvada (1):
  thermal/drivers/int340x: processor_thermal: Suppot 64 bit RFIM
    responses

Sumeet Pawnikar (1):
  thermal/drivers/int340x: Fix RFIM mailbox write commands

 drivers/thermal/intel/int340x_thermal/Kconfig |   4 +-
 .../intel/int340x_thermal/int3401_thermal.c   |   8 +-
 .../processor_thermal_device.c                |  36 ++++--
 .../processor_thermal_device.h                |   4 +-
 .../processor_thermal_device_pci.c            |  18 ++-
 .../processor_thermal_device_pci_legacy.c     |   8 +-
 .../int340x_thermal/processor_thermal_mbox.c  | 104 +++++++++++-------
 .../int340x_thermal/processor_thermal_rfim.c  |  23 ++--
 8 files changed, 139 insertions(+), 66 deletions(-)

Comments

Greg KH Feb. 11, 2022, 9:22 a.m. UTC | #1
On Fri, Feb 11, 2022 at 03:04:34PM +0530, Sumeet Pawnikar wrote:
> From: Antoine Tenart <atenart@kernel.org>
> 
> When the driver resumes, the tcc offset is set back to its previous
> value. But this only works if the value was user defined as otherwise
> the offset isn't saved. This asymmetric logic is harder to maintain and
> introduced some issues.
> 
> Improve the logic by saving the tcc offset in a suspend op, so the right
> value is always restored after a resume.
> 
> Signed-off-by: Antoine Tenart <atenart@kernel.org>
> Reviewed-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> Tested-by: Srinivas Pandruvada <srinivas.pI andruvada@linux.intel.com>
> Link: https://lore.kernel.org/r/20210909085613.5577-3-atenart@kernel.org
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> Signed-off-by: Sumeet Pawnikar <sumeet.r.pawnikar@intel.com>
> ---

What is the git commit id of this commit in Linus's tree?

Same for the other 3, I need a hint here please...

thanks,

greg k-h