On 21/10/14 16:13, Adrian Hunter wrote: > On 21/10/14 16:08, Rafael J. Wysocki wrote: >> On Tuesday, October 21, 2014 03:27:45 PM Adrian Hunter wrote: >>> On 24/09/14 16:49, Rafael J. Wysocki wrote: >>>> On Wednesday, September 24, 2014 11:00:37 AM Heikki Krogerus wrote: >>>>> Most devices are configured for 32-bit DMA addresses. >>>>> Setting the mask to 32-bit here removes the need for the >>>>> drivers to do it separately. >>>>> >>>>> Signed-off-by: Heikki Krogerus <heikki.krogerus@xxxxxxxxxxxxxxx> >>>>> Cc: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx> >>>> >>>> ACK >>> >>> Hi >>> >>> I need this for another driver. Did this patch go anywhere? >> >> It's not in 3.18-rc1 as far as I can say. >> >>> Note Heikki is away at the moment. >> >> That's OK. I guess I can queue up this one for you. >> >> When do you need this to get into the Linus' tree? > > My patches are aiming for 3.19 Actually it would be easier for me if Heikki's patch is already in 3.18, but all I need to know is when it will hit? > >> >> >>>>> --- >>>>> drivers/acpi/acpi_platform.c | 2 ++ >>>>> 1 file changed, 2 insertions(+) >>>>> >>>>> diff --git a/drivers/acpi/acpi_platform.c b/drivers/acpi/acpi_platform.c >>>>> index 2bf9082..8d099e6 100644 >>>>> --- a/drivers/acpi/acpi_platform.c >>>>> +++ b/drivers/acpi/acpi_platform.c >>>>> @@ -16,6 +16,7 @@ >>>>> #include <linux/err.h> >>>>> #include <linux/kernel.h> >>>>> #include <linux/module.h> >>>>> +#include <linux/dma-mapping.h> >>>>> #include <linux/platform_device.h> >>>>> >>>>> #include "internal.h" >>>>> @@ -102,6 +103,7 @@ struct platform_device *acpi_create_platform_device(struct acpi_device *adev) >>>>> pdevinfo.res = resources; >>>>> pdevinfo.num_res = count; >>>>> pdevinfo.acpi_node.companion = adev; >>>>> + pdevinfo.dma_mask = DMA_BIT_MASK(32); >>>>> pdev = platform_device_register_full(&pdevinfo); >>>>> if (IS_ERR(pdev)) >>>>> dev_err(&adev->dev, "platform device creation failed: %ld\n", >>>>> >>>> >>> >> > > > -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
