public inbox for iommu@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Joerg Roedel <joro@8bytes.org>, iommu@lists.linux-foundation.org
Cc: Joerg Roedel <jroedel@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/9] ACPI/IORT: Use helper functions to access dev->iommu_fwspec
Date: Wed, 5 Dec 2018 17:50:23 +0000	[thread overview]
Message-ID: <ecfaa990-9257-0592-ee4d-ca3f8537783d@arm.com> (raw)
In-Reply-To: <20181204163002.15800-3-joro@8bytes.org>

On 04/12/2018 16:29, Joerg Roedel wrote:
> From: Joerg Roedel <jroedel@suse.de>
> 
> Use the new helpers dev_iommu_fwspec_get()/set() to access
> the dev->iommu_fwspec pointer. This makes it easier to move
> that pointer later into another struct.
> 
> Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> Signed-off-by: Joerg Roedel <jroedel@suse.de>
> ---
>   drivers/acpi/arm64/iort.c | 12 +++++++-----
>   1 file changed, 7 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c
> index 70f4e80b9246..754a67ba49e5 100644
> --- a/drivers/acpi/arm64/iort.c
> +++ b/drivers/acpi/arm64/iort.c
> @@ -779,7 +779,7 @@ static inline bool iort_iommu_driver_enabled(u8 type)
>   static struct acpi_iort_node *iort_get_msi_resv_iommu(struct device *dev)
>   {
>   	struct acpi_iort_node *iommu;
> -	struct iommu_fwspec *fwspec = dev->iommu_fwspec;
> +	struct iommu_fwspec *fwspec = dev_iommu_fwspec_get(dev);
>   
>   	iommu = iort_get_iort_node(fwspec->iommu_fwnode);
>   
> @@ -824,6 +824,7 @@ static inline int iort_add_device_replay(const struct iommu_ops *ops,
>    */
>   int iort_iommu_msi_get_resv_regions(struct device *dev, struct list_head *head)
>   {
> +	struct iommu_fwspec *fwspec = dev_iommu_fwspec_get(dev);
>   	struct acpi_iort_its_group *its;
>   	struct acpi_iort_node *iommu_node, *its_node = NULL;
>   	int i, resv = 0;
> @@ -841,9 +842,9 @@ int iort_iommu_msi_get_resv_regions(struct device *dev, struct list_head *head)
>   	 * a given PCI or named component may map IDs to.
>   	 */
>   
> -	for (i = 0; i < dev->iommu_fwspec->num_ids; i++) {
> +	for (i = 0; i < fwspec->num_ids; i++) {
>   		its_node = iort_node_map_id(iommu_node,
> -					dev->iommu_fwspec->ids[i],
> +					fwspec->ids[i],
>   					NULL, IORT_MSI_TYPE);
>   		if (its_node)
>   			break;
> @@ -1036,6 +1037,7 @@ void iort_dma_setup(struct device *dev, u64 *dma_addr, u64 *dma_size)
>    */
>   const struct iommu_ops *iort_iommu_configure(struct device *dev)
>   {
> +	struct iommu_fwspec *fwspec = dev_iommu_fwspec_get(dev);
>   	struct acpi_iort_node *node, *parent;
>   	const struct iommu_ops *ops;
>   	u32 streamid = 0;
> @@ -1045,7 +1047,7 @@ const struct iommu_ops *iort_iommu_configure(struct device *dev)
>   	 * If we already translated the fwspec there
>   	 * is nothing left to do, return the iommu_ops.
>   	 */
> -	ops = iort_fwspec_iommu_ops(dev->iommu_fwspec);
> +	ops = iort_fwspec_iommu_ops(fwspec);
>   	if (ops)
>   		return ops;
>   
> @@ -1084,7 +1086,7 @@ const struct iommu_ops *iort_iommu_configure(struct device *dev)
>   	 * add_device callback for dev, replay it to get things in order.
>   	 */
>   	if (!err) {
> -		ops = iort_fwspec_iommu_ops(dev->iommu_fwspec);
> +		ops = iort_fwspec_iommu_ops(fwspec);

This needs to reload the new fwspec initialised by iort_iommu_xlate(), 
in the same manner as the OF code. I think the best thing to do is 
encapsulate the dev_iommu_fwspec_get() call in iort_fwspec_iommu_ops(), 
and have that take dev as its argument directly.

Robin.

>   		err = iort_add_device_replay(ops, dev);
>   	}
>   
> 

  reply	other threads:[~2018-12-05 17:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 16:29 [PATCH 0/9] Access dev->iommu_fwspec through functions Joerg Roedel
2018-12-04 16:29 ` [PATCH 1/9] iommu: Introduce wrappers around dev->iommu_fwspec Joerg Roedel
2018-12-04 16:29 ` [PATCH 3/9] iommu/arm-smmu: Use helper functions to access dev->iommu_fwspec Joerg Roedel
     [not found]   ` <20181204163002.15800-4-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2018-12-06 13:11     ` Will Deacon
     [not found] ` <20181204163002.15800-1-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2018-12-04 16:29   ` [PATCH 2/9] ACPI/IORT: " Joerg Roedel
2018-12-05 17:50     ` Robin Murphy [this message]
     [not found]       ` <ecfaa990-9257-0592-ee4d-ca3f8537783d-5wv7dgnIgG8@public.gmane.org>
2018-12-06 13:53         ` Joerg Roedel
2018-12-04 16:29   ` [PATCH 4/9] iommu/dma: " Joerg Roedel
2018-12-04 16:29 ` [PATCH 5/9] iommu/ipmmu-vmsa: " Joerg Roedel
2018-12-04 16:29 ` [PATCH 6/9] iommu/mediatek: " Joerg Roedel
2018-12-04 16:30 ` [PATCH 7/9] iommu/of: " Joerg Roedel
2018-12-05 17:41   ` Robin Murphy
2018-12-06 14:16     ` Joerg Roedel
2018-12-04 16:30 ` [PATCH 8/9] iommu/qcom: " Joerg Roedel
2018-12-04 16:30 ` [PATCH 9/9] iommu/tegra: " Joerg Roedel
  -- strict thread matches above, loose matches on Subject: below --
2018-12-11 12:19 [PATCH 0/9 v2] Access dev->iommu_fwspec through functions Joerg Roedel
     [not found] ` <20181211121910.5604-1-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2018-12-11 12:19   ` [PATCH 2/9] ACPI/IORT: Use helper functions to access dev->iommu_fwspec Joerg Roedel
2018-12-17  9:17     ` Hanjun Guo

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=ecfaa990-9257-0592-ee4d-ca3f8537783d@arm.com \
    --to=robin.murphy@arm.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=jroedel@suse.de \
    --cc=linux-kernel@vger.kernel.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