linux-kernel - Re: [PATCH v2 2/4] PCI: rcar: Support runtime PM link state L1 handling in pcie-rcar

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160106083536.GC1525@katana>
Date:	Wed, 6 Jan 2016 09:35:36 +0100
From:	Wolfram Sang <wsa@...-dreams.de>
To:	Phil Edworthy <phil.edworthy@...esas.com>
Cc:	Simon Horman <horms@...ge.net.au>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
	linux-sh@...r.kernel.org
Subject: Re: [PATCH v2 2/4] PCI: rcar: Support runtime PM link state L1
 handling in pcie-rcar

On Tue, Jan 05, 2016 at 01:00:29PM +0000, Phil Edworthy wrote:
> The R-Car PCIe host controller does not handle L1 ASPM. Instead, the
> hardware needs assistance to transition to L1. When the controller
> has received a PM_ENTER_L1 DLLP, we can't access a card's config regs
> until we have got it out of L1 link state. The host controller will
> handle this as long as it has also been transitioned to L1 link state.
> 
> So, when attempting a config access, check to see if the card has gone
> into L1, and if so, do the same for the host controller.
> 
> This is based on a patch by Hien Dang <hien.dang.eb@....renesas.com>
> 
> Signed-off-by: Phil Edworthy <phil.edworthy@...esas.com>
> ---
> v2:
>  - Use readl_poll_timeout_atomic when waiting until we are in L1.

Acked-by: Wolfram Sang <wsa+renesas@...g-engineering.com>


Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)