Hello Pavel, DT maintainers,
[a question about DT bindings below]
On Wed, 6 Mar 2024 08:43:57 +0100
Pavel Hofman <pavel.hofman@xxxxxxxxxxx> wrote:
> On 05. 03. 24 15:36, Luca Ceresoli wrote:
> > The sample rates set by the rockchip_i2s_tdm driver in master mode are
> > inaccurate up to 5% in several cases, due to the driver logic to configure
> > clocks and a nasty interaction with the Common Clock Framework.
> >
> > To understand what happens, here is the relevant section of the clock tree
> > (slightly simplified), along with the names used in the driver:
> >
> > vpll0 _OR_ vpll1 "mclk_root"
> > clk_i2s2_8ch_tx_src "mclk_parent"
> > clk_i2s2_8ch_tx_mux
> > clk_i2s2_8ch_tx "mclk" or "mclk_tx"
> >
> > This is what happens when playing back e.g. at 192 kHz using
> > audio-graph-card (when recording the same applies, only s/tx/rx/):
> >
> > 0. at probe, rockchip_i2s_tdm_set_sysclk() stores the passed frequency in
> > i2s_tdm->mclk_tx_freq (*) which is 50176000, and that is never modified
> > afterwards
> >
> > 1. when playback is started, rockchip_i2s_tdm_hw_params() is called and
> > does the following two calls
> >
> > 2. rockchip_i2s_tdm_calibrate_mclk():
> >
> > 2a. selects mclk_root0 (vpll0) as a parent for mclk_parent
> > (mclk_tx_src), which is OK because the vpll0 rate is a good for
> > 192000 (and sumbultiple) rates
> >
> > 2b. sets the mclk_root frequency based on ppm calibration computations
> >
> > 2c. sets mclk_tx_src to 49152000 (= 256 * 192000), which is also OK as
> > it is a multiple of the required bit clock
> >
> > 3. rockchip_i2s_tdm_set_mclk()
> >
> > 3a. calls clk_set_rate() to set the rate of mclk_tx (clk_i2s2_8ch_tx)
> > to the value of i2s_tdm->mclk_tx_freq (*), i.e. 50176000 which is
> > not a multiple of the sampling frequency -- this is not OK
> >
> > 3a1. clk_set_rate() reacts by reparenting clk_i2s2_8ch_tx_src to
> > vpll1 -- this is not OK because the default vpll1 rate can be
> > divided to get 44.1 kHz and related rates, not 192 kHz
> >
> > The result is that the driver does a lot of ad-hoc decisions about clocks
> > and ends up in using the wrong parent at an unoptimal rate.
> >
> > Step 0 is one part of the problem: unless the card driver calls set_sysclk
> > at each stream start, whatever rate is set in mclk_tx_freq during boot will
> > be taken and used until reboot. Moreover the driver does not care if its
> > value is not a multiple of any audio frequency.
> >
> > Another part of the problem is that the whole reparenting and clock rate
> > setting logic is conflicting with the CCF algorithms to achieve largely the
> > same goal: selecting the best parent and setting the closest clock
> > rate. And it turns out that only calling once clk_set_rate() on
> > clk_i2s2_8ch_tx picks the correct vpll and sets the correct rate.
> >
> > The fix is based on removing the custom logic in the driver to select the
> > parent and set the various clocks, and just let the Clock Framework do it
> > all. As a side effect, the set_sysclk() op becomes useless because we now
> > let the CCF compute the appropriate value for the sampling rate. It also
> > implies that the whole calibration logic is now dead code and so it is
> > removed along with the "PCM Clock Compensation in PPM" kcontrol, which has
> > always been broken anyway. The handling of the 4 optional clocks also
> > becomes dead code and is removed.
> >
> > The actual rates have been tested playing 30 seconds of audio at various
> > sampling rates before and after this change using sox:
> >
> > time play -r <sample_rate> -n synth 30 sine 950 gain -3
> >
> > The time reported in the table below is the 'real' value reported by the
> > 'time' command in the above command line.
> >
> > rate before after
> > --------- ------ ------
> > 8000 Hz 30.60s 30.63s
> > 11025 Hz 30.45s 30.51s
> > 16000 Hz 30.47s 30.50s
> > 22050 Hz 30.78s 30.41s
> > 32000 Hz 31.02s 30.43s
> > 44100 Hz 30.78s 30.41s
> > 48000 Hz 29.81s 30.45s
> > 88200 Hz 30.78s 30.41s
> > 96000 Hz 29.79s 30.42s
> > 176400 Hz 27.40s 30.41s
> > 192000 Hz 29.79s 30.42s
> >
> > While the tests are running the clock tree confirms that:
> >
> > * without the patch, vpll1 is always used and clk_i2s2_8ch_tx always
> > produces 50176000 Hz, which cannot be divided for most audio rates
> > except the slowest ones, generating inaccurate rates
> > * with the patch:
> > - for 192000 Hz vpll0 is used
> > - for 176400 Hz vpll1 is used
> > - clk_i2s2_8ch_tx always produces (256 * <rate>) Hz
> >
> > Tested on the RK3308 using the internal audio codec.
> >
> > Fixes: 081068fd6414 ("ASoC: rockchip: add support for i2s-tdm controller")
> > Signed-off-by: Luca Ceresoli <luca.ceresoli@xxxxxxxxxxx>
> >
>
> I tested this patch, it works OK on 8ch I2S0 of RK3308 Radxa Pi S,
> frequencies checked in clock summary and clock pins with an
> oscilloscope. It's basically identical issue with the same cause as I
> reported in
> https://lore.kernel.org/alsa-devel/20240304134329.392c75bf@booty/T/#m19d69461aa827f15a86d6d31ed1b1520e80a909e
>
>
> Just a note - the patch changes mclk frequencies from fixed 256 x
> 192000/176400 to variable 256 x fs. While 256 x fs is more standard
> than the fixed mclk for all samplerates of the same family, it may cause
> changes for existing users if using the mclk output pins. But the
> existing code was broken and had to be hacked to work anyway. Perhaps
> this may need some considering.
Thanks for clearly describing this difference.
This is something I considered and in the end I found no reason to use
256 x 192000/176400 as it would use higher clocks than needed (or
equal, at 192 and 176.4 kHz), deviating from the common practice and
probably consuming a little more power, all apparently without any
gains. And, last but not least, without a motivation in the docs I have
available.
Of course, should there be known reasons to keep the 256 x
192000/176400 frequencies, I'd be fine with changing my patch.
> Also I wonder if the DTS description rockchip,i2s-tdm.yaml file may be
> updated too, as some clocks listed by it are removed by the patch:
>
> -const: mclk_tx_src
> -const: mclk_rx_src
> -const: mclk_root0
> -const: mclk_root1
>
> IMO it may be a bit confusing if the description lists parameters which
> are not actually used by the driver anymore.
You have a good point. I just checked the git history and indeed these
four clocks have never been mentioned by any of the device trees in
mainline.
However removal of parts of bindings is normally never supposed to
happen for backward compatibility.
@DT maintainers: would removal of optional clocks from bindings allowed
in this specific case?
Quick facts:
* bindings introduced in 2021, with the 4 optional clocks from the
beginning, no changes afterwards
* none of the optional clocks ever appeared in arch/.../*.dts
* the 4 optional clocks actually describe a part of the clock topology,
so their presence in I2S bindings is debatable at least
* the I2S controller described by the bindings does not need the
4 optional clocks to work properly if the clocks are used correctly,
as this patch proves
If this looks like a good idea, I can send a patch to remove those
optional clocks. Otherwise I can send one to add a comment to
discourage people from using them.
Best regards,
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
