On Mon, Feb 20, 2017 at 10:33:32AM +0800, Simon Ho wrote:
On Sun, Feb 19, 2017 at 04:27:17PM +0000, Mark Brown wrote:
through standard interfaces? This tends to end up creating problems with things like power management as for example userspace might not figure out that things like suspend and resume are happening.
This device is designed for virtual assisant application need to be always open, listening for users to summon it. There is no any power saving mode support on this device. The processed voice data will be sent to automatic
Power management is just one example of system integration, and frankly even there it's entirely possible that someone will want to disable the functionality some of the time and hence power down the device.
So such as mute and volume gain control are not necessary. These tunnels commands are actucally for debugging purpose only, they won't be used on normal operation.
So are they even needed in mainline? How will the device function within the system, there's no visible interface for reading back status...? Right now it's hard to see how this device functions usefully in a system.