public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: <Rengarajan.S@microchip.com>
To: <jirislaby@kernel.org>, <linux-serial@vger.kernel.org>,
	<gregkh@linuxfoundation.org>, <UNGLinuxDriver@microchip.com>,
	<Kumaravel.Thiagarajan@microchip.com>,
	<linux-kernel@vger.kernel.org>,
	<Tharunkumar.Pasumarthi@microchip.com>
Subject: Re: [PATCH v1 tty-next] 8250: microchip: pci1xxxx: Add PCIe Hot reset disable support for Rev C0 and later devices
Date: Thu, 24 Apr 2025 03:57:29 +0000	[thread overview]
Message-ID: <52fb85019a97095c081609b4f106fe10023b441f.camel@microchip.com> (raw)
In-Reply-To: <3292610b-acb0-4b72-8aa8-9eec491238c5@kernel.org>

Hi Jiri Slaby,

Thanks for reviewing the patch.

On Wed, 2025-04-23 at 07:11 +0200, Jiri Slaby wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
> 
> On 23. 04. 25, 5:38, 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@microchip.com>
> > ---
> >   drivers/tty/serial/8250/8250_pci1xxxx.c | 18 ++++++++++++++++--
> >   1 file changed, 16 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/tty/serial/8250/8250_pci1xxxx.c
> > b/drivers/tty/serial/8250/8250_pci1xxxx.c
> > index e9c51d4e447d..ec573327590f 100644
> > --- a/drivers/tty/serial/8250/8250_pci1xxxx.c
> > +++ b/drivers/tty/serial/8250/8250_pci1xxxx.c
> > @@ -115,6 +115,7 @@
> > 
> >   #define UART_RESET_REG                              0x94
> >   #define UART_RESET_D3_RESET_DISABLE         BIT(16)
> > +#define UART_RESET_HOT_RESET_DISABLE            BIT(17)
> > 
> >   #define UART_BURST_STATUS_REG                       0x9C
> >   #define UART_TX_BURST_FIFO                  0xA0
> > @@ -620,7 +621,13 @@ static int pci1xxxx_suspend(struct device
> > *dev)
> >       }
> > 
> >       data = readl(p + UART_RESET_REG);
> > -     writel(data | UART_RESET_D3_RESET_DISABLE, p +
> > UART_RESET_REG);
> > +
> > +     if (priv->dev_rev >= 0xC0)
> > +             writel(data | (UART_RESET_D3_RESET_DISABLE |
> > +                    UART_RESET_HOT_RESET_DISABLE), p +
> > UART_RESET_REG);
> > +     else
> > +             writel(data | UART_RESET_D3_RESET_DISABLE,
> > +                    p + UART_RESET_REG);
> 
> Instead of this overly long lines, could you just:
>    data |= UART_RESET_HOT_RESET_DISABLE;
> and keep the writel() as is?

Sure will update the code in the next revision.

> 
> thanks,
> --
> js
> suse labs

      reply	other threads:[~2025-04-24  3:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23  3:38 [PATCH v1 tty-next] 8250: microchip: pci1xxxx: Add PCIe Hot reset disable support for Rev C0 and later devices Rengarajan S
2025-04-23  5:11 ` Jiri Slaby
2025-04-24  3:57   ` Rengarajan.S [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52fb85019a97095c081609b4f106fe10023b441f.camel@microchip.com \
    --to=rengarajan.s@microchip.com \
    --cc=Kumaravel.Thiagarajan@microchip.com \
    --cc=Tharunkumar.Pasumarthi@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox