From: Jishnu Prakash <quic_jprakash@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <jic23@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<agross@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>, <daniel.lezcano@linaro.org>,
<linus.walleij@linaro.org>, <linux-arm-msm@vger.kernel.org>,
<andriy.shevchenko@linux.intel.com>, <quic_subbaram@quicinc.com>,
<quic_collinsd@quicinc.com>, <quic_amelende@quicinc.com>,
<quic_kamalw@quicinc.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <marijn.suijten@somainline.org>,
<lars@metafoo.de>, <luca@z3ntu.xyz>, <linux-iio@vger.kernel.org>,
<lee@kernel.org>, <rafael@kernel.org>, <rui.zhang@intel.com>,
<lukasz.luba@arm.com>, <cros-qcom-dts-watchers@chromium.org>,
<sboyd@kernel.org>, <linux-pm@vger.kernel.org>,
<linux-arm-msm-owner@vger.kernel.org>, <kernel@quicinc.com>
Subject: Re: [PATCH V2 0/3] iio: adc: Add support for QCOM SPMI PMIC5 Gen3 ADC
Date: Thu, 16 Nov 2023 11:59:58 +0530 [thread overview]
Message-ID: <5a476b51-5916-74f8-0395-60d94f210aa0@quicinc.com> (raw)
In-Reply-To: <CAA8EJprJuiFq5UXc9weNr1hy2vW_10TaQweN_ZW5XW=3LKrgtA@mail.gmail.com>
Hi Dmitry,
On 11/16/2023 10:52 AM, Dmitry Baryshkov wrote:
> On Thu, 16 Nov 2023 at 05:26, Jishnu Prakash <quic_jprakash@quicinc.com> wrote:
>> PMIC5 Gen3 has a similar ADC architecture to that on PMIC5 Gen2,
>> with all SW communication to ADC going through PMK8550 which
>> communicates with other PMICs through PBS. The major difference is
>> that the register interface used here is that of an SDAM present on
>> PMK8550, rather than a dedicated ADC peripheral. There may be more than one
>> SDAM used for ADC5 Gen3. Each ADC SDAM has eight channels, each of which may
>> be used for either immediate reads (same functionality as previous PMIC5 and
>> PMIC5 Gen2 ADC peripherals) or recurring measurements (same as PMIC5 and PMIC5
>> Gen2 ADC_TM functionality). In this case, we have VADC and ADC_TM functionality
>> combined into the same driver.
>>
>> Patches 1 adds bindings for ADC5 Gen3 peripheral.
>>
>> Patches 2 adds driver support for ADC5 Gen3.
> For some reason I don't see this patch in my inbox. Maybe it will
> arrive later. Immediate response: please add
> devm_thermal_add_hwmon_sysfs().
Yes, I'll check and add this in the next patch series, I'll wait for
some more comments on the existing patches for now.
I ran into some error after sending the first two mails (cover letter
and patch 1), so I sent patches 2 and 3 separately after it, I think you
may have received them separately.
>
>> Patch 3 is a cleanup, to move the QCOM ADC dt-bindings files from
>> dt-bindings/iio to dt-bindings/iio/adc folder, as they are
>> specifically for ADC devices. It also fixes all compilation errors
>> with this change in driver and devicetree files and similar errors
>> in documentation for dtbinding check.
> NAK. The kernel is expected to build and work after each commit.
> Otherwise git-bisecting the kernel becomes impossible.
> So, please rework your series in a way that there are no compilation
> errors after any of the patches. The easiest way would be to rearrange
> your patches in 3-1-2 order.
I think you may have misunderstood the meaning here, I had verified
compilation works each time after applying each of the three patches in
this series. It's not that this last patch fixes compilation errors
caused by the first two, this is a completely separate patch which
affects existing QCOM ADC code (driver and devicetree) including ADC5 Gen3.
This patch does two things mainly:
Move the ADC binding files from dt-bindings/iio folder to
dt-bindings/iio/adc folder (this would naturally cause some errors in
driver and devicetree code due to path update)
Fix all compilation and dtbinding errors generated by the move
I added this change at the end of the series as I was not completely
sure if it could get picked, just wanted to make it easier to drop if
that is the final decision.
Thanks,
Jishnu
>
>
>> Changes since v1:
>> - Dropped patches 1-5 for changing 'ADC7' peripheral name to 'ADC5 Gen2'.
>> - Addressed reviewer comments for binding and driver patches for ADC5 Gen3.
>> - Combined patches 8-11 into a single patch as requested by reviewers to make
>> the change clearer and made all fixes required in same patch.
>>
>> .../iio/{ => adc}/qcom,spmi-adc7-pm8350b.h | 2 +-
>> .../iio/{ => adc}/qcom,spmi-adc7-pmk8350.h | 2 +-
>> .../iio/{ => adc}/qcom,spmi-adc7-pmr735a.h | 2 +-
>> .../iio/{ => adc}/qcom,spmi-adc7-pmr735b.h | 0
>> .../iio/{ => adc}/qcom,spmi-vadc.h | 81 ++
>> 46 files changed, 1725 insertions(+), 61 deletions(-)
>> create mode 100644 drivers/iio/adc/qcom-spmi-adc5-gen3.c
>> create mode 100644 include/dt-bindings/iio/adc/qcom,spmi-adc5-gen3-pm8550.h
>> create mode 100644 include/dt-bindings/iio/adc/qcom,spmi-adc5-gen3-pm8550b.h
>> create mode 100644 include/dt-bindings/iio/adc/qcom,spmi-adc5-gen3-pm8550vx.h
>> create mode 100644 include/dt-bindings/iio/adc/qcom,spmi-adc5-gen3-pmk8550.h
>> rename include/dt-bindings/iio/{ => adc}/qcom,spmi-adc7-pm8350.h (98%)
>> rename include/dt-bindings/iio/{ => adc}/qcom,spmi-adc7-pm8350b.h (99%)
>> rename include/dt-bindings/iio/{ => adc}/qcom,spmi-adc7-pmk8350.h (97%)
>> rename include/dt-bindings/iio/{ => adc}/qcom,spmi-adc7-pmr735a.h (95%)
>> rename include/dt-bindings/iio/{ => adc}/qcom,spmi-adc7-pmr735b.h (100%)
>> rename include/dt-bindings/iio/{ => adc}/qcom,spmi-vadc.h (77%)
>>
>> --
>> 2.25.1
>>
>
> --
> With best wishes
> Dmitry
next prev parent reply other threads:[~2023-11-16 6:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 3:25 [PATCH V2 0/3] iio: adc: Add support for QCOM SPMI PMIC5 Gen3 ADC Jishnu Prakash
2023-11-16 3:25 ` [PATCH V2 1/3] dt-bindings: iio: adc: Add QCOM PMIC5 Gen3 ADC bindings Jishnu Prakash
2023-11-16 11:43 ` Krzysztof Kozlowski
2023-12-21 8:00 ` Jishnu Prakash
2023-12-21 8:04 ` Krzysztof Kozlowski
2023-11-16 5:22 ` [PATCH V2 0/3] iio: adc: Add support for QCOM SPMI PMIC5 Gen3 ADC Dmitry Baryshkov
2023-11-16 6:29 ` Jishnu Prakash [this message]
2023-11-16 6:58 ` Dmitry Baryshkov
2023-11-25 19:35 ` Jonathan Cameron
2023-11-20 11:31 ` Andy Shevchenko
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=5a476b51-5916-74f8-0395-60d94f210aa0@quicinc.com \
--to=quic_jprakash@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=jic23@kernel.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=lee@kernel.org \
--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=luca@z3ntu.xyz \
--cc=lukasz.luba@arm.com \
--cc=marijn.suijten@somainline.org \
--cc=quic_amelende@quicinc.com \
--cc=quic_collinsd@quicinc.com \
--cc=quic_kamalw@quicinc.com \
--cc=quic_subbaram@quicinc.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.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).