From: "Gorski, Mateusz" <mateusz.gorski@linux.intel.com>
To: Jaroslav Kysela <perex@perex.cz>, alsa-devel@alsa-project.org
Cc: cezary.rojewski@intel.com, tiwai@suse.com
Subject: Re: [PATCH] ucm2: hdadsp: add basic ucm config
Date: Tue, 17 Mar 2020 12:45:59 +0100 [thread overview]
Message-ID: <7a44ec22-ed38-5ddd-0f04-097b2befd796@linux.intel.com> (raw)
In-Reply-To: <1bd9d86c-e19f-183c-5355-5b7359c6e4c0@perex.cz>
>>>> Basic UCM configuration for HDA DSP generic enabling codec playback
>>>> and
>>>> capture on both HDA codec and DMIC ports.
>>>
>>> Could you describe for what Linux driver (source code) is this
>>> configuration?
>>
>>
>> This file is for Intel Skylake SST driver. Information added in v2.
>
> Ok, do we have this code in the vanilla linux kernel? Which .c file?
> The driver name 'hdadsp' looks suspicious. We usually have a delimiter
> in the driver name (like sof-hda-dsp).
Yes, it is a part of Skylake driver, "hdadsp" is the name of sound card
created on machine when using HDA generic machine driver. This machine
driver is made of 2 .c files:
- skl_hda_dsp_common.c
- skl_hda_dsp_generic.c
both are located in: sound/soc/intel/boards/
Example on production laptop:
test@test-Swift-SF515-51T:/proc/asound$ cat cards
0 [hdadsp ]: hda-dsp - hda-dsp
WL-SwiftSF515_51T-V1.02-Guinness_WL
>
>>>> +ValueDefaults {
>>>> + PlaybackChannels "2"
>>>> + PlaybackPriority "1"
>>>> + CaptureChannels "2"
>>>> + CapturePriority "2"
>>>> +}
>>>
>>> Remove PlaybackChannel and Priority defaults. The priorities should be
>>> defined in the device section.
>
> I will check...
>
>>
>>
>> Thanks, moved to device section in v2.
>>
>>
>>>> +
>>>> +SectionDefaults [
>>>> + cdev "hw:hdadsp"
>>>
>>> It should be "hw:${CardId}" for ucm2.
>>
>>
>> Thanks, applied in v2.
>>
>>
>>>> + cset "name='codec0_out mo media0_in mi Switch' 1"
>>>> + cset "name='media0_out mo codec0_in mi Switch' 1"
>>>> + cset "name='mch_cap_out mo mch_cap_in mi Switch' 1"
>>>> +]
>>>
>>> This file does not define any devices. Does pulseaudio work with this
>>> configuration?
>>
>>
>> Devices added in v2. Regarding pulseaudio - are there any guidelines on
>> how to test UCM files with it? These UCM files were writted mainly based
>> on existing ones for other cards. Of course basic tests were made.
>
> I wrote an ucm validator:
>
> https://github.com/alsa-project/alsa-tests/tree/master/python/ucm-validator
>
>
> Just type 'make' in the ucm-validator directory, the alsa-info.sh
> output should be added to the configs subtree.
>
> The PA should be used latest from gitlab with the volume control and
> HDMI support.
>
> Jaroslav
Thanks, used the validator on PATCH v2, it pointed out one more thing to
be corrected. One thing that I've noticed - there are some problems when
validating "included" files, for example:
<skylake-rt286/Hdmi1.conf>
<skylake-rt286/Hdmi2.conf>
raise "aconfig.AlsaConfigError: unable to load config" error
Mateusz
next prev parent reply other threads:[~2020-03-17 11:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 11:30 [PATCH] ucm2: hdadsp: add basic ucm config Mateusz Gorski
2020-03-09 13:01 ` Jaroslav Kysela
2020-03-13 10:59 ` Gorski, Mateusz
2020-03-13 11:14 ` Jaroslav Kysela
2020-03-17 11:45 ` Gorski, Mateusz [this message]
2020-03-17 13:23 ` Jaroslav Kysela
2020-03-18 10:25 ` Gorski, Mateusz
2020-03-25 12:21 ` Gorski, Mateusz
2020-03-18 15:34 ` Kai Vehmanen
2020-03-19 8:21 ` Gorski, Mateusz
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=7a44ec22-ed38-5ddd-0f04-097b2befd796@linux.intel.com \
--to=mateusz.gorski@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=cezary.rojewski@intel.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).