From: Jonathan Cameron <jic23@kernel.org>
To: Robert Marko <robimarko@gmail.com>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
konrad.dybcio@somainline.org, lee@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, lars@metafoo.de,
sboyd@kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v8 3/5] iio: adc: qcom-spmi-adc5: add ADC5_VREF_VADC to rev2 ADC5
Date: Fri, 19 Aug 2022 18:30:52 +0100 [thread overview]
Message-ID: <20220819183052.49cf14e9@jic23-huawei> (raw)
In-Reply-To: <20220818221815.346233-3-robimarko@gmail.com>
On Fri, 19 Aug 2022 00:18:13 +0200
Robert Marko <robimarko@gmail.com> wrote:
> Add support for ADC5_VREF_VADC channel to rev2 ADC5 channel list.
> This channel measures the VADC reference LDO output.
>
> Signed-off-by: Robert Marko <robimarko@gmail.com>
> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
I've changed my mind on this, mostly because we've reached a new
cycle and I'd rather not see a v9 series + Lee is (I think)
keen to only take stuff through MFD if there is a build time
dependency.
Applied this patch directly to the togreg branch of iio.git
and pushed that out as testing for 0-day to play with it.
> ---
> drivers/iio/adc/qcom-spmi-adc5.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/iio/adc/qcom-spmi-adc5.c b/drivers/iio/adc/qcom-spmi-adc5.c
> index e96da2ef1964..821fee60a765 100644
> --- a/drivers/iio/adc/qcom-spmi-adc5.c
> +++ b/drivers/iio/adc/qcom-spmi-adc5.c
> @@ -597,6 +597,8 @@ static const struct adc5_channels adc5_chans_rev2[ADC5_MAX_CHANNEL] = {
> SCALE_HW_CALIB_DEFAULT)
> [ADC5_1P25VREF] = ADC5_CHAN_VOLT("vref_1p25", 0,
> SCALE_HW_CALIB_DEFAULT)
> + [ADC5_VREF_VADC] = ADC5_CHAN_VOLT("vref_vadc", 0,
> + SCALE_HW_CALIB_DEFAULT)
> [ADC5_VPH_PWR] = ADC5_CHAN_VOLT("vph_pwr", 1,
> SCALE_HW_CALIB_DEFAULT)
> [ADC5_VBAT_SNS] = ADC5_CHAN_VOLT("vbat_sns", 1,
next prev parent reply other threads:[~2022-08-19 17:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 22:18 [PATCH v8 1/5] dt-bindings: mfd: qcom-spmi-pmic: add support for PMP8074 Robert Marko
2022-08-18 22:18 ` [PATCH v8 2/5] " Robert Marko
2022-09-08 8:16 ` Lee Jones
2022-08-18 22:18 ` [PATCH v8 3/5] iio: adc: qcom-spmi-adc5: add ADC5_VREF_VADC to rev2 ADC5 Robert Marko
2022-08-19 17:30 ` Jonathan Cameron [this message]
2022-08-20 10:06 ` Robert Marko
2022-08-18 22:18 ` [PATCH v8 4/5] arm64: dts: qcom: add PMP8074 DTSI Robert Marko
2022-08-18 22:18 ` [PATCH v8 5/5] arm64: dts: qcom: ipq8074-hk01: add VQMMC supply Robert Marko
2022-08-19 6:40 ` [PATCH v8 1/5] dt-bindings: mfd: qcom-spmi-pmic: add support for PMP8074 Krzysztof Kozlowski
2022-09-08 8:15 ` Lee Jones
2022-10-18 3:14 ` (subset) " Bjorn Andersson
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=20220819183052.49cf14e9@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robimarko@gmail.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;
as well as URLs for NNTP newsgroup(s).