[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b56a3b02-3fd9-4461-b223-ba8b50d25157@kernel.org>
Date: Mon, 28 Apr 2025 07:34:29 +0200
From: Jiri Slaby <jirislaby@...nel.org>
To: Rengarajan S <rengarajan.s@...rochip.com>,
kumaravel.thiagarajan@...rochip.com, tharunkumar.pasumarthi@...rochip.com,
gregkh@...uxfoundation.org, linux-serial@...r.kernel.org,
linux-kernel@...r.kernel.org, unglinuxdriver@...rochip.com
Subject: Re: [PATCH v3 tty-next] 8250: microchip: pci1xxxx: Add PCIe Hot reset
disable support for Rev C0 and later devices
On 25. 04. 25, 16:55, Rengarajan S wrote:
> Systems that issue PCIe hot reset requests during a suspend/resume
> cycle cause PCI1XXXX device revisions prior to C0 to get its UART
> configuration registers reset to hardware default values. This results
> in device inaccessibility and data transfer failures. Starting with
> Revision C0, support was added in the device hardware (via the Hot
> Reset Disable Bit) to allow resetting only the PCIe interface and its
> associated logic, but preserving the UART configuration during a hot
> reset. This patch enables the hot reset disable feature during suspend/
> resume for C0 and later revisions of the device.
>
> Signed-off-by: Rengarajan S <rengarajan.s@...rochip.com>
My
Reviewed-by: Jiri Slaby <jirislaby@...nel.org>
still holds.
--
js
suse labs
Powered by blists - more mailing lists