All of lore.kernel.org
 help / color / mirror / Atom feed
* [alsa-devel] alsa conformance test fails to run for playback (and works for capture)
@ 2019-10-17 14:14 Hin-Tak Leung
  2019-10-18  2:59 ` Yu-hsuan Hsu
  0 siblings, 1 reply; 9+ messages in thread
From: Hin-Tak Leung @ 2019-10-17 14:14 UTC (permalink / raw)
  To: Yu-Hsuan Hsu; +Cc: alsa-devel

Hi Yu-Hsuan,

I have encountered another problem with the alsa conformance test. It works for capture, but not for playback.

The device is - 

http://wiki.seeedstudio.com/ReSpeaker_6-Mic_Circular_Array_kit_for_Raspberry_Pi/

and running on a pi / raspbian buster.

The actual message is:

Fail - ALSA lib pcm_hw.c:1822:(_snd_pcm_hw_open) Invalid value for card
snd_pcm_open hw:CARD=seeed8micvoi: No such device

I think the truncation is harmless .

The actual device name according to aplay -L is "hw:CARD=seeed8micvoicec,DEV=0" and as I noted earlier, arecord -L shows it as "hw:CARD=seeed8micvoicec,DEV=0" also, and the comformance test running in CAPTURE mode works, just not in PLAYBACK mode.

Is there anything I can do to look further?

Since it says "invalid value", I tried deleting the parameters around line 190 of src/alsa_conformance_helper.c, but perhaps I should do something else?

src/alsa_conformance_helper.c-191-    conformance_timer_start(timer, SND_PCM_OPEN);
src/alsa_conformance_helper.c:192:    rc = snd_pcm_open(handle,
src/alsa_conformance_helper.c-193-                      dev_name,
src/alsa_conformance_helper.c-194-                      stream,
src/alsa_conformance_helper.c-195-                      SND_PCM_NONBLOCK |
src/alsa_conformance_helper.c-196-                      SND_PCM_NO_AUTO_RESAMPLE |
src/alsa_conformance_helper.c-197-                      SND_PCM_NO_AUTO_CHANNELS |
src/alsa_conformance_helper.c-198-                      SND_PCM_NO_AUTO_FORMAT);
src/alsa_conformance_helper.c-199-    conformance_timer_stop(timer, SND_PCM_OPEN);


Regards,
Hin-Tak

 
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [alsa-devel] alsa conformance test fails to run for playback (and works for capture)
  2019-10-17 14:14 [alsa-devel] alsa conformance test fails to run for playback (and works for capture) Hin-Tak Leung
@ 2019-10-18  2:59 ` Yu-hsuan Hsu
  2019-10-18 10:56   ` Hin-Tak Leung
  0 siblings, 1 reply; 9+ messages in thread
From: Yu-hsuan Hsu @ 2019-10-18  2:59 UTC (permalink / raw)
  To: htl10; +Cc: alsa-devel, Yu-Hsuan Hsu

Hi Hin-Tak,

How about using index instead? You should find the card index and device
index by running "aplay -l" command. The pcm format
is hw:{CARD_INDEX},{DEVICE_INDEX}.
See example part in
https://chromium.googlesource.com/chromiumos/platform/audiotest/+/refs/heads/master/alsa_conformance_test.md
for
more information.

Best,
Yu-Hsuan

On Thu, Oct 17, 2019 at 10:14 PM Hin-Tak Leung <htl10@users.sourceforge.net>
wrote:

> Hi Yu-Hsuan,
>
> I have encountered another problem with the alsa conformance test. It
> works for capture, but not for playback.
>
> The device is -
>
>
> http://wiki.seeedstudio.com/ReSpeaker_6-Mic_Circular_Array_kit_for_Raspberry_Pi/
>
> and running on a pi / raspbian buster.
>
> The actual message is:
>
> Fail - ALSA lib pcm_hw.c:1822:(_snd_pcm_hw_open) Invalid value for card
> snd_pcm_open hw:CARD=seeed8micvoi: No such device
>
> I think the truncation is harmless .
>
> The actual device name according to aplay -L is
> "hw:CARD=seeed8micvoicec,DEV=0" and as I noted earlier, arecord -L shows it
> as "hw:CARD=seeed8micvoicec,DEV=0" also, and the comformance test running
> in CAPTURE mode works, just not in PLAYBACK mode.
>
> Is there anything I can do to look further?
>
> Since it says "invalid value", I tried deleting the parameters around line
> 190 of src/alsa_conformance_helper.c, but perhaps I should do something
> else?
>
> src/alsa_conformance_helper.c-191-    conformance_timer_start(timer,
> SND_PCM_OPEN);
> src/alsa_conformance_helper.c:192:    rc = snd_pcm_open(handle,
> src/alsa_conformance_helper.c-193-                      dev_name,
> src/alsa_conformance_helper.c-194-                      stream,
> src/alsa_conformance_helper.c-195-                      SND_PCM_NONBLOCK |
> src/alsa_conformance_helper.c-196-
> SND_PCM_NO_AUTO_RESAMPLE |
> src/alsa_conformance_helper.c-197-
> SND_PCM_NO_AUTO_CHANNELS |
> src/alsa_conformance_helper.c-198-
> SND_PCM_NO_AUTO_FORMAT);
> src/alsa_conformance_helper.c-199-    conformance_timer_stop(timer,
> SND_PCM_OPEN);
>
>
> Regards,
> Hin-Tak
>
>
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [alsa-devel] alsa conformance test fails to run for playback (and works for capture)
  2019-10-18  2:59 ` Yu-hsuan Hsu
