Hi > > - .endianness > > - .non_legacy_dai_naming > > + .is_codec > > Yeah I considered this but it didn't really feel like the right > way to go to me. Firstly, at this stage we almost certainly need > to keep the endianness and non_legacy_dai_naming flags, there are > corner cases when endianness probably shouldn't be applied to CODECs > (as noted in my endianness series), and there are platform drivers > that use non_legacy_dai_naming. Oops, yes indeed :) Thank you for pointing it. > We could add an is_codec flag along side the other two. But it > means a whole extra flag and means the the core is still requiring > a concept of what is a CODEC driver, which really we want to get > rid of as part of componentisation. Hmm... yes, indeed. Thank you for your help !! Best regards --- Kuninori Morimoto
