Unverified Commit 290a7c55 authored by Pierre-Louis Bossart's avatar Pierre-Louis Bossart Committed by Mark Brown
Browse files

ASoC: SOF: Intel: add comment on JasperLake support 



Explain why JasperLake is exposed in cnl.c instead of icl.c
No functionality change.

Signed-off-by: default avatarPierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Reviewed-by: default avatarKai Vehmanen <kai.vehmanen@linux.intel.com>
Reviewed-by: default avatarBard Liao <yung-chuan.liao@linux.intel.com>
Link: https://lore.kernel.org/r/20211207193947.71080-8-pierre-louis.bossart@linux.intel.com


Signed-off-by: default avatarMark Brown <broonie@kernel.org>
parent 924631df

sound/soc/sof/intel/cnl.c

+7 −0
Original line number Diff line number Diff line
@@ -358,6 +358,13 @@ const struct sof_intel_dsp_desc cnl_chip_info = { 
};

EXPORT_SYMBOL_NS(cnl_chip_info, SND_SOC_SOF_INTEL_HDA_COMMON);



/*

 * JasperLake is technically derived from IceLake, and should be in

 * described in icl.c. However since JasperLake was designed with

 * two cores, it cannot support the IceLake-specific power-up sequences

 * which rely on core3. To simplify, JasperLake uses the CannonLake ops and

 * is described in cnl.c

 */

const struct sof_intel_dsp_desc jsl_chip_info = {

	/* Jasperlake */

	.cores_num = 2,