public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 2/2] ARM: tegra: Add high speed UARTs to Jetson TK1 device tree
Date: Tue, 26 Jan 2016 12:27:50 -0700	[thread overview]
Message-ID: <56A7C8B6.6090405@wwwdotorg.org> (raw)
In-Reply-To: <1453827558-10954-3-git-send-email-ralf@ramses-pyramidenbau.de>

On 01/26/2016 09:59 AM, Ralf Ramsauer wrote:
> This patch enables the APB DMA high speed UARTs of the Jetson TK1. So
> far, they were only enabled in NVidia's official BSP.
>
> Those additional UARTs are exposed on the expansion connector J3A2:
>
>   UART1:
>    Pin 41: BR_UART1_TXD
>    Pin 44: BR_UART1_RXD
>
>   UART2:
>    Pin 65: UART2_RXD
>    Pin 68: UART2_TXD
>    Pin 71: UART2_CTS_L
>    Pin 74: UART2_RTS_L

The series,
Acked-by: Stephen Warren <swarren@nvidia•com>


As an aside, this is perfectly OK, but I wonder why you chose to use 
compatible=nvidia,tegra124-hsuart rather than 
compatible=nvidia,tegra124-uart. The -hsuart driver has had less testing 
upstream, whereas the regular -uart driver is heavily used for the main 
serial console. I assume you tested the new driver when enabling the 
ports:-)

  reply	other threads:[~2016-01-26 19:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 16:59 [PATCH v2 0/2] ARM: tegra: Enable high speed UARTs of the Jetson TK1 Ralf Ramsauer
2016-01-26 16:59 ` [PATCH v2 1/2] ARM: tegra: Fixed typo Ralf Ramsauer
2016-01-27  7:59   ` Alexandre Courbot
2016-01-27  8:45     ` Ralf Ramsauer
2016-01-27  9:15       ` Alexandre Courbot
2016-01-27 14:10         ` Thierry Reding
2016-01-26 16:59 ` [PATCH v2 2/2] ARM: tegra: Add high speed UARTs to Jetson TK1 device tree Ralf Ramsauer
2016-01-26 19:27   ` Stephen Warren [this message]
2016-01-26 19:35     ` Ralf Ramsauer
2016-01-27 14:15   ` Thierry Reding

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=56A7C8B6.6090405@wwwdotorg.org \
    --to=swarren@wwwdotorg$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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