devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Jagath Jog J <jagathjog1996@gmail.com>
Cc: lars@metafoo.de, andy.shevchenko@gmail.com, sst@poczta.fm,
	robh+dt@kernel.org, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/7] iio: potentiometer: Add support for DS3502
Date: Sun, 20 Feb 2022 14:33:48 +0000	[thread overview]
Message-ID: <20220220143348.44f71d62@jic23-huawei> (raw)
In-Reply-To: <20220220024632.4183-1-jagathjog1996@gmail.com>

On Sun, 20 Feb 2022 08:16:25 +0530
Jagath Jog J <jagathjog1996@gmail.com> wrote:

> Add dt-bindings and support for Maxim DS3502 into existing ds1803 driver.
> DS3502 is a 7 bit Nonvolatile Digital Potentiometer.

Looks good to me.  Will leave it on list a few more days though
to allow others to comment if they wish.

Nice work,

Thanks,

Jonathan

> 
> Changes since v3:
> 1. Dropped the chip type switch statement in read_raw function.
> 2. Added device specific read function pointer in their structure.
> 3. Added two separate functions to read values from two different types
>    of devices.
> 
> Changes since v2:
> 1. Addressed Andy Shevchenko comments.
> 2. Adding device name in Kconfig file.
> 3. Spliting up of patch into 3 patches.
> 4. Adding channel info into ds1803_cfg in separate patch.
> 5. Dropping the use of enum in firmware data instead using previous
>    pointer method for accessing device specific data.
> 6. Separate patch for using firmware provided data instead of 
>    id->driver_data.
> 7. Adding DS3502 support in separate patch.
> 
> Changes since v1:
> 1. Fixes the alignment to match the open parenthesis in separate patch.
> 2. Adding available functionality for ds1803 driver in separate patch.
> 3. Moving maxim_potentiometer members into ds1803_cfg structure.
> 4. Droping of the INFO_ENABLE channel type.
> 5. Firmware entry with data is used instead of id->driver_data to
>    to retrieve the chip specific data.
> 
> Jagath Jog J (7):
>   iio: potentiometer: Alignment to match the open parenthesis
>   iio: potentiometer: Add available functionality
>   iio: potentiometer: Add channel information in device data
>   iio: potentiometer: Change to firmware provided data
>   iio: potentiometer: Add device specific read_raw function
>   iio: potentiometer: Add support for Maxim DS3502
>   dt-bindings: iio: potentiometer: Add Maxim DS3502 in trivial-devices
> 
>  .../devicetree/bindings/trivial-devices.yaml  |   2 +
>  drivers/iio/potentiometer/Kconfig             |   6 +-
>  drivers/iio/potentiometer/ds1803.c            | 153 +++++++++++++-----
>  3 files changed, 121 insertions(+), 40 deletions(-)
> 


      parent reply	other threads:[~2022-02-20 14:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-20  2:46 [PATCH v4 0/7] iio: potentiometer: Add support for DS3502 Jagath Jog J
2022-02-20  2:46 ` [PATCH v4 1/7] iio: potentiometer: Alignment to match the open parenthesis Jagath Jog J
2022-02-20  2:46 ` [PATCH v4 2/7] iio: potentiometer: Add available functionality Jagath Jog J
2022-02-20  2:46 ` [PATCH v4 3/7] iio: potentiometer: Add channel information in device data Jagath Jog J
2022-02-20  2:46 ` [PATCH v4 4/7] iio: potentiometer: Change to firmware provided data Jagath Jog J
2022-02-20  2:46 ` [PATCH v4 5/7] iio: potentiometer: Add device specific read_raw function Jagath Jog J
2022-02-20  2:46 ` [PATCH v4 6/7] iio: potentiometer: Add support for Maxim DS3502 Jagath Jog J
2022-02-20  2:46 ` [PATCH v4 7/7] dt-bindings: iio: potentiometer: Add Maxim DS3502 in trivial-devices Jagath Jog J
2022-02-20 14:33 ` Jonathan Cameron [this message]

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=20220220143348.44f71d62@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jagathjog1996@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sst@poczta.fm \
    /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).