public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Suman Anna <s-anna@ti.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	Joerg Roedel <jroedel@suse.de>
Subject: Re: [PATCH 2/5] iommu/omap: Permanently keep iommu_dev pointer in arch_data
Date: Fri, 7 Apr 2017 16:35:20 +0200	[thread overview]
Message-ID: <20170407143520.GB7266@8bytes.org> (raw)
In-Reply-To: <c3305742-b927-c789-c7c2-883f98a77ada@ti.com>

Hi Suman,

On Mon, Apr 03, 2017 at 03:35:46PM -0500, Suman Anna wrote:
> > +	iommu = platform_get_drvdata(pdev);
> > +	if (!iommu) {
> > +		of_node_put(np);
> > +		return -EINVAL;
> > +	}
> 
> This change is causing the issues. OMAP IOMMU driver is not probed yet,
> but this gets called during the driver's init function in
> bus_set_iommu() and bus's iommu_ops gets set to NULL. The add_device
> today is used to add the linking to an IOMMU device (currently name
> primarily to support the legacy non-DT mode which is no longer an issue,
> but a dev pointer can be used instead here, and the real enabling is
> done during the domain's attach_dev callback.

Yeah, okay. Solving this problem requires more sophisticated handling in
the iommu core code, which is not implemented yet.

I drop this patch for now and do the device-linking and group-handling
in attach_dev. This makes iommu-groups on omap useless for now, but it
is a start.


	Joerg

  reply	other threads:[~2017-04-07 14:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31 12:10 [PATCH 0/5] iommu/omap: Add support for iommu-groups and 'struct iommu_device' Joerg Roedel
2017-03-31 12:10 ` [PATCH 1/5] iommu/omap: Move data structures to omap-iommu.h Joerg Roedel
2017-04-03 17:22   ` Suman Anna
2017-03-31 12:10 ` [PATCH 2/5] iommu/omap: Permanently keep iommu_dev pointer in arch_data Joerg Roedel
2017-04-03 20:35   ` Suman Anna
2017-04-07 14:35     ` Joerg Roedel [this message]
2017-03-31 12:10 ` [PATCH 3/5] iommu/omap: Set dev->archdata.iommu = NULL in omap_iommu_remove_device Joerg Roedel
2017-04-03 18:25   ` Suman Anna
2017-03-31 12:10 ` [PATCH 4/5] iommu/omap: Make use of 'struct iommu_device' Joerg Roedel
2017-03-31 12:10 ` [PATCH 5/5] iommu/omap: Add iommu-group support Joerg Roedel
2017-04-03 17:09 ` [PATCH 0/5] iommu/omap: Add support for iommu-groups and 'struct iommu_device' Suman Anna

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=20170407143520.GB7266@8bytes.org \
    --to=joro@8bytes.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jroedel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s-anna@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox