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?
