From: Philipp Zabel <p.zabel@pengutronix.de>
To: Tero Kristo <t-kristo@ti.com>,
ssantosh@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, robh+dt@kernel.org
Cc: tony@atomide.com, devicetree@vger.kernel.org
Subject: Re: [PATCHv2 05/11] soc: ti: omap-prm: sync func clock status with resets
Date: Thu, 29 Aug 2019 15:25:14 +0200 [thread overview]
Message-ID: <1567085114.5345.12.camel@pengutronix.de> (raw)
In-Reply-To: <20190828071941.32378-6-t-kristo@ti.com>
On Wed, 2019-08-28 at 10:19 +0300, Tero Kristo wrote:
> Hardware reset signals are tightly coupled with associated clocks, and
> basically de-asserting a reset won't succeed properly if the clock is
> not enabled, and vice-versa. Also, disabling a clock won't fully succeed
> if the associated hardware resets are not asserted. Add status sync
> functionality between these two for TI drivers so that the situations
> can be handled properly without generating any timeouts.
>
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> ---
> drivers/soc/ti/omap_prm.c | 36 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
>
> diff --git a/drivers/soc/ti/omap_prm.c b/drivers/soc/ti/omap_prm.c
> index 38998ce19c71..e876bad8f8d5 100644
> --- a/drivers/soc/ti/omap_prm.c
> +++ b/drivers/soc/ti/omap_prm.c
> @@ -15,6 +15,8 @@
> #include <linux/platform_device.h>
> #include <linux/reset-controller.h>
> #include <linux/delay.h>
> +#include <linux/clk.h>
> +#include <linux/clk/ti.h>
>
> #include <linux/platform_data/ti-prm.h>
>
> @@ -42,7 +44,9 @@ struct omap_reset_data {
> struct reset_controller_dev rcdev;
> struct omap_prm *prm;
> struct clockdomain *clkdm;
> + struct clk *clk;
> struct device *dev;
> + u32 mask;
> };
>
> #define to_omap_reset_data(p) container_of((p), struct omap_reset_data, rcdev)
> @@ -102,6 +106,8 @@ static int omap_reset_assert(struct reset_controller_dev *rcdev,
> v |= 1 << id;
> writel_relaxed(v, reset->prm->base + reset->prm->data->rstctrl);
>
> + ti_clk_notify_resets(reset->clk, v == reset->mask);
> +
> return 0;
> }
>
> @@ -163,9 +169,19 @@ static int omap_reset_deassert(struct reset_controller_dev *rcdev,
> v &= ~(1 << id);
> writel_relaxed(v, reset->prm->base + reset->prm->data->rstctrl);
>
> + ti_clk_notify_resets(reset->clk, v == reset->mask);
> +
> if (!has_rstst)
> goto exit;
>
> + /* If associated clock is disabled, we can't poll completion status */
> + if (reset->clk) {
> + struct clk_hw *hw = __clk_get_hw(reset->clk);
> +
> + if (!clk_hw_is_enabled(hw))
> + return ret;
> + }
> +
> /* wait for the status to be set */
> while (1) {
> v = readl_relaxed(reset->prm->base + reset->prm->data->rstst);
> @@ -199,8 +215,10 @@ static int omap_prm_reset_init(struct platform_device *pdev,
> struct omap_prm *prm)
> {
> struct omap_reset_data *reset;
> + const struct omap_rst_map *map;
> struct ti_prm_platform_data *pdata = dev_get_platdata(&pdev->dev);
> char buf[32];
> + u32 v;
>
> /*
> * Check if we have controllable resets. If either rstctrl is non-zero
> @@ -215,6 +233,10 @@ static int omap_prm_reset_init(struct platform_device *pdev,
> !pdata->clkdm_allow_idle)
> return -EINVAL;
>
> + map = prm->data->rstmap;
> + if (!map)
> + return -EINVAL;
Can this actually happen?
> +
> reset = devm_kzalloc(&pdev->dev, sizeof(*reset), GFP_KERNEL);
> if (!reset)
> return -ENOMEM;
> @@ -224,6 +246,10 @@ static int omap_prm_reset_init(struct platform_device *pdev,
> reset->rcdev.of_node = pdev->dev.of_node;
> reset->rcdev.nr_resets = OMAP_MAX_RESETS;
> reset->dev = &pdev->dev;
> + reset->clk = of_clk_get(pdev->dev.of_node, 0);
> +
> + if (IS_ERR(reset->clk))
> + reset->clk = NULL;
Maybe only ignore -ENOENT?
> reset->prm = prm;
>
> @@ -234,6 +260,16 @@ static int omap_prm_reset_init(struct platform_device *pdev,
> if (!reset->clkdm)
> return -EINVAL;
>
> + while (map->rst >= 0) {
> + reset->mask |= BIT(map->rst);
> + map++;
> + }
With this, you could use reset->mask to simplify _is_valid_reset.
regards
Philipp
next prev parent reply other threads:[~2019-08-29 13:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 7:19 [PATCHv2 00/11] soc: ti: add OMAP PRM driver (for reset) Tero Kristo
2019-08-28 7:19 ` [PATCHv2 01/11] dt-bindings: omap: add new binding for PRM instances Tero Kristo
2019-08-30 9:18 ` Tero Kristo
2019-08-28 7:19 ` [PATCHv2 02/11] soc: ti: add initial PRM driver with reset control support Tero Kristo
2019-08-29 13:12 ` Philipp Zabel
2019-08-30 7:28 ` Tero Kristo
2019-08-30 9:02 ` Philipp Zabel
2019-08-30 9:11 ` Tero Kristo
2019-08-28 7:19 ` [PATCHv2 03/11] soc: ti: omap-prm: poll for reset complete during de-assert Tero Kristo
2019-08-29 13:14 ` Philipp Zabel
2019-08-30 9:07 ` Tero Kristo
2019-08-28 7:19 ` [PATCHv2 04/11] soc: ti: omap-prm: add support for denying idle for reset clockdomain Tero Kristo
2019-08-28 7:19 ` [PATCHv2 05/11] soc: ti: omap-prm: sync func clock status with resets Tero Kristo
2019-08-29 13:25 ` Philipp Zabel [this message]
2019-08-30 7:03 ` Tero Kristo
2019-08-28 7:19 ` [PATCHv2 06/11] soc: ti: omap-prm: support resets with no associated clockdomain Tero Kristo
2019-08-28 7:19 ` [PATCHv2 07/11] soc: ti: omap-prm: add omap4 PRM data Tero Kristo
2019-08-28 7:19 ` [PATCHv2 08/11] soc: ti: omap-prm: add data for am33xx Tero Kristo
2019-08-28 7:19 ` [PATCHv2 09/11] soc: ti: omap-prm: add dra7 PRM data Tero Kristo
2019-08-28 7:19 ` [PATCHv2 10/11] soc: ti: omap-prm: add am4 " Tero Kristo
2019-08-28 7:19 ` [PATCHv2 11/11] soc: ti: omap-prm: add omap5 " Tero Kristo
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=1567085114.5345.12.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
/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