Re: [PATCH 05/13] memory: mtk-smi: Add device-link between smi-larb and smi-common
From: Evan Green <hidden>
Date: 2019-03-05 19:03:41
Also in:
linux-devicetree, linux-iommu, linux-mediatek, lkml
On Wed, Feb 27, 2019 at 6:33 AM Yong Wu [off-list ref] wrote:
On Mon, 2019-02-25 at 15:54 -0800, Evan Green wrote:quoted
On Mon, Dec 31, 2018 at 8:52 PM Yong Wu [off-list ref] wrote:quoted
Normally, If the smi-larb HW need work, we should enable the smi-common HW power and clock firstly. This patch adds device-link between the smi-larb dev and the smi-common dev. then If pm_runtime_get_sync(smi-larb-dev), the pm_runtime_get_sync (smi-common-dev) will be called automatically. Since smi is built-in driver like IOMMU and never unbound, DL_FLAG_AUTOREMOVE_* is not needed. CC: Matthias Brugger <matthias.bgg@gmail.com> Suggested-by: Tomasz Figa <tfiga@chromium.org> Signed-off-by: Yong Wu <yong.wu@mediatek.com> --- drivers/memory/mtk-smi.c | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-)diff --git a/drivers/memory/mtk-smi.c b/drivers/memory/mtk-smi.c index 9688341..30930e4 100644 --- a/drivers/memory/mtk-smi.c +++ b/drivers/memory/mtk-smi.c@@ -271,6 +271,7 @@ static int mtk_smi_larb_probe(struct platform_device *pdev) struct device *dev = &pdev->dev; struct device_node *smi_node; struct platform_device *smi_pdev; + struct device_link *link; larb = devm_kzalloc(dev, sizeof(*larb), GFP_KERNEL); if (!larb)@@ -310,6 +311,12 @@ static int mtk_smi_larb_probe(struct platform_device *pdev) if (!platform_get_drvdata(smi_pdev)) return -EPROBE_DEFER; larb->smi_common_dev = &smi_pdev->dev; + link = device_link_add(dev, larb->smi_common_dev, + DL_FLAG_PM_RUNTIME);Doesn't this need to be torn down in remove()? You mention that it's built-in and never removed, but it does seem to have a remove()The MTK IOMMU driver need depend on this SMI driver. the IOMMU is a builtin driver, thus the SMI also should be a builtin driver. Technically, If the driver is builtin, then the "remove" function can be removed? If yes, I could use a new patch do it.
Yeah, I guess so. It's always sad to see cleanup code getting removed, but it makes sense to me.
It looks the MACRO(builtin_platform_driver) only support one driver, but we have two driver(smi-common and smi-larb) here.quoted
function that tears down everything else, so it seemed a shame to start leaking now. Maybe the AUTOREMOVE flag would do it.
_______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel