From: Jishnu Prakash <quic_jprakash@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
<agross@kernel.org>, <bjorn.andersson@linaro.org>,
<devicetree@vger.kernel.org>, <mka@chromium.org>,
<robh+dt@kernel.org>, <knaack.h@gmx.de>, <lars@metafoo.de>,
<pmeerw@pmeerw.net>, <manivannan.sadhasivam@linaro.org>,
<linus.walleij@linaro.org>, <quic_kgunda@quicinc.com>,
<quic_aghayal@quicinc.com>, <daniel.lezcano@linaro.org>,
<rui.zhang@intel.com>, <quic_subbaram@quicinc.com>,
<jic23@kernel.org>, <amitk@kernel.org>,
Thara Gopinath <thara.gopinath@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
<linux-pm@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <linux-arm-msm-owner@vger.kernel.org>, <linux-iio@vger.kernel.org>
Subject: Re: [PATCH V3 3/4] thermal: qcom: Add support for multiple generations of devices
Date: Sun, 23 Jan 2022 20:20:02 +0530 [thread overview]
Message-ID: <7e659952-98b0-bfcd-1087-cdd0538d2250@quicinc.com> (raw)
In-Reply-To: <47228209-552e-b148-c93a-4fbb5a36583e@linaro.org>
Hi Dmitry,
On 11/29/2021 7:55 AM, Dmitry Baryshkov wrote:
> On 23/11/2021 08:57, Jishnu Prakash wrote:
>> Refactor code to support multiple generations of ADC_TM devices
>> by defining gen number, irq name and disable, configure and isr
>> APIs in the individual data structs.
>>
>> Signed-off-by: Jishnu Prakash <quic_jprakash@quicinc.com>
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>
> Minor question below.
>
>> ---
>> drivers/thermal/qcom/qcom-spmi-adc-tm5.c | 76
>> ++++++++++++++++++++------------
>> 1 file changed, 48 insertions(+), 28 deletions(-)
>>
>> diff --git a/drivers/thermal/qcom/qcom-spmi-adc-tm5.c
>> b/drivers/thermal/qcom/qcom-spmi-adc-tm5.c
>> index 824671c..fc8cd45 100644
>> --- a/drivers/thermal/qcom/qcom-spmi-adc-tm5.c
>> +++ b/drivers/thermal/qcom/qcom-spmi-adc-tm5.c
>> @@ -78,11 +78,10 @@ enum adc5_timer_select {
>> ADC5_TIMER_SEL_NONE,
>> };
>> -struct adc_tm5_data {
>> - const u32 full_scale_code_volt;
>> - unsigned int *decimation;
>> - unsigned int *hw_settle;
>> - bool is_hc;
>> +enum adc5_gen {
>> + ADC_TM5,
>> + ADC_TM_HC,
>> + ADC_TM5_MAX
>> };
>> enum adc_tm5_cal_method {
>> @@ -92,6 +91,18 @@ enum adc_tm5_cal_method {
>> };
>> struct adc_tm5_chip;
>> +struct adc_tm5_channel;
>> +
>> +struct adc_tm5_data {
>> + const u32 full_scale_code_volt;
>> + unsigned int *decimation;
>> + unsigned int *hw_settle;
>> + int (*disable_channel)(struct adc_tm5_channel *channel);
>> + int (*configure)(struct adc_tm5_channel *channel, int low, int
>> high);
>> + irqreturn_t (*isr)(int irq, void *data);
>> + char *irq_name;
>> + int gen;
>> +};
>
> Any reason for moving the adc_tm5_data definition? It is still prefix
> with the adc_tmp5_channel declaration.
There's no strong reason, I just thought it would look better to keep
all the major struct definitions together after the enum definitions.
>
>> /**
>> * struct adc_tm5_channel - ADC Thermal Monitoring channel data.
>> @@ -139,22 +150,6 @@ struct adc_tm5_chip {
>> u16 base;
>> };
>> -static const struct adc_tm5_data adc_tm5_data_pmic = {
>> - .full_scale_code_volt = 0x70e4,
>> - .decimation = (unsigned int []) { 250, 420, 840 },
>> - .hw_settle = (unsigned int []) { 15, 100, 200, 300, 400, 500,
>> 600, 700,
>> - 1000, 2000, 4000, 8000, 16000, 32000,
>> - 64000, 128000 },
>> -};
>> -
>> -static const struct adc_tm5_data adc_tm_hc_data_pmic = {
>> - .full_scale_code_volt = 0x70e4,
>> - .decimation = (unsigned int []) { 256, 512, 1024 },
>> - .hw_settle = (unsigned int []) { 0, 100, 200, 300, 400, 500,
>> 600, 700,
>> - 1000, 2000, 4000, 6000, 8000, 10000 },
>> - .is_hc = true,
>> -};
>> -
Thanks,
Jishnu
next prev parent reply other threads:[~2022-01-23 14:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 5:57 [PATCH V3 0/4] thermal: qcom: Add support for PMIC5 Gen2 ADC_TM Jishnu Prakash
2021-11-23 5:57 ` [PATCH V3 1/4] dt-bindings: thermal: qcom: add PMIC5 Gen2 ADC_TM bindings Jishnu Prakash
2021-11-26 18:31 ` Jonathan Cameron
2021-11-29 0:45 ` Rob Herring
2021-11-23 5:57 ` [PATCH V3 2/4] iio: adc: qcom-vadc-common: add reverse scaling for PMIC5 Gen2 ADC_TM Jishnu Prakash
2021-11-23 5:57 ` [PATCH V3 3/4] thermal: qcom: Add support for multiple generations of devices Jishnu Prakash
2021-11-26 18:34 ` Jonathan Cameron
2021-11-29 2:25 ` Dmitry Baryshkov
2022-01-23 14:50 ` Jishnu Prakash [this message]
2021-11-23 5:57 ` [PATCH V3 4/4] thermal: qcom: add support for PMIC5 Gen2 ADCTM Jishnu Prakash
2021-11-26 18:46 ` Jonathan Cameron
2022-01-23 14:46 ` Jishnu Prakash
2021-11-29 2:32 ` Dmitry Baryshkov
2022-01-23 14:56 ` Jishnu Prakash
2021-11-26 18:29 ` [PATCH V3 0/4] thermal: qcom: Add support for PMIC5 Gen2 ADC_TM Jonathan Cameron
2022-01-23 14:43 ` Jishnu Prakash
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=7e659952-98b0-bfcd-1087-cdd0538d2250@quicinc.com \
--to=quic_jprakash@quicinc.com \
--cc=agross@kernel.org \
--cc=amitk@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm-owner@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mka@chromium.org \
--cc=pmeerw@pmeerw.net \
--cc=quic_aghayal@quicinc.com \
--cc=quic_kgunda@quicinc.com \
--cc=quic_subbaram@quicinc.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=thara.gopinath@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