From: Takashi Iwai <tiwai@suse.de>
To: Hans de Goede <hdegoede@redhat.com>
Cc: youling257 <youling257@gmail.com>,
alsa-devel@alsa-project.org,
pierre-louis.bossart@linux.intel.com
Subject: Re: [PATCH v2 01/13] conf/ucm: bytcr-rt5645: Use the generic bytcr/PlatformEnableSeq.conf
Date: Mon, 26 Nov 2018 15:18:52 +0100 [thread overview]
Message-ID: <s5ho9abzzub.wl-tiwai@suse.de> (raw)
In-Reply-To: <11fd58d6-4008-3ba1-be85-b648b849379a@redhat.com>
On Mon, 26 Nov 2018 14:40:48 +0100,
Hans de Goede wrote:
>
> > some of the recently added UCM profiles are the files to be included
> > by others, and they are not card targets. Unfortunately alsaucm
> > doesn't know about it, and it aborts with error, e.g.
> >
> > ====
> > % alsaucm
> > ALSA lib utils.c:67:(uc_mgr_config_load) could not open configuration file /usr/share/alsa/ucm/bytcr/bytcr.conf
> > ALSA lib parser.c:1427:(load_master_config) error: could not parse configuration for card bytcr
> > alsaucm: unable to obtain card list: No such file or directory
> > ====
> >
> > The similar error is found in nau8824, rt5640 and rt5651. After
> > putting a placeholder card config file (e.g. bytcr.conf), the error is
> > gone. But certainly we don't want to allow user to choose this as the
> > proper card.
> >
> > So, I guess we need to put some flag to each such directory indicating
> > that it's no card config. For example, putting
> > /usr/share/alsa/ucm/bytcr/.nocard file or such...
> >
> > Not sure whether it's wise to have a file starting with dot, though.
> > Maybe clearer to be "nocard" or any other visible one?
>
> All the HiFi.conf files using the "include" snippets I added to avoid
> copy and pasting a lot, already need to have this at the top for
> this to work:
>
> <searchdir:ucm>
>
> So it might be best to move all the dirs holding include files rather
> then proper card configs from /usr/share/alsa/ucm to
> /usr/share/alsa/ucm-includes and then change the searchdir part of
> the configs using these to:
>
> <searchdir:ucm-includes>
This sounds like a good solution, indeed.
Care to submit a fix patch? I'll apply it unless anyone objects.
Thanks!
Takashi
next prev parent reply other threads:[~2018-11-26 14:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 9:05 [PATCH v2 01/13] conf/ucm: bytcr-rt5645: Use the generic bytcr/PlatformEnableSeq.conf Hans de Goede
2018-08-08 9:05 ` [PATCH v2 02/13] conf/ucm: bytcr-rt5651: Do not use both DAC1 and HPVOL inputs for HP Hans de Goede
2018-08-08 9:05 ` [PATCH v2 03/13] conf/ucm: bytcr-rt5651: Configure all volumes at 0dB Hans de Goede
2018-08-08 9:05 ` [PATCH v2 04/13] conf/ucm: bytcr-rt5651: Start with all outputs and inputs disabled Hans de Goede
2018-08-08 9:05 ` [PATCH v2 05/13] conf/ucm: bytcr-rt5651: Change Speaker/Headphone en/disable sequences to fix switching Hans de Goede
2018-08-08 9:05 ` [PATCH v2 06/13] conf/ucm: bytcr-rt5651: Use generic SSP enable + disable sequence, support SSP0 Hans de Goede
2018-08-08 9:05 ` [PATCH v2 07/13] conf/ucm: bytcr-rt5651: Fix ADC and Mic capture volumes Hans de Goede
2018-08-08 9:05 ` [PATCH v2 08/13] conf/ucm: bytcr-rt5651: Add support for mic input on various pins Hans de Goede
2018-08-08 9:05 ` [PATCH v2 09/13] conf/ucm: bytcr-rt5651: Split into 1 .conf file per input / output Hans de Goede
2018-08-08 9:05 ` [PATCH v2 10/13] conf/ucm: bytcr-rt5651: Add mono speaker output profile Hans de Goede
2018-08-08 9:05 ` [PATCH v2 11/13] conf/ucm: bytcr-rt5651: Add long-name UCM profiles Hans de Goede
2018-08-08 9:05 ` [PATCH v2 12/13] conf/ucm: bytcr-rt5651: Add bytcr-rt5651-mono-spk-in2-mic-hp-swapped config Hans de Goede
2018-08-08 9:05 ` [PATCH v2 13/13] conf/ucm: bytcr-rt5640: Improve human readable input/output names Hans de Goede
2018-08-08 9:46 ` [PATCH v2 01/13] conf/ucm: bytcr-rt5645: Use the generic bytcr/PlatformEnableSeq.conf Jaroslav Kysela
2018-11-25 11:11 ` youling257
2018-11-26 8:25 ` Takashi Iwai
2018-11-26 9:37 ` youling 257
2018-11-26 9:49 ` youling257
2018-11-26 10:07 ` Takashi Iwai
2018-11-26 13:40 ` Hans de Goede
2018-11-26 14:18 ` Takashi Iwai [this message]
2018-11-26 15:28 ` Jaroslav Kysela
2018-11-26 17:20 ` Pierre-Louis Bossart
2018-11-27 13:08 ` Takashi Iwai
2018-11-27 17:08 ` Pierre-Louis Bossart
2018-11-27 17:12 ` Takashi Iwai
2018-11-28 4:35 ` youling 257
2018-11-28 9:51 ` Takashi Iwai
2018-11-28 2:53 ` youling 257
2018-11-28 3:04 ` youling 257
2018-11-28 3:27 ` youling 257
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=s5ho9abzzub.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=hdegoede@redhat.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=youling257@gmail.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 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.