Devicetree
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>,
	Kees Cook <kees@kernel.org>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	Jonathan Cameron <jic23@kernel.org>,
	Francisco Munoz Ruiz <francisco.ruiz@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v2 0/3] Retrieve System Cache Table (SCT) descriptors from a shared memory region.
Date: Wed, 13 May 2026 14:08:39 -0500	[thread overview]
Message-ID: <177869930353.1496076.4629367562375349504.b4-ty@kernel.org> (raw)
In-Reply-To: <20260407-external_llcc_changes2set-v2-0-b5017ce2020b@oss.qualcomm.com>


On Tue, 07 Apr 2026 14:51:46 -0700, Francisco Munoz Ruiz wrote:
> On newer Qualcomm platforms, SCT initialization and programming are
> handled entirely by firmware outside of Linux. The kernel is expected
> to consume the pre-initialized descriptor data rather than configure
> the SCT itself. The LLCC driver therefore only needs to locate and
> parse the descriptor table provided by firmware.
> 
> This change implements support for this mechanism in the llcc-qcom
> driver, enabling SCT consumption on platforms that expose SCT
> programming through firmware. The existing behavior for SoCs where
> the kernel programs SCT directly remains unchanged.
> 
> [...]

Applied, thanks!

[1/3] dt-bindings: cache: qcom,llcc: Document Hawi SoC
      commit: cb4a414bacbfdcb837048146b8979032d87e4961
[2/3] soc: qcom: llcc-qcom: get SCT descriptors from fw-populated memory
      commit: ac23106a9b9a0f6ed90002ae3d6fe7c14e97e6bf
[3/3] soc: qcom: llcc-qcom: Capitalize LLCC/EDAC in comments and diagnostics
      commit: 06a84c2d3ca4b9b54724e79717c2cfd9a59947d9

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

      parent reply	other threads:[~2026-05-13 19:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 21:51 [PATCH v2 0/3] Retrieve System Cache Table (SCT) descriptors from a shared memory region Francisco Munoz Ruiz
2026-04-07 21:51 ` [PATCH v2 1/3] dt-bindings: cache: qcom,llcc: Document Hawi SoC Francisco Munoz Ruiz
2026-04-08  7:37   ` Krzysztof Kozlowski
2026-04-07 21:51 ` [PATCH v2 2/3] soc: qcom: llcc-qcom: get SCT descriptors from fw-populated memory Francisco Munoz Ruiz
2026-04-07 21:51 ` [PATCH v2 3/3] soc: qcom: llcc-qcom: Capitalize LLCC/EDAC in comments and diagnostics Francisco Munoz Ruiz
2026-04-13 15:25   ` Mukesh Ojha
2026-04-13 16:10     ` Krzysztof Kozlowski
2026-04-13 16:23       ` Mukesh Ojha
2026-05-13 19:08 ` 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=177869930353.1496076.4629367562375349504.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=francisco.ruiz@oss.qualcomm.com \
    --cc=gustavoars@kernel.org \
    --cc=jic23@kernel.org \
    --cc=kees@kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    /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