[Sound-open-firmware] [PATCH v4 7/7] topology: add DMIC dai support in test capture m4

Seppo Ingalsuo seppo.ingalsuo at linux.intel.com
Mon May 28 13:40:59 CEST 2018



On 27.05.2018 09:30, Ranjani Sridharan wrote:
> Add support for adding DMIC config for DMIC DAI type.
>
> Signed-off-by: Ranjani Sridharan <ranjani.sridharan at linux.intel.com>
> ---
>   topology/test/test-capture.m4 | 24 +++++++++++++++++-------
>   1 file changed, 17 insertions(+), 7 deletions(-)
>
> diff --git a/topology/test/test-capture.m4 b/topology/test/test-capture.m4
> index a1f283f..56fda8f 100644
> --- a/topology/test/test-capture.m4
> +++ b/topology/test/test-capture.m4
> @@ -69,10 +69,20 @@ PCM_CAPTURE_ADD(Passthrough, 3, 0, 0, PIPELINE_PCM_2)
>   # TEST_SSP_DATA_BITS bit I2S using TEST_SSP_PHY_BITS bit sample conatiner on SSP TEST_DAI_PORT
>   #
>   DAI_CONFIG(TEST_DAI_TYPE, TEST_DAI_PORT, TEST_DAI_LINK_NAME,
> -	   SSP_CONFIG(TEST_SSP_MODE,
> -		      DAI_CLOCK(mclk, TEST_SSP_MCLK, codec_mclk_in),
> -		      DAI_CLOCK(bclk, TEST_SSP_BCLK, codec_slave),
> -		      DAI_CLOCK(fsync, 48000, codec_slave),
> -		      DAI_TDM(2, TEST_SSP_PHY_BITS, 3, 3),
> -		      SSP_SAMPLE_BITS(TEST_DAI_TYPE, TEST_DAI_PORT,
> -				      TEST_SSP_DATA_BITS)))
> +	   ifelse(TEST_DAI_TYPE, `SSP',
> +		  SSP_CONFIG(TEST_SSP_MODE,
> +			     DAI_CLOCK(mclk, TEST_SSP_MCLK, codec_mclk_in),
> +			     DAI_CLOCK(bclk, TEST_SSP_BCLK, codec_slave),
> +			     DAI_CLOCK(fsync, 48000, codec_slave),
> +			     DAI_TDM(2, TEST_SSP_PHY_BITS, 3, 3),
> +			     SSP_SAMPLE_BITS(TEST_DAI_TYPE, TEST_DAI_PORT,
> +					     TEST_SSP_DATA_BITS)),
> +		  TEST_DAI_TYPE, `DMIC',
> +		  DMIC_CONFIG(TEST_DMIC_DRIVER_VERSION,TEST_DMIC_CLK_MIN,
> +			      TEST_DMIC_CLK_MAX, TEST_DMIC_DUTY_MIN,
> +			      TEST_DMIC_DUTY_MAX, TEST_PDM_ACTIVE,
> +			      TEST_DMIC_SAMPLE_RATE, DMIC_WORD_LENGTH(TEST_DAI_FORMAT),
> +			      TEST_DAI_TYPE, TEST_DAI_PORT,
> +			      PDM_CONFIG(TEST_DAI_TYPE, TEST_DAI_PORT,
> +					 LIST(`', PDM_TUPLES(0, 1, 1, 0, 0, 0, 0)))),

When there's need to make a 4ch capture topology would TEST_PDM_ACTIVE 
be set to 2 and the PDM_TUPLES macro arguments be duplicated with 
another 0110000 (where the "1" values are mic enables)? Or is this 
function OK as such to use with any value of TEST_PDM_ACTIVE within HW 
capability limits and as long as both microphones of a stereo PDM 
controller are used?

Creating a mono single microphone capture topology obviously needs a new 
test test-capture.m4 macro version.


Thanks,
Seppo



> +		  `'))



More information about the Sound-open-firmware mailing list