On Wed, Apr 22, 2020 at 07:04:36PM +0200, Jaroslav Kysela wrote: > I am fighting actually with the ASoC driver names. The current situation, > where each hardware variant (card name) is mapped to the driver name is not > very practical (and not correct). The driver name should describe the common > part (usually the controller - like 'HDA-Intel' or bus 'USB-Audio'). With ASoC systems there is no clear controller - you've got a bunch of different components, usually connected by separate buses, and it's not super obvious what if anything should be the singular name that gets picked for some grouping of devices. The whole point of the subsystem is to glue a bunch of independent devices together, we've generally picked that glue as the driver name. > I am talking about the situation, where the ASoC card name is set via the > device tree (snd_soc_of_parse_card_name) like in [1], but the change may be > considered for other drivers like Intel SST: > Card driver name: Lenovo-YOGA-C63 > Card name: Lenovo-YOGA-C630-13Q50 > Card long name: LENOVO-81JL-LenovoYOGAC630_13Q50-LNVNB161216 > My question is, can we change / add the more apropriate driver names > conditionally with a new kernel CONFIG option? Will you accept this change? Without knowing what you're actually proposing it's hard to know, and there is the risk of userspace breakage here when you change things people are relying on. > The goal is to group the related UCM2 configurations and do the required > split inside the UCM2 top-level configuration file based on card components > string or other card identificators (related to the driver). This sounds like you either want some enumeration of the card components or perhaps you're looking for some for some indication of the reference design that an individual board is based off so you can have a generic configuration for that reference design and then override bits of it?
Attachment:
signature.asc
Description: PGP signature
