reedesktop.org; Christoph Haag;
> > Koenig, Christian; amd-gfx at lists.freedesktop.org; Zhang, Hawking
> > Subject: Re: ATPX changes in drm-next-4.8 and D3cold handling
> >
> > On Thu, Jul 28, 2016 at 05:40:31PM +0200, Lukas Wunner wrote:
> > > On Thu, Jul 28, 2016 at 03
king
> Subject: Re: ATPX changes in drm-next-4.8 and D3cold handling
>
> On Thu, Jul 28, 2016 at 05:40:31PM +0200, Lukas Wunner wrote:
> > On Thu, Jul 28, 2016 at 03:33:25PM +, Deucher, Alexander wrote:
> > > > From: Peter Wu [mailto:peter at lekensteyn.nl]
On Thu, Jul 28, 2016 at 05:40:31PM +0200, Lukas Wunner wrote:
> On Thu, Jul 28, 2016 at 03:33:25PM +, Deucher, Alexander wrote:
> > > From: Peter Wu [mailto:peter at lekensteyn.nl]
> > > Sent: Thursday, July 21, 2016 6:43 AM
> > > In case you missed it, Dave's D3cold patches were succeeded by
On Thu, Jul 28, 2016 at 03:33:25PM +, Deucher, Alexander wrote:
> > From: Peter Wu [mailto:peter at lekensteyn.nl]
> > Sent: Thursday, July 21, 2016 6:43 AM
> > In case you missed it, Dave's D3cold patches were succeeded by changes
> > in PCI core. Relevant commits in the pci/pm branch:
> >
>
Subject: ATPX changes in drm-next-4.8 and D3cold handling
>
> Hi Alex,
>
> There are a couple of changes for 4.8 that try to detect whether the
> "power_cntl" flag is present. Originally attributed to a firmware bug,
> it seems that the detection is performed too late r
Hi Alex,
There are a couple of changes for 4.8 that try to detect whether the
"power_cntl" flag is present. Originally attributed to a firmware bug,
it seems that the detection is performed too late resulting in flags
that are always zero
(https://bugzilla.kernel.org/show_bug.cgi?id=115321).
