From: Ulrich Hecht <uli@fpond.eu>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: Eric Auger <eric.auger@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
kvm@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reset: Add reset_control_get_count()
Date: Wed, 14 Nov 2018 07:30:21 +0100 (CET) [thread overview]
Message-ID: <1090034354.41357.1542177021922@webmail.strato.com> (raw)
In-Reply-To: <20181113124744.7769-1-geert+renesas@glider.be>
Thank you for your patch.
> On November 13, 2018 at 1:47 PM Geert Uytterhoeven <geert+renesas@glider.be> wrote:
>
>
> Currently the reset core has internal support for counting the number of
> resets for a device described in DT. Generalize this to devices using
> lookup resets, and export it for public use.
>
> This will be used by generic drivers that need to be sure a device is
> controlled by a single, dedicated reset line (e.g. vfio-platform).
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> See https://lore.kernel.org/lkml/1539003437.11512.20.camel@pengutronix.de/
> for the rationale to ensure a single, dedicated reset line.
>
> drivers/reset/core.c | 41 +++++++++++++++++++++++++++++++++++++++++
> include/linux/reset.h | 7 +++++++
> 2 files changed, 48 insertions(+)
>
> diff --git a/drivers/reset/core.c b/drivers/reset/core.c
> index 654e20ff2d5da9d4..c32b755ec373c338 100644
> --- a/drivers/reset/core.c
> +++ b/drivers/reset/core.c
> @@ -859,3 +859,44 @@ devm_reset_control_array_get(struct device *dev, bool shared, bool optional)
> return rstc;
> }
> EXPORT_SYMBOL_GPL(devm_reset_control_array_get);
> +
> +static int reset_control_get_count_from_lookup(struct device *dev)
> +{
> + const struct reset_control_lookup *lookup;
> + const char *dev_id = dev_name(dev);
> + int count = 0;
> +
> + if (!dev)
> + return -EINVAL;
> +
> + mutex_lock(&reset_lookup_mutex);
> +
> + list_for_each_entry(lookup, &reset_lookup_list, list) {
> + if (!strcmp(lookup->dev_id, dev_id))
> + count++;
> + }
> +
> + mutex_unlock(&reset_lookup_mutex);
> +
> + if (count == 0)
> + count = -ENOENT;
> +
> + return count;
> +}
> +
> +/**
> + * of_reset_control_get_count - Count number of resets available with a device
Should be "reset_control_get_count", without of_ prefix.
> + *
> + * @dev: device for which to return the number of resets
> + *
> + * Returns positive reset count on success, or error number on failure and
> + * on count being zero.
> + */
> +int reset_control_get_count(struct device *dev)
> +{
> + if (dev->of_node)
> + return of_reset_control_get_count(dev->of_node);
> +
> + return reset_control_get_count_from_lookup(dev);
> +}
> +EXPORT_SYMBOL_GPL(reset_control_get_count);
> diff --git a/include/linux/reset.h b/include/linux/reset.h
> index f0b094130686bf32..2698b36bd1eb3e0c 100644
> --- a/include/linux/reset.h
> +++ b/include/linux/reset.h
> @@ -32,6 +32,8 @@ struct reset_control *devm_reset_control_array_get(struct device *dev,
> struct reset_control *of_reset_control_array_get(struct device_node *np,
> bool shared, bool optional);
>
> +int reset_control_get_count(struct device *dev);
> +
> #else
>
> static inline int reset_control_reset(struct reset_control *rstc)
> @@ -97,6 +99,11 @@ of_reset_control_array_get(struct device_node *np, bool shared, bool optional)
> return optional ? NULL : ERR_PTR(-ENOTSUPP);
> }
>
> +static inline int reset_control_get_count(struct device *dev)
> +{
> + return -ENOENT;
> +}
> +
> #endif /* CONFIG_RESET_CONTROLLER */
>
> static inline int __must_check device_reset(struct device *dev)
> --
> 2.17.1
>
CU
Uli
next prev parent reply other threads:[~2018-11-14 6:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 12:47 Geert Uytterhoeven
2018-11-13 14:29 ` Philipp Zabel
2018-11-14 6:30 ` Ulrich Hecht [this message]
2018-11-14 8:58 ` Geert Uytterhoeven
2018-11-14 9:26 ` Philipp Zabel
2018-11-14 9:37 ` Geert Uytterhoeven
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=1090034354.41357.1542177021922@webmail.strato.com \
--to=uli@fpond.eu \
--cc=alex.williamson@redhat.com \
--cc=eric.auger@redhat.com \
--cc=geert+renesas@glider.be \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/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
all inboxes | Powered by JetHome®