public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Dikshita Agarwal <quic_dikshita@quicinc.com>,
	Vikash Garodia <quic_vgarodia@quicinc.com>,
	Manivannan Sadhasivam <mani@kernel.org>
Subject: Re: [PATCH 02/18] clk: qcom: reset: Commonize the de/assert functions
Date: Tue, 9 Jan 2024 00:29:52 +0000	[thread overview]
Message-ID: <dcd80eba-e00e-4e29-b46f-9c972bf018f3@linaro.org> (raw)
In-Reply-To: <20240105-topic-venus_reset-v1-2-981c7a624855@linaro.org>

On 08/01/2024 12:32, Konrad Dybcio wrote:
> -static int
> -qcom_reset_assert(struct reset_controller_dev *rcdev, unsigned long id)
> +static int qcom_reset_set_assert(struct reset_controller_dev *rcdev, unsigned long id,
> +			     bool assert)

Personally I'd not elongate the function declaration.

>   {
>   	struct qcom_reset_controller *rst;
>   	const struct qcom_reset_map *map;
> @@ -33,21 +33,17 @@ qcom_reset_assert(struct reset_controller_dev *rcdev, unsigned long id)
>   	map = &rst->reset_map[id];
>   	mask = map->bitmask ? map->bitmask : BIT(map->bit);
>   
> -	return regmap_update_bits(rst->regmap, map->reg, mask, mask);
> +	return regmap_update_bits(rst->regmap, map->reg, mask, assert ? mask : 0);

and I'd probably do

u32 bits = 0;

if (assert)
     bits = mask;

regmap_update_bits(rst->regmap, map->reg, mask, bits);

because I prefer for aesthetic reasons not to do ternary inputs like that.

However its up to you to change or not.

Reviewed-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>

---
bod

  reply	other threads:[~2024-01-09  0:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 12:32 [PATCH 00/18] Qualcomm GCC/VIDEOCC reset overhaul for Venus Konrad Dybcio
2024-01-08 12:32 ` [PATCH 01/18] clk: qcom: reset: Increase max reset delay Konrad Dybcio
2024-01-08 12:32 ` [PATCH 02/18] clk: qcom: reset: Commonize the de/assert functions Konrad Dybcio
2024-01-09  0:29   ` Bryan O'Donoghue [this message]
2024-01-08 12:32 ` [PATCH 03/18] clk: qcom: reset: Ensure write completion on reset de/assertion Konrad Dybcio
2024-01-08 12:32 ` [PATCH 04/18] clk: qcom: gcc-sa8775p: Set delay for Venus CLK resets Konrad Dybcio
2024-01-08 12:32 ` [PATCH 05/18] clk: qcom: gcc-sc8180x: " Konrad Dybcio
2024-01-08 12:32 ` [PATCH 06/18] clk: qcom: gcc-sc8280xp: " Konrad Dybcio
2024-01-08 12:32 ` [PATCH 07/18] clk: qcom: gcc-sm4450: " Konrad Dybcio
2024-01-08 12:32 ` [PATCH 08/18] clk: qcom: gcc-sm7150: " Konrad Dybcio
2024-01-08 12:32 ` [PATCH 09/18] clk: qcom: gcc-sm8250: " Konrad Dybcio
2024-01-09  0:34   ` Bryan O'Donoghue
2024-01-09  9:33     ` Konrad Dybcio
2024-01-27 23:05       ` Bjorn Andersson
2024-01-08 12:32 ` [PATCH 10/18] clk: qcom: gcc-sm8350: " Konrad Dybcio
2024-01-08 12:32 ` [PATCH 11/18] clk: qcom: gcc-sm8450: " Konrad Dybcio
2024-01-08 12:32 ` [PATCH 12/18] clk: qcom: gcc-sm8550: " Konrad Dybcio
2024-01-08 12:32 ` [PATCH 13/18] clk: qcom: gcc-sm8650: " Konrad Dybcio
2024-01-08 12:32 ` [PATCH 14/18] clk: qcom: videocc-sm8150: " Konrad Dybcio
2024-01-08 12:32 ` [PATCH 15/18] clk: qcom: videocc-sm8250: " Konrad Dybcio
2024-01-08 12:32 ` [PATCH 16/18] clk: qcom: videocc-sm8350: " Konrad Dybcio
2024-01-08 12:32 ` [PATCH 17/18] clk: qcom: videocc-sm8450: " Konrad Dybcio
2024-01-08 12:32 ` [PATCH 18/18] clk: qcom: videocc-sm8550: " Konrad Dybcio
2024-01-08 23:45 ` [PATCH 00/18] Qualcomm GCC/VIDEOCC reset overhaul for Venus Bryan O'Donoghue

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=dcd80eba-e00e-4e29-b46f-9c972bf018f3@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=andersson@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=mturquette@baylibre.com \
    --cc=p.zabel@pengutronix.de \
    --cc=quic_dikshita@quicinc.com \
    --cc=quic_vgarodia@quicinc.com \
    --cc=sboyd@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