Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Ralf Ramsauer <ralf-ex4EvEgDZR1o7HI0AxOeTKwczVv4G7md@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/2] ARM: tegra: Add high speed UARTs to Jetson TK1 device tree
Date: Thu, 21 Jan 2016 01:10:20 +0100	[thread overview]
Message-ID: <56A021EC.7010409@ramses-pyramidenbau.de> (raw)
In-Reply-To: <56A01499.9060509-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

Hi Stephen,

On 01/21/16 00:13, Stephen Warren wrote:
> On 01/19/2016 06:12 AM, Ralf Ramsauer wrote:
>> This patch enables the APB DMA high speed UARTs of the Jetson TK1.
>
>> diff --git a/arch/arm/boot/dts/tegra124-jetson-tk1.dts
>> b/arch/arm/boot/dts/tegra124-jetson-tk1.dts
>
>> +    /* First high speed UART */
>> +    serial@0,70006000 {
>> +        compatible = "nvidia,tegra124-hsuart", "nvidia,tegra30-hsuart";
>> +        status = "okay";
>> +    };
>
> It would be nice if the comment described the HW connectivity, i.e.
> which signals the UART was connected to on the board, just like the
> comments for other IO controllers already enabled in the DT file. I'd
> suggest replacing the comment above with:
>
> /* Expansion BR_UART1_RXD/_TXD */
I'll be more verbose with commenting in the next round
>
>> +    /* Second high speed UART */
>> +    serial@0,70006040 {
>> +        compatible = "nvidia,tegra124-hsuart", "nvidia,tegra30-hsuart";
>> +        status = "okay";
>> +    };
>
> ... and that commetn with:
>
> /* Expansion UART2_RXD/_TXD/_RTS/_CTS */
Ack
>
>> +
>> +    /* Third high speed UART */
>> +    serial@0,70006200 {
>> +        compatible = "nvidia,tegra124-hsuart", "nvidia,tegra30-hsuart";
>> +        status = "okay";
>> +    };
>
> That UART doesn't seem to be used at all according to the schematics
> and pinmux spreadsheet. Do you have any reference to the contrary
> aside from the L4T DT file? I believe it shouldn't be enabled.
Just checked it, and yes, you're absolutely right. I used the L4T device
tree as reference. Can't tell you why, but it appears that they
activated all uarts.
This is a short excerpt of Nvidias official DT:

            serial@70006000 {
                    compatible = "nvidia,tegra114-hsuart";
                    status = "okay";
            };

            serial@70006040 {
                    compatible = "nvidia,tegra114-hsuart";
                    status = "okay";
            };

            serial@70006200 {
                    compatible = "nvidia,tegra114-hsuart";
                    status = "okay";
            };

        serial@70006300 {
            compatible = "nvidia,tegra20-uart", "nvidia,tegra114-hsuart";
            console-port;
            sqa-automation-port;
            status = "okay";
        };


This is a short excerpt of /proc/iomem of a Jetson TK1 running latest
stock L4T linux:

    70006000-7000603f : /serial@70006000
    70006040-7000607f : /serial@70006040
    70006200-7000623f : /serial@70006200
    70006300-7000631f : serial

Let me doublecheck that again - in fact only two of three high speed
UARTs are actually exposed to the expansion header. (besides the strange
fact, that nvidia seems to have all uarts enabled...)

According to [1]:
uart1 - expansion connector
uart2 - expansion connector
uart3 - ???
uart4 - DB9 RS232 connector

I'll check this in a few days again. Thanks for review, Stephen!

Ralf

[1]
http://developer.download.nvidia.com/embedded/jetson/TK1/2014-03-24/JetsonTK1_ModuleSpecification_PM375_V1.0.pdf

-- 
Ralf Ramsauer
GPG: 0x8F10049B

  parent reply	other threads:[~2016-01-21  0:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 13:12 [PATCH 0/2] ARM: tegra: Enable high speed UARTs of the Jetson TK1 Ralf Ramsauer
     [not found] ` <1453209155-6213-1-git-send-email-ralf-ex4EvEgDZR1o7HI0AxOeTKwczVv4G7md@public.gmane.org>
2016-01-19 13:12   ` [PATCH 1/2] ARM: tegra: Fixed typo Ralf Ramsauer
     [not found]     ` <1453209155-6213-2-git-send-email-ralf-ex4EvEgDZR1o7HI0AxOeTKwczVv4G7md@public.gmane.org>
2016-01-19 16:29       ` Stephen Warren
     [not found]         ` <569E6469.10301-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2016-01-19 16:36           ` Ralf Ramsauer
2016-01-19 13:12   ` [PATCH 2/2] ARM: tegra: Add high speed UARTs to Jetson TK1 device tree Ralf Ramsauer
     [not found]     ` <1453209155-6213-3-git-send-email-ralf-ex4EvEgDZR1o7HI0AxOeTKwczVv4G7md@public.gmane.org>
2016-01-19 16:32       ` Stephen Warren
     [not found]         ` <569E652E.5020907-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2016-01-19 17:16           ` Ralf Ramsauer
     [not found]             ` <569E6F72.1000702-ex4EvEgDZR1o7HI0AxOeTKwczVv4G7md@public.gmane.org>
2016-01-20 22:54               ` Stephen Warren
2016-01-20 23:13       ` Stephen Warren
     [not found]         ` <56A01499.9060509-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2016-01-21  0:10           ` Ralf Ramsauer [this message]
2016-01-26 16:26           ` Ralf Ramsauer

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=56A021EC.7010409@ramses-pyramidenbau.de \
    --to=ralf-ex4evegdzr1o7hi0axoetkwczvv4g7md@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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