From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv4 1/2] soc: qcom: llcc: Move attribute config to its own function
Date: Tue, 15 Sep 2020 10:55:29 +0530 [thread overview]
Message-ID: <edf5677e4363b42184a47a7483ce8ec6@codeaurora.org> (raw)
In-Reply-To: <160010909573.4188128.171199552773965552@swboyd.mtv.corp.google.com>
On 2020-09-15 00:14, Stephen Boyd wrote:
> Quoting Sai Prakash Ranjan (2020-09-14 04:12:59)
>> Cleanup qcom_llcc_cfg_program() by moving llcc attribute
>> configuration to a separate function of its own. Also
>> correct misspelled 'instance' caught by checkpatch.
>>
>> Suggested-by: Stephen Boyd <swboyd@chromium.org>
>> Signed-off-by: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
>> ---
>> drivers/soc/qcom/llcc-qcom.c | 75
>> ++++++++++++++++++++----------------
>> 1 file changed, 41 insertions(+), 34 deletions(-)
>>
>> diff --git a/drivers/soc/qcom/llcc-qcom.c
>> b/drivers/soc/qcom/llcc-qcom.c
>> index 429b5a60a1ba..60ee31842dea 100644
>> --- a/drivers/soc/qcom/llcc-qcom.c
>> +++ b/drivers/soc/qcom/llcc-qcom.c
>> @@ -318,14 +318,50 @@ size_t llcc_get_slice_size(struct
>> llcc_slice_desc *desc)
>> }
>> EXPORT_SYMBOL_GPL(llcc_get_slice_size);
>>
>> -static int qcom_llcc_cfg_program(struct platform_device *pdev)
>> +static int qcom_llcc_attr_cfg(const struct llcc_slice_config *table)
>
> Call it config? It's certainly not a table.
>
Yes, will do.
>> {
>> - int i;
>> u32 attr1_cfg;
>> u32 attr0_cfg;
>> u32 attr1_val;
>> u32 attr0_val;
>> u32 max_cap_cacheline;
>> + int ret;
>> +
>> + attr1_cfg = LLCC_TRP_ATTR1_CFGn(table->slice_id);
>> + attr0_cfg = LLCC_TRP_ATTR0_CFGn(table->slice_id);
>
> Can this move down to near where it is used?
>
Sure.
>> +
>> + attr1_val = table->cache_mode;
>> + attr1_val |= table->probe_target_ways <<
>> ATTR1_PROBE_TARGET_WAYS_SHIFT;
>> + attr1_val |= table->fixed_size << ATTR1_FIXED_SIZE_SHIFT;
>> + attr1_val |= table->priority << ATTR1_PRIORITY_SHIFT;
>> +
>> + max_cap_cacheline = MAX_CAP_TO_BYTES(table->max_cap);
>> +
>> + /* LLCC instances can vary for each target.
>
> The /* should be on a line by itself.
>
This was there before I moved this hunk but I will fix it.
>> + * The SW writes to broadcast register which gets propagated
>> + * to each llcc instance (llcc0,.. llccN).
>> + * Since the size of the memory is divided equally amongst the
>> + * llcc instances, we need to configure the max cap
>> accordingly.
>> + */
>> + max_cap_cacheline = max_cap_cacheline / drv_data->num_banks;
>> + max_cap_cacheline >>= CACHE_LINE_SIZE_SHIFT;
>> + attr1_val |= max_cap_cacheline << ATTR1_MAX_CAP_SHIFT;
>> +
>> + attr0_val = table->res_ways & ATTR0_RES_WAYS_MASK;
>> + attr0_val |= table->bonus_ways << ATTR0_BONUS_WAYS_SHIFT;
>> +
>> + ret = regmap_write(drv_data->bcast_regmap, attr1_cfg,
>> attr1_val);
>> + if (ret)
>> + return ret;
>> +
>> + ret = regmap_write(drv_data->bcast_regmap, attr0_cfg,
>> attr0_val);
>> +
>> + return ret;
>
> return regmap_write(...)
>
Ok done.
Thanks,
Sai
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member
of Code Aurora Forum, hosted by The Linux Foundation
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-15 5:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 11:12 [PATCHv4 0/2] soc: qcom: llcc: Support chipsets that can write to llcc regs Sai Prakash Ranjan
2020-09-14 11:12 ` [PATCHv4 1/2] soc: qcom: llcc: Move attribute config to its own function Sai Prakash Ranjan
2020-09-14 18:44 ` Stephen Boyd
2020-09-15 5:25 ` Sai Prakash Ranjan [this message]
2020-09-14 11:13 ` [PATCHv4 2/2] soc: qcom: llcc: Support chipsets that can write to llcc regs Sai Prakash Ranjan
2020-09-14 18:46 ` Stephen Boyd
2020-09-15 5:22 ` Sai Prakash Ranjan
2020-09-15 16:01 ` Stephen Boyd
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=edf5677e4363b42184a47a7483ce8ec6@codeaurora.org \
--to=saiprakash.ranjan@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swboyd@chromium.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).