@ 2019-10-18 10:56   ` Hin-Tak Leung
  2019-10-20 10:51     ` Yu-Hsuan Hsu
  0 siblings, 1 reply; 9+ messages in thread
From: Hin-Tak Leung @ 2019-10-18 10:56 UTC (permalink / raw)
  To: Yu-hsuan Hsu; +Cc: alsa-devel, Yu-Hsuan Hsu

 > On Friday, 18 October 2019, 04:27:29 BST, Yu-hsuan Hsu <yuhsuan@google.com> wrote:

> How about using index instead? You should find the card index and device index by running "aplay -l" command. The pcm format is hw:{CARD_INDEX},{DEVICE_INDEX}.
> See example part in https://chromium.googlesource.com/chromiumos/platform/audiotest/+/refs/heads/master/alsa_conformance_test.md for more information.

Dear Yu-Hsuan,

Yes, using card index and device index works. Here is the output:

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
 Subdevices: 7/7
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
 Subdevice #2: subdevice #2
 Subdevice #3: subdevice #3
 Subdevice #4: subdevice #4
 Subdevice #5: subdevice #5
 Subdevice #6: subdevice #6
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 IEC958/HDMI [bcm2835 IEC958/HDMI]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 0: ALSA [bcm2835 ALSA], device 2: bcm2835 IEC958/HDMI1 [bcm2835 IEC958/HDMI1]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 1: seeed8micvoicec [seeed-8mic-voicecard], device 0: bcm2835-i2s-ac10x-codec0 ac10x-codec.1-0035-0 []
 Subdevices: 1/1
 Subdevice #0: subdevice #0

As I mentioned earlier I am interested in card 1, the seeed8micvoicec entry. Here it is the conformance test output: 


20 passed, 0 failed
Device Information
 Name: hw:CARD=1,0
 Stream: PLAYBACK
 Format: ['S32_LE']
 Channels: [8]
 Rate: [8000, 11025, 16000, 22050, 44100, 48000]
 Period_size range: [8, 8192]
 Buffer_size range: [16, 16384]
Test Params
 Set channels 8: pass
 Set format S32_LE: pass
 Set rate 8000: pass
 Set rate 11025: pass
 Set rate 16000: pass
 Set rate 22050: pass
 Set rate 44100: pass
 Set rate 48000: pass
Test Rates
 Set rate 8000: pass
 Set rate 11025: pass
 Set rate 16000: pass
 Set rate 22050: pass
 Set rate 44100: pass
 Set rate 48000: pass
