From: jeffy.chen@rock-chips.com (JeffyChen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 13/13] iommu/rockchip: Support sharing IOMMU between masters
Date: Wed, 17 Jan 2018 21:32:00 +0800 [thread overview]
Message-ID: <5A5F5050.5040308@rock-chips.com> (raw)
In-Reply-To: <1bd5378d-8285-e0d9-8105-f9dd9f8cfdcb@arm.com>
Hi Robin,
On 01/17/2018 09:00 PM, Robin Murphy wrote:
> On 16/01/18 13:25, Jeffy Chen wrote:
>> There would be some masters sharing the same IOMMU device. Put them in
>> the same iommu group and share the same iommu domain.
>>
>> Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
>> ---
>>
>> Changes in v2: None
>>
>> drivers/iommu/rockchip-iommu.c | 39
>> +++++++++++++++++++++++++++++++--------
>> 1 file changed, 31 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/iommu/rockchip-iommu.c
>> b/drivers/iommu/rockchip-iommu.c
>> index c8de1456a016..6c316dd0dd2d 100644
>> --- a/drivers/iommu/rockchip-iommu.c
>> +++ b/drivers/iommu/rockchip-iommu.c
>> @@ -100,11 +100,13 @@ struct rk_iommu {
>> struct iommu_device iommu;
>> struct list_head node; /* entry in rk_iommu_domain.iommus */
>> struct iommu_domain *domain; /* domain to which iommu is
>> attached */
>> + struct iommu_group *group;
>> struct mutex pm_mutex; /* serializes power transitions */
>> };
>> struct rk_iommudata {
>> struct device_link *link; /* runtime PM link from IOMMU to
>> master */
>> + struct iommu_domain *domain; /* domain to which device is
>> attached */
>
> I don't see why this is needed - for example, mtk_iommu does the same
> thing without needing to track the active domain in more than one place.
>
> Fundamentally, for this kind of IOMMU without the notion of multiple
> translation contexts, the logic should look like:
>
> iommudrv_attach_device(dev, domain) {
> iommu = dev_get_iommu(dev);
> if (iommu->curr_domain != domain) {
> update_hw_state(iommu, domain);
> iommu->curr_domain = domain;
> }
> }
>
> which I think is essentially what you have anyway. When a group contains
> multiple devices, you update the IOMMU state for the first device, then
> calls for subsequent devices in the group do nothing since they see the
> IOMMU state is already up-to-date with the new domain.
>
right, will remove it.
> Robin.
prev parent reply other threads:[~2018-01-17 13:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180116132540.18939-1-jeffy.chen@rock-chips.com>
[not found] ` <20180116132540.18939-3-jeffy.chen@rock-chips.com>
2018-01-17 4:23 ` [PATCH v2 02/13] iommu/rockchip: Suppress unbinding Tomasz Figa
2018-01-17 5:32 ` Tomasz Figa
[not found] ` <20180116132540.18939-5-jeffy.chen@rock-chips.com>
2018-01-17 5:22 ` [PATCH v2 04/13] iommu/rockchip: Fix error handling in probe Tomasz Figa
[not found] ` <20180116132540.18939-6-jeffy.chen@rock-chips.com>
2018-01-17 5:26 ` [PATCH v2 05/13] iommu/rockchip: Fix error handling in init Tomasz Figa
[not found] ` <5A5EF7D3.90405@rock-chips.com>
2018-01-17 7:19 ` Tomasz Figa
2018-01-17 12:27 ` Tomasz Figa
2018-01-17 11:36 ` Robin Murphy
[not found] ` <20180116132540.18939-11-jeffy.chen@rock-chips.com>
2018-01-17 5:37 ` [PATCH v2 10/13] iommu/rockchip: Use IOMMU device for dma mapping operations Tomasz Figa
[not found] ` <20180116132540.18939-12-jeffy.chen@rock-chips.com>
2018-01-17 5:44 ` [PATCH v2 11/13] iommu/rockchip: Use OF_IOMMU to attach devices automatically Tomasz Figa
[not found] ` <5A5EF94E.7010806@rock-chips.com>
2018-01-17 7:30 ` Tomasz Figa
2018-01-17 7:47 ` JeffyChen
[not found] ` <20180116132540.18939-13-jeffy.chen@rock-chips.com>
2018-01-17 6:20 ` [PATCH v2 12/13] iommu/rockchip: Add runtime PM support Tomasz Figa
[not found] ` <5A5EFAB2.7040001@rock-chips.com>
2018-01-17 7:38 ` Tomasz Figa
2018-01-17 7:52 ` JeffyChen
2018-01-17 8:48 ` JeffyChen
[not found] ` <20180116132540.18939-2-jeffy.chen@rock-chips.com>
2018-01-17 4:21 ` [PATCH v2 01/13] iommu/rockchip: Request irqs in rk_iommu_probe() Tomasz Figa
[not found] ` <5A5EF672.6040304@rock-chips.com>
2018-01-17 7:16 ` Tomasz Figa
2018-01-17 7:45 ` JeffyChen
2018-01-17 12:18 ` Robin Murphy
2018-01-17 12:46 ` JeffyChen
[not found] ` <20180116132540.18939-10-jeffy.chen@rock-chips.com>
2018-01-17 12:31 ` [PATCH v2 09/13] iommu/rockchip: Use iommu_group_get_for_dev() for add_device Robin Murphy
2018-01-17 12:47 ` JeffyChen
2018-01-17 12:53 ` JeffyChen
[not found] ` <20180116132540.18939-14-jeffy.chen@rock-chips.com>
2018-01-17 13:00 ` [PATCH v2 13/13] iommu/rockchip: Support sharing IOMMU between masters Robin Murphy
2018-01-17 13:32 ` JeffyChen [this message]
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=5A5F5050.5040308@rock-chips.com \
--to=jeffy.chen@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).