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 1/4] reset: Add API to count number of reset available with device
Date: Wed, 19 Apr 2017 12:25:32 +0200 [thread overview]
Message-ID: <1492597532.2970.61.camel@pengutronix.de> (raw)
In-Reply-To: <1492514488-27385-2-git-send-email-vivek.gautam@codeaurora.org>
On Tue, 2017-04-18 at 16:51 +0530, Vivek Gautam wrote:
> Count number of reset phandles available with the device node
> to know the resets a given device has.
>
> Cc: Philipp Zabel <p.zabel@pengutronix.de>
> Signed-off-by: Vivek Gautam <vivek.gautam@codeaurora.org>
> ---
> drivers/reset/core.c | 23 +++++++++++++++++++++++
> include/linux/reset.h | 6 ++++++
> 2 files changed, 29 insertions(+)
>
> diff --git a/drivers/reset/core.c b/drivers/reset/core.c
> index cd739d2fa160..f0a06a7aca93 100644
> --- a/drivers/reset/core.c
> +++ b/drivers/reset/core.c
> @@ -465,3 +465,26 @@ int device_reset(struct device *dev)
> return ret;
> }
> EXPORT_SYMBOL_GPL(device_reset);
> +
> +/**
> + * of_reset_control_get_count - Count number of resets available with a device
> + *
> + * @node: device node that contains 'resets'.
> + *
> + * Returns positive reset count on success, or error number on failure and
> + * on count being zero.
> + */
> +int of_reset_control_get_count(struct device_node *node)
> +{
> + int count;
> +
> + if (!node)
> + return -EINVAL;
> +
> + count = of_count_phandle_with_args(node, "resets", "#reset-cells");
> + if (count == 0)
> + count = -ENOENT;
> +
> + return count;
> +}
> +EXPORT_SYMBOL_GPL(of_reset_control_get_count);
This doesn't need to be public anymore. You can make it static and merge
it into the second patch.
regards
Philipp
next prev parent reply other threads:[~2017-04-19 10:25 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
2017-04-19 10:25 ` Philipp Zabel [this message]
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
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
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
2017-04-24 12:45 ` Jon Hunter
2017-04-25 4:15 ` Vivek Gautam
2017-04-25 10:05 ` Jon Hunter
2017-04-25 10:33 ` Philipp Zabel
2017-04-25 10:54 ` Jon Hunter
2017-04-25 11:06 ` Vivek Gautam
2017-04-25 11:11 ` Jon Hunter
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=1492597532.2970.61.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).