Test All Pairs
 Set channels 8, format S32_LE, rate 8000: pass
 Set channels 8, format S32_LE, rate 11025: pass
 Set channels 8, format S32_LE, rate 16000: pass
 Set channels 8, format S32_LE, rate 22050: pass
 Set channels 8, format S32_LE, rate 44100: pass
 Set channels 8, format S32_LE, rate 48000: pass

There is probably a bug somewhere on not being able to use the card name?

Regards,
Hin-Tak
  
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [alsa-devel] alsa conformance test fails to run for playback (and works for capture)
  2019-10-18 10:56   ` Hin-Tak Leung
@ 2019-10-20 10:51     ` Yu-Hsuan Hsu
  2019-10-21 13:57       ` Hin-Tak Leung
  0 siblings, 1 reply; 9+ messages in thread
From: Yu-Hsuan Hsu @ 2019-10-20 10:51 UTC (permalink / raw)
  To: htl10; +Cc: alsa-devel

Hi Hin-Tak,
Maybe it is not the correct pcm name.  I guess the correct one is
"hw:seeed8micvoicec,0". Could you try it?
By the way, you can also use aplay -D {device_name} to make sure
whether the name is correct or not.

Best,
Yu-Hsuan

Hin-Tak Leung <htl10@users.sourceforge.net> 於 2019年10月18日 週五 下午6:56寫道:
>
> > On Friday, 18 October 2019, 04:27:29 BST, Yu-hsuan Hsu <yuhsuan@google.com> wrote:
>
> > How about using index instead? You should find the card index and device index by running "aplay -l" command. The pcm format is hw:{CARD_INDEX},{DEVICE_INDEX}.
> > See example part in https://chromium.googlesource.com/chromiumos/platform/audiotest/+/refs/heads/master/alsa_conformance_test.md for more information.
>
> Dear Yu-Hsuan,
>
> Yes, using card index and device index works. Here is the output:
>
> $ aplay -l
> **** List of PLAYBACK Hardware Devices ****
> card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
> Subdevices: 7/7
> Subdevice #0: subdevice #0
> Subdevice #1: subdevice #1
> Subdevice #2: subdevice #2
> Subdevice #3: subdevice #3
> Subdevice #4: subdevice #4
> Subdevice #5: subdevice #5
> Subdevice #6: subdevice #6
> card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 IEC958/HDMI [bcm2835 IEC958/HDMI]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> card 0: ALSA [bcm2835 ALSA], device 2: bcm2835 IEC958/HDMI1 [bcm2835 IEC958/HDMI1]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> card 1: seeed8micvoicec [seeed-8mic-voicecard], device 0: bcm2835-i2s-ac10x-codec0 ac10x-codec.1-0035-0 []
> Subdevices: 1/1
> Subdevice #0: subdevice #0
>
> As I mentioned earlier I am interested in card 1, the seeed8micvoicec entry. Here it is the conformance test output:
>
>
> 20 passed, 0 failed
> Device Information
> Name: hw:CARD=1,0
> Stream: PLAYBACK
> Format: ['S32_LE']
> Channels: [8]
> Rate: [8000, 11025, 16000, 22050, 44100, 48000]
> Period_size range: [8, 8192]
> Buffer_size range: [16, 16384]
> Test Params
> Set channels 8: pass
> Set format S32_LE: pass
> Set rate 8000: pass
> Set rate 11025: pass
> Set rate 16000: pass
> Set rate 22050: pass
> Set rate 44100: pass
> Set rate 48000: pass
> Test Rates
> Set rate 8000: pass
> Set rate 11025: pass
> Set rate 16000: pass
> Set rate 22050: pass
> Set rate 44100: pass
> Set rate 48000: pass
> Test All Pairs
> Set channels 8, format S32_LE, rate 8000: pass
> Set channels 8, format S32_LE, rate 11025: pass
> Set channels 8, format S32_LE, rate 16000: pass
> Set channels 8, format S32_LE, rate 22050: pass
> Set channels 8, format S32_LE, rate 44100: pass
> Set channels 8, format S32_LE, rate 48000: pass
>
> There is probably a bug somewhere on not being able to use the card name?
>
> Regards,
> Hin-Tak
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [alsa-devel] alsa conformance test fails to run for playback (and works for capture)
  2019-10-20 10:51     ` Yu-Hsuan Hsu
