On Thu, May 7, 2015 at 1:52 AM, Suravee Suthikulanit
wrote:
> Rafael,
>
> Any comments on this patch?
Well, as long as acpi_dma_is_coherent() does the right thing on all
architectures, I have no objections.
Thanks,
Rafael
> On 5/5/2015 10:12 AM, Suravee Suthikulpanit wrote:
>>
>> Currently,
Rafael,
Any comments on this patch?
Thanks,
Suravee
On 5/5/2015 10:12 AM, Suravee Suthikulpanit wrote:
Currently, device drivers, which support both OF and ACPI,
need to call two separate APIs, of_dma_is_coherent() and
acpi_dma_is_coherent()) to determine device coherency attribute.
This
Rafael,
Any comments on this patch?
Thanks,
Suravee
On 5/5/2015 10:12 AM, Suravee Suthikulpanit wrote:
Currently, device drivers, which support both OF and ACPI,
need to call two separate APIs, of_dma_is_coherent() and
acpi_dma_is_coherent()) to determine device coherency attribute.
This
On Thu, May 7, 2015 at 1:52 AM, Suravee Suthikulanit
suravee.suthikulpa...@amd.com wrote:
Rafael,
Any comments on this patch?
Well, as long as acpi_dma_is_coherent() does the right thing on all
architectures, I have no objections.
Thanks,
Rafael
On 5/5/2015 10:12 AM, Suravee Suthikulpanit
Currently, device drivers, which support both OF and ACPI,
need to call two separate APIs, of_dma_is_coherent() and
acpi_dma_is_coherent()) to determine device coherency attribute.
This patch simplifies this process by introducing a new device
property API, device_dma_is_coherent(), which calls
Currently, device drivers, which support both OF and ACPI,
need to call two separate APIs, of_dma_is_coherent() and
acpi_dma_is_coherent()) to determine device coherency attribute.
This patch simplifies this process by introducing a new device
property API, device_dma_is_coherent(), which calls
6 matches
Mail list logo
