From: "Alessandrelli, Daniele" <daniele.alessandrelli@intel.com>
To: "Murphy, Paul J" <paul.j.murphy@intel.com>,
"jacopo@jmondi.org" <jacopo@jmondi.org>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"bryan.odonoghue@linaro.org" <bryan.odonoghue@linaro.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"sakari.ailus@iki.fi" <sakari.ailus@iki.fi>
Cc: "hfink@snap.com" <hfink@snap.com>,
"robert.foss@linaro.org" <robert.foss@linaro.org>,
"vladimir.zapolskiy@linaro.org" <vladimir.zapolskiy@linaro.org>,
"dmitry.baryshkov@linaro.org" <dmitry.baryshkov@linaro.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"jgrahsl@snap.com" <jgrahsl@snap.com>
Subject: Re: [PATCH v5 2/4] media: i2c: imx412: Fix power_off ordering
Date: Mon, 25 Apr 2022 14:43:48 +0000 [thread overview]
Message-ID: <4875c1f26d3978ad499b04bc08f9f8aebfcdc320.camel@intel.com> (raw)
In-Reply-To: <20220415115954.1649217-3-bryan.odonoghue@linaro.org>
On Fri, 2022-04-15 at 12:59 +0100, Bryan O'Donoghue wrote:
> The enable path does
> - gpio
> - clock
>
> The disable path does
> - gpio
> - clock
>
> Fix the order on the power-off path so that power-off and power-on have
> the
> same ordering for clock and gpio.
>
> Fixes: 9214e86c0cc1 ("media: i2c: Add imx412 camera sensor driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> ---
> drivers/media/i2c/imx412.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/i2c/imx412.c b/drivers/media/i2c/imx412.c
> index e6be6b4250f5..84279a680873 100644
> --- a/drivers/media/i2c/imx412.c
> +++ b/drivers/media/i2c/imx412.c
> @@ -1040,10 +1040,10 @@ static int imx412_power_off(struct device *dev)
> struct v4l2_subdev *sd = dev_get_drvdata(dev);
> struct imx412 *imx412 = to_imx412(sd);
>
> - gpiod_set_value_cansleep(imx412->reset_gpio, 1);
> -
> clk_disable_unprepare(imx412->inclk);
>
> + gpiod_set_value_cansleep(imx412->reset_gpio, 1);
> +
> return 0;
> }
>
LGTM, thanks for the patch!
Reviewed-by: Daniele Alessandrelli <daniele.alessandrelli@intel.com>
next prev parent reply other threads:[~2022-04-25 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 11:59 [PATCH v5 0/4] media: i2c: imx412: Add regulator control to imx412 Bryan O'Donoghue
2022-04-15 11:59 ` [PATCH v5 1/4] media: i2c: imx412: Fix reset GPIO polarity Bryan O'Donoghue
2022-04-25 14:41 ` Alessandrelli, Daniele
2022-04-15 11:59 ` [PATCH v5 2/4] media: i2c: imx412: Fix power_off ordering Bryan O'Donoghue
2022-04-25 14:43 ` Alessandrelli, Daniele [this message]
2022-04-15 11:59 ` [PATCH v5 3/4] media: dt-bindings: imx412: Add regulator descriptions Bryan O'Donoghue
2022-04-15 11:59 ` [PATCH v5 4/4] media: i2c: imx412: Add bulk regulator support Bryan O'Donoghue
2022-04-15 15:12 ` Jacopo Mondi
2022-04-26 16:52 ` Alessandrelli, Daniele
2022-05-06 14:26 ` Sakari Ailus
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=4875c1f26d3978ad499b04bc08f9f8aebfcdc320.camel@intel.com \
--to=daniele.alessandrelli@intel.com \
--cc=bryan.odonoghue@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=hfink@snap.com \
--cc=jacopo@jmondi.org \
--cc=jgrahsl@snap.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=paul.j.murphy@intel.com \
--cc=robert.foss@linaro.org \
--cc=sakari.ailus@iki.fi \
--cc=stable@vger.kernel.org \
--cc=vladimir.zapolskiy@linaro.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).