From: Matthias Brugger <matthias.bgg@gmail.com> To: Yong Wu <yong.wu@mediatek.com>, Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org> Cc: Robin Murphy <robin.murphy@arm.com>, iommu@lists.linux.dev, linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, mingyuan.ma@mediatek.com, yf.wang@mediatek.com, libo.kang@mediatek.com, chengci.xu@mediatek.com, youlin.pei@mediatek.com, anan.sun@mediatek.com, xueqi.zhang@mediatek.com, Guenter Roeck <groeck@chromium.org>, Dan Carpenter <dan.carpenter@oracle.com> Subject: Re: [PATCH v7 2/6] iommu/mediatek: Use component_match_add Date: Tue, 22 Nov 2022 17:28:58 +0100 [thread overview] Message-ID: <451e69dc-ad89-9ffc-1e91-70796e908003@gmail.com> (raw) In-Reply-To: <20221018024258.19073-3-yong.wu@mediatek.com> On 18/10/2022 04:42, Yong Wu wrote: > In order to simplify the error patch(avoid call of_node_put), Use > component_match_add instead component_match_add_release since we are only > interested in the "device" here. Then we could always call of_node_put in > normal path. > > Strictly this is not a fixes patch, but it is a prepare for adding the > error path, thus I add a Fixes tag too. > > Fixes: d2e9a1102cfc ("iommu/mediatek: Contain MM IOMMU flow with the MM TYPE") > Suggested-by: Robin Murphy <robin.murphy@arm.com> > Signed-off-by: Yong Wu <yong.wu@mediatek.com> > Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com> > --- > drivers/iommu/mtk_iommu.c | 10 ++++------ > 1 file changed, 4 insertions(+), 6 deletions(-) > > diff --git a/drivers/iommu/mtk_iommu.c b/drivers/iommu/mtk_iommu.c > index 3189b585725f..38112ad87d70 100644 > --- a/drivers/iommu/mtk_iommu.c > +++ b/drivers/iommu/mtk_iommu.c > @@ -1068,19 +1068,17 @@ static int mtk_iommu_mm_dts_parse(struct device *dev, struct component_match **m > id = i; > > plarbdev = of_find_device_by_node(larbnode); > - if (!plarbdev) { > - of_node_put(larbnode); > + of_node_put(larbnode); > + if (!plarbdev) > return -ENODEV; > - } > + > if (!plarbdev->dev.driver) { > - of_node_put(larbnode); > platform_device_put(plarbdev); > return -EPROBE_DEFER; > } > data->larb_imu[id].dev = &plarbdev->dev; > > - component_match_add_release(dev, match, component_release_of, > - component_compare_of, larbnode); > + component_match_add(dev, match, component_compare_dev, &plarbdev->dev); > platform_device_put(plarbdev); > } >
WARNING: multiple messages have this Message-ID (diff)
From: Matthias Brugger <matthias.bgg@gmail.com> To: Yong Wu <yong.wu@mediatek.com>, Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org> Cc: Robin Murphy <robin.murphy@arm.com>, iommu@lists.linux.dev, linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, mingyuan.ma@mediatek.com, yf.wang@mediatek.com, libo.kang@mediatek.com, chengci.xu@mediatek.com, youlin.pei@mediatek.com, anan.sun@mediatek.com, xueqi.zhang@mediatek.com, Guenter Roeck <groeck@chromium.org>, Dan Carpenter <dan.carpenter@oracle.com> Subject: Re: [PATCH v7 2/6] iommu/mediatek: Use component_match_add Date: Tue, 22 Nov 2022 17:28:58 +0100 [thread overview] Message-ID: <451e69dc-ad89-9ffc-1e91-70796e908003@gmail.com> (raw) In-Reply-To: <20221018024258.19073-3-yong.wu@mediatek.com> On 18/10/2022 04:42, Yong Wu wrote: > In order to simplify the error patch(avoid call of_node_put), Use > component_match_add instead component_match_add_release since we are only > interested in the "device" here. Then we could always call of_node_put in > normal path. > > Strictly this is not a fixes patch, but it is a prepare for adding the > error path, thus I add a Fixes tag too. > > Fixes: d2e9a1102cfc ("iommu/mediatek: Contain MM IOMMU flow with the MM TYPE") > Suggested-by: Robin Murphy <robin.murphy@arm.com> > Signed-off-by: Yong Wu <yong.wu@mediatek.com> > Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com> > --- > drivers/iommu/mtk_iommu.c | 10 ++++------ > 1 file changed, 4 insertions(+), 6 deletions(-) > > diff --git a/drivers/iommu/mtk_iommu.c b/drivers/iommu/mtk_iommu.c > index 3189b585725f..38112ad87d70 100644 > --- a/drivers/iommu/mtk_iommu.c > +++ b/drivers/iommu/mtk_iommu.c > @@ -1068,19 +1068,17 @@ static int mtk_iommu_mm_dts_parse(struct device *dev, struct component_match **m > id = i; > > plarbdev = of_find_device_by_node(larbnode); > - if (!plarbdev) { > - of_node_put(larbnode); > + of_node_put(larbnode); > + if (!plarbdev) > return -ENODEV; > - } > + > if (!plarbdev->dev.driver) { > - of_node_put(larbnode); > platform_device_put(plarbdev); > return -EPROBE_DEFER; > } > data->larb_imu[id].dev = &plarbdev->dev; > > - component_match_add_release(dev, match, component_release_of, > - component_compare_of, larbnode); > + component_match_add(dev, match, component_compare_dev, &plarbdev->dev); > platform_device_put(plarbdev); > } > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-22 16:29 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-18 2:42 [PATCH v7 0/6] iommu/mediatek: Improve safety from invalid dts input Yong Wu 2022-10-18 2:42 ` Yong Wu 2022-10-18 2:42 ` [PATCH v7 1/6] iommu/mediatek: Add platform_device_put for recovering the device refcnt Yong Wu 2022-10-18 2:42 ` Yong Wu 2022-11-22 16:24 ` Matthias Brugger 2022-11-22 16:24 ` Matthias Brugger 2022-10-18 2:42 ` [PATCH v7 2/6] iommu/mediatek: Use component_match_add Yong Wu 2022-10-18 2:42 ` Yong Wu 2022-11-22 16:28 ` Matthias Brugger [this message] 2022-11-22 16:28 ` Matthias Brugger 2022-10-18 2:42 ` [PATCH v7 3/6] iommu/mediatek: Add error path for loop of mm_dts_parse Yong Wu 2022-10-18 2:42 ` Yong Wu 2022-11-22 16:32 ` Matthias Brugger 2022-11-22 16:32 ` Matthias Brugger 2022-10-18 2:42 ` [PATCH v7 4/6] iommu/mediatek: Validate number of phandles associated with "mediatek,larbs" Yong Wu 2022-10-18 2:42 ` Yong Wu 2022-11-22 16:43 ` Matthias Brugger 2022-11-22 16:43 ` Matthias Brugger 2022-10-18 2:42 ` [PATCH v7 5/6] iommu/mediatek: Improve safety for mediatek,smi property in larb nodes Yong Wu 2022-10-18 2:42 ` Yong Wu 2022-11-22 16:49 ` Matthias Brugger 2022-11-22 16:49 ` Matthias Brugger 2022-10-18 2:42 ` [PATCH v7 6/6] iommu/mediatek: Remove unused "mapping" member from mtk_iommu_data Yong Wu 2022-10-18 2:42 ` Yong Wu 2022-11-22 1:13 ` [PATCH v7 0/6] iommu/mediatek: Improve safety from invalid dts input Yong Wu (吴勇) 2022-11-22 1:13 ` Yong Wu (吴勇) 2022-11-22 8:30 ` joro 2022-11-22 8:30 ` joro 2022-12-05 10:46 ` Joerg Roedel 2022-12-05 10:46 ` Joerg Roedel
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=451e69dc-ad89-9ffc-1e91-70796e908003@gmail.com \ --to=matthias.bgg@gmail.com \ --cc=anan.sun@mediatek.com \ --cc=angelogioacchino.delregno@collabora.com \ --cc=chengci.xu@mediatek.com \ --cc=dan.carpenter@oracle.com \ --cc=groeck@chromium.org \ --cc=iommu@lists.linux.dev \ --cc=joro@8bytes.org \ --cc=libo.kang@mediatek.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=mingyuan.ma@mediatek.com \ --cc=robin.murphy@arm.com \ --cc=will@kernel.org \ --cc=xueqi.zhang@mediatek.com \ --cc=yf.wang@mediatek.com \ --cc=yong.wu@mediatek.com \ --cc=youlin.pei@mediatek.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: 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.