From: Dinh Nguyen <dinguyen@opensource.altera.com>
To: <p.zabel@pengutronix.de>
Cc: <dinh.linux@gmail.com>, <atull@opensource.altera.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv3] reset: add reset_control_status helper function
Date: Thu, 23 Oct 2014 10:01:45 -0500 [thread overview]
Message-ID: <54491859.5010007@opensource.altera.com> (raw)
In-Reply-To: <1412954474-25775-1-git-send-email-dinguyen@opensource.altera.com>
Hi Philipp,
On 10/10/2014 10:21 AM, dinguyen@opensource.altera.com wrote:
> From: Dinh Nguyen <dinguyen@opensource.altera.com>
>
> There are cases where a system will want to read a reset status bit before
> doing any other toggling. Add a reset_control_status helper function to the
> reset controller API.
>
> Signed-off-by: Dinh Nguyen <dinguyen@opensource.altera.com>
> ---
> v3: Remove last unsigned int and update comment
> v2: reset_control_status should be returning an int, and add a comment about
> status in reset-controller.h
> ---
> drivers/reset/core.c | 15 +++++++++++++++
> include/linux/reset-controller.h | 2 ++
> include/linux/reset.h | 7 +++++++
> 3 files changed, 24 insertions(+)
>
> diff --git a/drivers/reset/core.c b/drivers/reset/core.c
> index baeaf82..7955e00 100644
> --- a/drivers/reset/core.c
> +++ b/drivers/reset/core.c
> @@ -126,6 +126,21 @@ int reset_control_deassert(struct reset_control *rstc)
> EXPORT_SYMBOL_GPL(reset_control_deassert);
>
> /**
> + * reset_control_status - returns a negative errno if not supported, a
> + * positive value if the reset line is asserted, or zero if the reset
> + * line is not asserted.
> + * @rstc: reset controller
> + */
> +int reset_control_status(struct reset_control *rstc)
> +{
> + if (rstc->rcdev->ops->status)
> + return rstc->rcdev->ops->status(rstc->rcdev, rstc->id);
> +
> + return -ENOSYS;
> +}
> +EXPORT_SYMBOL_GPL(reset_control_status);
> +
> +/**
> * of_reset_control_get - Lookup and obtain a reference to a reset controller.
> * @node: device to be reset by the controller
> * @id: reset line name
> diff --git a/include/linux/reset-controller.h b/include/linux/reset-controller.h
> index 41a4695..ce6b962 100644
> --- a/include/linux/reset-controller.h
> +++ b/include/linux/reset-controller.h
> @@ -12,11 +12,13 @@ struct reset_controller_dev;
> * things to reset the device
> * @assert: manually assert the reset line, if supported
> * @deassert: manually deassert the reset line, if supported
> + * @status: return the status of the reset line, if supported
> */
> struct reset_control_ops {
> int (*reset)(struct reset_controller_dev *rcdev, unsigned long id);
> int (*assert)(struct reset_controller_dev *rcdev, unsigned long id);
> int (*deassert)(struct reset_controller_dev *rcdev, unsigned long id);
> + int (*status)(struct reset_controller_dev *rcdev, unsigned long id);
> };
>
> struct module;
> diff --git a/include/linux/reset.h b/include/linux/reset.h
> index 349f150..da5602b 100644
> --- a/include/linux/reset.h
> +++ b/include/linux/reset.h
> @@ -10,6 +10,7 @@ struct reset_control;
> int reset_control_reset(struct reset_control *rstc);
> int reset_control_assert(struct reset_control *rstc);
> int reset_control_deassert(struct reset_control *rstc);
> +int reset_control_status(struct reset_control *rstc);
>
> struct reset_control *reset_control_get(struct device *dev, const char *id);
> void reset_control_put(struct reset_control *rstc);
> @@ -57,6 +58,12 @@ static inline int reset_control_deassert(struct reset_control *rstc)
> return 0;
> }
>
> +static inline int reset_control_status(struct reset_control *rstc)
> +{
> + WARN_ON(1);
> + return 0;
> +}
> +
> static inline void reset_control_put(struct reset_control *rstc)
> {
> WARN_ON(1);
>
Do you have any further comments on this version of that patch? If not,
can I get an Ack-by?
Thanks,
Dinh
next prev parent reply other threads:[~2014-10-23 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 15:21 [PATCHv3] reset: add reset_control_status helper function dinguyen
2014-10-23 15:01 ` Dinh Nguyen [this message]
2014-10-24 12:07 ` Philipp Zabel
2014-10-24 15:43 ` Dinh Nguyen
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=54491859.5010007@opensource.altera.com \
--to=dinguyen@opensource.altera.com \
--cc=atull@opensource.altera.com \
--cc=dinh.linux@gmail.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).