From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Francisco Munoz Ruiz <francisco.ruiz@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Unnathi Chalicheemala <unnathi.chalicheemala@oss.qualcomm.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH 0/2] Fix slice accounting and simplify descriptor and locking logic
Date: Sun, 15 Mar 2026 21:02:29 -0500 [thread overview]
Message-ID: <177362655073.7429.1560095184450386966.b4-ty@kernel.org> (raw)
In-Reply-To: <20260305-external_llcc_changes1set-v1-0-6347e52e648e@oss.qualcomm.com>
On Thu, 05 Mar 2026 19:12:04 -0800, Francisco Munoz Ruiz wrote:
> This series addresses correctness issues in the LLCC slice
> activation logic and simplifies both descriptor management and
> locking within the driver.
>
> Patch 1 fixes incorrect slice activation and deactivation
> accounting. The current bitmap-based scheme fails when multiple
> client drivers vote for the same slice or when
> llcc_slice_getd() is called multiple times. This can lead to
> mismatched activation and deactivation pairs and incorrect slice
> state.
>
> [...]
Applied, thanks!
[1/2] soc: qcom: llcc: Add per-slice counter and common llcc slice descriptor
commit: 45c2a55d13c698ba6a281315676934c44225b034
[2/2] soc: qcom: llcc: Use guards for mutex handling
commit: eda32f68ce7a3d16071870c7af0803fdfae40401
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-03-16 2:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 3:12 Francisco Munoz Ruiz
2026-03-06 3:12 ` [PATCH 1/2] soc: qcom: llcc: Add per-slice counter and common llcc slice descriptor Francisco Munoz Ruiz
2026-03-06 3:12 ` [PATCH 2/2] soc: qcom: llcc: Use guards for mutex handling Francisco Munoz Ruiz
2026-03-16 2:02 ` Bjorn Andersson [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=177362655073.7429.1560095184450386966.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=francisco.ruiz@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=unnathi.chalicheemala@oss.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®