2013/7/5 Bo Shen :
> Yes, I aware this issue.
> Actually the system not hang, the resource all are occupied by the
> interrupt. This because, we enable the interrupt, when once interrupt occur,
> I try many methods to clear it, however we can not clear it. So, it
> generates the interrupt all the
2013/7/5 Bo Shen voice.s...@atmel.com:
Yes, I aware this issue.
Actually the system not hang, the resource all are occupied by the
interrupt. This because, we enable the interrupt, when once interrupt occur,
I try many methods to clear it, however we can not clear it. So, it
generates the
Hi Richard,
On 7/4/2013 21:44, Richard Genoud wrote:
2013/7/4 Bo Shen :
Hi Richard,
On 7/3/2013 23:51, Richard Genoud wrote:
but there's a violent hang (kernel stops, no trace) when I try the
record :
arecord -v -V stereo -Dplug:default -f cd -t wav -c 2 /tmp/toto.wav
last thing I see is
2013/7/4 Bo Shen :
> Hi Richard,
>
>
> On 7/3/2013 23:51, Richard Genoud wrote:
>>>
>>> >but there's a violent hang (kernel stops, no trace) when I try the
>>> > record :
>>> >arecord -v -V stereo -Dplug:default -f cd -t wav -c 2 /tmp/toto.wav
>>> >last thing I see is :
>>> >dma dma0chan3:
2013/7/4 Bo Shen voice.s...@atmel.com:
Hi Richard,
On 7/3/2013 23:51, Richard Genoud wrote:
but there's a violent hang (kernel stops, no trace) when I try the
record :
arecord -v -V stereo -Dplug:default -f cd -t wav -c 2 /tmp/toto.wav
last thing I see is :
dma dma0chan3: atc_control
Hi Richard,
On 7/4/2013 21:44, Richard Genoud wrote:
2013/7/4 Bo Shen voice.s...@atmel.com:
Hi Richard,
On 7/3/2013 23:51, Richard Genoud wrote:
but there's a violent hang (kernel stops, no trace) when I try the
record :
arecord -v -V stereo -Dplug:default -f cd -t wav -c 2 /tmp/toto.wav
Hi Richard,
On 7/3/2013 23:51, Richard Genoud wrote:
>but there's a violent hang (kernel stops, no trace) when I try the record :
>arecord -v -V stereo -Dplug:default -f cd -t wav -c 2 /tmp/toto.wav
>last thing I see is :
>dma dma0chan3: atc_control (3)
I don't meet this issue. Playback and
2013/7/3 Richard Genoud :
> 2013/7/2 Bo Shen :
>> Hi Richard,
>>
>>
>> On 7/2/2013 16:13, Richard Genoud wrote:
Please hold on of this, as to the ASoC dmaengine will deal with this. So,
we
>not need do it manually.
>
>Now, I am working on it. And will send out the
2013/7/2 Bo Shen :
> Hi Richard,
>
>
> On 7/2/2013 16:13, Richard Genoud wrote:
>>>
>>> Please hold on of this, as to the ASoC dmaengine will deal with this. So,
>>> we
>>> >not need do it manually.
>>> >
>>> >Now, I am working on it. And will send out the patch soon after testing
>>> > OK.
>>
>>
2013/7/2 Bo Shen voice.s...@atmel.com:
Hi Richard,
On 7/2/2013 16:13, Richard Genoud wrote:
Please hold on of this, as to the ASoC dmaengine will deal with this. So,
we
not need do it manually.
Now, I am working on it. And will send out the patch soon after testing
OK.
Ok, I stay
2013/7/3 Richard Genoud richard.gen...@gmail.com:
2013/7/2 Bo Shen voice.s...@atmel.com:
Hi Richard,
On 7/2/2013 16:13, Richard Genoud wrote:
Please hold on of this, as to the ASoC dmaengine will deal with this. So,
we
not need do it manually.
Now, I am working on it. And will send out
Hi Richard,
On 7/3/2013 23:51, Richard Genoud wrote:
but there's a violent hang (kernel stops, no trace) when I try the record :
arecord -v -V stereo -Dplug:default -f cd -t wav -c 2 /tmp/toto.wav
last thing I see is :
dma dma0chan3: atc_control (3)
I don't meet this issue. Playback and
Hi Richard,
On 7/2/2013 16:13, Richard Genoud wrote:
Please hold on of this, as to the ASoC dmaengine will deal with this. So, we
>not need do it manually.
>
>Now, I am working on it. And will send out the patch soon after testing OK.
Ok, I stay tuned !
I think you can go on working with the
2013/7/2 Bo Shen :
> Hi Richard,
>
>
> On 7/1/2013 16:39, Richard Genoud wrote:
>>
>> The ssc device has to fill the at_dma_slave structure with the
>> device tree informations.
>> Doing a of_dma_request_slave_channel()+dma_release_channel() for that
>> seems wrong (or at least not very clean).
>
2013/7/2 Bo Shen voice.s...@atmel.com:
Hi Richard,
On 7/1/2013 16:39, Richard Genoud wrote:
The ssc device has to fill the at_dma_slave structure with the
device tree informations.
Doing a of_dma_request_slave_channel()+dma_release_channel() for that
seems wrong (or at least not very
Hi Richard,
On 7/2/2013 16:13, Richard Genoud wrote:
Please hold on of this, as to the ASoC dmaengine will deal with this. So, we
not need do it manually.
Now, I am working on it. And will send out the patch soon after testing OK.
Ok, I stay tuned !
I think you can go on working with the
Hi Richard,
On 7/1/2013 16:39, Richard Genoud wrote:
The ssc device has to fill the at_dma_slave structure with the
device tree informations.
Doing a of_dma_request_slave_channel()+dma_release_channel() for that
seems wrong (or at least not very clean).
Please hold on of this, as to the ASoC
The ssc device has to fill the at_dma_slave structure with the
device tree informations.
Doing a of_dma_request_slave_channel()+dma_release_channel() for that
seems wrong (or at least not very clean).
Signed-off-by: Richard Genoud
---
drivers/misc/atmel-ssc.c| 56
The ssc device has to fill the at_dma_slave structure with the
device tree informations.
Doing a of_dma_request_slave_channel()+dma_release_channel() for that
seems wrong (or at least not very clean).
Signed-off-by: Richard Genoud richard.gen...@gmail.com
---
drivers/misc/atmel-ssc.c
Hi Richard,
On 7/1/2013 16:39, Richard Genoud wrote:
The ssc device has to fill the at_dma_slave structure with the
device tree informations.
Doing a of_dma_request_slave_channel()+dma_release_channel() for that
seems wrong (or at least not very clean).
Please hold on of this, as to the ASoC
20 matches
Mail list logo
