public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Florian Vaussard <florian.vaussard@epfl.ch>,
	iommu@lists.linux-foundation.org, linux-omap@vger.kernel.org,
	Suman Anna <s-anna@ti.com>
Subject: [PATCH 0/2] OMAP IOMMU Fixes for DT-clients
Date: Wed, 3 Sep 2014 18:58:30 -0500	[thread overview]
Message-ID: <1409788712-10741-1-git-send-email-s-anna@ti.com> (raw)

Hi,

Following are couple of minor fixes to the OMAP IOMMU driver for DT-based
client devices. The first patch adds an additional check to detect invalid
usage of IOMMU API for devices with no IOMMUs, and the second patch fixes
the failure to attach to an OMAP IOMMU for properly configured DT devices.
The kernel does not yet have any OMAP IOMMU users represented in DT, so
this failure is not currently seen, but will be seen when users like OMAP3
ISP or OMAP4 remoteprocs are converted to DT.

regards
Suman

Suman Anna (2):
  iommu/omap: Check for valid archdata in attach_dev
  iommu/omap: Fix iommu archdata name for DT-based devices

 drivers/iommu/omap-iommu.c | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

-- 
2.0.4


             reply	other threads:[~2014-09-03 23:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-03 23:58 Suman Anna [this message]
     [not found] ` <1409788712-10741-1-git-send-email-s-anna-l0cyMroinI0@public.gmane.org>
2014-09-03 23:58   ` [PATCH 1/2] iommu/omap: Check for valid archdata in attach_dev Suman Anna
     [not found]     ` <1593534.HBLyulJI44@avalon>
2014-09-04 19:37       ` Suman Anna
2014-09-03 23:58   ` [PATCH 2/2] iommu/omap: Fix iommu archdata name for DT-based devices Suman Anna
     [not found]     ` <2755871.jyTSgisx8z@avalon>
2014-09-04 21:17       ` Suman Anna
2014-09-05 11:11         ` Laurent Pinchart

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=1409788712-10741-1-git-send-email-s-anna@ti.com \
    --to=s-anna@ti.com \
    --cc=florian.vaussard@epfl.ch \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-omap@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