From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Artem Mygaiev <Artem_Mygaiev@epam.com>,
"peng.fan@nxp.com" <peng.fan@nxp.com>,
Oleksandr Andrushchenko <Oleksandr_Andrushchenko@epam.com>
Cc: "sstabellini@kernel.org" <sstabellini@kernel.org>,
"julien@xen.org" <julien@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] vsnd issue
Date: Mon, 25 Nov 2019 12:55:38 +0200 [thread overview]
Message-ID: <076b6dc8-d94f-cc21-0687-b50401818240@gmail.com> (raw)
In-Reply-To: <b0a79631326ba4452aac053dff7918014050fe3c.camel@epam.com>
On 11/25/19 12:40 PM, Artem Mygaiev wrote:
> Hello Peng Fan
>
> Please contact Oleksandr Andrushchenko (added to this thread) on this
> issue.
>
> -- Artem
>
> On Mon, 2019-11-25 at 10:24 +0000, Julien Grall wrote:
>> On 25/11/2019 10:19, Peng Fan wrote:
>>> Hi All,
>> Hi,
>>
>>> I am trying vsnd from xen-troops with xen 4.13 and Linux 5.4, but
>>> domu reports:
>> xen-troops is not part of Xen Project. Please contact the owner of
>> the
>> repo for any help here.
>>
>> I have CCed Artem who should be able to point to the author of vsnd.
>>
>> Best regards,
>>
>>> aplay compl.mp3
Hm, could you please try the same with wav and not mp3
and get back with the logs?
>>> ALSA lib ../../../alsa-lib-
>>> 1.1.9/src/pcm/pcm_direct.c:1156:(snd1_pcm_direct_initialize_slave)
>>> slave plugin does not support mmap interleaved or mmap
>>> noninterleaved access
ALSA frontend does not support mmap because of [1],
so this is expected
>>> ALSA lib ../../../alsa-lib-
>>> 1.1.9/src/pcm/pcm_dmix.c:1120:(snd_pcm_dmix_open) unable to
>>> initialize slave
>>> aplay: main:828: audio open error: Invalid argument
>>>
>>> When executing aplay in domu, dom0 side log:
>>> root@imx8qmmek:~# 13.11.19 08:24:57.484 | XenEvtchn | DBG -
>>> Event received, port: 10
>>> 13.11.19 08:24:57.491 | StreamRing | DBG - Request received,
>>> id: alsa<hw:2;0>, cmd:9
>>> 13.11.19 08:24:57.500 | CommandHandler | DBG - Handle command
>>> [QUERY_HW_PARAM]
>>> 13.11.19 08:24:57.508 | AlsaPcm | DBG - Query pcm device
>>> hw:2,0 for HW parameters
>>> 13.11.19 08:24:57.516 | CommandHandler | DBG - Return status: [0]
>>> 13.11.19 08:24:57.523 | XenEvtchn | DBG - Notify event
>>> channel, port: 10
>>> 13.11.19 08:24:57.531 | XenEvtchn | DBG - Event received,
>>> port: 10
>>> 13.11.19 08:24:57.538 | StreamRing | DBG - Request received,
>>> id: alsa<hw:2;0>, cmd:9
>>> 13.11.19 08:24:57.546 | CommandHandler | DBG - Handle command
>>> [QUERY_HW_PARAM]
>>> 13.11.19 08:24:57.554 | AlsaPcm | DBG - Query pcm device
>>> hw:2,0 for HW parameters
>>> 13.11.19 08:24:57.563 | CommandHandler | DBG - Return status: [0]
>>> 13.11.19 08:24:57.570 | XenEvtchn | DBG - Notify event
>>> channel, port: 10
>>> 13.11.19 08:24:57.577 | XenEvtchn | DBG - Event received,
>>> port: 10
>>> 13.11.19 08:24:57.584 | StreamRing | DBG - Request received,
>>> id: alsa<hw:2;0>, cmd:9
>>> 13.11.19 08:24:57.593 | CommandHandler | DBG - Handle command
>>> [QUERY_HW_PARAM]
>>> 13.11.19 08:24:57.601 | AlsaPcm | DBG - Query pcm device
>>> hw:2,0 for HW parameters
>>> 13.11.19 08:24:57.610 | CommandHandler | DBG - Return status: [0]
>>> 13.11.19 08:24:57.616 | XenEvtchn | DBG - Notify event
>>> channel, port: 10
>>> 13.11.19 08:24:57.624 | XenEvtchn | DBG - Event received,
>>> port: 10
>>> 13.11.19 08:24:57.631 | StreamRing | DBG - Request received,
>>> id: alsa<hw:2;0>, cmd:9
>>> 13.11.19 08:24:57.640 | CommandHandler | DBG - Handle command
>>> [QUERY_HW_PARAM]
>>> 13.11.19 08:24:57.647 | AlsaPcm | DBG - Query pcm device
>>> hw:2,0 for HW parameters
>>> 13.11.19 08:24:57.656 | CommandHandler | DBG - Return status: [0]
>>> 13.11.19 08:24:57.663 | XenEvtchn | DBG - Notify event
>>> channel, port: 10
>>> 13.11.19 08:24:57.671 | XenEvtchn | DBG - Event received,
>>> port: 10
>>> 13.11.19 08:24:57.678 | StreamRing | DBG - Request received,
>>> id: alsa<hw:2;0>, cmd:9
>>> 13.11.19 08:24:57.686 | CommandHandler | DBG - Handle command
>>> [QUERY_HW_PARAM]
>>> 13.11.19 08:24:57.694 | AlsaPcm | DBG - Query pcm device
>>> hw:2,0 for HW parameters
>>> 13.11.19 08:24:57.703 | CommandHandler | DBG - Return status: [0]
>>> 13.11.19 08:24:57.709 | XenEvtchn | DBG - Notify event
>>> channel, port: 10
>>>
>>>
>>> My xl.cfg:
>>> vsnd = [
>>> ['CARD, short-name=Main, sample-formats=s16_le;s8;u32_be',
>>> 'PCM, name=Main',
>>> 'STREAM, unique-id=alsa<hw:2;0>, type=p',
>>> 'STREAM, unique-id=alsa<hw:2;1>, type=c, channels-
>>> max=2'
>>> ],
>>> ]
Config seems to be ok
>>> The audio device on my board:
>>> aplay -l
>>> **** List of PLAYBACK Hardware Devices ****
>>> card 0: imxaudmix [imx-audmix], device 0: HiFi-AUDMIX-FE (*) []
>>> Subdevices: 1/1
>>> Subdevice #0: subdevice #0
>>> card 0: imxaudmix [imx-audmix], device 1: HiFi-AUDMIX-FE (*) []
>>> Subdevices: 1/1
>>> Subdevice #0: subdevice #0
>>> card 1: cs42888audio [cs42888-audio], device 0: HiFi cs42888-0
>>> [HiFi cs42888-0]
>>> Subdevices: 1/1
>>> Subdevice #0: subdevice #0
>>> card 1: cs42888audio [cs42888-audio], device 1: HiFi-ASRC-FE (*) []
>>> Subdevices: 1/1
>>> Subdevice #0: subdevice #0
>>> card 2: wm8960audio [wm8960-audio], device 0: HiFi wm8960-hifi-0 []
>>> Subdevices: 0/1
>>> Subdevice #0: subdevice #0
>>>
>>> Is there something wrong in my configuration?
>>>
>>> Thanks,
>>> Peng.
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xenproject.org
>>>
>>> https://urldefense.com/v3/__https://lists.xenproject.org/mailman/listinfo/xen-devel__;!K6dmGCEab4ueJg!iTeJON61Y2nUcGMQr_y7-27bR_QlOG8gXqvRMaU8yy8nJuDhzWizylvl_6stD-ILOQ$
>>>
>>>
>>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-devel
[1]
https://elixir.bootlin.com/linux/v5.4-rc8/source/sound/xen/xen_snd_front_alsa.c#L685
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-11-25 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 10:19 [Xen-devel] vsnd issue Peng Fan
2019-11-25 10:24 ` Julien Grall
2019-11-25 10:40 ` Artem Mygaiev
2019-11-25 10:55 ` Oleksandr Andrushchenko [this message]
2019-11-25 12:22 ` Peng Fan
2019-11-25 13:31 ` Oleksandr Grytsov
2019-11-25 13:34 ` Oleksandr Andrushchenko
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=076b6dc8-d94f-cc21-0687-b50401818240@gmail.com \
--to=andr2000@gmail.com \
--cc=Artem_Mygaiev@epam.com \
--cc=Oleksandr_Andrushchenko@epam.com \
--cc=julien@xen.org \
--cc=peng.fan@nxp.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xen.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.