On Fri, 27 Jul 2018 12:44:18 +0200, Jorge wrote:
On 19/07/18 12:56, Takashi Iwai wrote:
On Thu, 19 Jul 2018 13:22:11 +0200, Jorge Sanjuan wrote:
This patchset add support for UAC3 Power Domains. This feature of the USB audio class 3 allows the host to notify the device what it is making use of so power comsumption can be optimized.
This proposal implements this feature for Power Domains that include an Input/Output Terminal associated to an audio Streaming interface. This is the main usage of this feature according to the spec. For that reason, the logic for the Power Domain state change has been implemented within the ALSA PCMs logic and the suspend/resume callbacks of the usb_driver. The behaviour would be as follows:
- Power Domain State D0: A Power Domain will reach this state only when the audio substream associated to that domain is being used (i,e. Audio playback/capture is happening).
- Power Domain State D1: This is the Idle state where the driver is going to always want to be in order to reduce power consumption.
- Power Domain State D2: This state is only set when the usb driver asumes the device is not going to be used anymore and hence, it wont care about getting any interrupts from the device. This will only happen when power level is set to "auto" in sysfs so the usb driver gets suspended when the interfaces are not in use. NOTE: The way this has been implemented will always try to put
the Power Domain in state D1 if the Power Domain exists so there is not a way a user could disable this feature. It may be worth getting a control exposed to userland that enables/disables this feature (?).
Can it be tied with runtime PM?
Need to read through your patchset at first...
thanks,
Takashi
Hi,
I just realized I accidentally only replied to alsa-devel.. Sorry about that.
Thanks for resending.
I think it should be possible to tie up the D1 state changes (low power but still interrupt capable) to runtime PM. Changes to D2 are already tied to PM in this patchset. Just need to find the way to cleanly access `dev->power.runtime_auto` before the driver attempts to set D1 state. We could also let the driver only do D2<->D0 changes for now.
Hm, OK, so the partial coverage looks feasible with the runtime PM framework, at least.
I got some kbuild errors due to missing include. Should I re-send this patchset or try to go around getting it tied up to runtime PM first?
Let's fix the easy issues with kbuild and get them merged. The proper power state support can be implemented later.
thanks,
Takashi