From: Lars-Peter Clausen <lars@metafoo.de>
To: Lee Jones <lee.jones@linaro.org>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org,
linus.walleij@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ASoC: ux500_pcm: Differentiate between pdata and DT initialisation
Date: Tue, 03 Dec 2013 13:15:50 +0100 [thread overview]
Message-ID: <529DCB76.4070705@metafoo.de> (raw)
In-Reply-To: <20131203120420.GC12031@lee--X1>
On 12/03/2013 01:04 PM, Lee Jones wrote:
> On Tue, 03 Dec 2013, Lars-Peter Clausen wrote:
>
>> On 12/03/2013 11:27 AM, Lee Jones wrote:
>>> If booting with full DT support (i.e. DMA too, the last piece of the
>>> puzzle), then we don't need to use the compatible_request_channel call
>>> back or require some of the historical bumph which probably isn't
>>> required by a platform data start-up now either. This will also be
>>> ripped out in upcoming commits.
>>>
>>> Cc: alsa-devel@alsa-project.org
>>> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>>> Signed-off-by: Lee Jones <lee.jones@linaro.org>
>>
>> Strictly speaking you do not need the second config, but well considering
>> that this will all hopefully be removed soon anyway it should be fine.
>
> That's true it will, but why don't we need the second config? I won't
> want the compat function to be called in the DT case.
It will only be called if it was not possible to request the DMA channel
from the DT.
- Lars
WARNING: multiple messages have this Message-ID (diff)
From: lars@metafoo.de (Lars-Peter Clausen)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH 1/2] ASoC: ux500_pcm: Differentiate between pdata and DT initialisation
Date: Tue, 03 Dec 2013 13:15:50 +0100 [thread overview]
Message-ID: <529DCB76.4070705@metafoo.de> (raw)
In-Reply-To: <20131203120420.GC12031@lee--X1>
On 12/03/2013 01:04 PM, Lee Jones wrote:
> On Tue, 03 Dec 2013, Lars-Peter Clausen wrote:
>
>> On 12/03/2013 11:27 AM, Lee Jones wrote:
>>> If booting with full DT support (i.e. DMA too, the last piece of the
>>> puzzle), then we don't need to use the compatible_request_channel call
>>> back or require some of the historical bumph which probably isn't
>>> required by a platform data start-up now either. This will also be
>>> ripped out in upcoming commits.
>>>
>>> Cc: alsa-devel at alsa-project.org
>>> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>>> Signed-off-by: Lee Jones <lee.jones@linaro.org>
>>
>> Strictly speaking you do not need the second config, but well considering
>> that this will all hopefully be removed soon anyway it should be fine.
>
> That's true it will, but why don't we need the second config? I won't
> want the compat function to be called in the DT case.
It will only be called if it was not possible to request the DMA channel
from the DT.
- Lars
WARNING: multiple messages have this Message-ID (diff)
From: Lars-Peter Clausen <lars@metafoo.de>
To: Lee Jones <lee.jones@linaro.org>
Cc: alsa-devel@alsa-project.org, linus.walleij@linaro.org,
broonie@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [alsa-devel] [PATCH 1/2] ASoC: ux500_pcm: Differentiate between pdata and DT initialisation
Date: Tue, 03 Dec 2013 13:15:50 +0100 [thread overview]
Message-ID: <529DCB76.4070705@metafoo.de> (raw)
In-Reply-To: <20131203120420.GC12031@lee--X1>
On 12/03/2013 01:04 PM, Lee Jones wrote:
> On Tue, 03 Dec 2013, Lars-Peter Clausen wrote:
>
>> On 12/03/2013 11:27 AM, Lee Jones wrote:
>>> If booting with full DT support (i.e. DMA too, the last piece of the
>>> puzzle), then we don't need to use the compatible_request_channel call
>>> back or require some of the historical bumph which probably isn't
>>> required by a platform data start-up now either. This will also be
>>> ripped out in upcoming commits.
>>>
>>> Cc: alsa-devel@alsa-project.org
>>> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>>> Signed-off-by: Lee Jones <lee.jones@linaro.org>
>>
>> Strictly speaking you do not need the second config, but well considering
>> that this will all hopefully be removed soon anyway it should be fine.
>
> That's true it will, but why don't we need the second config? I won't
> want the compat function to be called in the DT case.
It will only be called if it was not possible to request the DMA channel
from the DT.
- Lars
next prev parent reply other threads:[~2013-12-03 12:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 10:27 [PATCH 1/2] ASoC: ux500_pcm: Differentiate between pdata and DT initialisation Lee Jones
2013-12-03 10:27 ` Lee Jones
2013-12-03 10:27 ` [PATCH 2/2] ASoC: ux500: Dynamically fill DAI driver data on probe Lee Jones
2013-12-03 10:27 ` Lee Jones
2013-12-03 11:55 ` [alsa-devel] [PATCH 1/2] ASoC: ux500_pcm: Differentiate between pdata and DT initialisation Lars-Peter Clausen
2013-12-03 11:55 ` Lars-Peter Clausen
2013-12-03 12:04 ` Lee Jones
2013-12-03 12:04 ` Lee Jones
2013-12-03 12:15 ` Lars-Peter Clausen [this message]
2013-12-03 12:15 ` Lars-Peter Clausen
2013-12-03 12:15 ` Lars-Peter Clausen
2013-12-03 12:24 ` Lars-Peter Clausen
2013-12-03 12:24 ` Lars-Peter Clausen
2013-12-03 12:29 ` Lee Jones
2013-12-03 12:29 ` Lee Jones
2013-12-03 15:07 ` Mark Brown
2013-12-03 15:07 ` Mark Brown
2013-12-03 15:07 ` Mark Brown
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=529DCB76.4070705@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.