From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Martitz Subject: Re: [PATCH] PCI: Reprogram bridge prefetch registers on resume Date: Sat, 8 Sep 2018 13:05:11 +0200 Message-ID: References: <20180907053614.6540-1-drake@endlessm.com> <20180907150515.GA28739@al> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; Format="flowed" Content-Transfer-Encoding: base64 Cc: nic_swsd-Rasf1IRRPZFBDgjK7y7TUQ@public.gmane.org, mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org, linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, rafael.j.wysocki-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org, keith.busch-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org, bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org, andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org, linux-6IF/jdPJHihWk0Htik3J/w@public.gmane.org, davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org, jonathan.derrick-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org, hkallweit1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org To: Peter Wu , Daniel Drake Return-path: In-Reply-To: <20180907150515.GA28739@al> Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Sender: "Nouveau" List-Id: netdev.vger.kernel.org QW0gMDcuMDkuMTggdW0gMTc6MDUgc2NocmllYiBQZXRlciBXdToKPiBPbiBGcmksIFNlcCAwNywg MjAxOCBhdCAwMTozNjoxNFBNICswODAwLCBEYW5pZWwgRHJha2Ugd3JvdGU6Cj4gPC4uPgo+PiBU aG9tYXMgTWFydGl0eiByZXBvcnRzIHRoYXQgdGhpcyB3b3JrYXJvdW5kIGFsc28gc29sdmVzIGFu IGlzc3VlIHdoZXJlCj4+IHRoZSBBTUQgUmFkZW9uIFBvbGFyaXMgMTAgR1BVIG9uIHRoZSBIUCBa Ym9vayAxNHUgRzUgaXMgdW5yZXNwb25zaXZlCj4+IGFmdGVyIFMzIHN1c3BlbmQvcmVzdW1lLgo+ IAo+IFdoZXJlIHdhcyB0aGlzIGNsYWltZWQ/IEl0IGlzIG5vdCBzdGF0ZWQgaW4gdGhlIGxpbmtl ZCBidWc6Cj4gKGh0dHBzOi8vYnVncy5mcmVlZGVza3RvcC5vcmcvc2hvd19idWcuY2dpP2lkPTEw NTc2MAo+IAoKCkFjdHVhbGx5LCBJIHJlcG9ydGVkIHRoYXQgaHR0cHM6Ly9wYXRjaHdvcmsua2Vy bmVsLm9yZy9wYXRjaC8xMDU4MzIyOS8gCndvcmtzLiBJIHVwZGF0ZWQgdGhlIGJ1ZyBub3csIEkg ZGlkbid0IGRvIHNvIHlldCBiZWNhdXNlIGl0J3MgY2xvc2VkLgoKSG93ZXZlciwgSSBkaWQgbm90 IGFjdHVhbGx5IHRlc3QgdGhlIGV4YWN0IHBhdGNoICp0aGlzKiB0aHJlYWQgaXMgYWJvdXQuIApE byB5b3Ugd2FudCBtZSB0byBnaXZlIGl0IGEgc3Bpbj8KCkJlc3QgcmVnYXJkcy4KX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBtYWlsaW5nIGxp c3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5mcmVlZGVza3Rv cC5vcmcvbWFpbG1hbi9saXN0aW5mby9ub3V2ZWF1Cg== From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.mailbox.org ([80.241.60.215]:10868 "EHLO mx2.mailbox.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726315AbeIHPu6 (ORCPT ); Sat, 8 Sep 2018 11:50:58 -0400 Subject: Re: [PATCH] PCI: Reprogram bridge prefetch registers on resume To: Peter Wu , Daniel Drake Cc: bhelgaas@google.com, linux-pci@vger.kernel.org, linux@endlessm.com, nouveau@lists.freedesktop.org, linux-pm@vger.kernel.org, kherbst@redhat.com, andriy.shevchenko@linux.intel.com, rafael.j.wysocki@intel.com, keith.busch@intel.com, mika.westerberg@linux.intel.com, jonathan.derrick@intel.com, davem@davemloft.net, hkallweit1@gmail.com, netdev@vger.kernel.org, nic_swsd@realtek.com References: <20180907053614.6540-1-drake@endlessm.com> <20180907150515.GA28739@al> From: Thomas Martitz Message-ID: Date: Sat, 8 Sep 2018 13:05:11 +0200 MIME-Version: 1.0 In-Reply-To: <20180907150515.GA28739@al> Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-pci-owner@vger.kernel.org List-ID: Am 07.09.18 um 17:05 schrieb Peter Wu: > On Fri, Sep 07, 2018 at 01:36:14PM +0800, Daniel Drake wrote: > <..> >> Thomas Martitz reports that this workaround also solves an issue where >> the AMD Radeon Polaris 10 GPU on the HP Zbook 14u G5 is unresponsive >> after S3 suspend/resume. > > Where was this claimed? It is not stated in the linked bug: > (https://bugs.freedesktop.org/show_bug.cgi?id=105760 > Actually, I reported that https://patchwork.kernel.org/patch/10583229/ works. I updated the bug now, I didn't do so yet because it's closed. However, I did not actually test the exact patch *this* thread is about. Do you want me to give it a spin? Best regards.