[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230324140141.6743-1-ddrokosov@sberdevices.ru>
Date: Fri, 24 Mar 2023 17:01:41 +0300
From: Dmitry Rokosov <ddrokosov@...rdevices.ru>
To: <krzysztof.kozlowski@...aro.org>, <robh@...nel.org>,
<neil.armstrong@...aro.org>, <khilman@...libre.com>,
<jbrunet@...libre.com>, <martin.blumenstingl@...glemail.com>,
<jianxin.pan@...ogic.com>
CC: <kernel@...rdevices.ru>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-amlogic@...ts.infradead.org>, <devicetree@...r.kernel.org>,
<rockosov@...il.com>, Dmitry Rokosov <ddrokosov@...rdevices.ru>
Subject: [PATCH v2] firmware: meson_sm: populate platform devices from sm device tree data
In some meson boards, secure monitor device has children, for example,
power secure controller. By default, secure monitor isn't the bus in terms
of device tree subsystem, so the of_platform initialization code doesn't
populate its device tree data. As a result, secure monitor's children
aren't probed at all.
Run the 'of_platform_populate()' routine manually to resolve such issues.
Signed-off-by: Dmitry Rokosov <ddrokosov@...rdevices.ru>
---
drivers/firmware/meson/meson_sm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/firmware/meson/meson_sm.c b/drivers/firmware/meson/meson_sm.c
index 77aa5c6398aa..b79d0e316cb1 100644
--- a/drivers/firmware/meson/meson_sm.c
+++ b/drivers/firmware/meson/meson_sm.c
@@ -316,7 +316,7 @@ static int __init meson_sm_probe(struct platform_device *pdev)
if (sysfs_create_group(&pdev->dev.kobj, &meson_sm_sysfs_attr_group))
goto out_in_base;
- return 0;
+ return devm_of_platform_populate(dev);
out_in_base:
iounmap(fw->sm_shmem_in_base);
--
2.36.0
Powered by blists - more mailing lists