From: Philipp Zabel <p.zabel@pengutronix.de>
To: Tony Lindgren <tony@atomide.com>, linux-omap@vger.kernel.org
Cc: "Andrew F . Davis" <afd@ti.com>, Dave Gerlach <d-gerlach@ti.com>,
Faiz Abbas <faiz_abbas@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Keerthy <j-keerthy@ti.com>, Nishanth Menon <nm@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Roger Quadros <rogerq@ti.com>, Suman Anna <s-anna@ti.com>,
Tero Kristo <t-kristo@ti.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-remoteproc@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org
Subject: Re: [PATCH 9/9] remoteproc/wkup_m3: Use reset control driver if available
Date: Mon, 26 Oct 2020 12:35:21 +0100 [thread overview]
Message-ID: <c8ea80c2eb79f80539911f3563398957beedaa41.camel@pengutronix.de> (raw)
In-Reply-To: <20201026111049.54835-10-tony@atomide.com>
Hi Tony,
On Mon, 2020-10-26 at 13:10 +0200, Tony Lindgren wrote:
> In order to move wkup_m3 to probe without platform data, let's add
> support for using optional reset control driver if configured in the
> dts. With this change and the related dts change, we can start
> dropping the platform data for am335x.
>
> And once wkup_m3 no longer needs platform data, we can simply drop the
> related legacy reset platform data callbacks from wkup_m3 driver later
> on after also am437x no longer depends on it.
>
> Cc: linux-remoteproc@vger.kernel.org
> Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
> Cc: Dave Gerlach <d-gerlach@ti.com>
> Cc: Philipp Zabel <p.zabel@pengutronix.de>
> Cc: Suman Anna <s-anna@ti.com>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> ---
>
> Please review and ack if no issues. If you guys instead want to set up an
> immutable remoteproc branch with just this patch in it against v5.10-rc1
> that works too :)
>
> ---
> drivers/remoteproc/wkup_m3_rproc.c | 28 +++++++++++++++++++++-------
> 1 file changed, 21 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/remoteproc/wkup_m3_rproc.c b/drivers/remoteproc/wkup_m3_rproc.c
> --- a/drivers/remoteproc/wkup_m3_rproc.c
> +++ b/drivers/remoteproc/wkup_m3_rproc.c
> @@ -17,6 +17,7 @@
> #include <linux/platform_device.h>
> #include <linux/pm_runtime.h>
> #include <linux/remoteproc.h>
> +#include <linux/reset.h>
>
> #include <linux/platform_data/wkup_m3.h>
>
> @@ -43,11 +44,13 @@ struct wkup_m3_mem {
> * @rproc: rproc handle
> * @pdev: pointer to platform device
> * @mem: WkupM3 memory information
> + * @rsts: reset control
> */
> struct wkup_m3_rproc {
> struct rproc *rproc;
> struct platform_device *pdev;
> struct wkup_m3_mem mem[WKUPM3_MEM_MAX];
> + struct reset_control *rsts;
> };
>
> static int wkup_m3_rproc_start(struct rproc *rproc)
> @@ -57,6 +60,9 @@ static int wkup_m3_rproc_start(struct rproc *rproc)
> struct device *dev = &pdev->dev;
> struct wkup_m3_platform_data *pdata = dev_get_platdata(dev);
>
> + if (wkupm3->rsts)
No need for this check, reset_control_deassert() just returns 0 if the
rstc parameter is NULL.
> + return reset_control_deassert(wkupm3->rsts);
> +
> if (pdata->deassert_reset(pdev, pdata->reset_name)) {
> dev_err(dev, "Unable to reset wkup_m3!\n");
> return -ENODEV;
> @@ -72,6 +78,9 @@ static int wkup_m3_rproc_stop(struct rproc *rproc)
> struct device *dev = &pdev->dev;
> struct wkup_m3_platform_data *pdata = dev_get_platdata(dev);
>
> + if (wkupm3->rsts)
Same as above.
> + return reset_control_assert(wkupm3->rsts);
> +
> if (pdata->assert_reset(pdev, pdata->reset_name)) {
> dev_err(dev, "Unable to assert reset of wkup_m3!\n");
> return -ENODEV;
> @@ -132,12 +141,6 @@ static int wkup_m3_rproc_probe(struct platform_device *pdev)
> int ret;
> int i;
>
> - if (!(pdata && pdata->deassert_reset && pdata->assert_reset &&
> - pdata->reset_name)) {
> - dev_err(dev, "Platform data missing!\n");
> - return -ENODEV;
> - }
> -
> ret = of_property_read_string(dev->of_node, "ti,pm-firmware",
> &fw_name);
> if (ret) {
> @@ -165,6 +168,17 @@ static int wkup_m3_rproc_probe(struct platform_device *pdev)
> wkupm3->rproc = rproc;
> wkupm3->pdev = pdev;
>
> + wkupm3->rsts = devm_reset_control_get_optional_shared(dev, "rstctrl");
> + if (PTR_ERR_OR_ZERO(wkupm3->rsts)) {
Please properly return errors. rsts will be NULL if the optional rstctrl
reset is not specified:
if (IS_ERR(wkump3->rsts))
return PTR_ERR(wkump3->rsts);
if (!wkump3->rsts) {
> + if (!(pdata && pdata->deassert_reset && pdata->assert_reset &&
> + pdata->reset_name)) {
> + dev_err(dev, "Platform data missing!\n");
> + ret = -ENODEV;
> + goto err_put_rproc;
> + }
> + wkupm3->rsts = NULL;
I assume this will later be dropped with the platform data support?
> + }
> +
> for (i = 0; i < ARRAY_SIZE(mem_names); i++) {
> res = platform_get_resource_byname(pdev, IORESOURCE_MEM,
> mem_names[i]);
> @@ -173,7 +187,7 @@ static int wkup_m3_rproc_probe(struct platform_device *pdev)
> dev_err(&pdev->dev, "devm_ioremap_resource failed for resource %d\n",
> i);
> ret = PTR_ERR(wkupm3->mem[i].cpu_addr);
> - goto err;
> + goto err_put_rproc;
> }
> wkupm3->mem[i].bus_addr = res->start;
> wkupm3->mem[i].size = resource_size(res);
regards
Philipp
next prev parent reply other threads:[~2020-10-26 11:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 11:10 [PATCH 0/9] Genpd related code changes to drop am335x pdata Tony Lindgren
2020-10-26 11:10 ` [PATCH 1/9] ARM: OMAP2+: Check for inited flag Tony Lindgren
2020-10-26 11:10 ` [PATCH 2/9] ARM: OMAP2+: Probe PRCM first to probe l4_wkup with simple-pm-bus Tony Lindgren
2020-10-26 11:10 ` [PATCH 3/9] clk: ti: am33xx: Keep am3 l3 main clock always on for genpd Tony Lindgren
2020-10-26 11:10 ` [PATCH 4/9] bus: ti-sysc: Support modules without control registers Tony Lindgren
2020-10-26 11:10 ` [PATCH 5/9] bus: ti-sysc: Implement GPMC debug quirk to drop platform data Tony Lindgren
2020-10-26 11:10 ` [PATCH 6/9] soc: ti: omap-prm: Add pm_clk for genpd Tony Lindgren
2020-10-26 11:10 ` [PATCH 7/9] soc: ti: omap-prm: am3: add genpd support for remaining PRM instances Tony Lindgren
2020-10-26 11:10 ` [PATCH 8/9] soc: ti: pm33xx: Enable basic PM runtime support for genpd Tony Lindgren
2020-10-26 11:10 ` [PATCH 9/9] remoteproc/wkup_m3: Use reset control driver if available Tony Lindgren
2020-10-26 11:35 ` Philipp Zabel [this message]
2020-10-26 13:02 ` Tony Lindgren
2020-10-26 13:13 ` [PATCH 0/9] Genpd related code changes to drop am335x pdata Tony Lindgren
2020-11-10 11:20 [PATCHv2 " Tony Lindgren
2020-11-10 11:20 ` [PATCH 9/9] remoteproc/wkup_m3: Use reset control driver if available Tony Lindgren
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=c8ea80c2eb79f80539911f3563398957beedaa41.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=afd@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=d-gerlach@ti.com \
--cc=faiz_abbas@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=grygorii.strashko@ti.com \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nm@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=rogerq@ti.com \
--cc=s-anna@ti.com \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).