From: Adrian Hunter <adrian.hunter@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Felipe Balbi <balbi@ti.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
linux-usb@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [resend PATCH 1/3] ACPI / platform: provide default DMA mask
Date: Wed, 22 Oct 2014 10:33:08 +0300 [thread overview]
Message-ID: <54475DB4.5000005@intel.com> (raw)
In-Reply-To: <54465C0E.50801@intel.com>
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@linux.intel.com>
>>>>> Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
>>>>
>>>> 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",
>>>>>
>>>>
>>>
>>
>
>
>
next prev parent reply other threads:[~2014-10-22 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 8:00 [resend PATCH 0/3] usb: dwc3: ACPI support Heikki Krogerus
2014-09-24 8:00 ` [resend PATCH 1/3] ACPI / platform: provide default DMA mask Heikki Krogerus
2014-09-24 13:49 ` Rafael J. Wysocki
2014-10-21 12:27 ` Adrian Hunter
2014-10-21 13:08 ` Rafael J. Wysocki
2014-10-21 13:13 ` Adrian Hunter
2014-10-22 7:33 ` Adrian Hunter [this message]
2014-10-22 14:19 ` Rafael J. Wysocki
2014-10-23 15:06 ` Felipe Balbi
2014-10-23 21:29 ` Rafael J. Wysocki
2014-09-24 8:00 ` [resend PATCH 2/3] usb: dwc3: core: only setting the dma_mask when needed Heikki Krogerus
2014-09-24 8:00 ` [resend PATCH 3/3] usb: dwc3: add ACPI support Heikki Krogerus
2014-09-24 14:50 ` Felipe Balbi
2014-09-25 7:57 ` [PATCHv2 " Heikki Krogerus
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=54475DB4.5000005@intel.com \
--to=adrian.hunter@intel.com \
--cc=balbi@ti.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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