[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210204100021.GA2542@lahna.fi.intel.com>
Date: Thu, 4 Feb 2021 12:00:21 +0200
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: mingchuang.qiao@...iatek.com
Cc: bhelgaas@...gle.com, matthias.bgg@...il.com,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, haijun.liu@...iatek.com,
lambert.wang@...iatek.com, kerun.zhu@...iatek.com,
alex.williamson@...hat.com, rjw@...ysocki.net,
utkarsh.h.patel@...el.com
Subject: Re: [v4] PCI: Avoid unsync of LTR mechanism configuration
On Thu, Feb 04, 2021 at 05:51:25PM +0800, mingchuang.qiao@...iatek.com wrote:
> From: Mingchuang Qiao <mingchuang.qiao@...iatek.com>
>
> In bus scan flow, the "LTR Mechanism Enable" bit of DEVCTL2 register is
> configured in pci_configure_ltr(). If device and bridge both support LTR
> mechanism, the "LTR Mechanism Enable" bit of device and bridge will be
> enabled in DEVCTL2 register. And pci_dev->ltr_path will be set as 1.
>
> If PCIe link goes down when device resets, the "LTR Mechanism Enable" bit
> of bridge will change to 0 according to PCIe r5.0, sec 7.5.3.16. However,
> the pci_dev->ltr_path value of bridge is still 1.
>
> For following conditions, check and re-configure "LTR Mechanism Enable" bit
> of bridge to make "LTR Mechanism Enable" bit match ltr_path value.
> -before configuring device's LTR for hot-remove/hot-add
> -before restoring device's DEVCTL2 register when restore device state
>
> Signed-off-by: Mingchuang Qiao <mingchuang.qiao@...iatek.com>
Reviewed-by: Mika Westerberg <mika.westerberg@...ux.intel.com>
Powered by blists - more mailing lists