tree a55b8f0ff8153cc3cebf89e740f19e3c81e065f9
parent ed1220df6e666500ebf58c4f2fccc681941646fb
author Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> 1592412473 -0500
committer Mark Brown <broonie@kernel.org> 1592420460 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQFHBAABCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl7qaGwTHGJyb29uaWVA
 a2VybmVsLm9yZwAKCRAk1otyXVSH0JTjB/9P3TVT4vT8bU2xTK+L/G0nYQKVyAcU
 UeMDnb1CxPfZfA0sU0IQ/b7zHqk8zGNuR1eBKJGoqV0J5cSttnp2fqBE6P8bD5by
 2U79i3DsxNZwexKsSlJLOjFQ3KsSpINoi2TXipCGgmS27JKYIHCIokqkGCZx3wFt
 IkyQp3x3KkYhApuvFB4mQGg4/PsK3YlclxbS5emOsGEOKR7MFxZGPEHo+YJ5yd9N
 2pkHYnP6BoTDoxx+KJXJK7oArx/JRB5gHo/Lm2lv4Qazyu4rkuvikcGWkaZ1VN78
 6VmIPvh7DRvHw4L6c4WqcDHOtatS8stjUU9tE7TL0h9ShBmJhBqfAGCd
 =5JM2
 -----END PGP SIGNATURE-----

ASoC: Intel: SOF: merge COMETLAKE_LP and COMETLAKE_H

We already have two configurations for CometLake, and a third one
coming. On other platforms, we used a single Kconfig option, so we
should follow the same trend by merging the two cases in a backwards
compatible way.

The backwards compatibility is handled by overloading the COMETLAKE_LP
kconfig as COMETLAKE. In practice we've never seen a case where
COMETLAKE_H is not selected along with COMETLAKE_LP, so keeping one
of the two is enough.

Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Reviewed-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
Reviewed-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Link: https://lore.kernel.org/r/20200617164755.18104-2-pierre-louis.bossart@linux.intel.com
Signed-off-by: Mark Brown <broonie@kernel.org>