All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: devajithvs <devajithvs@gmail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Rob Herring <robh+dt@kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Robert Yang <decatf@gmail.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: accel: kxcjk1013: Add rudimentary regulator support
Date: Sun, 13 Dec 2020 18:04:25 +0000	[thread overview]
Message-ID: <20201213180425.34eb8a3a@archlinux> (raw)
In-Reply-To: <20201213172437.2779-2-devajithvs@gmail.com>

On Sun, 13 Dec 2020 22:54:36 +0530
devajithvs <devajithvs@gmail.com> wrote:

> From: Devajith V S <devajithvs@gmail.com>
> 
> kxcjk1013 devices have VDD and VDDIO power lines. Need
> to make sure the regulators are enabled before any
> communication with kxcjk1013. This patch introduces
> vdd/vddio regulators for kxcjk1013.
> 
> Signed-off-by: Devajith V S <devajithvs@gmail.com>
Looks good to me. Trivial comment on the comment inline that I can fix
whilst applying.

I'll let this sit on the list for a little while though in case
anyone else spots something I have missed.

Thanks,

Jonathan

> ---
>  drivers/iio/accel/kxcjk-1013.c | 31 +++++++++++++++++++++++++++++++
>  1 file changed, 31 insertions(+)
> 
> diff --git a/drivers/iio/accel/kxcjk-1013.c b/drivers/iio/accel/kxcjk-1013.c
> index e92c7e676..67d3d8270 100644
> --- a/drivers/iio/accel/kxcjk-1013.c
> +++ b/drivers/iio/accel/kxcjk-1013.c
> @@ -14,6 +14,7 @@
>  #include <linux/acpi.h>
>  #include <linux/pm.h>
>  #include <linux/pm_runtime.h>
> +#include <linux/regulator/consumer.h>
>  #include <linux/iio/iio.h>
>  #include <linux/iio/sysfs.h>
>  #include <linux/iio/buffer.h>
> @@ -133,6 +134,7 @@ enum kx_acpi_type {
>  };
>  
>  struct kxcjk1013_data {
> +	struct regulator_bulk_data regulators[2];
>  	struct i2c_client *client;
>  	struct iio_trigger *dready_trig;
>  	struct iio_trigger *motion_trig;
> @@ -1300,6 +1302,13 @@ static const char *kxcjk1013_match_acpi_device(struct device *dev,
>  	return dev_name(dev);
>  }
>  
> +static void kxcjk1013_disable_regulators(void *d)
> +{
> +	struct kxcjk1013_data *data = d;
> +
> +	regulator_bulk_disable(ARRAY_SIZE(data->regulators), data->regulators);
> +}
> +
>  static int kxcjk1013_probe(struct i2c_client *client,
>  			   const struct i2c_device_id *id)
>  {
> @@ -1330,6 +1339,28 @@ static int kxcjk1013_probe(struct i2c_client *client,
>  			return ret;
>  	}
>  
> +	data->regulators[0].supply = "vdd";
> +	data->regulators[1].supply = "vddio";
> +	ret = devm_regulator_bulk_get(&client->dev, ARRAY_SIZE(data->regulators),
> +				      data->regulators);
> +	if (ret)
> +		return dev_err_probe(&client->dev, ret, "Failed to get regulators\n");
> +
> +	ret = regulator_bulk_enable(ARRAY_SIZE(data->regulators),
> +				    data->regulators);
> +	if (ret)
> +		return ret;
> +
> +	ret = devm_add_action_or_reset(&client->dev, kxcjk1013_disable_regulators, data);
> +	if (ret)
> +		return ret;
> +
> +	/*
> +	 * A typical delay of 10ms is required for powering up
> +	 * according to the data sheets of supported chips.

Probably want to add something like "so double it to play safe."

> +	 */
> +	msleep(20);
> +
>  	if (id) {
>  		data->chipset = (enum kx_chipset)(id->driver_data);
>  		name = id->name;


  reply	other threads:[~2020-12-13 18:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-13 17:24 [PATCH 1/2] dt-bindings: iio: accel: kxcjk1013: Document regulator supplies devajithvs
2020-12-13 17:24 ` [PATCH 2/2] iio: accel: kxcjk1013: Add rudimentary regulator support devajithvs
2020-12-13 18:04   ` Jonathan Cameron [this message]
2020-12-15 17:03 ` [PATCH 1/2] dt-bindings: iio: accel: kxcjk1013: Document regulator supplies Rob Herring

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=20201213180425.34eb8a3a@archlinux \
    --to=jic23@kernel.org \
    --cc=decatf@gmail.com \
    --cc=devajithvs@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.