Hi Joerg,
On 10/22/2014 08:29 AM, Joerg Roedel wrote:
> On Tue, Oct 21, 2014 at 04:28:27PM -0500, Suman Anna wrote:
>> I am looking to refresh this series for 3.19, and this is the only patch
>> that may need some changes. Please let me know what your preference is,
>> and I can rework this patch
On Tue, Oct 21, 2014 at 04:28:27PM -0500, Suman Anna wrote:
> I am looking to refresh this series for 3.19, and this is the only patch
> that may need some changes. Please let me know what your preference is,
> and I can rework this patch if needed. Either way,
> the plan is to not have an OMAP IOM
Hi Joerg,
On 10/01/2014 11:07 AM, Anna, Suman wrote:
> Hi Laurent,
>
>> On Tuesday 30 September 2014 16:16:07 Suman Anna wrote:
>>> The debugfs support for OMAP IOMMU is currently implemented
>>> as a module, warranting certain OMAP-specific IOMMU API to
>>> be exported. The OMAP IOMMU, when enab
Hi Laurent,
> On Tuesday 30 September 2014 16:16:07 Suman Anna wrote:
>> The debugfs support for OMAP IOMMU is currently implemented
>> as a module, warranting certain OMAP-specific IOMMU API to
>> be exported. The OMAP IOMMU, when enabled, can only be built-in
>> into the kernel, so integrate the
Hi Suman,
Thank you for the patch.
On Tuesday 30 September 2014 16:16:07 Suman Anna wrote:
> The debugfs support for OMAP IOMMU is currently implemented
> as a module, warranting certain OMAP-specific IOMMU API to
> be exported. The OMAP IOMMU, when enabled, can only be built-in
> into the kernel
The debugfs support for OMAP IOMMU is currently implemented
as a module, warranting certain OMAP-specific IOMMU API to
be exported. The OMAP IOMMU, when enabled, can only be built-in
into the kernel, so integrate the OMAP IOMMU debug module
into the OMAP IOMMU driver. This helps in eliminating the
