From: joro@8bytes.org (joro at 8bytes.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: IOMMU: Tegra20: Add iommu_ops for GART driver
Date: Thu, 26 Jan 2012 12:58:13 +0100 [thread overview]
Message-ID: <20120126115813.GF6269@8bytes.org> (raw)
In-Reply-To: <20120125.094020.983282777619146490.hdoyu@nvidia.com>
On Wed, Jan 25, 2012 at 08:40:20AM +0100, Hiroshi Doyu wrote:
> From: Hiroshi DOYU <hdoyu@nvidia.com>
> Date: Wed, 16 Nov 2011 17:36:37 +0200
> Subject: [PATCH 1/2] ARM: IOMMU: Tegra20: Add iommu_ops for GART driver
>
> Tegra 20 IOMMU H/W, GART (Graphics Address Relocation Table). This
> patch implements struct iommu_ops for GART for the upper IOMMU API.
>
> This H/W module supports only single virtual address space(domain),
> and manages a single level 1-to-1 mapping H/W translation page table.
Thanks. Applied with a few minor changes and fixes. Please see below.
> +config TEGRA_IOMMU_GART
> + bool "Tegra GART IOMMU Support"
> + depends on ARCH_TEGRA_2x_SOC
> + default y
I removed 'default y'. New drivers shouldn't be selected by default.
> +static int gart_iommu_map(struct iommu_domain *domain, unsigned long iova,
> + phys_addr_t pa, size_t bytes, int prot)
> +{
> + struct gart_device *gart = domain->priv;
> + unsigned long flags;
> + unsigned long pfn;
> +
> + if (!gart_iova_range_valid(gart, iova, bytes))
> + return -EINVAL;
> +
> + spin_lock_irqsave(&gart->pte_lock, flags);
> + pfn = __phys_to_pfn(pa);
> + if (!pfn_valid(pfn)) {
> + dev_err(gart->dev, "Invalid page: %08x\n", pa);
> + spin_unlock(&gart->pte_lock);
Changed this to spin_unlock_irqrestore().
> + return -EINVAL;
> + }
> + gart_set_pte(gart, iova, GART_PTE(pfn));
> + FLUSH_GART_REGS(gart);
> + spin_unlock_irqrestore(&gart->pte_lock, flags);
> + return 0;
> +}
> +
> +static size_t gart_iommu_unmap(struct iommu_domain *domain, unsigned long iova,
> + size_t bytes)
> +{
> + struct gart_device *gart = domain->priv;
> + unsigned long flags;
> +
> + if (!gart_iova_range_valid(gart, iova, bytes))
> + return -EINVAL;
Return 0 here instead of -EINVAL. Size_t is unsigned and the unmap path
returns 0 on failure.
next prev parent reply other threads:[~2012-01-26 11:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 7:11 [PATCH v3 0/2] ARM: IOMMU: tegra: Add iommu_ops for GART/SMMU driver Hiroshi DOYU
2012-01-05 7:11 ` [PATCH 1/2] ARM: IOMMU: Tegra20: Add iommu_ops for GART driver Hiroshi DOYU
2012-01-23 15:00 ` Joerg Roedel
2012-01-25 7:40 ` Hiroshi Doyu
2012-01-26 11:58 ` joro at 8bytes.org [this message]
2012-01-26 14:45 ` Hiroshi Doyu
2012-01-05 7:11 ` [PATCH 2/2] ARM: IOMMU: Tegra30: Add iommu_ops for SMMU driver Hiroshi DOYU
2012-01-23 15:43 ` Joerg Roedel
2012-01-24 9:57 ` Hiroshi Doyu
2012-01-24 11:04 ` Joerg Roedel
2012-01-24 11:36 ` Hiroshi Doyu
2012-01-24 11:57 ` joerg.roedel at amd.com
2012-01-24 12:07 ` Hiroshi Doyu
2012-01-24 13:41 ` Hiroshi Doyu
2012-01-24 13:46 ` Felipe Balbi
2012-01-24 14:25 ` joro at 8bytes.org
2012-01-25 7:39 ` Hiroshi Doyu
2012-01-26 14:59 ` joro at 8bytes.org
2012-01-05 7:17 ` [PATCH v3 0/2] ARM: IOMMU: tegra: Add iommu_ops for GART/SMMU driver Hiroshi Doyu
2012-01-05 12:53 ` Russell King - ARM Linux
2012-01-05 14:29 ` Hiroshi Doyu
2012-01-05 14:46 ` Russell King - ARM Linux
2012-01-11 14:24 ` Hiroshi Doyu
2012-01-09 0:39 ` KyongHo Cho
2012-01-09 11:45 ` Russell King - ARM Linux
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=20120126115813.GF6269@8bytes.org \
--to=joro@8bytes.org \
--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).