From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
robh+dt@kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/3] soc: qcom: llcc-qcom: Add support for SM8250 SoC
Date: Fri, 27 Nov 2020 19:09:09 +0530 [thread overview]
Message-ID: <9b7ed6f800980361dc216275fcf63b26@codeaurora.org> (raw)
In-Reply-To: <20201127121127.158082-4-manivannan.sadhasivam@linaro.org>
Hi Mani,
On 2020-11-27 17:41, Manivannan Sadhasivam wrote:
> SM8250 SoC uses LLCC IP version 2. In this version, the WRSC_EN
> register
> needs to be written to enable the Write Sub Cache for each SCID. Hence,
> use a dedicated "write_scid_en" member with predefined values and write
> them for SoCs enabling the "llcc_v2" flag.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
> drivers/soc/qcom/llcc-qcom.c | 40 ++++++++++++++++++++++++++++++
> include/linux/soc/qcom/llcc-qcom.h | 1 +
> 2 files changed, 41 insertions(+)
>
> diff --git a/drivers/soc/qcom/llcc-qcom.c
> b/drivers/soc/qcom/llcc-qcom.c
> index 16b421608e9c..3ec4cdffa852 100644
> --- a/drivers/soc/qcom/llcc-qcom.c
> +++ b/drivers/soc/qcom/llcc-qcom.c
> @@ -47,6 +47,7 @@
>
> #define LLCC_TRP_SCID_DIS_CAP_ALLOC 0x21f00
> #define LLCC_TRP_PCB_ACT 0x21f04
> +#define LLCC_TRP_WRSC_EN 0x21f20
>
> #define BANK_OFFSET_STRIDE 0x80000
>
> @@ -73,6 +74,7 @@
> * then the ways assigned to this client are not flushed
> on power
> * collapse.
> * @activate_on_init: Activate the slice immediately after it is
> programmed
> + * @write_scid_en: Bit enables write cache support for a given scid.
> */
> struct llcc_slice_config {
> u32 usecase_id;
> @@ -87,12 +89,14 @@ struct llcc_slice_config {
> bool dis_cap_alloc;
> bool retain_on_pc;
> bool activate_on_init;
> + bool write_scid_en;
> };
>
> struct qcom_llcc_config {
> const struct llcc_slice_config *sct_data;
> int size;
> bool need_llcc_cfg;
> + bool llcc_v2;
> };
We can extract the version from HW info register and so
would not have to maintain a flag for every new version
of LLCC. I had a patch to do that which I have sent to you
now, perhaps you can check if that works for you and take
it with this series?
Thanks,
Sai
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member
of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2020-11-27 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 12:11 [PATCH 0/3] Add LLCC support for SM8250 SoC Manivannan Sadhasivam
2020-11-27 12:11 ` [PATCH 1/3] dt-bindings: msm: Add LLCC for SM8250 Manivannan Sadhasivam
2020-12-08 19:46 ` Rob Herring
2020-11-27 12:11 ` [PATCH 2/3] arm64: dts: qcom: sm8250: Add support for LLCC block Manivannan Sadhasivam
2020-11-27 12:11 ` [PATCH 3/3] soc: qcom: llcc-qcom: Add support for SM8250 SoC Manivannan Sadhasivam
2020-11-27 13:39 ` Sai Prakash Ranjan [this message]
2020-11-27 16:07 ` Manivannan Sadhasivam
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=9b7ed6f800980361dc216275fcf63b26@codeaurora.org \
--to=saiprakash.ranjan@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).