From: Thierry Reding <thierry.reding@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 15/15] ARM: tegra: Add NVIDIA Jetson Nano Developer Kit support
Date: Wed, 20 Mar 2019 11:37:54 +0100 [thread overview]
Message-ID: <20190320103754.GF6043@ulmo> (raw)
In-Reply-To: <8859e2f1-0ac3-63d5-b71a-6eb660198b90@wwwdotorg.org>
On Tue, Mar 19, 2019 at 11:18:39AM -0600, Stephen Warren wrote:
> On 3/18/19 5:24 PM, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > The Jetson Nano Developer Kit is a Tegra X1 based development board. It
> > is similar to Jetson TX1 but it is not pin compatible. It features 4 GB
> > of LPDDR4, an SPI NOR flash for early boot firmware and an SD card slot
> > used for storage.
> >
> > HDMI 2.0 or DP 1.2 are available for display, four USB ports (3 USB 2.0
> > and 1 USB 3.0) can be used to attach a variety of peripherals and a PCI
> > Ethernet controller provides onboard network connectivity.
> >
> > A 40-pin header on the board can be used to extend the capabilities and
> > exposed interfaces of the Jetson Nano.
>
> > diff --git a/arch/arm/dts/tegra210-p3450-0000.dts b/arch/arm/dts/tegra210-p3450-0000.dts
>
> > +/ {
> > + model = "NVIDIA Jetson Nano Development Kit";
>
> Technically, it's marketed as a "Developer Kit", not a "Development Kit".
Good catch. Fixed now.
> > + aliases {
> > + i2c0 = "/i2c at 7000d000";
> > + i2c2 = "/i2c at 7000c400";
> > + i2c3 = "/i2c at 7000c500";
> > + i2c4 = "/i2c at 7000c700";
> > + sdhci0 = "/sdhci at 700b0600";
> > + sdhci1 = "/sdhci at 700b0000";
>
> SKU 0 (the -0000 in the board name) only has 1 SD card slot and no eMMC.
>
> I personally would prefer a different build of U-Boot for each SKU (or at
> least a separate DT), so that each U-Boot exposes exactly what's present,
> not the union of all SKUs. That said, I know there's resistance to that in
> our downstream builds of U-Boot for L4T.
I had realized that at the last minute and removed the sdhci at 700b0600
node but forgot to remove the alias. I've removed it now.
> > diff --git a/arch/arm/mach-tegra/tegra210/Kconfig b/arch/arm/mach-tegra/tegra210/Kconfig
> > +config TARGET_P3450_0000
> > + bool "NVIDIA Jetson Nano Development Kit"
>
> Developer.
>
> > diff --git a/board/nvidia/p3450-0000/pinmux-config-p3450-0000.h b/board/nvidia/p3450-0000/pinmux-config-p3450-0000.h
> > +/*
> > + * THIS FILE IS AUTO-GENERATED - DO NOT EDIT!
> > + *
> > + * To generate this file, use the tegra-pinmux-scripts tool available from
> > + * https://github.com/NVIDIA/tegra-pinmux-scripts
> > + * Run "board-to-uboot.py p3450-0000".
> > + */
>
> I'd like to see the pinmux-scripts patches. And some questions there:
> - Confirm this is for the A02 board revision.
I just went through the process again of extracting the data from the
pinmux sheet and it seems like there are subtle differences. But, yes,
the new version is for the A02 revision of the board.
> - Confirm which pinmux spreadsheet version the data came from.
I've added a comment providing the origin of the data to the
tegra-pinmux-scripts patch that I've prepared.
> - Does this copy of the file delete the GPIO setup entries that are
> different between HW A01 and A02, so it will run on both boards, or does it
> contain everything so that it's only valid for A02 HW?
>
> We are only shipping A02 publicly, so I think it makes sense to include the
> complete pinmux table here, and let internal NVIDIA users of A01 just use
> only the downstream code.
The tegra-pinmux-scripts patch contains an unmodified version of the
data extracted from the pinmux spreadsheet, so I'm assuming that it has
A02 specific settings for the GPIOs. I agree that there's no need to
support anything prior to A02 in U-Boot if that hardware was never
publicly available.
> > diff --git a/include/configs/p3450-0000.h b/include/configs/p3450-0000.h
>
> > +#define CONFIG_PREBOOT
> > +
> > +#define BOARD_EXTRA_ENV_SETTINGS \
> > + "preboot=if test -e mmc 1:1 /u-boot-preboot.scr; then " \
> > + "load mmc 1:1 ${scriptaddr} /u-boot-preboot.scr; " \
> > + "source ${scriptaddr}; " \
> > + "fi\0"
>
> We might want to hold off on that until we've discussed what we want to do
> for preboot scripts and environment in L4T, so that we don't introduce some
> downstream/upstream incompatibility split here?
Good point, I'll remove this from the patch for now.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190320/386d4b51/attachment.sig>
next prev parent reply other threads:[~2019-03-20 10:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 23:24 [U-Boot] [PATCH v2 00/15] ARM: tegra: Add NVIDIA Jetson Nano Developer Kit support Thierry Reding
2019-03-18 23:24 ` [U-Boot] [PATCH v2 01/15] ARM: tegra: Use common header for PMU declarations Thierry Reding
2019-03-18 23:24 ` [U-Boot] [PATCH v2 02/15] ARM: tegra: Guard clock code with a Kconfig symbol Thierry Reding
2019-03-18 23:24 ` [U-Boot] [PATCH v2 03/15] ARM: tegra: Guard GP pad control " Thierry Reding
2019-03-18 23:24 ` [U-Boot] [PATCH v2 04/15] ARM: tegra: Guard memory controller " Thierry Reding
2019-03-18 23:24 ` [U-Boot] [PATCH v2 05/15] ARM: tegra: Guard pin " Thierry Reding
2019-03-18 23:24 ` [U-Boot] [PATCH v2 06/15] ARM: tegra: Guard powergate " Thierry Reding
2019-03-18 23:24 ` [U-Boot] [PATCH v2 07/15] ARM: tegra: Fix save_boot_params() prototype Thierry Reding
2019-03-18 23:24 ` [U-Boot] [PATCH v2 08/15] ARM: tegra: Allow boards to override boot target devices Thierry Reding
2019-03-18 23:24 ` [U-Boot] [PATCH v2 09/15] ARM: tegra: Support TZ-only access to PMC Thierry Reding
2019-03-18 23:24 ` [U-Boot] [PATCH v2 10/15] ARM: tegra: Workaround UDC boot issues only if necessary Thierry Reding
2019-03-18 23:24 ` [U-Boot] [PATCH v2 11/15] ARM: tegra: Restore DRAM bank count Thierry Reding
2019-03-18 23:24 ` [U-Boot] [PATCH v2 12/15] ARM: tegra: Unify Tegra186 builds Thierry Reding
2019-03-18 23:24 ` [U-Boot] [PATCH v2 13/15] ARM: tegra: Implement cboot_save_boot_params() in C Thierry Reding
2019-03-18 23:24 ` [U-Boot] [PATCH v2 14/15] ARM: tegra: Implement cboot_get_ethaddr() Thierry Reding
2019-03-18 23:24 ` [U-Boot] [PATCH v2 15/15] ARM: tegra: Add NVIDIA Jetson Nano Developer Kit support Thierry Reding
2019-03-19 17:18 ` Stephen Warren
2019-03-20 10:37 ` Thierry Reding [this message]
2019-03-20 11:22 ` [U-Boot] [PATCH v2 00/15] " Peter Robinson
2019-03-26 16:00 ` Thierry Reding
2019-03-26 16:06 ` Peter Robinson
2019-03-26 17:19 ` 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=20190320103754.GF6043@ulmo \
--to=thierry.reding@gmail.com \
--cc=u-boot@lists.denx.de \
/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