@ 2019-10-21 13:57       ` Hin-Tak Leung
  2019-10-22  3:11         ` Yu-Hsuan Hsu
  0 siblings, 1 reply; 9+ messages in thread
From: Hin-Tak Leung @ 2019-10-21 13:57 UTC (permalink / raw)
  To: Yu-Hsuan Hsu; +Cc: alsa-devel

 On Sunday, 20 October 2019, 11:51:42 BST, Yu-Hsuan Hsu <yuhsuan@chromium.org> wrote:


> Hi Hin-Tak,
> Maybe it is not the correct pcm name.  I guess the correct one is
> "hw:seeed8micvoicec,0". Could you try it?
> By the way, you can also use aplay -D {device_name} to make sure
> whether the name is correct or not.

> Best,
> Yu-Hsuan

Dear Yu-Hsuan,

No "hw:seeed8micvoicec,0" did not work as input to the conformance test. As input to 'aplay -D', both the ,0 and without it sort of works.
(it waits for input from stdin).

When I actually gave it an channel file to play, both forms ('aplay -D hw:CARD=seeed8micvoicec ...' and 'aplay -D hw:CARD=seeed8micvoicec,0 ...') stopped with:

Playing WAVE 'Untitled recording 2019-10-11 19.15.11.wav' : Signed 16 bit Little Endian, Rate 16000 Hz, Channels 6
aplay: set_params:1339: Sample format non available
Available formats:
- S32_LE

The interesting part of 'aplay -L' is (there is another device):

sysdefault:CARD=seeed8micvoicec
 seeed-8mic-voicecard, 
 Default Audio Device
dmix:CARD=seeed8micvoicec,DEV=0
 seeed-8mic-voicecard, 
 Direct sample mixing device
dsnoop:CARD=seeed8micvoicec,DEV=0
 seeed-8mic-voicecard, 
 Direct sample snooping device
hw:CARD=seeed8micvoicec,DEV=0
 seeed-8mic-voicecard, 
 Direct hardware device without any conversions
plughw:CARD=seeed8micvoicec,DEV=0
 seeed-8mic-voicecard, 
 Hardware device with all software conversions
usbstream:CARD=seeed8micvoicec
 seeed-8mic-voicecard
 USB Stream Output

As I mentioned at the beginning, 'arecord -L' and running the conformance test in CAPTURE mode using 'hw:CARD=seeed8micvoicec' works. It is PLAYBACK which does not.

