public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Manaf Meethalavalappu Pallikunhi
	<manaf.pallikunhi@oss.qualcomm.com>,
	Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	amit.kucheria@oss.qualcomm.com,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Gaurav Kohli <gaurav.kohli@oss.qualcomm.com>
Cc: linux-hwmon@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] hwmon: Add Qualcomm PMIC BCL hardware monitor driver
Date: Fri, 6 Feb 2026 10:38:42 +0100	[thread overview]
Message-ID: <57a1a5fc-5ae0-40b7-97fa-1612b8da997e@kernel.org> (raw)
In-Reply-To: <7911bbae-c507-4420-a05c-89242941f774@oss.qualcomm.com>

On 06/02/2026 10:27, Konrad Dybcio wrote:
> On 2/5/26 10:14 PM, Manaf Meethalavalappu Pallikunhi wrote:
> 
>> +static unsigned int bcl_get_version_major(const struct bcl_device *bcl)
>> +{
>> +	u32 raw_val = 0;
>> +
>> +	bcl_read_field_value(bcl, F_V_MAJOR, &raw_val);
>> +
>> +	return raw_val;
>> +}
>> +
>> +static unsigned int bcl_get_version_minor(const struct bcl_device *bcl)
>> +{
>> +	u32 raw_val = 0;
>> +
>> +	bcl_read_field_value(bcl, F_V_MINOR, &raw_val);
>> +
>> +	return raw_val;
>> +}
> 
> Do we really need so many read-1-value functions?

Yes, because we need multiple layers of indirections and multiple
abstract layers, so the code will be difficult to understand. This gives
us job security. Also, more lines of code justifies our spent time.
That's why this should also include kerneldoc of at least 10 lines.

Best regards,
Krzysztof

  reply	other threads:[~2026-02-06  9:38 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 21:14 [PATCH 0/4] hwmon: Add Qualcomm PMIC BCL hardware monitor driver Manaf Meethalavalappu Pallikunhi
2026-02-05 21:14 ` [PATCH 1/4] dt-bindings: hwmon: Add qcom,bcl-hwmon yaml bindings Manaf Meethalavalappu Pallikunhi
2026-02-06  8:09   ` Krzysztof Kozlowski
2026-02-12 20:24     ` Manaf Meethalavalappu Pallikunhi
2026-02-06  9:08   ` Dmitry Baryshkov
2026-02-12 20:41     ` Manaf Meethalavalappu Pallikunhi
2026-02-06  9:08   ` Konrad Dybcio
2026-02-13  6:04     ` Manaf Meethalavalappu Pallikunhi
2026-02-13 10:41       ` Konrad Dybcio
2026-02-13 12:00         ` Manaf Meethalavalappu Pallikunhi
2026-02-05 21:14 ` [PATCH 2/4] hwmon: Add Qualcomm PMIC BCL hardware monitor driver Manaf Meethalavalappu Pallikunhi
2026-02-06  8:12   ` Krzysztof Kozlowski
2026-02-13  6:21     ` Manaf Meethalavalappu Pallikunhi
2026-02-06  9:27   ` Konrad Dybcio
2026-02-06  9:38     ` Krzysztof Kozlowski [this message]
2026-02-13  9:42     ` Manaf Meethalavalappu Pallikunhi
2026-02-13 10:55       ` Konrad Dybcio
2026-02-06 13:24   ` Bjorn Andersson
2026-02-13 11:38     ` Manaf Meethalavalappu Pallikunhi
2026-02-08  1:27   ` kernel test robot
2026-03-20 14:52   ` Daniel Lezcano
2026-03-20 15:22     ` Guenter Roeck
2026-03-20 16:08       ` Daniel Lezcano
2026-03-20 16:59         ` Guenter Roeck
2026-03-20 17:23           ` Daniel Lezcano
2026-02-05 21:14 ` [PATCH 3/4] arm64: dts: qcom: pm7250b: Enable Qualcomm BCL device Manaf Meethalavalappu Pallikunhi
2026-02-06  8:13   ` Krzysztof Kozlowski
2026-02-13 11:44     ` Manaf Meethalavalappu Pallikunhi
2026-02-06  9:11   ` Konrad Dybcio
2026-02-13 11:55     ` Manaf Meethalavalappu Pallikunhi
2026-02-16 11:48       ` Konrad Dybcio
2026-02-19 11:34         ` Manaf Meethalavalappu Pallikunhi
2026-02-19 13:04           ` Konrad Dybcio
2026-02-24 18:35             ` Manaf Meethalavalappu Pallikunhi
2026-02-25 11:47               ` Konrad Dybcio
2026-02-06  9:11   ` Konrad Dybcio
2026-02-13 11:56     ` Manaf Meethalavalappu Pallikunhi
2026-02-05 21:14 ` [PATCH 4/4] arm64: dts: qcom: pm8350c: " Manaf Meethalavalappu Pallikunhi

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=57a1a5fc-5ae0-40b7-97fa-1612b8da997e@kernel.org \
    --to=krzk@kernel.org \
    --cc=amit.kucheria@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gaurav.kohli@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=manaf.pallikunhi@oss.qualcomm.com \
    --cc=robh@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