From: Greg KH <gregkh@linuxfoundation.org>
To: Mihai Sain <mihai.sain@microchip.com>
Cc: alexandre.belloni@bootlin.com, claudiu.beznea@tuxon.dev,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
jirislaby@kernel.org, richard.genoud@bootlin.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] tty: atmel_serial: print the controller version
Date: Tue, 8 Oct 2024 11:13:35 +0200 [thread overview]
Message-ID: <2024100822-mantra-customize-cab1@gregkh> (raw)
In-Reply-To: <20241008083459.51249-1-mihai.sain@microchip.com>
On Tue, Oct 08, 2024 at 11:34:59AM +0300, Mihai Sain wrote:
> Add support to print the controller version similar
> to other at91 drivers like spi and twi.
>
> Signed-off-by: Mihai Sain <mihai.sain@microchip.com>
> ---
> drivers/tty/serial/atmel_serial.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/tty/serial/atmel_serial.c b/drivers/tty/serial/atmel_serial.c
> index 09b246c9e389..5f93974918c0 100644
> --- a/drivers/tty/serial/atmel_serial.c
> +++ b/drivers/tty/serial/atmel_serial.c
> @@ -2970,6 +2970,8 @@ static int atmel_serial_probe(struct platform_device *pdev)
> */
> clk_disable_unprepare(atmel_port->clk);
>
> + dev_info(&pdev->dev, "AT91 USART Controller version %#x",
> + atmel_uart_readl(&atmel_port->uart, ATMEL_US_VERSION));
> return 0;
>
> err_add_port:
>
> base-commit: 87d6aab2389e5ce0197d8257d5f8ee965a67c4cd
> --
> 2.47.0
>
Did I miss patch 2/2 of this series? I don't see it anywhere :(
prev parent reply other threads:[~2024-10-08 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 8:34 [PATCH 1/2] tty: atmel_serial: print the controller version Mihai Sain
2024-10-08 8:37 ` Greg KH
[not found] ` <PH8PR11MB6804E661B89912C18703AC6A827E2@PH8PR11MB6804.namprd11.prod.outlook.com>
2024-10-08 9:09 ` Greg KH
2024-10-08 9:13 ` Greg KH [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=2024100822-mantra-customize-cab1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=jirislaby@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mihai.sain@microchip.com \
--cc=richard.genoud@bootlin.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;
as well as URLs for NNTP newsgroup(s).