devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "Nechita, Ramona" <Ramona.Nechita@analog.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	"Tanislav, Cosmin" <Cosmin.Tanislav@analog.com>,
	"Hennerich, Michael" <Michael.Hennerich@analog.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"Sa, Nuno" <Nuno.Sa@analog.com>,
	Andy Shevchenko <andy@kernel.org>,
	David Lechner <dlechner@baylibre.com>,
	"Schmitt, Marcelo" <Marcelo.Schmitt@analog.com>,
	Olivier Moysan <olivier.moysan@foss.st.com>,
	Dumitru Ceclan <mitrutzceclan@gmail.com>,
	Matteo Martelli <matteomartelli3@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Alisa-Dariana Roman <alisadariana@gmail.com>,
	Ivan Mikhaylov <fr0st61te@gmail.com>,
	Mike Looijmans <mike.looijmans@topic.nl>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v5 3/3] drivers: iio: adc: add support for ad777x family
Date: Sat, 28 Sep 2024 15:31:09 +0100	[thread overview]
Message-ID: <20240928153109.52ff4c5e@jic23-huawei> (raw)
In-Reply-To: <DM6PR03MB4315306944DE2E5E8CD3B236F36A2@DM6PR03MB4315.namprd03.prod.outlook.com>


> >> +
> >> +	ret = ad7779_reset(indio_dev, reset_gpio);
> >> +	if (ret)
> >> +		return ret;
> >> +
> >> +	ad7779_powerup(st, start_gpio);
> >> +	if (ret)
> >> +		return ret;  
> >What powers the device down again if we hit an error?
> >
> >Probably need a devm_add_action_or_reset() or if it self powers down may a comment on that.  
> 
> In the powerup function there are only some register writes and the start gpio is only a synchronization pulse (perhaps the name powerup is not very appropriate), 
> would an action or reset be necessary in this case? Since the regulators are not used in the driver, should there be a function disabling them anyway?
> 
If there is nothing useful to do indeed not but when I see
a power up, I rather expect a power down.  Is there anything
that can do that or is it a case of it will go to sleep anyway
for some other reason?

Jonathan

> 
> Best Regards,
> Ramona
> 


  reply	other threads:[~2024-09-28 14:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 12:15 [PATCH v5 0/3] add support for ad777x family Ramona Alexandra Nechita
2024-09-12 12:15 ` [PATCH v5 1/3] dt-bindings: iio: adc: add a7779 doc Ramona Alexandra Nechita
2024-09-12 13:15   ` Rob Herring (Arm)
2024-09-14 16:38   ` Jonathan Cameron
2024-09-12 12:15 ` [PATCH v5 2/3] Documentation: ABI: added filter mode doc in sysfs-bus-iio Ramona Alexandra Nechita
2024-09-12 14:47   ` Andy Shevchenko
2024-09-13 14:06     ` Nechita, Ramona
2024-09-13 17:36       ` Andy Shevchenko
2024-09-14 16:42         ` Jonathan Cameron
2024-09-13  4:16   ` kernel test robot
2024-09-14 16:43     ` Jonathan Cameron
2024-09-12 12:15 ` [PATCH v5 3/3] drivers: iio: adc: add support for ad777x family Ramona Alexandra Nechita
2024-09-12 15:15   ` Andy Shevchenko
2024-09-14 16:46     ` Jonathan Cameron
2024-09-14  1:44   ` kernel test robot
2024-09-14 16:48     ` Jonathan Cameron
2024-09-14 17:06   ` Jonathan Cameron
2024-09-20 13:24     ` Nechita, Ramona
2024-09-23 12:51       ` David Lechner
2024-09-28 14:29         ` Jonathan Cameron
2024-09-26 13:41     ` Nechita, Ramona
2024-09-28 14:31       ` Jonathan Cameron [this message]
2024-10-10 14:35         ` Nechita, Ramona
2024-10-10 16:40           ` Jonathan Cameron

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=20240928153109.52ff4c5e@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Cosmin.Tanislav@analog.com \
    --cc=Marcelo.Schmitt@analog.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=Nuno.Sa@analog.com \
    --cc=Ramona.Nechita@analog.com \
    --cc=alisadariana@gmail.com \
    --cc=andy@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=fr0st61te@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matteomartelli3@gmail.com \
    --cc=mike.looijmans@topic.nl \
    --cc=mitrutzceclan@gmail.com \
    --cc=olivier.moysan@foss.st.com \
    --cc=robh@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).