From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [RFC SOF 1/2] topology: Add sof-byt-codec-tdm4.m4 file
Date: Mon, 7 Dec 2020 09:11:10 -0600 [thread overview]
Message-ID: <1272e367-6600-198d-e93f-ba2bfa2c6c0f@linux.intel.com> (raw)
In-Reply-To: <20201206124626.13932-2-hdegoede@redhat.com>
Hi Hans,
> Some BYT/CHT boards (mostly Cherry Trail) use TDM 4 slots 24 bit as
> wire format to the codec, rather then standard I2S 2 channel 24 bit.
>
> Add a new m4 file for this. This is a copy of sof-byt-codec.m4 with
> the following changes:
>
> @@ -1,4 +1,4 @@
> -`# Topology for generic' PLATFORM `board with' CODEC `on SSP' SSP_NUM
> +`# Topology for generic' PLATFORM `board with' CODEC `on SSP' SSP_NUM `using TDM 4 slots 24 bit'
>
> # Include topology builder
> include(`utils.m4')
> @@ -97,8 +97,8 @@
> # BE configurations - overrides config in ACPI if present
> #
> DAI_CONFIG(SSP, SSP_NUM, 0, SSP2-Codec,
> - SSP_CONFIG(I2S, SSP_CLOCK(mclk, 19200000, codec_mclk_in),
> - SSP_CLOCK(bclk, 2400000, codec_slave),
> + SSP_CONFIG(DSP_B, SSP_CLOCK(mclk, 19200000, codec_mclk_in),
> + SSP_CLOCK(bclk, 4800000, codec_slave),
> SSP_CLOCK(fsync, 48000, codec_slave),
> - SSP_TDM(2, 25, 3, 3),
> + SSP_TDM(4, 25, 3, 3),
> SSP_CONFIG_DATA(SSP, SSP_NUM, 24)))
I don't think this change is necessary, the problem is probably that we
still rely on the hard-coded 4 slots in the machine driver which was the
default for the Atom/SST driver.
If I look at the cht_bsw_nau8824.c driver, the only place where there is
a reference to 4 slots is in the cht_codec_init() function.
https://elixir.bootlin.com/linux/latest/source/sound/soc/intel/boards/cht_bsw_nau8824.c#L104
In other drivers, this was moved to the codec_fixup routine which is
overridden/ignored when SOF is used.
see e.g.
https://elixir.bootlin.com/linux/latest/source/sound/soc/intel/boards/cht_bsw_max98090_ti.c
https://elixir.bootlin.com/linux/latest/source/sound/soc/intel/boards/cht_bsw_rt5645.c
If you follow the same pattern that should make this problem go away.
When SOF is used we typically don't have any hard-coded format and
whatever is defined in the topology is propagated to the codec driver.
Hope this helps
-Pierre
next prev parent reply other threads:[~2020-12-07 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 12:46 [RFC SOF 0/2] topology: Try to add sof-cht-nau8824 topology file Hans de Goede
2020-12-06 12:46 ` [RFC SOF 1/2] topology: Add sof-byt-codec-tdm4.m4 file Hans de Goede
2020-12-07 15:11 ` Pierre-Louis Bossart [this message]
2020-12-07 15:17 ` Hans de Goede
2020-12-06 12:46 ` [RFC SOF 2/2] topology: Add sof-cht-nau8824 topology file Hans de Goede
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1272e367-6600-198d-e93f-ba2bfa2c6c0f@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=hdegoede@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.