From: Mika Westerberg <mika.westerberg@intel.com>
To: Karol Herbst <kherbst@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Lyude Paul <lyude@redhat.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Linux PCI <linux-pci@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
nouveau <nouveau@lists.freedesktop.org>
Subject: Re: [PATCH v3] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges
Date: Mon, 21 Oct 2019 16:21:12 +0300 [thread overview]
Message-ID: <20191021132112.GH2819@lahna.fi.intel.com> (raw)
In-Reply-To: <CACO55tvYEvPHwFLDmLOQ_BCiNw7ZRA7dun9P=KdLb4bvYTtrcg@mail.gmail.com>
On Mon, Oct 21, 2019 at 03:02:23PM +0200, Karol Herbst wrote:
> > No, just block runtime PM from the device in nouveau driver.
>
> but that's not what the patch does. It only skips the PCI PM reg
> write, but still let the ACPI method be invoked to put the device into
> D3cold
Oh, indeed it does. I did not realize that.
Which makes me wonder whether ACPI _OFF() expects the device to be in D0
for some reason.
prev parent reply other threads:[~2019-10-21 13:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 14:44 [PATCH v3] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges Karol Herbst
2019-10-16 19:14 ` Bjorn Helgaas
2019-10-16 19:18 ` Karol Herbst
2019-10-16 21:37 ` Bjorn Helgaas
2019-10-16 21:48 ` Karol Herbst
2019-10-16 22:03 ` Bjorn Helgaas
2019-10-21 13:33 ` Mika Westerberg
2019-10-21 13:54 ` Karol Herbst
2019-10-21 14:08 ` Mika Westerberg
2019-10-21 14:49 ` Karol Herbst
2019-10-21 15:46 ` Mika Westerberg
2019-10-21 16:40 ` Karol Herbst
2019-10-22 9:16 ` Karol Herbst
2019-10-22 12:44 ` Mika Westerberg
2019-10-22 12:51 ` Karol Herbst
2019-10-23 9:00 ` Mika Westerberg
2019-10-21 11:40 ` Mika Westerberg
2019-10-21 12:00 ` Karol Herbst
2019-10-21 12:06 ` Mika Westerberg
2019-10-21 13:02 ` Karol Herbst
2019-10-21 13:21 ` Mika Westerberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191021132112.GH2819@lahna.fi.intel.com \
--to=mika.westerberg@intel.com \
--cc=bhelgaas@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox