All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
	ALSA development <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] ALSA: core - add more card sysfs entries
Date: Thu, 8 Apr 2021 11:50:08 -0500	[thread overview]
Message-ID: <da26eb5e-aaa6-8170-1e75-c53c7bbcda60@linux.intel.com> (raw)
In-Reply-To: <20210408162250.GN4516@sirena.org.uk>



On 4/8/21 11:22 AM, Mark Brown wrote:
>> Actually, the generic ASoC drivers are too much generic and they didn't
>> provide a solid information about the hardware.
> So if the information provided through the driver is too generic then we
> should ideally be fixing those drivers/systems to do something sensible.
> For the DT systems the generic cards have properties that let the system
> just specify names directly so it will just be a case of setting them
> properly and it should just be the x86 systems that are a problem.  ACPI
> is a bit of a lost cause here, most of the systems aren't interested in
> supporting Linux in the first place and the idioms there aren't great,
> but for DT it's reasonably tractable to push back on people if there's
> issues and it's much more scalable to do that than telling individual
> users to do that.

Even in the DT case, you may be able to set a specific path for DSP 
firmware and topology but would you really have enough information to 
describe what the DSP firmware and topology actually do? That 
information is part of the DSP firmware manifest and topology.

In addition, the firmware/topology are typically located on the file 
system, it'd be a hassle to have to edit DT properties every time you 
have a new distribution update, wouldn't it?

  reply	other threads:[~2021-04-08 16:51 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08  9:43 [PATCH] ALSA: core - add more card sysfs entries Jaroslav Kysela
2021-04-08 10:38 ` Takashi Sakamoto
2021-04-08 11:05   ` Takashi Iwai
2021-04-08 11:21     ` Jaroslav Kysela
2021-04-08 12:05       ` Mark Brown
2021-04-08 13:18         ` Takashi Iwai
2021-04-08 14:12           ` Pierre-Louis Bossart
2021-04-08 14:47             ` Mark Brown
2021-04-08 15:04               ` Jaroslav Kysela
2021-04-08 15:11                 ` Amadeusz Sławiński
2021-04-08 15:01           ` Jaroslav Kysela
2021-04-08 15:32             ` Pierre-Louis Bossart
2021-04-08 16:53               ` Jaroslav Kysela
2021-04-08 18:51                 ` Pierre-Louis Bossart
2021-04-08 19:25                   ` Jaroslav Kysela
2021-04-08 19:41                     ` Pierre-Louis Bossart
2021-04-08 19:56                       ` Curtis Malainey
2021-04-08 20:01                       ` Jaroslav Kysela
2021-04-09 16:43                         ` Jaroslav Kysela
2021-04-09  7:39                   ` Takashi Iwai
2021-04-09  8:34                     ` Jaroslav Kysela
2021-04-09  8:55                       ` Takashi Iwai
2021-04-09  9:09                       ` Amadeusz Sławiński
2021-04-09 13:54                         ` Jaroslav Kysela
2021-04-09 15:55                         ` Pierre-Louis Bossart
2021-04-09 16:38                           ` Takashi Iwai
2021-04-09 18:55                             ` Pierre-Louis Bossart
2021-04-09 16:39                           ` Mark Brown
2021-04-08 16:22             ` Mark Brown
2021-04-08 16:50               ` Pierre-Louis Bossart [this message]
2021-04-08 18:20                 ` Mark Brown
2021-04-08 17:20               ` Jaroslav Kysela
2021-04-08 17:47                 ` Mark Brown
2021-04-08 11:25   ` Jaroslav Kysela
2021-04-10 19:11 ` Jaroslav Kysela

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=da26eb5e-aaa6-8170-1e75-c53c7bbcda60@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.de \
    /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.