From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Unnathi Chalicheemala <quic_uchalich@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@quicinc.com
Subject: Re: [PATCH v3 2/5] soc: qcom: llcc: Add regmap for Broadcast_AND region
Date: Tue, 12 Mar 2024 02:05:05 +0100 [thread overview]
Message-ID: <61232fd6-2b76-4ab0-af64-2d49ae405610@linaro.org> (raw)
In-Reply-To: <c3456b3d182f5139339400e49b228fa4840ae0e2.1708551850.git.quic_uchalich@quicinc.com>
On 2/23/24 00:07, Unnathi Chalicheemala wrote:
> Define new regmap structure for Broadcast_AND region and initialize
> this regmap when HW block version is greater than 4.1, otherwise
> initialize as a NULL pointer for backwards compatibility.
>
> Switch from broadcast_OR to broadcast_AND region (when defined in DT)
> for checking status bit 1 as Broadcast_OR region checks only for bit 0.
>
> Signed-off-by: Unnathi Chalicheemala <quic_uchalich@quicinc.com>
> ---
> drivers/soc/qcom/llcc-qcom.c | 15 ++++++++++++++-
> include/linux/soc/qcom/llcc-qcom.h | 4 +++-
> 2 files changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/soc/qcom/llcc-qcom.c b/drivers/soc/qcom/llcc-qcom.c
> index 4ca88eaebf06..cfdc7d9d7773 100644
> --- a/drivers/soc/qcom/llcc-qcom.c
> +++ b/drivers/soc/qcom/llcc-qcom.c
> @@ -826,6 +826,7 @@ static int llcc_update_act_ctrl(u32 sid,
> u32 status_reg;
> u32 slice_status;
> int ret;
> + struct regmap *regmap;
Reverse-Christmas-tree, please
>
> if (IS_ERR(drv_data))
> return PTR_ERR(drv_data);
> @@ -849,7 +850,9 @@ static int llcc_update_act_ctrl(u32 sid,
> return ret;
>
> if (drv_data->version >= LLCC_VERSION_4_1_0_0) {
> - ret = regmap_read_poll_timeout(drv_data->bcast_regmap, status_reg,
> + regmap = (!drv_data->bcast_and_regmap) ? drv_data->bcast_regmap
> + : drv_data->bcast_and_regmap;
<raised eyebrow emoji>
regmap = drv_data->bcast_and_regmap ?: drv_data->bcast_regmap
Konrad
next prev parent reply other threads:[~2024-03-12 1:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 23:07 [PATCH v3 0/5] LLCC: Support for Broadcast_AND region Unnathi Chalicheemala
2024-02-22 23:07 ` [PATCH v3 1/5] dt-bindings: arm: msm: Add llcc Broadcast_AND register Unnathi Chalicheemala
2024-02-27 15:47 ` Krzysztof Kozlowski
2024-02-28 1:04 ` Unnathi Chalicheemala
2024-02-28 7:14 ` Krzysztof Kozlowski
2024-02-28 17:54 ` Unnathi Chalicheemala
2024-02-22 23:07 ` [PATCH v3 2/5] soc: qcom: llcc: Add regmap for Broadcast_AND region Unnathi Chalicheemala
2024-03-12 1:05 ` Konrad Dybcio [this message]
2024-02-22 23:07 ` [PATCH v3 3/5] arm64: dts: qcom: sm8450: Add mapping to llcc " Unnathi Chalicheemala
2024-02-27 15:48 ` Krzysztof Kozlowski
2024-02-22 23:07 ` [PATCH v3 4/5] arm64: dts: qcom: sm8550: " Unnathi Chalicheemala
2024-02-27 15:49 ` Krzysztof Kozlowski
2024-02-28 1:17 ` Unnathi Chalicheemala
2024-03-02 0:09 ` 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=61232fd6-2b76-4ab0-af64-2d49ae405610@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_uchalich@quicinc.com \
--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).