On Thu, 12 Dec 2019 at 17:48, Rafael J. Wysocki wrote:
>
> On Thu, Dec 12, 2019 at 2:32 PM Ulf Hansson wrote:
> >
> > On Thu, 12 Dec 2019 at 13:33, Thierry Reding
> > wrote:
> > >
> > > On Thu, Dec 12, 2019 at 09:52:22AM +0100, Ulf Hansson wrote:
> > > > On Mon, 9 Dec 2019 at 14:03, Thierry
On Mon, 9 Dec 2019 at 14:03, Thierry Reding wrote:
>
> From: Thierry Reding
>
> The Tegra DRM driver heavily relies on the implementations for runtime
> suspend/resume to be called at specific times. Unfortunately, there are
> some cases where that doesn't work. One example is if the user
On Thu, 12 Dec 2019 at 13:33, Thierry Reding wrote:
>
> On Thu, Dec 12, 2019 at 09:52:22AM +0100, Ulf Hansson wrote:
> > On Mon, 9 Dec 2019 at 14:03, Thierry Reding
> > wrote:
> > >
> > > From: Thierry Reding
> > >
> > > The Tegra DRM driver heavily relies on the implementations for runtime
>
On Thu, Dec 12, 2019 at 2:32 PM Ulf Hansson wrote:
>
> On Thu, 12 Dec 2019 at 13:33, Thierry Reding wrote:
> >
> > On Thu, Dec 12, 2019 at 09:52:22AM +0100, Ulf Hansson wrote:
> > > On Mon, 9 Dec 2019 at 14:03, Thierry Reding
> > > wrote:
> > > >
> > > > From: Thierry Reding
> > > >
> > > >
On Thu, Dec 12, 2019 at 09:52:22AM +0100, Ulf Hansson wrote:
> On Mon, 9 Dec 2019 at 14:03, Thierry Reding wrote:
> >
> > From: Thierry Reding
> >
> > The Tegra DRM driver heavily relies on the implementations for runtime
> > suspend/resume to be called at specific times. Unfortunately, there
From: Thierry Reding
The Tegra DRM driver heavily relies on the implementations for runtime
suspend/resume to be called at specific times. Unfortunately, there are
some cases where that doesn't work. One example is if the user disables
runtime PM for a given subdevice. Another example is that
