On 2020-11-23 6:35 PM, Mark Brown wrote:
On Fri, Nov 20, 2020 at 09:02:24PM +0000, Rojewski, Cezary wrote:
There are no circumstances under which Intel recommends distros to try to convert out of catpt though. Don't believe aligning all the drivers to some general idea just for the sake of aligning is a good move. That's why drivers have their own specifics in the first place - their complexity and performance could have been negatively impacted otherwise.
It could equally be that someone has stuck with the older, now deprecated, implementations due to compatibility fears and this could help them deploy the catpt implementation without worrying so much about breaking things for users.
Except that it (i.e.: patchset) doesn't touch old _HASWELL kconfig at all as the code behind it is already removed.
Believe we are desync'ed here.
What the patchset presents catpt vs SOF. /sof/ runs through SOF firmware so it cannot be account as old-implementation. It's a mix of not recommended fw + incorrect sw flow. As old /haswell/ is no more, there is no worrying about catpt deployment - it's your only option. As there is no userspace involved (lack of topology files), base firmware binary remains the same and amixer kcontrols behave 1:1 when compared to its predecessor, compatibility is left intact.
That's exactly why we should be explicit in driver selection. Pretty sure hsw/bdw case is still mistakenly addressed to as if it was atom-based platform.
Czarek