Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Ralf Ramsauer <ralf-ex4EvEgDZR1o7HI0AxOeTKwczVv4G7md@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@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: Tue, 26 Jan 2016 17:26:06 +0100	[thread overview]
Message-ID: <56A79E1E.8040103@ramses-pyramidenbau.de> (raw)
In-Reply-To: <56A01499.9060509-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

Hi,

Now it's for sure: According to the TK1 schematics [1], uart3 is not
connected. Hence it makes no sense to enable it.
I'll prepare a next patch round.

Cheers
  Ralf

[1]
https://developer.nvidia.com/rdp/assets/jetson-tk1-datasheet-orcad-schematics
(warning, restricted access)

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 */
>
>> +    /* 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 */
>
>> +
>> +    /* 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.
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Ralf Ramsauer
GPG: 0x8F10049B

      parent reply	other threads:[~2016-01-26 16:26 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
2016-01-26 16:26           ` Ralf Ramsauer [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=56A79E1E.8040103@ramses-pyramidenbau.de \
    --to=ralf-ex4evegdzr1o7hi0axoetkwczvv4g7md@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@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