From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Richard Genoud <richard.genoud@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-serial@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tty/serial: atmel: ensure state is restored after suspending
Date: Mon, 6 Feb 2017 10:31:42 +0100 [thread overview]
Message-ID: <8d788b97-5dfa-1beb-e561-2a558a62e56b@atmel.com> (raw)
In-Reply-To: <20170203225316.10466-1-alexandre.belloni@free-electrons.com>
Le 03/02/2017 à 23:53, Alexandre Belloni a écrit :
> When going to suspend, the UART registers may be lost because the power to
> VDDcore is cut. This is not an issue in the normal case but when
> no_console_suspend is used, we need to restore the registers in order to
> get a functional console.
>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Reviewed-by: Nicolas Ferre <nicolas.ferre@microchip.com>
Thanks,
> ---
> drivers/tty/serial/atmel_serial.c | 44 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 44 insertions(+)
>
> diff --git a/drivers/tty/serial/atmel_serial.c b/drivers/tty/serial/atmel_serial.c
> index 168b10cad47b..22e0a73c0cb7 100644
> --- a/drivers/tty/serial/atmel_serial.c
> +++ b/drivers/tty/serial/atmel_serial.c
> @@ -175,6 +175,17 @@ struct atmel_uart_port {
> unsigned int pending_status;
> spinlock_t lock_suspended;
>
> + struct {
> + u32 cr;
> + u32 mr;
> + u32 imr;
> + u32 brgr;
> + u32 rtor;
> + u32 ttgr;
> + u32 fmr;
> + u32 fimr;
> + } cache;
> +
> int (*prepare_rx)(struct uart_port *port);
> int (*prepare_tx)(struct uart_port *port);
> void (*schedule_rx)(struct uart_port *port);
> @@ -2649,6 +2660,20 @@ static int atmel_serial_suspend(struct platform_device *pdev,
> cpu_relax();
> }
>
> + if (atmel_is_console_port(port) && !console_suspend_enabled) {
> + /* Cache register values as we won't get a full shutdown/startup
> + * cycle
> + */
> + atmel_port->cache.mr = atmel_uart_readl(port, ATMEL_US_MR);
> + atmel_port->cache.imr = atmel_uart_readl(port, ATMEL_US_IMR);
> + atmel_port->cache.brgr = atmel_uart_readl(port, ATMEL_US_BRGR);
> + atmel_port->cache.rtor = atmel_uart_readl(port,
> + atmel_port->rtor);
> + atmel_port->cache.ttgr = atmel_uart_readl(port, ATMEL_US_TTGR);
> + atmel_port->cache.fmr = atmel_uart_readl(port, ATMEL_US_FMR);
> + atmel_port->cache.fimr = atmel_uart_readl(port, ATMEL_US_FIMR);
> + }
> +
> /* we can not wake up if we're running on slow clock */
> atmel_port->may_wakeup = device_may_wakeup(&pdev->dev);
> if (atmel_serial_clk_will_stop()) {
> @@ -2671,6 +2696,25 @@ static int atmel_serial_resume(struct platform_device *pdev)
> struct atmel_uart_port *atmel_port = to_atmel_uart_port(port);
> unsigned long flags;
>
> + if (atmel_is_console_port(port) && !console_suspend_enabled) {
> + atmel_uart_writel(port, ATMEL_US_MR, atmel_port->cache.mr);
> + atmel_uart_writel(port, ATMEL_US_IER, atmel_port->cache.imr);
> + atmel_uart_writel(port, ATMEL_US_BRGR, atmel_port->cache.brgr);
> + atmel_uart_writel(port, atmel_port->rtor,
> + atmel_port->cache.rtor);
> + atmel_uart_writel(port, ATMEL_US_TTGR, atmel_port->cache.ttgr);
> +
> + if (atmel_port->fifo_size) {
> + atmel_uart_writel(port, ATMEL_US_CR, ATMEL_US_FIFOEN |
> + ATMEL_US_RXFCLR | ATMEL_US_TXFLCLR);
> + atmel_uart_writel(port, ATMEL_US_FMR,
> + atmel_port->cache.fmr);
> + atmel_uart_writel(port, ATMEL_US_FIER,
> + atmel_port->cache.fimr);
> + }
> + atmel_start_rx(port);
> + }
> +
> spin_lock_irqsave(&atmel_port->lock_suspended, flags);
> if (atmel_port->pending) {
> atmel_handle_receive(port, atmel_port->pending);
>
--
Nicolas Ferre
next prev parent reply other threads:[~2017-02-06 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 22:53 Alexandre Belloni
2017-02-06 9:31 ` Nicolas Ferre [this message]
2017-02-06 11:10 ` Richard Genoud
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=8d788b97-5dfa-1beb-e561-2a558a62e56b@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=richard.genoud@gmail.com \
/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
all inboxes | Powered by JetHome®