All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Julien Grall <julien.grall@arm.com>,
	Oleksandr Tyshchenko <olekstysh@gmail.com>
Cc: xen-devel@lists.xenproject.org, sstabellini@kernel.org,
	volodymyr_babchuk@epam.com,
	Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Subject: Re: [Xen-devel] [PATCH V6 7/8] iommu/arm: Introduce iommu_add_dt_device API
Date: Thu, 26 Sep 2019 16:34:10 +0200	[thread overview]
Message-ID: <533737e0-ff60-c6a3-f38d-f4b7ffb1581b@suse.com> (raw)
In-Reply-To: <55a32546-9a54-c326-f4ae-83c0dc5fb69d@arm.com>

On 26.09.2019 14:52, Julien Grall wrote:
> On 9/26/19 12:20 PM, Oleksandr Tyshchenko wrote:
>> From: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
>>
>> The main puprose of this patch is to add a way to register DT device
>> (which is behind the IOMMU) using the generic IOMMU DT bindings [1]
>> before assigning that device to a domain.
>>
>> So, this patch adds new "iommu_add_dt_device" API for adding DT device
>> to the IOMMU using generic IOMMU DT bindings and previously added
>> "iommu_fwspec" support. As devices can be assigned to the hardware domain
>> and other domains this function is called from two places: handle_device()
>> and iommu_do_dt_domctl().
>>
>> Besides that, this patch adds new "dt_xlate" callback (borrowed from
>> Linux "of_xlate") for providing the driver with DT IOMMU specifier
>> which describes the IOMMU master interfaces of that device (device IDs, etc).
>> According to the generic IOMMU DT bindings the context of required
>> properties for IOMMU device/master node (#iommu-cells, iommus) depends
>> on many factors and is really driver depended thing.
>>
>> Please note, all IOMMU drivers which support generic IOMMU DT bindings
>> should use "dt_xlate" and "add_device" callbacks.
>>
>> [1] https://www.kernel.org/doc/Documentation/devicetree/bindings/iommu/iommu.txt
>>
>> Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
> 
> Acked-by: Julien Grall <julien.grall@arm.com>

Acked-by: Jan Beulich <jbeulich@suse.com>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2019-09-26 14:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 11:20 [Xen-devel] [PATCH V6 0/8] iommu/arm: Add Renesas IPMMU-VMSA support + Linux's iommu_fwspec Oleksandr Tyshchenko
2019-09-26 11:20 ` [Xen-devel] [PATCH V6 1/8] iommu/arm: Add iommu_helpers.c file to keep common for IOMMUs stuff Oleksandr Tyshchenko
2019-09-26 11:20 ` [Xen-devel] [PATCH V6 2/8] iommu/arm: Add ability to handle deferred probing request Oleksandr Tyshchenko
2019-09-26 11:20 ` [Xen-devel] [PATCH V6 3/8] xen/common: Introduce _xrealloc function Oleksandr Tyshchenko
2019-09-26 12:19   ` Jan Beulich
2019-09-26 13:39     ` Oleksandr
2019-09-26 11:20 ` [Xen-devel] [PATCH V6 4/8] xen/common: Introduce xrealloc_flex_struct() helper macros Oleksandr Tyshchenko
2019-09-26 11:20 ` [Xen-devel] [PATCH V6 5/8] iommu/arm: Add lightweight iommu_fwspec support Oleksandr Tyshchenko
2019-09-26 11:20 ` [Xen-devel] [PATCH V6 6/8] iommu: Order the headers alphabetically in device_tree.c Oleksandr Tyshchenko
2019-09-26 11:20 ` [Xen-devel] [PATCH V6 7/8] iommu/arm: Introduce iommu_add_dt_device API Oleksandr Tyshchenko
2019-09-26 12:52   ` Julien Grall
2019-09-26 13:34     ` Oleksandr
2019-09-26 14:34     ` Jan Beulich [this message]
2019-09-26 11:20 ` [Xen-devel] [PATCH V6 8/8] iommu/arm: Add Renesas IPMMU-VMSA support Oleksandr Tyshchenko
2019-09-26 12:22   ` Jan Beulich
2019-09-26 13:32     ` Oleksandr
2019-09-26 14:56 ` [Xen-devel] [PATCH V6 0/8] iommu/arm: Add Renesas IPMMU-VMSA support + Linux's iommu_fwspec Julien Grall
2019-09-26 15:16   ` Oleksandr
2019-09-27 22:50     ` Stefano Stabellini
2019-09-27 23:52       ` Oleksandr Tyshchenko
2019-09-28  9:36         ` Julien Grall
2019-09-30 20:58           ` Stefano Stabellini
2019-10-01  9:23             ` Oleksandr

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=533737e0-ff60-c6a3-f38d-f4b7ffb1581b@suse.com \
    --to=jbeulich@suse.com \
    --cc=julien.grall@arm.com \
    --cc=oleksandr_tyshchenko@epam.com \
    --cc=olekstysh@gmail.com \
    --cc=sstabellini@kernel.org \
    --cc=volodymyr_babchuk@epam.com \
    --cc=xen-devel@lists.xenproject.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 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.