From: Pengfei Li <pengfei.li_1@nxp.com> To: ulf.hansson@linaro.org, shawnguo@kernel.org, s.hauer@pengutronix.de, kernel@pengutronix.de Cc: festevam@gmail.com, linux-imx@nxp.com, linus.walleij@linaro.org, rafael@kernel.org, heiko@sntech.de, robh@kernel.org, pengfei.li_1@nxp.com, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH] pmdomain: imx: Make imx pgc power domain also set the fwnode Date: Sat, 21 Oct 2023 02:59:49 +0800 [thread overview] Message-ID: <20231020185949.537083-1-pengfei.li_1@nxp.com> (raw) Currently, The imx pgc power domain doesn't set the fwnode pointer, which results in supply regulator device can't get consumer imx pgc power domain device from fwnode when creating a link. This causes the driver core to instead try to create a link between the parent gpc device of imx pgc power domain device and supply regulator device. However, at this point, the gpc device has already been bound, and the link creation will fail. So adding the fwnode pointer to the imx pgc power domain device will fix this issue. Signed-off-by: Pengfei Li <pengfei.li_1@nxp.com> --- drivers/pmdomain/imx/gpc.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/pmdomain/imx/gpc.c b/drivers/pmdomain/imx/gpc.c index 114f44ca07dd..7d81e3171d39 100644 --- a/drivers/pmdomain/imx/gpc.c +++ b/drivers/pmdomain/imx/gpc.c @@ -497,6 +497,7 @@ static int imx_gpc_probe(struct platform_device *pdev) pd_pdev->dev.parent = &pdev->dev; pd_pdev->dev.of_node = np; + pd_pdev->dev.fwnode = of_fwnode_handle(np); ret = platform_device_add(pd_pdev); if (ret) { -- 2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: Pengfei Li <pengfei.li_1@nxp.com> To: ulf.hansson@linaro.org, shawnguo@kernel.org, s.hauer@pengutronix.de, kernel@pengutronix.de Cc: festevam@gmail.com, linux-imx@nxp.com, linus.walleij@linaro.org, rafael@kernel.org, heiko@sntech.de, robh@kernel.org, pengfei.li_1@nxp.com, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH] pmdomain: imx: Make imx pgc power domain also set the fwnode Date: Sat, 21 Oct 2023 02:59:49 +0800 [thread overview] Message-ID: <20231020185949.537083-1-pengfei.li_1@nxp.com> (raw) Currently, The imx pgc power domain doesn't set the fwnode pointer, which results in supply regulator device can't get consumer imx pgc power domain device from fwnode when creating a link. This causes the driver core to instead try to create a link between the parent gpc device of imx pgc power domain device and supply regulator device. However, at this point, the gpc device has already been bound, and the link creation will fail. So adding the fwnode pointer to the imx pgc power domain device will fix this issue. Signed-off-by: Pengfei Li <pengfei.li_1@nxp.com> --- drivers/pmdomain/imx/gpc.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/pmdomain/imx/gpc.c b/drivers/pmdomain/imx/gpc.c index 114f44ca07dd..7d81e3171d39 100644 --- a/drivers/pmdomain/imx/gpc.c +++ b/drivers/pmdomain/imx/gpc.c @@ -497,6 +497,7 @@ static int imx_gpc_probe(struct platform_device *pdev) pd_pdev->dev.parent = &pdev->dev; pd_pdev->dev.of_node = np; + pd_pdev->dev.fwnode = of_fwnode_handle(np); ret = platform_device_add(pd_pdev); if (ret) { -- 2.34.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-10-20 3:00 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-20 18:59 Pengfei Li [this message] 2023-10-20 18:59 ` [PATCH] pmdomain: imx: Make imx pgc power domain also set the fwnode Pengfei Li 2023-10-20 3:07 ` Fabio Estevam 2023-10-20 3:07 ` Fabio Estevam 2023-10-26 7:53 ` Emil Kronborg Andersen 2023-10-26 7:53 ` Emil Kronborg Andersen 2023-10-26 14:26 ` Ulf Hansson 2023-10-26 14:26 ` Ulf Hansson
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=20231020185949.537083-1-pengfei.li_1@nxp.com \ --to=pengfei.li_1@nxp.com \ --cc=festevam@gmail.com \ --cc=heiko@sntech.de \ --cc=kernel@pengutronix.de \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-imx@nxp.com \ --cc=linux-pm@vger.kernel.org \ --cc=rafael@kernel.org \ --cc=robh@kernel.org \ --cc=s.hauer@pengutronix.de \ --cc=shawnguo@kernel.org \ --cc=ulf.hansson@linaro.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.