Using, # R32 (release), REVISION: 3.1
Per this post:
https://forums.developer.nvidia.com/t/tx2-rt5639-on-r32-1/76743/9?u=iank
I’m modifying the ‘01-tegra-rt565x.conf’ file with some amixer settings we’d like present at flash and moving forward. I had assumed that it would be a good idea to place these additional settings inside of the ‘Tegra RT565x Init’ section of the config file.
At around line 21 this is present:
CTL{name}="x TDM Data Mux",PROGRAM!="__ctl_search",GOTO="Tegra RT565x Next"
From debugging the this file by running:
alsactl init tegrasndt186ref
I’m inferring that this a conditional saying something to the effect of: If the ‘x TDM Data Mux’ control is being fooled with and the program parsing this file isn’t ‘__ctl_search’ then goto a specified label. At which point a seconds similar conditional below the referenced goto label terminates the parsing of the configuration file.
Question: In the larger scheme of things why is this conditional present (what does it mean)? And, if I want to have my amixer settings implemented where should I park them inside of the file? I’m assuming before the first conditional statement.
I know that if I blow away my ‘/var/lib/alsa/asound.state’ and reboot the settings I want do get set, which I’m assuming means something using ‘__ctl_search’ is initializing the ALSA settings. The preferred behavior would be that one could run ‘alsactl init ’ and have the desired setting be set.
Thanks,
Ian