From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Jonas Danielsson <jonas@orbital-systems.com>,
linux-serial@vger.kernel.org,
Richard Genoud <richard.genoud@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
Jiri Slaby <jslaby@suse.com>
Subject: Re: [PATCH] [PATCH] tty/serial: atmel: add new version check for usart
Date: Mon, 5 Feb 2018 13:36:02 +0100 [thread overview]
Message-ID: <e20ced24-666b-32b7-92cd-d30e1a10b42e@microchip.com> (raw)
In-Reply-To: <20180129113954.12011-1-jonas@orbital-systems.com>
On 29/01/2018 at 12:39, Jonas Danielsson wrote:
> On our at91sam9260 based board the usart0 and usart1 ports report
> their versions (ATMEL_US_VERSION) as 0x10302. This version is not
> included in the current checks in the driver.
>
> Signed-off-by: Jonas Danielsson <jonas@orbital-systems.com>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
It must be the AT91SAM9260 rev. B SoC, isn't it?
Thanks for your patch.
Best regards,
Nicolas
> ---
> drivers/tty/serial/atmel_serial.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/tty/serial/atmel_serial.c b/drivers/tty/serial/atmel_serial.c
> index efa25611ca0c..ae9f1dcbf3fc 100644
> --- a/drivers/tty/serial/atmel_serial.c
> +++ b/drivers/tty/serial/atmel_serial.c
> @@ -1734,6 +1734,7 @@ static void atmel_get_ip_name(struct uart_port *port)
> switch (version) {
> case 0x302:
> case 0x10213:
> + case 0x10302:
> dev_dbg(port->dev, "This version is usart\n");
> atmel_port->has_frac_baudrate = true;
> atmel_port->has_hw_timer = true;
>
--
Nicolas Ferre
next prev parent reply other threads:[~2018-02-05 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 11:39 [PATCH] [PATCH] tty/serial: atmel: add new version check for usart Jonas Danielsson
2018-02-05 12:36 ` Nicolas Ferre [this message]
2018-02-05 14:04 ` Jonas Danielsson
2018-02-05 14:37 ` Nicolas Ferre
2018-02-16 9:27 ` 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=e20ced24-666b-32b7-92cd-d30e1a10b42e@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonas@orbital-systems.com \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).