On Sun, 26 Sep 2021 17:49:20 +0800, Shengjiu Wang wrote: > From: Viorel Suman <viorel.suman@xxxxxxx> > > Implement SPDIF bypass mode. It implies internal SoC > routing of SPDIF input signal to SPDIF output signal. The > test bed requires two boards: B1 configured in bypass mode, > and B2 to feed B1 SPDIF RX port and read B1 SPDIF TX port: > B2 TX -> B1 RX, > B2 RX <- B1 TX. > The test procedure: > a) Boot both boards > b) B2: start "arecord <spdifcard> -r 48kHz | aplay <local DAC>" > c) B2: start "aplay <spdifcard> -r 48kHz <2ch 48kHz audio file>" > d) B1: enable bypass mode: > amixer -cimxspdif cset numid=8,iface=PCM,name='Bypass Mode' on > e) B2: check DAC audio, make sure the same sample rate is used at > steps b) and c), in example above the rate is 48kHz. > f) B1: try to run "aplay" or "arecord" on imxspdif card while in > bypass mode - both must fail until bypass mode is disabled > g) B1: disable bypass mode: > amixer -cimxspdif cset numid=8,iface=PCM,name='Bypass Mode' off > h) B1: check the usual playback and capture on imxspdif card. > During this test try to set bypass mode - must not be allowed > while playback or capture is running. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/1] ASoC: fsl_spdif: implement bypass mode from in to out commit: 83bea088f976a289bc2efe4e404af47ab79d6639 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark
