linux-kernel - RE: [EXT] Re: [PATCH] ARM: dts: imx6qdl: only enable pcie in the pcie dts file

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]

Date:   Thu, 9 Jul 2020 02:39:40 +0000
From:   Richard Zhu <hongxing.zhu@....com>
To:     Fabio Estevam <festevam@...il.com>
CC:     Shawn Guo <shawnguo@...nel.org>, dl-linux-imx <linux-imx@....com>,
        "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
        <linux-arm-kernel@...ts.infradead.org>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: RE: [EXT] Re: [PATCH] ARM: dts: imx6qdl: only enable pcie in the pcie
 dts file

> -----Original Message-----
> From: Fabio Estevam <festevam@...il.com>
> Sent: 2020年7月9日 1:49
> To: Richard Zhu <hongxing.zhu@....com>
> Cc: Shawn Guo <shawnguo@...nel.org>; dl-linux-imx <linux-imx@....com>;
> moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE
> <linux-arm-kernel@...ts.infradead.org>; linux-kernel
> <linux-kernel@...r.kernel.org>
> Subject: Re: [PATCH] ARM: dts: imx6qdl: only enable pcie in the pcie dts
> file
> 
> Hi Richard,
> 
> On Mon, Jul 6, 2020 at 5:49 AM Richard Zhu <hongxing.zhu@....com> wrote:
> >
> > Since iMX6Q/DL PCIe has the PM limitation (ERR005723 "PCIe PCIe does
> > not support L2 Power Down").
> > System suspend/resume would be broken by PCIe, if PCIe is enabled.
> > Only enable PCIe in the xxx-pcie.dts files to avoid the brokens when
> > other xxx.dtb files are used on sabresd and sabreauto boards.
> 
> We have several imx6 dts files that currently enable pcie.
> 
> Can't we have a proper software workaround for this issue instead?
> 
Hi Fabio:
Up to now, unfortunately, there is no solid confidential SW workaround for this issue.

Best Regards
Richard Zhu

> Thanks