On Wed, Dec 3, 2014 at 3:22 PM, Dylan Reid wrote:
> On Wed, Dec 3, 2014 at 3:03 PM, Sonny Rao wrote:
>> On Wed, Dec 3, 2014 at 12:03 PM, Mark Brown wrote:
>>> On Wed, Dec 03, 2014 at 11:38:13AM -0800, Sonny Rao wrote:
On Wed, Dec 3, 2014 at 11:20 AM, Mark Brown wrote:
>>>
> I would
On Wed, Dec 3, 2014 at 3:03 PM, Sonny Rao wrote:
> On Wed, Dec 3, 2014 at 12:03 PM, Mark Brown wrote:
>> On Wed, Dec 03, 2014 at 11:38:13AM -0800, Sonny Rao wrote:
>>> On Wed, Dec 3, 2014 at 11:20 AM, Mark Brown wrote:
>>
>>> > I would expect that the clock for the CODEC should be managed by
On Wed, Dec 3, 2014 at 12:03 PM, Mark Brown wrote:
> On Wed, Dec 03, 2014 at 11:38:13AM -0800, Sonny Rao wrote:
>> On Wed, Dec 3, 2014 at 11:20 AM, Mark Brown wrote:
>
>> > I would expect that the clock for the CODEC should be managed by the
>> > CODEC if at all possible - that seems more
On Wed, Dec 03, 2014 at 11:38:13AM -0800, Sonny Rao wrote:
> On Wed, Dec 3, 2014 at 11:20 AM, Mark Brown wrote:
> > I would expect that the clock for the CODEC should be managed by the
> > CODEC if at all possible - that seems more logical than having the CPU
> > I2S controller request and
On Wed, Dec 3, 2014 at 11:20 AM, Mark Brown wrote:
> On Wed, Dec 03, 2014 at 03:18:38PM +0800, Jianqun Xu wrote:
>> From: Sonny Rao
>>
>> We need to claim the clock which is driving the codec so that when we enable
>> clock gating, we continue to clock the codec when needed. I make this an
>>
On Wed, Dec 03, 2014 at 03:18:38PM +0800, Jianqun Xu wrote:
> From: Sonny Rao
>
> We need to claim the clock which is driving the codec so that when we enable
> clock gating, we continue to clock the codec when needed. I make this an
> optional clock since there might be some applications where
On Wed, Dec 03, 2014 at 03:18:38PM +0800, Jianqun Xu wrote:
From: Sonny Rao sonny...@chromium.org
We need to claim the clock which is driving the codec so that when we enable
clock gating, we continue to clock the codec when needed. I make this an
optional clock since there might be some
On Wed, Dec 3, 2014 at 11:20 AM, Mark Brown broo...@kernel.org wrote:
On Wed, Dec 03, 2014 at 03:18:38PM +0800, Jianqun Xu wrote:
From: Sonny Rao sonny...@chromium.org
We need to claim the clock which is driving the codec so that when we enable
clock gating, we continue to clock the codec
On Wed, Dec 03, 2014 at 11:38:13AM -0800, Sonny Rao wrote:
On Wed, Dec 3, 2014 at 11:20 AM, Mark Brown broo...@kernel.org wrote:
I would expect that the clock for the CODEC should be managed by the
CODEC if at all possible - that seems more logical than having the CPU
I2S controller
On Wed, Dec 3, 2014 at 12:03 PM, Mark Brown broo...@kernel.org wrote:
On Wed, Dec 03, 2014 at 11:38:13AM -0800, Sonny Rao wrote:
On Wed, Dec 3, 2014 at 11:20 AM, Mark Brown broo...@kernel.org wrote:
I would expect that the clock for the CODEC should be managed by the
CODEC if at all
On Wed, Dec 3, 2014 at 3:03 PM, Sonny Rao sonny...@chromium.org wrote:
On Wed, Dec 3, 2014 at 12:03 PM, Mark Brown broo...@kernel.org wrote:
On Wed, Dec 03, 2014 at 11:38:13AM -0800, Sonny Rao wrote:
On Wed, Dec 3, 2014 at 11:20 AM, Mark Brown broo...@kernel.org wrote:
I would expect that
On Wed, Dec 3, 2014 at 3:22 PM, Dylan Reid dgr...@chromium.org wrote:
On Wed, Dec 3, 2014 at 3:03 PM, Sonny Rao sonny...@chromium.org wrote:
On Wed, Dec 3, 2014 at 12:03 PM, Mark Brown broo...@kernel.org wrote:
On Wed, Dec 03, 2014 at 11:38:13AM -0800, Sonny Rao wrote:
On Wed, Dec 3, 2014 at
From: Sonny Rao
We need to claim the clock which is driving the codec so that when we enable
clock gating, we continue to clock the codec when needed. I make this an
optional clock since there might be some applications where we don't need it
but can still use the I2S block.
Signed-off-by:
From: Sonny Rao sonny...@chromium.org
We need to claim the clock which is driving the codec so that when we enable
clock gating, we continue to clock the codec when needed. I make this an
optional clock since there might be some applications where we don't need it
but can still use the I2S
Hi Jay,
On 11/19/2014 04:09 PM, Jianqun Xu wrote:
Patch is from Sonny Rao
Here should be,
From: Sonny Rao
- Kever
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Hi Jianqun,
Am Mittwoch, 19. November 2014, 16:09:27 schrieb Jianqun Xu:
> Patch is from Sonny Rao
that line above should read exactly:
From: Sonny Rao
that way git will also set the author correctly when importing the patch mbox.
>
> We need to claim the clock which is driving the codec so
Patch is from Sonny Rao
We need to claim the clock which is driving the codec so that when we enable
clock gating, we continue to clock the codec when needed. I make this an
optional clock since there might be some applications where we don't need it
but can still use the I2S block.
Patch is from Sonny Rao sonny...@chromium.org
We need to claim the clock which is driving the codec so that when we enable
clock gating, we continue to clock the codec when needed. I make this an
optional clock since there might be some applications where we don't need it
but can still use the
Hi Jianqun,
Am Mittwoch, 19. November 2014, 16:09:27 schrieb Jianqun Xu:
Patch is from Sonny Rao sonny...@chromium.org
that line above should read exactly:
From: Sonny Rao sonny...@chromium.org
that way git will also set the author correctly when importing the patch mbox.
We need to claim
Hi Jay,
On 11/19/2014 04:09 PM, Jianqun Xu wrote:
Patch is from Sonny Rao sonny...@chromium.org
Here should be,
From: Sonny Rao sonny...@chromium.org
- Kever
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More
20 matches
Mail list logo
