Add rt1015 support to CML boards
Subsystems (3)
cover Add rt1015 support to CML boards
First patch adds tdm 4-slot 100fs DAI setting to avoid jitter of using 64fs on CML boards. Second patch is a DMI quirk for HP Dooly.
Brent Lu (2):
ASoC: intel: sof_rt5682: Add support for cml_rt1015_rt5682
ASoC: intel: sof_rt5682: Add quirk for Dooly
sound/soc/intel/boards/sof_rt5682.c | 61 +++++++++++++++++-- .../intel/common/soc-acpi-intel-cml-match.c | 13 ++++ 2 files changed, 69 insertions(+), 5 deletions(-)
Signature · 1 line
2.17.1
PATCH 1/2 ASoC: intel: sof_rt5682: Add support for cml_rt1015_rt5682
This patch adds the driver data and updates quirk info for cml with rt1015 speaker amp and rt5682 headset codec. Due to different mclk frequency on JSL and CML, we need to use 4 slot TDM 100fs to avoid the SSP m/n counter.
--- sound/soc/intel/boards/sof_rt5682.c | 47 +++++++++++++++++-- .../intel/common/soc-acpi-intel-cml-match.c | 13 +++++ 2 files changed, 55 insertions(+), 5 deletions(-)
sound/soc/intel/boards/sof_rt5682.c +42 -5
@@ -42,8 +42,9 @@#define SOF_RT5682_NUM_HDMIDEV (quirk) \ ((quirk << SOF_RT5682_NUM_HDMIDEV_SHIFT) & SOF_RT5682_NUM_HDMIDEV_MASK)#define SOF_RT1015_SPEAKER_AMP_PRESENT BIT(13) -#define SOF_MAX98373_SPEAKER_AMP_PRESENT BIT(14) -#define SOF_MAX98360A_SPEAKER_AMP_PRESENT BIT(15) +#define SOF_RT1015_SPEAKER_AMP_100FS BIT(14) +#define SOF_MAX98373_SPEAKER_AMP_PRESENT BIT(15) +#define SOF_MAX98360A_SPEAKER_AMP_PRESENT BIT(16)/* Default: MCLK on, MCLK 19.2M, SSP0 */ static unsigned long sof_rt5682_quirk = SOF_RT5682_MCLK_EN |
@@ -291,21 +292,26 @@ static int sof_rt1015_hw_params(struct snd_pcm_substream *substream,struct snd_soc_pcm_runtime *rtd =asoc_substream_to_rtd (substream);struct snd_soc_card *card = rtd->card;struct snd_soc_dai *codec_dai; -int i, ret; +int i, fs, ret;if (!snd_soc_card_get_codec_dai (card,"rt1015-aif" ))return 0 ; +if (sof_rt5682_quirk &SOF_RT1015_SPEAKER_AMP_100FS ) + fs =100 ; +else + fs =64 ; +for_each_rtd_codec_dais (rtd, i, codec_dai) {/* Set tdm/i2s1 master bclk ratio */ - ret =snd_soc_dai_set_bclk_ratio (codec_dai,64 ); + ret =snd_soc_dai_set_bclk_ratio (codec_dai, fs);if (ret <0 ) {dev_err (card->dev,"failed to set bclk ratio\n" );return ret; } ret =snd_soc_dai_set_pll (codec_dai,0 ,RT1015_PLL_S_BCLK , -params_rate (params) *64 , +params_rate (params) * fs,params_rate (params) *256 );if (ret <0 ) {dev_err (card->dev,"failed to set pll\n" );
@@ -319,6 +325,26 @@ static int sof_rt1015_hw_params(struct snd_pcm_substream *substream,dev_err (card->dev,"failed to set sysclk\n" );return ret; } + +if (sof_rt5682_quirk &SOF_RT1015_SPEAKER_AMP_100FS ) { +if (!strcmp (codec_dai->component->name,"i2c-10EC1015:00" )) { + ret =snd_soc_dai_set_tdm_slot (codec_dai, +0x0 ,0x1 ,4 ,24 ); +if (ret <0 ) { +dev_err (card->dev,"failed to set tdm slot\n" ); +return ret; + } + } + +if (!strcmp (codec_dai->component->name,"i2c-10EC1015:01" )) { + ret =snd_soc_dai_set_tdm_slot (codec_dai, +0x0 ,0x2 ,4 ,24 ); +if (ret <0 ) { +dev_err (card->dev,"failed to set tdm slot\n" ); +return ret; + } + } + } }return 0 ;
@@ -875,6 +901,16 @@ static const struct platform_device_id board_ids[] = {SOF_MAX98360A_SPEAKER_AMP_PRESENT | SOF_RT5682_SSP_AMP(1)), }, + { + .name = "cml_rt1015_rt5682", + .driver_data = (kernel_ulong_t)(SOF_RT5682_MCLK_EN | +SOF_RT5682_MCLK_24MHZ | +SOF_RT5682_SSP_CODEC (0 ) | +SOF_SPEAKER_AMP_PRESENT | +SOF_RT1015_SPEAKER_AMP_PRESENT | +SOF_RT1015_SPEAKER_AMP_100FS | + SOF_RT5682_SSP_AMP(1)), + }, { } };
@@ -898,3 +934,4 @@ MODULE_ALIAS("platform:tgl_max98357a_rt5682");MODULE_ALIAS ("platform:jsl_rt5682_rt1015" );MODULE_ALIAS ("platform:tgl_max98373_rt5682" );MODULE_ALIAS ("platform:jsl_rt5682_max98360a" ); +MODULE_ALIAS ("platform:cml_rt1015_rt5682" );
sound/soc/intel/common/soc-acpi-intel-cml-match.c +13 -0
@@ -14,6 +14,11 @@ static struct snd_soc_acpi_codecs rt1011_spk_codecs = { .codecs = {"10EC1011"} }; +static struct snd_soc_acpi_codecs rt1015_spk_codecs = { + .num_codecs =1 , + .codecs = {"10EC1015" } +}; +static struct snd_soc_acpi_codecs max98357a_spk_codecs = { .num_codecs =1 , .codecs = {"MX98357A" }
@@ -38,6 +43,14 @@ struct snd_soc_acpi_mach snd_soc_acpi_intel_cml_machines[] = { .sof_fw_filename = "sof-cml.ri", .sof_tplg_filename = "sof-cml-rt1011-rt5682.tplg", }, + { + .id = "10EC5682", + .drv_name = "cml_rt1015_rt5682", + .machine_quirk = snd_soc_acpi_codec_list, + .quirk_data = &rt1015_spk_codecs, + .sof_fw_filename = "sof-cml.ri", + .sof_tplg_filename = "sof-cml-rt1011-rt5682.tplg", + }, { .id = "10EC5682", .drv_name = "sof_rt5682",
Signature · 1 line
2.17.1
PATCH 2/2 ASoC: intel: sof_rt5682: Add quirk for Dooly
In reply to Brent LuThis DMI product family string of this board is "Google_Hatch" so the DMI quirk will take place. However, this board is using rt1015 speaker amp instead of max98357a specified in the quirk. Therefore, we need an new DMI quirk for this board.
--- sound/soc/intel/boards/sof_rt5682.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+)
sound/soc/intel/boards/sof_rt5682.c +14 -0
@@ -100,6 +100,20 @@ static const struct dmi_system_id sof_rt5682_quirk_table[] = {SOF_RT5682_MCLK_24MHZ | SOF_RT5682_SSP_CODEC(1)), }, + { + .callback = sof_rt5682_quirk_cb, + .matches = { +DMI_MATCH (DMI_SYS_VENDOR ,"HP" ), + DMI_MATCH(DMI_PRODUCT_NAME, "Dooly"), + }, + .driver_data = (void *)(SOF_RT5682_MCLK_EN | +SOF_RT5682_MCLK_24MHZ | +SOF_RT5682_SSP_CODEC (0 ) | +SOF_SPEAKER_AMP_PRESENT | +SOF_RT1015_SPEAKER_AMP_PRESENT | +SOF_RT1015_SPEAKER_AMP_100FS | + SOF_RT5682_SSP_AMP(1)), + }, { .callback = sof_rt5682_quirk_cb, .matches = {
Signature · 1 line
2.17.1
Re: [PATCH 2/2] ASoC: intel: sof_rt5682: Add quirk for Dooly
Quoted 4 lines · Brent Lu
This DMI product family string of this board is "
Google_Hatch" so the DMI quirk will take place. However, this board is using rt1015 speaker amp instead of max98357a specified in the quirk. Therefore, we need an new DMI quirk for this board.
Do you actually need a DMI quirk for this platform?
the .driver_data below uses the exact same settings as what you would use with the generic solution based on ACPI IDs, see below.
Wondering if patch1 would be enough?
Quoted 18 lines
Signed-off-by Brent Lu <[email protected]>--- sound/soc/intel/boards/sof_rt5682.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+)sound/soc/intel/boards/sof_rt5682.c +4
-0@@ -100,6 +100,20 @@ static const struct dmi_system_id sof_rt5682_quirk_table[] = {SOF_RT5682_MCLK_24MHZ | SOF_RT5682_SSP_CODEC(1)), }, + { + .callback = sof_rt5682_quirk_cb, + .matches = { + DMI_MATCH(DMI_SYS_VENDOR, "HP"),
sound/soc/intel/boards/sof_rt5682.c static const struct dmi_system_id sof_rt5682_quirk_table[] = { · line 116
Quoted 10 lines
sound/soc/intel/boards/sof_rt5682.c +10
-0+ DMI_MATCH(DMI_PRODUCT_NAME, "Dooly"), + }, + .driver_data = (void *)(SOF_RT5682_MCLK_EN | +SOF_RT5682_MCLK_24MHZ | +SOF_RT5682_SSP_CODEC (0 ) | +SOF_SPEAKER_AMP_PRESENT | +SOF_RT1015_SPEAKER_AMP_PRESENT | +SOF_RT1015_SPEAKER_AMP_100FS | + SOF_RT5682_SSP_AMP(1)), + },
is this really needed? it's the same as the .driver_data below:
@@ -875,6 +901,16 @@ static const struct platform_device_id board_ids[] = {
SOF_MAX98360A_SPEAKER_AMP_PRESENT | SOF_RT5682_SSP_AMP(1)),
},
+ {
+ .name = "cml_rt1015_rt5682",
+ .driver_data = (kernel_ulong_t)(SOF_RT5682_MCLK_EN |
+ SOF_RT5682_MCLK_24MHZ |
+ SOF_RT5682_SSP_CODEC(0) |
+ SOF_SPEAKER_AMP_PRESENT |
+ SOF_RT1015_SPEAKER_AMP_PRESENT |
+ SOF_RT1015_SPEAKER_AMP_100FS |
+ SOF_RT5682_SSP_AMP(1)),
+ },
RE: [PATCH 2/2] ASoC: intel: sof_rt5682: Add quirk for Dooly
Quoted 5 lines · Brent Lu
Quoted 4 lines
This DMI product family string of this board is "
Google_Hatch" so the DMI quirk will take place. However, this board is using rt1015 speaker amp instead of max98357a specified in the quirk. Therefore, we need an new DMI quirk for this board.
Quoted 7 lines
Do you actually need a DMI quirk for this platform?
the .driver_data below uses the exact same settings as what you would use with the generic solution based on ACPI IDs, see below.
Wondering if patch1 would be enough?
Dooly has DMI family string " Google_Hatch" so the DMI quirk will overwrite the driver_data. I asked google but they prefer not removing this string so it seems to me that one extra DMI quirk is needed.
{
.callback = sof_rt5682_quirk_cb,
.matches = {
DMI_MATCH(DMI_PRODUCT_FAMILY, "Google_Hatch"),
},
.driver_data = (void *)(SOF_RT5682_MCLK_EN |
SOF_RT5682_MCLK_24MHZ |
SOF_RT5682_SSP_CODEC(0) |
SOF_SPEAKER_AMP_PRESENT |
SOF_RT5682_SSP_AMP(1)),
},The other way is using acpi_dev_present() in probe to update the quirk with correct codec setting. Which one do you think is better?
Regards,
Brent
Re: [PATCH 2/2] ASoC: intel: sof_rt5682: Add quirk for Dooly
Quoted 11 lines · Brent
Quoted 10 lines · Brent Lu
Quoted 4 lines
This DMI product family string of this board is "
Google_Hatch" so the DMI quirk will take place. However, this board is using rt1015 speaker amp instead of max98357a specified in the quirk. Therefore, we need an new DMI quirk for this board.Do you actually need a DMI quirk for this platform?
the .driver_data below uses the exact same settings as what you would use with the generic solution based on ACPI IDs, see below.
Quoted 6 lines
Quoted 2 lines
Wondering if patch1 would be enough?
Dooly has DMI family string "
Google_Hatch" so the DMI quirk will overwrite thedriver_data. I asked google but they prefer not removing this string so it seems to me that one extra DMI quirk is needed.
I find this pretty funny. The PRODUCT_FAMILY was added to reduce the number of quirks, but of course there's a variant that has nothing to do with this 'FAMILY'.
You should add a comment on this, to make sure this information remains in the code and we don't lose it during code cleanups.
Quoted 13 lines
{
.callback = sof_rt5682_quirk_cb,
.matches = {
DMI_MATCH(DMI_PRODUCT_FAMILY, "Google_Hatch"),
},
.driver_data = (void *)(SOF_RT5682_MCLK_EN |
SOF_RT5682_MCLK_24MHZ |
SOF_RT5682_SSP_CODEC(0) |
SOF_SPEAKER_AMP_PRESENT |
SOF_RT5682_SSP_AMP(1)),
},Quoted 2 lines
The other way is using
acpi_dev_present()in probe to update the quirk with correct codec setting. Which one do you think is better?
The DMI quirk you added is probably better for now, I don't know if the odds of getting things right with acpi_dev_present() are that high or if we are going to get even more variants on top of this variant (e.g. tweeter/booster cases...). If we get too many quirks we'll see later if we can simplify.
So if you don't mind adding a comment on the 'Dooly' quirk in a v3 that series is good to go. Thank you!
Mark Brown
maintainerRe: [PATCH 2/2] ASoC: intel: sof_rt5682: Add quirk for Dooly
In reply to Lu, BrentQuoted 7 lines · Brent
Quoted 1 line · Brent Lu
Wondering if patch1 would be enough?
Dooly has DMI family string "
Google_Hatch" so the DMI quirk will overwrite thedriver_data. I asked google but they prefer not removing this string so it seems to me that one extra DMI quirk is needed.
I think this needs at least a comment otherwise someone might come along later and clean it up.
Quoted 2 lines
The other way is using
acpi_dev_present()in probe to update the quirk with correct codec setting. Which one do you think is better?
I don't have a strong opinion either way.