[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTin0eBk1tMDUJQQ6KuM6eOu1gu+JmwY-Nz0V+jw8@mail.gmail.com>
Date: Tue, 14 Dec 2010 17:08:42 +0200
From: Felipe Contreras <felipe.contreras@...il.com>
To: Fernando Guzman Lugo <fernando.lugo@...com>
Cc: Hiroshi.DOYU@...ia.com, linux@....linux.org.uk, h-kanigeri2@...com,
felipe.contreras@...ia.com, linux-kernel@...r.kernel.org,
linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
tony@...mide.com, "Guzman Lugo, Fernando" <x0095840@...com>
Subject: Re: [PATCHv6 4/4] omap: iommu - create new api to set valid da range
On Tue, Dec 14, 2010 at 3:07 PM, Fernando Guzman Lugo
<fernando.lugo@...com> wrote:
> From: Guzman Lugo, Fernando <x0095840@...com>
>
> Some IOMMUs cannot use the whole 0x0 - 0xFFFFFFFF rage.
> With this new API the valid range can be set.
>
> Signed-off-by: Fernando Guzman Lugo <x0095840@...com>
> Acked-by: Hiroshi DOYU <Hiroshi.DOYU@...ia.com>
I still don't see where this API is being used.
Also, the point of using platform data was to add it to omap3_devices
in omap-iommu.c, see[1]. I thought the platform data start/end would
move to struct iommu, and iommu_set_da_range would change the
start/end on struct iommu, but that would only be necessary if the
platform data doesn't match that.
If there's no sensible platform data default, then there's no point in
using platform data, as the platform is not the limiting factor, but
the DSP SW.
[1] http://article.gmane.org/gmane.linux.kernel/1051268
--
Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists