From: Andrew Lunn <andrew@lunn.ch>
To: Steen Hegelund <steen.hegelund@microchip.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-kernel@vger.kernel.org,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
Gregory Clement <gregory.clement@bootlin.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] reset: mchp: sparx5: add switch reset driver
Date: Thu, 14 Jan 2021 00:23:49 +0100 [thread overview]
Message-ID: <X/+BBaYqLciJ5PsA@lunn.ch> (raw)
In-Reply-To: <20210113201915.2734205-3-steen.hegelund@microchip.com>
> +static int sparx5_switch_reset(struct reset_controller_dev *rcdev,
> + unsigned long id)
> +{
> + struct mchp_reset_context *ctx =
> + container_of(rcdev, struct mchp_reset_context, reset_ctrl);
> + u32 val;
> +
> + /* Make sure the core is PROTECTED from reset */
> + regmap_update_bits(ctx->cpu_ctrl, PROTECT_REG, PROTECT_BIT, PROTECT_BIT);
> +
> + dev_info(ctx->dev, "soft reset of switchcore\n");
dev_dbg()?
> +
> + /* Start soft reset */
> + regmap_write(ctx->gcb_ctrl, SOFT_RESET_REG, SOFT_RESET_BIT);
> +
> + /* Wait for soft reset done */
> + return read_poll_timeout(sparx5_read_soft_rst, val,
> + (val & SOFT_RESET_BIT) == 0,
> + 1, 100, false,
> + ctx);
> +}
> +static int mchp_sparx5_reset_config(struct platform_device *pdev,
> + struct mchp_reset_context *ctx)
> +{
> + struct device_node *dn = pdev->dev.of_node;
> + struct regmap *cpu_ctrl, *gcb_ctrl;
> + struct device_node *syscon_np;
> + int err;
> +
> + syscon_np = of_parse_phandle(dn, "syscons", 0);
> + if (!syscon_np)
> + return -ENODEV;
> + cpu_ctrl = syscon_node_to_regmap(syscon_np);
> + if (IS_ERR(cpu_ctrl))
> + goto err_cpu;
> + of_node_put(syscon_np);
> +
> + syscon_np = of_parse_phandle(dn, "syscons", 1);
> + if (!syscon_np)
> + return -ENODEV;
> + gcb_ctrl = syscon_node_to_regmap(syscon_np);
> + if (IS_ERR(gcb_ctrl))
> + goto err_gcb;
> + of_node_put(syscon_np);
> +
> + ctx->cpu_ctrl = cpu_ctrl;
> + ctx->gcb_ctrl = gcb_ctrl;
> +
> + ctx->reset_ctrl.owner = THIS_MODULE;
> + ctx->reset_ctrl.nr_resets = 1;
> + ctx->reset_ctrl.ops = &sparx5_reset_ops;
> + ctx->reset_ctrl.of_node = dn;
> +
> + err = devm_reset_controller_register(&pdev->dev, &ctx->reset_ctrl);
> + if (err)
> + dev_err(&pdev->dev, "could not register reset controller\n");
> + pr_info("%s:%d\n", __func__, __LINE__);
> + return err;
> +err_cpu:
> + of_node_put(syscon_np);
> + dev_err(&pdev->dev, "No cpu syscon map\n");
> + return PTR_ERR(cpu_ctrl);
> +err_gcb:
> + of_node_put(syscon_np);
> + dev_err(&pdev->dev, "No gcb syscon map\n");
> + return PTR_ERR(gcb_ctrl);
It would be normal to put the dev_err() before the goto, set err =
PTR_ERR() and then goto out;
> +}
> +
> +static int mchp_sparx5_reset_probe(struct platform_device *pdev)
> +{
> + struct device *dev = &pdev->dev;
> + struct mchp_reset_context *ctx;
> +
> + pr_info("%s:%d\n", __func__, __LINE__);
More left over debug.
> + ctx = devm_kzalloc(dev, sizeof(*ctx), GFP_KERNEL);
> + if (!ctx)
> + return -ENOMEM;
> + ctx->dev = dev;
> + return mchp_sparx5_reset_config(pdev, ctx);
> +}
> +
> +static const struct of_device_id mchp_sparx5_reset_of_match[] = {
> + {
> + .compatible = "microchip,sparx5-switch-reset",
> + },
> + { /*sentinel*/ }
> +};
> +static int __init mchp_sparx5_reset_init(void)
> +{
> + return platform_driver_register(&mchp_sparx5_reset_driver);
> +}
> +
> +postcore_initcall(mchp_sparx5_reset_init);
Does it actually need to be postcore? The users of the reset should
look for -EPROBE_DEFER and try again later. And this then becomes just
a normal driver.
Andrew
next prev parent reply other threads:[~2021-01-14 2:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 20:19 [PATCH 0/3] Adding the Sparx5 Switch Reset Driver Steen Hegelund
2021-01-13 20:19 ` [PATCH 1/3] dt-bindings: reset: microchip sparx5 reset driver bindings Steen Hegelund
2021-01-14 9:39 ` Philipp Zabel
2021-01-14 13:25 ` Steen Hegelund
2021-01-13 20:19 ` [PATCH 2/3] reset: mchp: sparx5: add switch reset driver Steen Hegelund
2021-01-13 23:23 ` Andrew Lunn [this message]
2021-01-14 8:30 ` Steen Hegelund
2021-01-14 9:39 ` Philipp Zabel
2021-01-14 13:36 ` Steen Hegelund
2021-01-13 20:19 ` [PATCH 3/3] arm64: dts: reset: add microchip sparx5 " Steen Hegelund
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=X/+BBaYqLciJ5PsA@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=steen.hegelund@microchip.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