linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Rokosov <DDRokosov@sberdevices.ru>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: "andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"jic23@kernel.org" <jic23@kernel.org>,
	kernel <kernel@sberdevices.ru>,
	"lars@metafoo.de" <lars@metafoo.de>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"stano.jakubek@gmail.com" <stano.jakubek@gmail.com>,
	"stephan@gerhold.net" <stephan@gerhold.net>
Subject: Re: [PATCH v4 2/3] iio: add MEMSensing MSA311 3-axis accelerometer driver
Date: Wed, 3 Aug 2022 18:39:49 +0000	[thread overview]
Message-ID: <20220803184001.fcappv7grdjyaetn@CAB-WSD-L081021.sigma.sbrf.ru> (raw)
In-Reply-To: <67041dbe-ad6c-c53f-9760-bd7b5988d137@wanadoo.fr>

Hello Christophe,

Thank you for quick review

On Wed, Aug 03, 2022 at 08:11:05PM +0200, Christophe JAILLET wrote:
> Le 03/08/2022 à 15:11, Dmitry Rokosov a écrit :
> > MSA311 is a tri-axial, low-g accelerometer with I2C digital output for
> > sensitivity consumer applications. It has dynamic user-selectable full
> > scales range of +-2g/+-4g/+-8g/+-16g and allows acceleration measurements
> > with output data rates from 1Hz to 1000Hz.
> > 
> > Spec: https://cdn-shop.adafruit.com/product-files/5309/MSA311-V1.1-ENG.pdf
> > 
> > This driver supports following MSA311 features:
> >      - IIO interface
> >      - Different power modes: NORMAL and SUSPEND (using pm_runtime)
> >      - ODR (Output Data Rate) selection
> >      - Scale and samp_freq selection
> >      - IIO triggered buffer, IIO reg access
> >      - NEW_DATA interrupt + trigger
> > 
> > Below features to be done:
> >      - Motion Events: ACTIVE, TAP, ORIENT, FREEFALL
> >      - Low Power mode
> > 
> > Signed-off-by: Dmitry Rokosov <ddrokosov-i4r8oA+eLlH99rHkP+FxIw@public.gmane.org>
> > ---
> >   MAINTAINERS                |    6 +
> >   drivers/iio/accel/Kconfig  |   13 +
> >   drivers/iio/accel/Makefile |    2 +
> >   drivers/iio/accel/msa311.c | 1323 ++++++++++++++++++++++++++++++++++++
> >   4 files changed, 1344 insertions(+)
> >   create mode 100644 drivers/iio/accel/msa311.c
> > 
> 
> Hi,
> a few nits below.
> 
> [...]
> 
> > +static int msa311_check_partid(struct msa311_priv *msa311)
> > +{
> > +	struct device *dev = msa311->dev;
> > +	unsigned int partid;
> > +	int err;
> > +
> > +	err = regmap_read(msa311->regs, MSA311_PARTID_REG, &partid);
> > +	if (err)
> > +		return dev_err_probe(dev, err,
> > +				     "failed to read partid (%d)\n", err);
> 
> No need for "(%d)" and err.
> 

Do you mean for all dev_err() calls? I think sometimes it's helpful to
know the actual error value got from external API, isn't? Could you please
explain your point if possible?

> > +
> > +	if (partid == MSA311_WHO_AM_I)
> > +		dev_dbg(dev, "found MSA311 compatible chip[%#x]\n", partid);
> > +	else
> > +		dev_warn(dev, "invalid partid (%#x), expected (%#x)\n",
> > +			 partid, MSA311_WHO_AM_I);
> > +
> > +	return 0;
> > +}
> 
> [...]
> 
> > +static int msa311_probe(struct i2c_client *i2c)
> > +{
> > +	struct device *dev = &i2c->dev;
> > +	struct msa311_priv *msa311;
> > +	struct iio_dev *indio_dev;
> > +	int err;
> > +
> > +	indio_dev = devm_iio_device_alloc(dev, sizeof(*msa311));
> > +	if (!indio_dev)
> > +		return dev_err_probe(dev, -ENOMEM,
> > +				     "iio device allocation failed\n");
> > +
> > +	msa311 = iio_priv(indio_dev);
> > +	msa311->dev = dev;
> > +	i2c_set_clientdata(i2c, indio_dev);
> > +
> > +	err = msa311_regmap_init(msa311);
> > +	if (err)
> > +		return err;
> > +
> > +	mutex_init(&msa311->lock);
> > +
> > +	msa311->vdd = devm_regulator_get_optional(dev, "vdd");
> > +	if (IS_ERR(msa311->vdd)) {
> > +		err = PTR_ERR(msa311->vdd);
> > +		if (err == -ENODEV)
> > +			msa311->vdd = NULL;
> > +		else
> > +			return dev_err_probe(dev, PTR_ERR(msa311->vdd),
> > +					     "cannot get vdd supply\n");
> > +	}
> > +
> > +	if (msa311->vdd) {
> > +		err = regulator_enable(msa311->vdd);
> > +		if (err)
> > +			return dev_err_probe(dev, err,
> > +					     "cannot enable vdd supply\n");
> > +
> > +		err = devm_add_action_or_reset(dev, msa311_vdd_disable,
> > +					       msa311->vdd);
> > +		if (err) {
> > +			regulator_disable(msa311->vdd);
> 
> Double regulator_disable(), because of the _or_reset()?
> 

Yep. If devm_add_action_or_reset() returns an error, we will not
call regulator_disable() by devm subsystem. It means, we have to
call it directly.

> > +			return dev_err_probe(dev, err,
> > +					     "cannot add vdd disable action\n");
> > +		}
> > +	}
> > +
> > +	err = msa311_check_partid(msa311);
> > +	if (err)
> > +		return err;
> > +
> > +	err = msa311_soft_reset(msa311);
> > +	if (err)
> > +		return err;
> > +
> > +	err = msa311_set_pwr_mode(msa311, MSA311_PWR_MODE_NORMAL);
> > +	if (err)
> > +		return dev_err_probe(dev, err,
> > +				     "failed to power on device (%d)\n", err);
> 
> No need for "(%d)" and err

Asked for the clarification above.

> 
> CJ

-- 
Thank you,
Dmitry

  reply	other threads:[~2022-08-03 18:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03 13:11 [PATCH v4 0/3] iio: accel: add MSA311 accelerometer driver Dmitry Rokosov
2022-08-03 13:11 ` [PATCH v4 1/3] dt-bindings: vendor-prefixes: add MEMSensing Microsystems Co., Ltd Dmitry Rokosov
2022-08-03 13:11 ` [PATCH v4 2/3] iio: add MEMSensing MSA311 3-axis accelerometer driver Dmitry Rokosov
2022-08-03 17:49   ` Andy Shevchenko
2022-08-03 19:16     ` Dmitry Rokosov
2022-08-04 18:17       ` Dmitry Rokosov
2022-08-04 18:30         ` Andy Shevchenko
2022-08-05 14:04           ` Dmitry Rokosov
2022-08-05 16:03             ` Andy Shevchenko
2022-08-05 16:20               ` Dmitry Rokosov
2022-08-05 17:59                 ` Andy Shevchenko
2022-08-04 18:28       ` Andy Shevchenko
2022-08-05 14:19         ` Dmitry Rokosov
2022-08-06 14:55       ` Jonathan Cameron
2022-08-09  9:52         ` Dmitry Rokosov
2022-08-09 10:05           ` Andy Shevchenko
2022-08-09 10:35             ` Dmitry Rokosov
2022-08-13 15:27               ` Jonathan Cameron
2022-08-13 15:39                 ` Jonathan Cameron
2022-08-03 18:11   ` Christophe JAILLET
2022-08-03 18:39     ` Dmitry Rokosov [this message]
2022-08-03 19:18       ` Christophe JAILLET
2022-08-03 19:26         ` Dmitry Rokosov
2022-08-06 15:32   ` Jonathan Cameron
2022-08-09  9:47     ` Dmitry Rokosov
2022-08-13 15:34       ` Jonathan Cameron
2022-08-03 13:11 ` [PATCH v4 3/3] dt-bindings: iio: accel: add dt-binding schema for msa311 accel driver Dmitry Rokosov
2022-08-03 23:41   ` 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=20220803184001.fcappv7grdjyaetn@CAB-WSD-L081021.sigma.sbrf.ru \
    --to=ddrokosov@sberdevices.ru \
    --cc=andy.shevchenko@gmail.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=kernel@sberdevices.ru \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=stano.jakubek@gmail.com \
    --cc=stephan@gerhold.net \
    /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).