On Thu, Dec 23, 2021 at 4:31 PM srinivas pandruvada
<srinivas.pandruvada@xxxxxxxxxxxxxxx> wrote:
>
> On Thu, 2021-12-23 at 15:12 +0530, Sumeet Pawnikar wrote:
> > The existing mail mechanism only supports writing of workload types.
> > But mailbox command for RFIM (cmd = 0x08) also requires write operation
> > which was ignored. This results in failing to store RFI restriction.
> > This requires enhancing mailbox writes for non workload commands also.
> > So, remove the check for MBOX_CMD_WORKLOAD_TYPE_WRITE in mailbox write,
> > with this other write commands also can be supoorted. But at the same
> > time, we have to make sure that there is no impact on read commands,
> > by not writing anything in mailbox data register.
> > To properly implement, add two separate functions for mbox read and
> > write
> > command for processor thermal workload command type. This helps to
> > differentiate the read and write workload command types while sending
> > mbox
> > command.
> >
> > Fixes: 5d6fbc96bd36 ("thermal/drivers/int340x: processor_thermal:
> > Export additional attributes")
> > Signed-off-by: Sumeet Pawnikar <sumeet.r.pawnikar@xxxxxxxxx>
> > Cc: stable@xxxxxxxxxxxxxxx # 5.14+
> Acked-by: Srinivas Pandruvada <srinivas.pandruvada@xxxxxxxxxxxxxxx>
Applied (with some edits in the changelog) as 5.17 material, thanks!