Regards,
Hin-Tak




  
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [alsa-devel] alsa conformance test fails to run for playback (and works for capture)
  2019-10-21 13:57       ` Hin-Tak Leung
@ 2019-10-22  3:11         ` Yu-Hsuan Hsu
  2019-10-22  9:39           ` Hin-Tak Leung
  0 siblings, 1 reply; 9+ messages in thread
From: Yu-Hsuan Hsu @ 2019-10-22  3:11 UTC (permalink / raw)
  To: htl10; +Cc: alsa-devel

Hi Hin-Tak,

I finally found out the reason! It is because there is a length limit
of PCM name in ALSA conformance test.
I have increased it on
https://chromium-review.googlesource.com/c/chromiumos/platform/audiotest/+/1871792.
Waiting for the review and merge.
Thanks a lot for your catch!

Best,
Yu-Hsuan

Hin-Tak Leung <htl10@users.sourceforge.net> 於 2019年10月21日 週一 下午9:57寫道:
>
> On Sunday, 20 October 2019, 11:51:42 BST, Yu-Hsuan Hsu <yuhsuan@chromium.org> wrote:
>
>
> > Hi Hin-Tak,
> > Maybe it is not the correct pcm name.  I guess the correct one is
> > "hw:seeed8micvoicec,0". Could you try it?
> > By the way, you can also use aplay -D {device_name} to make sure
> > whether the name is correct or not.
>
> > Best,
> > Yu-Hsuan
>
> Dear Yu-Hsuan,
>
> No "hw:seeed8micvoicec,0" did not work as input to the conformance test. As input to 'aplay -D', both the ,0 and without it sort of works.
> (it waits for input from stdin).
>
> When I actually gave it an channel file to play, both forms ('aplay -D hw:CARD=seeed8micvoicec ...' and 'aplay -D hw:CARD=seeed8micvoicec,0 ...') stopped with:
>
> Playing WAVE 'Untitled recording 2019-10-11 19.15.11.wav' : Signed 16 bit Little Endian, Rate 16000 Hz, Channels 6
> aplay: set_params:1339: Sample format non available
> Available formats:
> - S32_LE
>
> The interesting part of 'aplay -L' is (there is another device):
>
> sysdefault:CARD=seeed8micvoicec
> seeed-8mic-voicecard,
> Default Audio Device
> dmix:CARD=seeed8micvoicec,DEV=0
> seeed-8mic-voicecard,
> Direct sample mixing device
> dsnoop:CARD=seeed8micvoicec,DEV=0
> seeed-8mic-voicecard,
> Direct sample snooping device
> hw:CARD=seeed8micvoicec,DEV=0
> seeed-8mic-voicecard,
> Direct hardware device without any conversions
> plughw:CARD=seeed8micvoicec,DEV=0
> seeed-8mic-voicecard,
> Hardware device with all software conversions
> usbstream:CARD=seeed8micvoicec
> seeed-8mic-voicecard
> USB Stream Output
>
> As I mentioned at the beginning, 'arecord -L' and running the conformance test in CAPTURE mode using 'hw:CARD=seeed8micvoicec' works. It is PLAYBACK which does not.
>
> Regards,
> Hin-Tak
>
>
>
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [alsa-devel] alsa conformance test fails to run for playback (and works for capture)
  2019-10-22  3:11         ` Yu-Hsuan Hsu
@ 2019-10-22  9:39           ` Hin-Tak Leung
  2019-10-22 16:13             ` Yu-Hsuan Hsu
  0 siblings, 1 reply; 9+ messages in thread
From: Hin-Tak Leung @ 2019-10-22  9:39 UTC (permalink / raw)
  To: Yu-Hsuan Hsu; +Cc: alsa-devel

 

On Tuesday, 22 October 2019, 04:12:12 BST, Yu-Hsuan Hsu <yuhsuan@chromium.org> wrote:


> Hi Hin-Tak,

> I finally found out the reason! It is because there is a length limit
> of PCM name in ALSA conformance test.
> I have increased it on
> https://chromium-review.googlesource.com/c/chromiumos/platform/audiotest/+/1871792.
> Waiting for the review and merge.
> Thanks a lot for your catch!

> Best,
> Yu-Hsuan

Dear Yu-Hsuan,

Yes, I hand-applied the one-line change, and it now works. I do wonder if you should change the args_set_capture_dev_name() also? 
At the moment, MAX_DEVICE_NAME_LENGTH is only used in exactly one place, for the playback device name. Hence the surprise that
capture works but playback does not:

src/alsa_conformance_args.c-119-void args_set_playback_dev_name(struct alsa_conformance_args *args,
src/alsa_conformance_args.c-120- const char *name)
src/alsa_conformance_args.c-121-{
src/alsa_conformance_args.c-122- free(args->playback_dev_name);
src/alsa_conformance_args.c:123: args->playback_dev_name = strndup(name, MAX_DEVICE_NAME_LENGTH);
src/alsa_conformance_args.c-124-}
src/alsa_conformance_args.c-125-
src/alsa_conformance_args.c-126-void args_set_capture_dev_name(struct alsa_conformance_args *args,
src/alsa_conformance_args.c-127- const char *name)
src/alsa_conformance_args.c-128-{
src/alsa_conformance_args.c-129- free(args->capture_dev_name);
src/alsa_conformance_args.c-130- args->capture_dev_name = strdup(name);
src/alsa_conformance_args.c-131-}
src/alsa_conformance_args.c-132-

