No, that would be quite the annoying unexpected behaviour. First, with only one tool running the other value would never be changed anyway, second, some ppl like to set it to eg 90% to reduce noise on some channels, they sure dont want this to be overruled.
Just dont look at the controls, problem solved. Why would we need a graphical tool when we have a physical wheel to turn?
I think the other one is for monitoring the battery. The pyra wiki needs to have more details. One needs to read the design file, list all hardware and make a table about which software controls which hardware....
I wasnt clear. I mean, I'd prefer the script to check the volume wheel every couple of seconds, even when there is no sound playing.
I don't think twl6030 is even loaded.
me@pyra:~$ lsmod | grep palmas
palmas_gpadc 20480 0
me@pyra:~$ lsmod | grep twl6030Use case: I've had the music at full blast in headphones. I then want to quietly play something through the speakers in a public place. I stop my loud track and unplug the headphones. I browse for a sound I want to share with the someone sat nearby. I turn the volume wheel down before starting so as not to wake the baby (lion, grandmother, whatever). I then start playing through the speakers, but its still at full blast. The baby screams, the lion eats my grandmother.
Ahh, that makes sense. Good.
It is just a little waste of SD card space for the twl6030 driver which is neither loaded nor used by the Pyra. But yes, the CONFIG can be removed which will also improve compile time a little.
Speed Delay between polling wheel in μs
Advised value: 100000 (0.1s)
Default value: 100000
Range Expected Maximal wheel value, default: 2000
Higher values limit the volume, lower allow an overdrive
Eg: 4000> 50% max volume; 1000> 200% max volume
Timout Time in seconds after polltime should be reduced to second value
Disabled when 0, Default: 0
Slow Same as Speed, applied after Timout seconds
Advised value: 1000000 (1s)
Default value: 1000000
Stayon Disables monitor of Soundcard, never turn polling off
Help This page oviously
Example: Poll very fast after sound starts playing and then every two seconds after the first 10 seconds:
vwheeld Speed 20000 Timeout 10 Slow 2000000
Example: Always poll slow, no monitoring, limit volume to 50%
vwheeld Speed 1000000 Stayon Range 4000Ah i finally got this, so lets say you decide for a slow 4s poll, then accidentally slip and set it to high, it will fry your ears for the next 4 seconds.
Once a reading is available, do some processing/filtering and, if the result differs from earlier results, wake up user space. That should be a bit more efficient than waking up an userspace application multiple times a second, which needs to switch back to kernel mode again to get the latest value.
github.com
