From: Philipp Zabel <p.zabel@pengutronix.de>
To: Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: swarren@wwwdotorg.org, balbi@kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-usb@vger.kernel.org, thierry.reding@gmail.com,
gregkh@linuxfoundation.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH V3 2/4] reset: Add APIs to manage array of resets
Date: Wed, 19 Apr 2017 12:31:52 +0200 [thread overview]
Message-ID: <1492597912.2970.65.camel@pengutronix.de> (raw)
In-Reply-To: <1492514488-27385-3-git-send-email-vivek.gautam@codeaurora.org>
On Tue, 2017-04-18 at 16:51 +0530, Vivek Gautam wrote:
> Many devices may want to request a bunch of resets
> and control them. So it's better to manage them as an
> array. Add APIs to _get(), _assert(), and _deassert()
> an array of reset_control.
Thanks! This looks good to me, one small issue below.
> Cc: Philipp Zabel <p.zabel@pengutronix.de>
> Signed-off-by: Vivek Gautam <vivek.gautam@codeaurora.org>
> ---
> drivers/reset/core.c | 177 ++++++++++++++++++++++++++++++++++++++++++++++++++
> include/linux/reset.h | 93 ++++++++++++++++++++++++++
> 2 files changed, 270 insertions(+)
>
> diff --git a/drivers/reset/core.c b/drivers/reset/core.c
> index f0a06a7aca93..54bd3be5e7a4 100644
> --- a/drivers/reset/core.c
> +++ b/drivers/reset/core.c
> @@ -488,3 +488,180 @@ int of_reset_control_get_count(struct device_node *node)
> return count;
> }
> EXPORT_SYMBOL_GPL(of_reset_control_get_count);
> +
> +/**
> + * APIs to manage an array of reset controls.
> + */
> +/**
> + * reset_control_array_assert: assert a list of resets
> + *
> + * @resets: reset control array holding info about the list of resets
> + *
> + * This API doesn't guarantee that the reset lines controlled by
> + * the reset array are asserted in any particular order.
> + *
> + * Returns 0 on success or error number on failure.
> + */
> +int reset_control_array_assert(struct reset_control_array *resets)
> +{
> + int ret, i;
> +
> + if (!resets)
> + return 0;
> +
> + if (IS_ERR(resets))
> + return -EINVAL;
> +
> + for (i = 0; i < resets->num_rstcs; i++) {
> + ret = reset_control_assert(resets->rstc[i]);
> + if (ret)
> + return ret;
This should try to deassert the already asserted resets in the error
case.
> + }
> +
> + return 0;
> +}
> +EXPORT_SYMBOL_GPL(reset_control_array_assert);
> +
> +/**
> + * reset_control_array_deassert: deassert a list of resets
> + *
> + * @resets: reset control array holding info about the list of resets
> + *
> + * This API doesn't guarantee that the reset lines controlled by
> + * the reset array are deasserted in any particular order.
> + *
> + * Returns 0 on success or error number on failure.
> + */
> +int reset_control_array_deassert(struct reset_control_array *resets)
> +{
> + int ret, i;
> +
> + if (!resets)
> + return 0;
> +
> + if (IS_ERR(resets))
> + return -EINVAL;
> +
> + for (i = 0; i < resets->num_rstcs; i++) {
> + ret = reset_control_deassert(resets->rstc[i]);
> + if (ret)
> + goto err;
> + }
> +
> + return 0;
> +
> +err:
> + while (i--)
> + reset_control_assert(resets->rstc[i]);
> + return ret;
> +}
> +EXPORT_SYMBOL_GPL(reset_control_array_deassert);
As this already does.
regards
Philipp
next prev parent reply other threads:[~2017-04-19 10:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 11:21 [PATCH V3 0/4] reset: APIs to manage a list of resets Vivek Gautam
2017-04-18 11:21 ` [PATCH V3 1/4] reset: Add API to count number of reset available with device Vivek Gautam
[not found] ` <1492514488-27385-2-git-send-email-vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-04-19 10:25 ` Philipp Zabel
[not found] ` <1492597532.2970.61.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-04-19 11:49 ` Vivek Gautam
2017-04-18 11:21 ` [PATCH V3 2/4] reset: Add APIs to manage array of resets Vivek Gautam
2017-04-19 10:31 ` Philipp Zabel [this message]
[not found] ` <1492597912.2970.65.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-04-19 11:55 ` Vivek Gautam
2017-04-18 11:21 ` [PATCH V3 3/4] usb: dwc3: of-simple: Add support to get resets for the device Vivek Gautam
[not found] ` <1492514488-27385-4-git-send-email-vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-04-19 10:32 ` Philipp Zabel
2017-04-19 12:02 ` Vivek Gautam
2017-04-18 11:21 ` [PATCH V3 4/4] soc/tegra: pmc: Use the new reset APIs to manage reset controllers Vivek Gautam
2017-04-19 10:40 ` Philipp Zabel
[not found] ` <1492514488-27385-5-git-send-email-vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-04-24 12:45 ` Jon Hunter
2017-04-25 4:15 ` Vivek Gautam
[not found] ` <afcddcbe-7086-2739-6de2-84f5c1d34374-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-04-25 10:05 ` Jon Hunter
[not found] ` <b3f2cbe5-4a1a-2f7b-2e4a-6a06eeadc890-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-04-25 10:33 ` Philipp Zabel
2017-04-25 10:54 ` Jon Hunter
[not found] ` <afdb02e5-9299-fec9-9451-8271c220744b-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-04-25 11:06 ` Vivek Gautam
[not found] ` <5e0c2030-ad96-15fc-1dc4-db6cd11d52c3-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-04-25 11:11 ` Jon Hunter
[not found] ` <ff663727-dcdf-b3e7-616d-5e770d32d782-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-04-25 17:50 ` Vivek Gautam
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=1492597912.2970.65.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=vivek.gautam@codeaurora.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).