Regards,
Hin-Tak
  
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [alsa-devel] alsa conformance test fails to run for playback (and works for capture)
  2019-10-22  9:39           ` Hin-Tak Leung
@ 2019-10-22 16:13             ` Yu-Hsuan Hsu
  2019-10-23 10:06               ` Hin-Tak Leung
  0 siblings, 1 reply; 9+ messages in thread
From: Yu-Hsuan Hsu @ 2019-10-22 16:13 UTC (permalink / raw)
  To: htl10; +Cc: alsa-devel

Hi Hin-Tak,

Good catch again. I have fixed it in the same CL. Thanks!

Best,
Yu-Hsuan

Hin-Tak Leung <htl10@users.sourceforge.net> 於 2019年10月22日 週二 下午5:39寫道:
>
>
>
> On Tuesday, 22 October 2019, 04:12:12 BST, Yu-Hsuan Hsu <yuhsuan@chromium.org> wrote:
>
>
> > Hi Hin-Tak,
>
> > I finally found out the reason! It is because there is a length limit
> > of PCM name in ALSA conformance test.
> > I have increased it on
> > https://chromium-review.googlesource.com/c/chromiumos/platform/audiotest/+/1871792.
> > Waiting for the review and merge.
> > Thanks a lot for your catch!
>
> > Best,
> > Yu-Hsuan
>
> Dear Yu-Hsuan,
>
> Yes, I hand-applied the one-line change, and it now works. I do wonder if you should change the args_set_capture_dev_name() also?
> At the moment, MAX_DEVICE_NAME_LENGTH is only used in exactly one place, for the playback device name. Hence the surprise that
> capture works but playback does not:
>
> src/alsa_conformance_args.c-119-void args_set_playback_dev_name(struct alsa_conformance_args *args,
> src/alsa_conformance_args.c-120- const char *name)
> src/alsa_conformance_args.c-121-{
> src/alsa_conformance_args.c-122- free(args->playback_dev_name);
> src/alsa_conformance_args.c:123: args->playback_dev_name = strndup(name, MAX_DEVICE_NAME_LENGTH);
> src/alsa_conformance_args.c-124-}
> src/alsa_conformance_args.c-125-
> src/alsa_conformance_args.c-126-void args_set_capture_dev_name(struct alsa_conformance_args *args,
> src/alsa_conformance_args.c-127- const char *name)
> src/alsa_conformance_args.c-128-{
> src/alsa_conformance_args.c-129- free(args->capture_dev_name);
> src/alsa_conformance_args.c-130- args->capture_dev_name = strdup(name);
> src/alsa_conformance_args.c-131-}
> src/alsa_conformance_args.c-132-
>
> Regards,
> Hin-Tak
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [alsa-devel] alsa conformance test fails to run for playback (and works for capture)
  2019-10-22 16:13             ` Yu-Hsuan Hsu
@ 2019-10-23 10:06               ` Hin-Tak Leung
  0 siblings, 0 replies; 9+ messages in thread
From: Hin-Tak Leung @ 2019-10-23 10:06 UTC (permalink / raw)
  To: Yu-Hsuan Hsu; +Cc: alsa-devel

 

On Wednesday, 23 October 2019, 04:25:30 BST, Yu-Hsuan Hsu <yuhsuan@chromium.org> wrote:


> Hi Hin-Tak,

> Good catch again. I have fixed it in the same CL. Thanks!

> Best,
> Yu-Hsuan

Dear Yu-Hsuan,

I am glad it is all working out in the end for the better!

Regards,
Hin-Tak  
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2019-10-23 10:08 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-17 14:14 [alsa-devel] alsa conformance test fails to run for playback (and works for capture) Hin-Tak Leung
2019-10-18  2:59 ` Yu-hsuan Hsu
2019-10-18 10:56   ` Hin-Tak Leung
2019-10-20 10:51     ` Yu-Hsuan Hsu
2019-10-21 13:57       ` Hin-Tak Leung
2019-10-22  3:11         ` Yu-Hsuan Hsu
2019-10-22  9:39           ` Hin-Tak Leung
2019-10-22 16:13             ` Yu-Hsuan Hsu
2019-10-23 10:06               ` Hin-Tak Leung

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.