From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Melody Olvera <quic_molvera@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Satya Durga Srinivasu Prabhala <quic_satyap@quicinc.com>,
Trilok Soni <quic_tsoni@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/4] soc: qcom: llcc-qcom: Add support for LLCC V6
Date: Wed, 26 Mar 2025 14:39:41 +0100 [thread overview]
Message-ID: <0ca929c6-6ff5-4ab0-8ebf-aed3cc5f350b@oss.qualcomm.com> (raw)
In-Reply-To: <20250324-sm8750_llcc_master-v3-2-2afd5c0fdbde@quicinc.com>
On 3/24/25 9:29 PM, Melody Olvera wrote:
> Add support for LLCC V6. V6 adds several additional usecase IDs,
> rearrages several registers and offsets, and supports slice IDs
> over 31, so add a new function for programming LLCC V6.
>
> Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
> ---
[...]
> +
> + if (config->parent_slice_id && config->fixed_size) {
> + attr2_val |= FIELD_PREP(ATTR2_PARENT_SCID_MASK, config->parent_slice_id);
> + attr2_val |= ATTR2_IN_A_GROUP_MASK;
> + }
This is fragile if parent_slice_id == 0, but let's say this is not an issue
for now..
> +
> + attr3_val = MAX_CAP_TO_BYTES(config->max_cap);
> + attr3_val /= drv_data->num_banks;
> + attr3_val >>= CACHE_LINE_SIZE_SHIFT;
> +
> + ret = regmap_write(drv_data->bcast_regmap, attr0_cfg, attr0_val);
> + if (ret)
> + return ret;
> +
> + ret = regmap_write(drv_data->bcast_regmap, attr1_cfg, attr1_val);
> + if (ret)
> + return ret;
> +
> + ret = regmap_write(drv_data->bcast_regmap, attr2_cfg, attr2_val);
> + if (ret)
> + return ret;
> +
> + ret = regmap_write(drv_data->bcast_regmap, attr3_cfg, attr3_val);
> + if (ret)
> + return ret;
> +
> + slice_offset = config->slice_id % 32;
> + reg_offset = (config->slice_id / 32) * 4;
> +
> + wren = config->write_scid_en << slice_offset;If I'm reading the wrappers right, you should be able to drop both the
shifting and intermediate variables with regmap_assign_bits()
Looks good otherwise
Konrad
next prev parent reply other threads:[~2025-03-26 13:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 20:29 [PATCH v3 0/4] Introduce LLCC v6 used on the SM8750 SoCs Melody Olvera
2025-03-24 20:29 ` [PATCH v3 1/4] dt-bindings: cache: qcom,llcc: Document SM8750 LLCC block Melody Olvera
2025-03-24 20:29 ` [PATCH v3 2/4] soc: qcom: llcc-qcom: Add support for LLCC V6 Melody Olvera
2025-03-26 13:39 ` Konrad Dybcio [this message]
2025-04-09 21:16 ` Melody Olvera
2025-04-14 13:17 ` Konrad Dybcio
2025-03-24 20:29 ` [PATCH v3 3/4] soc: qcom: llcc-qcom: Add support for SM8750 Melody Olvera
2025-04-14 13:24 ` Konrad Dybcio
2025-04-14 23:07 ` Melody Olvera
2025-03-24 20:29 ` [PATCH v3 4/4] arm64: dts: qcom: sm8750: Add LLCC node Melody Olvera
2025-03-26 13:40 ` Konrad Dybcio
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=0ca929c6-6ff5-4ab0-8ebf-aed3cc5f350b@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_molvera@quicinc.com \
--cc=quic_satyap@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--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
all inboxes | Powered by JetHome®