From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [RFC PATCH v11 4/5] PCI / PM: Add support for the PCIe WAKE# signal for OF Date: Fri, 29 Dec 2017 09:16:39 -0800 Message-ID: <20171229171639.GJ3875@atomide.com> References: <20171225114742.18920-1-jeffy.chen@rock-chips.com> <20171228165134.GH3875@atomide.com> <6120485.xubBpvge6h@aspire.rjw.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Rafael J. Wysocki" Cc: JeffyChen , Linux Kernel Mailing List , Bjorn Helgaas , Linux PM , Shawn Lin , Brian Norris , Doug Anderson , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Linux PCI , Rob Herring , Frank Rowand List-Id: devicetree@vger.kernel.org * Rafael J. Wysocki [171228 17:46]: > > To be precise, it is not quite possible to figure out which WAKE# > triggered, if they are sharing the line, without looking into the > config spaces of the devices below the switch. The switch is not > expected to do that AFAICS. It only generates a PME message meaning > "wakeup is being signaled somewhere below" and the PME driver that > handles the Root Port receiving it should look at the PME Status bits > of the devices below the switch (the pme.c driver does that IIRC or at > least it should do that ;-)). > > Still, the handling of WAKE# doesn't need to cover this case AFAICS. OK makes sense now. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html