All of lore.kernel.org
 help / color / mirror / Atom feed
From: Punit Agrawal <punit.agrawal@oss.qualcomm.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Punit Agrawal <punit.agrawal@oss.qualcomm.com>,
	jassisinghbrar@gmail.com, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Jamie Iles <jamie.iles@oss.qualcomm.com>
Subject: Re: [PATCH] mailbox: pcc: don't zero error register
Date: Wed, 03 Dec 2025 11:05:12 +0000	[thread overview]
Message-ID: <871plbn7vb.fsf@stealth> (raw)
In-Reply-To: <20251127-cherubic-chicken-of-honeydew-075eac@sudeepholla> (Sudeep Holla's message of "Thu, 27 Nov 2025 14:37:45 +0000")

Sudeep Holla <sudeep.holla@arm.com> writes:

> On Wed, Nov 05, 2025 at 02:42:29PM +0000, Punit Agrawal wrote:
>> From: Jamie Iles <jamie.iles@oss.qualcomm.com>
>> 
>> The error status mask for a type 3/4 subspace is used for reading the
>> error status, and the bitwise inverse is used for clearing the error
>> with the intent being to preserve any of the non-error bits.  However,
>> we were previously applying the mask to extract the status and then
>> applying the inverse to the result which ended up clearing all bits.
>> 
>> Instead, store the inverse mask in the preserve mask and then use that
>> on the original value read from the error status so that only the error
>> is cleared.
>> 
>> Fixes: c45ded7e1135 ("mailbox: pcc: Add support for PCCT extended PCC subspaces(type 3/4)")
>
> Good catch!
>
> Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>

Thanks! It looks like Jassi picked up the patch as a fix for v6.18.

      reply	other threads:[~2025-12-03 11:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 14:42 [PATCH] mailbox: pcc: don't zero error register Punit Agrawal
2025-11-27 14:37 ` Sudeep Holla
2025-12-03 11:05   ` Punit Agrawal [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871plbn7vb.fsf@stealth \
    --to=punit.agrawal@oss.qualcomm.com \
    --cc=jamie.iles@oss.qualcomm.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudeep.holla@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.