On Thu, 24 Jan 2019 20:01:13 +0100,
Sameer Pujar wrote:
>
>
> On 1/25/2019 12:13 AM, Takashi Iwai wrote:
> > On Thu, 24 Jan 2019 19:15:12 +0100,
> > Sameer Pujar wrote:
> >>
> >> On 1/24/2019 9:34 PM, Takashi Iwai wrote:
> >>> On Thu, 24 Jan 2019 16:57:11 +0100,
> >>> Sameer Pujar wrote:
>
On 1/25/2019 12:13 AM, Takashi Iwai wrote:
On Thu, 24 Jan 2019 19:15:12 +0100,
Sameer Pujar wrote:
On 1/24/2019 9:34 PM, Takashi Iwai wrote:
On Thu, 24 Jan 2019 16:57:11 +0100,
Sameer Pujar wrote:
The runtime PM count is incremented and set to active during hda codec
device init, but it is
On Thu, 24 Jan 2019 19:15:12 +0100,
Sameer Pujar wrote:
>
>
> On 1/24/2019 9:34 PM, Takashi Iwai wrote:
> > On Thu, 24 Jan 2019 16:57:11 +0100,
> > Sameer Pujar wrote:
> >> The runtime PM count is incremented and set to active during hda codec
> >> device init, but it is decremented and set to
On 1/24/2019 9:34 PM, Takashi Iwai wrote:
On Thu, 24 Jan 2019 16:57:11 +0100,
Sameer Pujar wrote:
The runtime PM count is incremented and set to active during hda codec
device init, but it is decremented and set to suspend during exit only.
Hence the runtime PM status is always active and hda
On Thu, 24 Jan 2019 16:57:11 +0100,
Sameer Pujar wrote:
>
> The runtime PM count is incremented and set to active during hda codec
> device init, but it is decremented and set to suspend during exit only.
> Hence the runtime PM status is always active and hda device cannot be
> put to runtime
The runtime PM count is incremented and set to active during hda codec
device init, but it is decremented and set to suspend during exit only.
Hence the runtime PM status is always active and hda device cannot be
put to runtime suspend. Keeping device usage active for entire period,
though nothing
6 matches
Mail list logo
