From: Robin Murphy <robin.murphy@arm.com>
To: Yong Wu <yong.wu@mediatek.com>, Rob Herring <robh@kernel.org>
Cc: youlin.pei@mediatek.com, devicetree@vger.kernel.org,
Nicolas Boichat <drinkcat@chromium.org>,
srv_heupstream@mediatek.com, chao.hao@mediatek.com,
Will Deacon <will@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
linux-kernel@vger.kernel.org, Evan Green <evgreen@chromium.org>,
Tomasz Figa <tfiga@google.com>,
iommu@lists.linux-foundation.org,
linux-mediatek@lists.infradead.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
anan.sun@mediatek.com, linux-arm-kernel@lists.infradead.org,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>
Subject: Re: [PATCH v6 06/33] of/device: Move dma_range_map before of_iommu_configure
Date: Mon, 18 Jan 2021 15:49:06 +0000 [thread overview]
Message-ID: <1853732d-0efd-171e-9e1f-7ee7ed72a98f@arm.com> (raw)
In-Reply-To: <1610688626.4578.1.camel@mhfsdcap03>
On 2021-01-15 05:30, Yong Wu wrote:
> On Thu, 2021-01-14 at 13:27 -0600, Rob Herring wrote:
>> On Mon, Jan 11, 2021 at 07:18:47PM +0800, Yong Wu wrote:
>>> "dev->dma_range_map" contains the devices' dma_ranges information,
>>> This patch moves dma_range_map before of_iommu_configure. The iommu
>>> driver may need to know the dma_address requirements of its iommu
>>> consumer devices.
>>>
>>> CC: Rob Herring <robh+dt@kernel.org>
>>> CC: Frank Rowand <frowand.list@gmail.com>
>>> Signed-off-by: Yong Wu <yong.wu@mediatek.com>
>>> ---
>>> drivers/of/device.c | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/of/device.c b/drivers/of/device.c
>>> index aedfaaafd3e7..1d84636149df 100644
>>> --- a/drivers/of/device.c
>>> +++ b/drivers/of/device.c
>>> @@ -170,9 +170,11 @@ int of_dma_configure_id(struct device *dev, struct device_node *np,
>>> dev_dbg(dev, "device is%sdma coherent\n",
>>> coherent ? " " : " not ");
>>>
>>> + dev->dma_range_map = map;
>>> iommu = of_iommu_configure(dev, np, id);
>>> if (PTR_ERR(iommu) == -EPROBE_DEFER) {
>>> kfree(map);
>>> + dev->dma_range_map = NULL;
>>
>> Not really going to matter, but you should probably clear dma_range_map
>> before what it points to is freed.
>>
>> With that,
>>
>> Reviewed-by: Rob Herring <robh@kernel.org>
>
> Thanks for the review. I will move it before "kfree(map)" in next
> version.
Paul noticed that we already have a bug in assigning to this
unconditionally[1] - I'd totally forgotten about this series when I
theorised about IOMMU drivers wanting the information earlier, but
sweeping my inbox now only goes to show I was right to think of it :)
We should really get something in as a fix independent of this series,
taking both angles into account.
Robin.
[1]
https://lore.kernel.org/linux-arm-kernel/5c7946f3-b56e-da00-a750-be097c7ceb32@arm.com/
>>
>>> return -EPROBE_DEFER;
>>> }
>>>
>>> @@ -181,7 +183,6 @@ int of_dma_configure_id(struct device *dev, struct device_node *np,
>>>
>>> arch_setup_dma_ops(dev, dma_start, size, iommu, coherent);
>>>
>>> - dev->dma_range_map = map;
>>> return 0;
>>> }
>>> EXPORT_SYMBOL_GPL(of_dma_configure_id);
>>> --
>>> 2.18.0
>>>
>
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
>
WARNING: multiple messages have this Message-ID (diff)
From: Robin Murphy <robin.murphy@arm.com>
To: Yong Wu <yong.wu@mediatek.com>, Rob Herring <robh@kernel.org>
Cc: youlin.pei@mediatek.com, devicetree@vger.kernel.org,
Nicolas Boichat <drinkcat@chromium.org>,
srv_heupstream@mediatek.com, Tomasz Figa <tfiga@google.com>,
Frank Rowand <frowand.list@gmail.com>,
linux-kernel@vger.kernel.org, Evan Green <evgreen@chromium.org>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
chao.hao@mediatek.com, iommu@lists.linux-foundation.org,
linux-mediatek@lists.infradead.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
anan.sun@mediatek.com, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 06/33] of/device: Move dma_range_map before of_iommu_configure
Date: Mon, 18 Jan 2021 15:49:06 +0000 [thread overview]
Message-ID: <1853732d-0efd-171e-9e1f-7ee7ed72a98f@arm.com> (raw)
In-Reply-To: <1610688626.4578.1.camel@mhfsdcap03>
On 2021-01-15 05:30, Yong Wu wrote:
> On Thu, 2021-01-14 at 13:27 -0600, Rob Herring wrote:
>> On Mon, Jan 11, 2021 at 07:18:47PM +0800, Yong Wu wrote:
>>> "dev->dma_range_map" contains the devices' dma_ranges information,
>>> This patch moves dma_range_map before of_iommu_configure. The iommu
>>> driver may need to know the dma_address requirements of its iommu
>>> consumer devices.
>>>
>>> CC: Rob Herring <robh+dt@kernel.org>
>>> CC: Frank Rowand <frowand.list@gmail.com>
>>> Signed-off-by: Yong Wu <yong.wu@mediatek.com>
>>> ---
>>> drivers/of/device.c | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/of/device.c b/drivers/of/device.c
>>> index aedfaaafd3e7..1d84636149df 100644
>>> --- a/drivers/of/device.c
>>> +++ b/drivers/of/device.c
>>> @@ -170,9 +170,11 @@ int of_dma_configure_id(struct device *dev, struct device_node *np,
>>> dev_dbg(dev, "device is%sdma coherent\n",
>>> coherent ? " " : " not ");
>>>
>>> + dev->dma_range_map = map;
>>> iommu = of_iommu_configure(dev, np, id);
>>> if (PTR_ERR(iommu) == -EPROBE_DEFER) {
>>> kfree(map);
>>> + dev->dma_range_map = NULL;
>>
>> Not really going to matter, but you should probably clear dma_range_map
>> before what it points to is freed.
>>
>> With that,
>>
>> Reviewed-by: Rob Herring <robh@kernel.org>
>
> Thanks for the review. I will move it before "kfree(map)" in next
> version.
Paul noticed that we already have a bug in assigning to this
unconditionally[1] - I'd totally forgotten about this series when I
theorised about IOMMU drivers wanting the information earlier, but
sweeping my inbox now only goes to show I was right to think of it :)
We should really get something in as a fix independent of this series,
taking both angles into account.
Robin.
[1]
https://lore.kernel.org/linux-arm-kernel/5c7946f3-b56e-da00-a750-be097c7ceb32@arm.com/
>>
>>> return -EPROBE_DEFER;
>>> }
>>>
>>> @@ -181,7 +183,6 @@ int of_dma_configure_id(struct device *dev, struct device_node *np,
>>>
>>> arch_setup_dma_ops(dev, dma_start, size, iommu, coherent);
>>>
>>> - dev->dma_range_map = map;
>>> return 0;
>>> }
>>> EXPORT_SYMBOL_GPL(of_dma_configure_id);
>>> --
>>> 2.18.0
>>>
>
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Robin Murphy <robin.murphy@arm.com>
To: Yong Wu <yong.wu@mediatek.com>, Rob Herring <robh@kernel.org>
Cc: youlin.pei@mediatek.com, devicetree@vger.kernel.org,
Nicolas Boichat <drinkcat@chromium.org>,
srv_heupstream@mediatek.com, Tomasz Figa <tfiga@google.com>,
Frank Rowand <frowand.list@gmail.com>,
linux-kernel@vger.kernel.org, Evan Green <evgreen@chromium.org>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
chao.hao@mediatek.com, iommu@lists.linux-foundation.org,
linux-mediatek@lists.infradead.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
anan.sun@mediatek.com, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 06/33] of/device: Move dma_range_map before of_iommu_configure
Date: Mon, 18 Jan 2021 15:49:06 +0000 [thread overview]
Message-ID: <1853732d-0efd-171e-9e1f-7ee7ed72a98f@arm.com> (raw)
In-Reply-To: <1610688626.4578.1.camel@mhfsdcap03>
On 2021-01-15 05:30, Yong Wu wrote:
> On Thu, 2021-01-14 at 13:27 -0600, Rob Herring wrote:
>> On Mon, Jan 11, 2021 at 07:18:47PM +0800, Yong Wu wrote:
>>> "dev->dma_range_map" contains the devices' dma_ranges information,
>>> This patch moves dma_range_map before of_iommu_configure. The iommu
>>> driver may need to know the dma_address requirements of its iommu
>>> consumer devices.
>>>
>>> CC: Rob Herring <robh+dt@kernel.org>
>>> CC: Frank Rowand <frowand.list@gmail.com>
>>> Signed-off-by: Yong Wu <yong.wu@mediatek.com>
>>> ---
>>> drivers/of/device.c | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/of/device.c b/drivers/of/device.c
>>> index aedfaaafd3e7..1d84636149df 100644
>>> --- a/drivers/of/device.c
>>> +++ b/drivers/of/device.c
>>> @@ -170,9 +170,11 @@ int of_dma_configure_id(struct device *dev, struct device_node *np,
>>> dev_dbg(dev, "device is%sdma coherent\n",
>>> coherent ? " " : " not ");
>>>
>>> + dev->dma_range_map = map;
>>> iommu = of_iommu_configure(dev, np, id);
>>> if (PTR_ERR(iommu) == -EPROBE_DEFER) {
>>> kfree(map);
>>> + dev->dma_range_map = NULL;
>>
>> Not really going to matter, but you should probably clear dma_range_map
>> before what it points to is freed.
>>
>> With that,
>>
>> Reviewed-by: Rob Herring <robh@kernel.org>
>
> Thanks for the review. I will move it before "kfree(map)" in next
> version.
Paul noticed that we already have a bug in assigning to this
unconditionally[1] - I'd totally forgotten about this series when I
theorised about IOMMU drivers wanting the information earlier, but
sweeping my inbox now only goes to show I was right to think of it :)
We should really get something in as a fix independent of this series,
taking both angles into account.
Robin.
[1]
https://lore.kernel.org/linux-arm-kernel/5c7946f3-b56e-da00-a750-be097c7ceb32@arm.com/
>>
>>> return -EPROBE_DEFER;
>>> }
>>>
>>> @@ -181,7 +183,6 @@ int of_dma_configure_id(struct device *dev, struct device_node *np,
>>>
>>> arch_setup_dma_ops(dev, dma_start, size, iommu, coherent);
>>>
>>> - dev->dma_range_map = map;
>>> return 0;
>>> }
>>> EXPORT_SYMBOL_GPL(of_dma_configure_id);
>>> --
>>> 2.18.0
>>>
>
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Robin Murphy <robin.murphy@arm.com>
To: Yong Wu <yong.wu@mediatek.com>, Rob Herring <robh@kernel.org>
Cc: youlin.pei@mediatek.com, devicetree@vger.kernel.org,
Nicolas Boichat <drinkcat@chromium.org>,
srv_heupstream@mediatek.com, Tomasz Figa <tfiga@google.com>,
Frank Rowand <frowand.list@gmail.com>,
linux-kernel@vger.kernel.org, Evan Green <evgreen@chromium.org>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
chao.hao@mediatek.com, iommu@lists.linux-foundation.org,
linux-mediatek@lists.infradead.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
anan.sun@mediatek.com, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 06/33] of/device: Move dma_range_map before of_iommu_configure
Date: Mon, 18 Jan 2021 15:49:06 +0000 [thread overview]
Message-ID: <1853732d-0efd-171e-9e1f-7ee7ed72a98f@arm.com> (raw)
In-Reply-To: <1610688626.4578.1.camel@mhfsdcap03>
On 2021-01-15 05:30, Yong Wu wrote:
> On Thu, 2021-01-14 at 13:27 -0600, Rob Herring wrote:
>> On Mon, Jan 11, 2021 at 07:18:47PM +0800, Yong Wu wrote:
>>> "dev->dma_range_map" contains the devices' dma_ranges information,
>>> This patch moves dma_range_map before of_iommu_configure. The iommu
>>> driver may need to know the dma_address requirements of its iommu
>>> consumer devices.
>>>
>>> CC: Rob Herring <robh+dt@kernel.org>
>>> CC: Frank Rowand <frowand.list@gmail.com>
>>> Signed-off-by: Yong Wu <yong.wu@mediatek.com>
>>> ---
>>> drivers/of/device.c | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/of/device.c b/drivers/of/device.c
>>> index aedfaaafd3e7..1d84636149df 100644
>>> --- a/drivers/of/device.c
>>> +++ b/drivers/of/device.c
>>> @@ -170,9 +170,11 @@ int of_dma_configure_id(struct device *dev, struct device_node *np,
>>> dev_dbg(dev, "device is%sdma coherent\n",
>>> coherent ? " " : " not ");
>>>
>>> + dev->dma_range_map = map;
>>> iommu = of_iommu_configure(dev, np, id);
>>> if (PTR_ERR(iommu) == -EPROBE_DEFER) {
>>> kfree(map);
>>> + dev->dma_range_map = NULL;
>>
>> Not really going to matter, but you should probably clear dma_range_map
>> before what it points to is freed.
>>
>> With that,
>>
>> Reviewed-by: Rob Herring <robh@kernel.org>
>
> Thanks for the review. I will move it before "kfree(map)" in next
> version.
Paul noticed that we already have a bug in assigning to this
unconditionally[1] - I'd totally forgotten about this series when I
theorised about IOMMU drivers wanting the information earlier, but
sweeping my inbox now only goes to show I was right to think of it :)
We should really get something in as a fix independent of this series,
taking both angles into account.
Robin.
[1]
https://lore.kernel.org/linux-arm-kernel/5c7946f3-b56e-da00-a750-be097c7ceb32@arm.com/
>>
>>> return -EPROBE_DEFER;
>>> }
>>>
>>> @@ -181,7 +183,6 @@ int of_dma_configure_id(struct device *dev, struct device_node *np,
>>>
>>> arch_setup_dma_ops(dev, dma_start, size, iommu, coherent);
>>>
>>> - dev->dma_range_map = map;
>>> return 0;
>>> }
>>> EXPORT_SYMBOL_GPL(of_dma_configure_id);
>>> --
>>> 2.18.0
>>>
>
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
>
_______________________________________________
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:[~2021-01-18 15:52 UTC|newest]
Thread overview: 206+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 11:18 [PATCH v6 00/33] MT8192 IOMMU support Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 01/33] dt-bindings: iommu: mediatek: Convert IOMMU to DT schema Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 02/33] dt-bindings: memory: mediatek: Add a common memory header file Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 03/33] dt-bindings: memory: mediatek: Extend LARB_NR_MAX to 32 Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 04/33] dt-bindings: memory: mediatek: Rename header guard for SMI header file Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 05/33] dt-bindings: mediatek: Add binding for mt8192 IOMMU Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 06/33] of/device: Move dma_range_map before of_iommu_configure Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-14 19:27 ` Rob Herring
2021-01-14 19:27 ` Rob Herring
2021-01-14 19:27 ` Rob Herring
2021-01-14 19:27 ` Rob Herring
2021-01-15 5:30 ` Yong Wu
2021-01-15 5:30 ` Yong Wu
2021-01-15 5:30 ` Yong Wu
2021-01-15 5:30 ` Yong Wu
2021-01-18 15:49 ` Robin Murphy [this message]
2021-01-18 15:49 ` Robin Murphy
2021-01-18 15:49 ` Robin Murphy
2021-01-18 15:49 ` Robin Murphy
2021-01-19 9:13 ` Paul Kocialkowski
2021-01-19 9:13 ` Paul Kocialkowski
2021-01-19 9:13 ` Paul Kocialkowski
2021-01-19 9:13 ` Paul Kocialkowski
2021-01-19 9:20 ` Yong Wu
2021-01-19 9:20 ` Yong Wu
2021-01-19 9:20 ` Yong Wu
2021-01-19 9:20 ` Yong Wu
2021-01-19 9:37 ` Paul Kocialkowski
2021-01-19 9:37 ` Paul Kocialkowski
2021-01-19 9:37 ` Paul Kocialkowski
2021-01-19 9:37 ` Paul Kocialkowski
2021-01-11 11:18 ` [PATCH v6 07/33] iommu: Avoid reallocate default domain for a group Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-26 22:23 ` Will Deacon
2021-01-26 22:23 ` Will Deacon
2021-01-26 22:23 ` Will Deacon
2021-01-26 22:23 ` Will Deacon
2021-01-27 9:39 ` Yong Wu
2021-01-27 9:39 ` Yong Wu
2021-01-27 9:39 ` Yong Wu
2021-01-27 9:39 ` Yong Wu
2021-01-28 21:10 ` Will Deacon
2021-01-28 21:10 ` Will Deacon
2021-01-28 21:10 ` Will Deacon
2021-01-28 21:10 ` Will Deacon
2021-01-28 21:14 ` Will Deacon
2021-01-28 21:14 ` Will Deacon
2021-01-28 21:14 ` Will Deacon
2021-01-28 21:14 ` Will Deacon
2021-01-29 0:03 ` Robin Murphy
2021-01-29 0:03 ` Robin Murphy
2021-01-29 0:03 ` Robin Murphy
2021-01-29 0:03 ` Robin Murphy
2021-01-29 1:52 ` Yong Wu
2021-01-29 1:52 ` Yong Wu
2021-01-29 1:52 ` Yong Wu
2021-01-29 1:52 ` Yong Wu
2021-01-29 8:47 ` Will Deacon
2021-01-29 8:47 ` Will Deacon
2021-01-29 8:47 ` Will Deacon
2021-01-11 11:18 ` [PATCH v6 08/33] iommu/mediatek: Use the common mtk-memory-port.h Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 09/33] iommu/io-pgtable-arm-v7s: Use ias to check the valid iova in unmap Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 10/33] iommu/io-pgtable-arm-v7s: Extend PA34 for MediaTek Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 11/33] iommu/io-pgtable-arm-v7s: Clarify LVL_SHIFT/BITS macro Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 12/33] iommu/io-pgtable-arm-v7s: Add cfg as a param in some macros Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 13/33] iommu/io-pgtable-arm-v7s: Quad lvl1 pgtable for MediaTek Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 14/33] iommu/mediatek: Add a flag for iova 34bits case Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 15/33] iommu/mediatek: Update oas for v7s Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 16/33] iommu/mediatek: Move hw_init into attach_device Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 17/33] iommu/mediatek: Add error handle for mtk_iommu_probe Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` [PATCH v6 18/33] iommu/mediatek: Add device link for smi-common and m4u Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:18 ` Yong Wu
2021-01-11 11:19 ` [PATCH v6 19/33] iommu/mediatek: Add pm runtime callback Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` [PATCH v6 20/33] iommu/mediatek: Add power-domain operation Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` [PATCH v6 21/33] iommu/mediatek: Support up to 34bit iova in tlb flush Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` [PATCH v6 22/33] iommu/mediatek: Support report iova 34bit translation fault in ISR Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` [PATCH v6 23/33] iommu/mediatek: Adjust the structure Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` [PATCH v6 24/33] iommu/mediatek: Move domain_finalise into attach_device Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` [PATCH v6 25/33] iommu/mediatek: Move geometry.aperture updating into domain_finalise Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` [PATCH v6 26/33] iommu/mediatek: Add iova_region structure Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` [PATCH v6 27/33] iommu/mediatek: Add get_domain_id from dev->dma_range_map Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` [PATCH v6 28/33] iommu/mediatek: Support for multi domains Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` [PATCH v6 29/33] iommu/mediatek: Add iova reserved function Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` [PATCH v6 30/33] iommu/mediatek: Support master use iova over 32bit Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` [PATCH v6 31/33] iommu/mediatek: Remove unnecessary check in attach_device Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` [PATCH v6 32/33] iommu/mediatek: Add mt8192 support Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` [PATCH v6 33/33] MAINTAINERS: Add entry for MediaTek IOMMU Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-11 11:19 ` Yong Wu
2021-01-26 22:25 ` [PATCH v6 00/33] MT8192 IOMMU support Will Deacon
2021-01-26 22:25 ` Will Deacon
2021-01-26 22:25 ` Will Deacon
2021-01-26 22:25 ` Will Deacon
2021-01-29 11:27 ` Tomasz Figa
2021-01-29 11:27 ` Tomasz Figa
2021-01-29 11:27 ` Tomasz Figa
2021-02-01 14:54 ` Will Deacon
2021-02-01 14:54 ` Will Deacon
2021-02-01 14:54 ` Will Deacon
2021-02-01 14:54 ` Will Deacon
2021-02-02 2:03 ` Yong Wu
2021-02-02 2:03 ` Yong Wu
2021-02-02 2:03 ` Yong Wu
2021-02-02 2:03 ` Yong Wu
2021-02-02 13:33 ` Will Deacon
2021-02-02 13:33 ` Will Deacon
2021-02-02 13:33 ` Will Deacon
2021-02-02 13:33 ` Will Deacon
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=1853732d-0efd-171e-9e1f-7ee7ed72a98f@arm.com \
--to=robin.murphy@arm.com \
--cc=anan.sun@mediatek.com \
--cc=chao.hao@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=evgreen@chromium.org \
--cc=frowand.list@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=robh@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@google.com \
--cc=will@kernel.org \
--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: link
Be 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.