devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Mukesh Ojha <quic_mojha@quicinc.com>,
	Komal Bajaj <quic_kbajaj@quicinc.com>,
	agross@kernel.org, andersson@kernel.org,
	konrad.dybcio@linaro.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	srinivas.kandagatla@linaro.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/6] soc: qcom: llcc: Refactor llcc driver to support multiple configuration
Date: Mon, 24 Jul 2023 15:26:49 +0200	[thread overview]
Message-ID: <aa2978d7-b0bb-e05c-6da1-3930e291643a@linaro.org> (raw)
In-Reply-To: <39b4bafd-410f-cae8-13ae-e18d751b51a2@quicinc.com>

On 24/07/2023 14:28, Mukesh Ojha wrote:
> On 7/24/2023 2:11 PM, Komal Bajaj wrote:
>> Refactor driver to support multiple configuration for llcc on a target.
>>
>> Signed-off-by: Komal Bajaj <quic_kbajaj@quicinc.com>
>> ---
>>   drivers/soc/qcom/llcc-qcom.c | 264 +++++++++++++++++++++++------------
>>   1 file changed, 178 insertions(+), 86 deletions(-)
>>
>> diff --git a/drivers/soc/qcom/llcc-qcom.c b/drivers/soc/qcom/llcc-qcom.c
>> index 67c19ed2219a..321f8d2079f7 100644
>> --- a/drivers/soc/qcom/llcc-qcom.c
>> +++ b/drivers/soc/qcom/llcc-qcom.c
>> @@ -127,6 +127,12 @@ struct qcom_llcc_config {
>>   	bool no_edac;
>>   };
>>   
>> +struct qcom_sct_config
> 
> const ?

What (and how) should be const above?

Best regards,
Krzysztof


  reply	other threads:[~2023-07-24 13:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24  8:41 [PATCH v5 0/6] soc: qcom: llcc: Add support for QDU1000/QRU1000 Komal Bajaj
2023-07-24  8:41 ` [PATCH v5 1/6] dt-bindings: cache: qcom,llcc: Add LLCC compatible " Komal Bajaj
2023-07-24  9:51   ` Krzysztof Kozlowski
2023-07-24  8:41 ` [PATCH v5 2/6] soc: qcom: llcc: Refactor llcc driver to support multiple configuration Komal Bajaj
2023-07-24 12:28   ` Mukesh Ojha
2023-07-24 13:26     ` Krzysztof Kozlowski [this message]
2023-07-24 16:14       ` Mukesh Ojha
2023-07-24 16:11     ` Mukesh Ojha
2023-08-02  8:53       ` Komal Bajaj
2023-07-24  8:41 ` [PATCH v5 3/6] nvmem: core: Add stub for nvmem_cell_read_u8 Komal Bajaj
2023-07-24 12:36   ` Mukesh Ojha
2023-08-02  8:53     ` Komal Bajaj
2023-07-24  8:41 ` [PATCH v5 4/6] soc: qcom: Add LLCC support for multi channel DDR Komal Bajaj
2023-07-24 12:40   ` Mukesh Ojha
2023-08-02  8:54     ` Komal Bajaj
2023-07-24  8:41 ` [PATCH v5 5/6] soc: qcom: llcc: Updating the macro name Komal Bajaj
2023-07-24 12:41   ` Mukesh Ojha
2023-07-24 12:48   ` Konrad Dybcio
2023-08-02  8:55     ` Komal Bajaj
2023-07-24  8:41 ` [PATCH v5 6/6] soc: qcom: llcc: Add QDU1000 and QRU1000 LLCC support Komal Bajaj
2023-07-24 12:45   ` Mukesh Ojha
2023-07-24 12:55     ` Konrad Dybcio
2023-08-02  9:00       ` Komal Bajaj
2023-08-02  8:57     ` Komal Bajaj
2023-07-24 12:54   ` 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=aa2978d7-b0bb-e05c-6da1-3930e291643a@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_kbajaj@quicinc.com \
    --cc=quic_mojha@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@linaro.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).