From: "Clément Léger" <clement.leger@bootlin.com>
To: Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
UNGLinuxDriver@microchip.com
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Allan Nielsen" <allan.nielsen@microchip.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Clément Léger" <clement.leger@bootlin.com>
Subject: [PATCH v2 3/3] reset: mchp: sparx5: set fwnode field of reset controller
Date: Thu, 24 Mar 2022 15:12:37 +0100 [thread overview]
Message-ID: <20220324141237.297207-4-clement.leger@bootlin.com> (raw)
In-Reply-To: <20220324141237.297207-1-clement.leger@bootlin.com>
Now that reset subsystem has fwnode support, use the fwnode field of
the rcdev to setup the fwnode to be used for the controller.
Signed-off-by: Clément Léger <clement.leger@bootlin.com>
---
drivers/reset/reset-microchip-sparx5.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/reset/reset-microchip-sparx5.c b/drivers/reset/reset-microchip-sparx5.c
index 00b612a0effa..eb648b40dffd 100644
--- a/drivers/reset/reset-microchip-sparx5.c
+++ b/drivers/reset/reset-microchip-sparx5.c
@@ -101,7 +101,6 @@ static int mchp_sparx5_map_io(struct platform_device *pdev, int index,
static int mchp_sparx5_reset_probe(struct platform_device *pdev)
{
- struct device_node *dn = pdev->dev.of_node;
struct mchp_reset_context *ctx;
int err;
@@ -119,7 +118,7 @@ static int mchp_sparx5_reset_probe(struct platform_device *pdev)
ctx->rcdev.owner = THIS_MODULE;
ctx->rcdev.nr_resets = 1;
ctx->rcdev.ops = &sparx5_reset_ops;
- ctx->rcdev.of_node = dn;
+ ctx->rcdev.fwnode = dev_fwnode(&pdev->dev);
ctx->props = device_get_match_data(&pdev->dev);
return devm_reset_controller_register(&pdev->dev, &ctx->rcdev);
--
2.34.1
next prev parent reply other threads:[~2022-03-24 14:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 14:12 [PATCH v2 0/3] add fwnode support to reset subsystem Clément Léger
2022-03-24 14:12 ` [PATCH v2 1/3] of: add function to convert fwnode_reference_args to of_phandle_args Clément Léger
2022-03-24 14:12 ` [PATCH v2 2/3] reset: add support for fwnode Clément Léger
2022-03-24 14:12 ` Clément Léger [this message]
2022-04-04 17:41 ` [PATCH v2 0/3] add fwnode support to reset subsystem Rob Herring
2022-04-05 7:24 ` Clément Léger
2022-04-05 14:47 ` Rob Herring
2022-04-05 15:51 ` Clément Léger
2022-04-05 17:11 ` Rob Herring
2022-04-05 21:28 ` Rob Herring
2022-04-06 7:52 ` Clément Léger
2022-04-06 13:04 ` Rob Herring
2022-04-06 7:40 ` Clément Léger
2022-04-06 13:19 ` Rob Herring
2022-04-06 13:33 ` Alexandre Belloni
2022-04-06 13:36 ` Clément Léger
2022-04-08 15:48 ` Clément Léger
2022-04-25 10:21 ` Philipp Zabel
2022-04-25 11:18 ` Clément Léger
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=20220324141237.297207-4-clement.leger@bootlin.com \
--to=clement.leger@bootlin.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=allan.nielsen@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=lars.povlsen@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.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).