From: p.zabel@pengutronix.de (Philipp Zabel)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 1/3] reset: allow using reset_control_reset with shared reset
Date: Tue, 15 Nov 2016 13:48:05 +0100 [thread overview]
Message-ID: <1479214085.2456.26.camel@pengutronix.de> (raw)
In-Reply-To: <20161112131305.26088-2-martin.blumenstingl@googlemail.com>
Hi Martin,
Am Samstag, den 12.11.2016, 14:13 +0100 schrieb Martin Blumenstingl:
> Some SoCs (for example Amlogic GXBB) implement a reset controller which
> only supports a reset pulse (triggered via reset_control_reset). At the
> same time multiple devices (in case of the Amlogic GXBB SoC both USB
> PHYs) are sharing the same reset line.
>
> This patch allows using reset_control_reset also for shared resets.
> There are limitations though:
> reset_control_reset can only be used if reset_control_assert was not
> used yet.
> reset_control_assert can only be used if reset_control_reset was not
> used yet.
> For shared resets the reset is only triggered once for the lifetime of
> the reset_control instance (the reset can be triggered again if all
> consumers of that specific reset_control are gone, as the reset
> framework will free the reset_control instance in that case).
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Looks good to me, I've applied it to the reset/next branch.
thanks
Philipp
> ---
> drivers/reset/core.c | 43 +++++++++++++++++++++++++++++++++++++------
> 1 file changed, 37 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/reset/core.c b/drivers/reset/core.c
> index b8ae1db..10368ed 100644
> --- a/drivers/reset/core.c
> +++ b/drivers/reset/core.c
> @@ -32,6 +32,9 @@ static LIST_HEAD(reset_controller_list);
> * @refcnt: Number of gets of this reset_control
> * @shared: Is this a shared (1), or an exclusive (0) reset_control?
> * @deassert_cnt: Number of times this reset line has been deasserted
> + * @triggered_count: Number of times this reset line has been reset. Currently
> + * only used for shared resets, which means that the value
> + * will be either 0 or 1.
> */
> struct reset_control {
> struct reset_controller_dev *rcdev;
> @@ -40,6 +43,7 @@ struct reset_control {
> unsigned int refcnt;
> int shared;
> atomic_t deassert_count;
> + atomic_t triggered_count;
> };
>
> /**
> @@ -134,18 +138,35 @@ EXPORT_SYMBOL_GPL(devm_reset_controller_register);
> * reset_control_reset - reset the controlled device
> * @rstc: reset controller
> *
> - * Calling this on a shared reset controller is an error.
> + * On a shared reset line the actual reset pulse is only triggered once for the
> + * lifetime of the reset_control instance: for all but the first caller this is
> + * a no-op.
> + * Consumers must not use reset_control_(de)assert on shared reset lines when
> + * reset_control_reset has been used.
> */
> int reset_control_reset(struct reset_control *rstc)
> {
> - if (WARN_ON(IS_ERR_OR_NULL(rstc)) ||
> - WARN_ON(rstc->shared))
> + int ret;
> +
> + if (WARN_ON(IS_ERR_OR_NULL(rstc)))
> return -EINVAL;
>
> - if (rstc->rcdev->ops->reset)
> - return rstc->rcdev->ops->reset(rstc->rcdev, rstc->id);
> + if (!rstc->rcdev->ops->reset)
> + return -ENOTSUPP;
>
> - return -ENOTSUPP;
> + if (rstc->shared) {
> + if (WARN_ON(atomic_read(&rstc->deassert_count) != 0))
> + return -EINVAL;
> +
> + if (atomic_inc_return(&rstc->triggered_count) != 1)
> + return 0;
> + }
> +
> + ret = rstc->rcdev->ops->reset(rstc->rcdev, rstc->id);
> + if (rstc->shared && !ret)
> + atomic_dec(&rstc->triggered_count);
> +
> + return ret;
> }
> EXPORT_SYMBOL_GPL(reset_control_reset);
>
> @@ -159,6 +180,8 @@ EXPORT_SYMBOL_GPL(reset_control_reset);
> *
> * For shared reset controls a driver cannot expect the hw's registers and
> * internal state to be reset, but must be prepared for this to happen.
> + * Consumers must not use reset_control_reset on shared reset lines when
> + * reset_control_(de)assert has been used.
> */
> int reset_control_assert(struct reset_control *rstc)
> {
> @@ -169,6 +192,9 @@ int reset_control_assert(struct reset_control *rstc)
> return -ENOTSUPP;
>
> if (rstc->shared) {
> + if (WARN_ON(atomic_read(&rstc->triggered_count) != 0))
> + return -EINVAL;
> +
> if (WARN_ON(atomic_read(&rstc->deassert_count) == 0))
> return -EINVAL;
>
> @@ -185,6 +211,8 @@ EXPORT_SYMBOL_GPL(reset_control_assert);
> * @rstc: reset controller
> *
> * After calling this function, the reset is guaranteed to be deasserted.
> + * Consumers must not use reset_control_reset on shared reset lines when
> + * reset_control_(de)assert has been used.
> */
> int reset_control_deassert(struct reset_control *rstc)
> {
> @@ -195,6 +223,9 @@ int reset_control_deassert(struct reset_control *rstc)
> return -ENOTSUPP;
>
> if (rstc->shared) {
> + if (WARN_ON(atomic_read(&rstc->triggered_count) != 0))
> + return -EINVAL;
> +
> if (atomic_inc_return(&rstc->deassert_count) != 1)
> return 0;
> }
next prev parent reply other threads:[~2016-11-15 12:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 15:21 [PATCH 0/3] enable reset_control_reset for shared reset lines Martin Blumenstingl
2016-10-01 15:21 ` [PATCH 1/3] reset: allow using reset_control_reset with shared reset Martin Blumenstingl
2016-10-04 8:36 ` Philipp Zabel
2016-10-01 15:21 ` [PATCH 2/3] phy: meson8b-usb2: request a shared reset line Martin Blumenstingl
2016-10-01 15:21 ` [PATCH 3/3] ARM64: dts: meson-gxbb: add the USB reset also to the second USB PHY Martin Blumenstingl
2016-11-12 13:13 ` [PATCH 0/3] enable reset_control_reset for shared reset lines Martin Blumenstingl
2016-11-12 13:13 ` [PATCH 1/3] reset: allow using reset_control_reset with shared reset Martin Blumenstingl
2016-11-15 12:48 ` Philipp Zabel [this message]
2016-11-12 13:13 ` [PATCH 2/3] phy: meson8b-usb2: request a shared reset line Martin Blumenstingl
2016-11-15 12:54 ` Kishon Vijay Abraham I
2016-11-12 13:13 ` [PATCH 3/3] ARM64: dts: meson-gxbb: add the USB reset also to the second USB PHY Martin Blumenstingl
2016-11-16 21:35 ` Kevin Hilman
2016-11-18 22:35 ` Martin Blumenstingl
2016-11-21 20:15 ` Kevin Hilman
2016-11-22 22:05 ` Martin Blumenstingl
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=1479214085.2456.26.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=linus-amlogic@lists.infradead.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).