All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: "Thierry Reding" <treding@nvidia.com>,
	"Tom Warren" <twarren@nvidia.com>,
	"Tom Rini" <trini@konsulko.com>, "Simon Glass" <sjg@chromium.org>,
	"Jonas Schwöbel" <jonasschwoebel@yahoo.de>,
	u-boot@lists.denx.de
Subject: Re: [PATCH v7 4/7] board: asus: transformer: add ASUS Transformer T30 family support
Date: Fri, 23 Jun 2023 13:32:30 +0200	[thread overview]
Message-ID: <ZJWCziALx2Akx63y@orome> (raw)
In-Reply-To: <20230623055600.246416-5-clamor95@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]

On Fri, Jun 23, 2023 at 08:55:57AM +0300, Svyatoslav Ryhel wrote:
[...]
> diff --git a/board/asus/transformer-t30/pinmux-config-transformer.h b/board/asus/transformer-t30/pinmux-config-transformer.h
> new file mode 100644
> index 0000000000..96ff45d375
> --- /dev/null
> +++ b/board/asus/transformer-t30/pinmux-config-transformer.h
> @@ -0,0 +1,365 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +/*
> + * Copyright (c) 2010-2013, NVIDIA CORPORATION.  All rights reserved.
> + *
> + * Copyright (c) 2021, Svyatoslav Ryhel.
> + */

I don't recall if we discussed this during upstreaming of the Linux
device tree files, but shortly after the initial support for Tegra20 and
Tegra30 was upstreamed (both in U-Boot and in Linux) we decided to move
towards generating the pinmux configuration for the various consumers
(i.e. U-Boot and Linux) from data tables using a set of scripts. This
was done because we noticed that various inconsistencies kept creeping
into the various drivers/tables.

You can find the scripts for this here:

	https://github.com/NVIDIA/tegra-pinmux-scripts

I think there'd be some benefit if these new boards were also converted
to use these scripts.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-06-23 11:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23  5:55 [PATCH v7 0/7] Tegra: add ASUS/Google Nexus 7 (2012) support Svyatoslav Ryhel
2023-06-23  5:55 ` [PATCH v7 1/7] configs: tegra-common-post: add GPIO keyboard as STDIN device Svyatoslav Ryhel
2023-06-23  5:55 ` [PATCH v7 2/7] configs: tegra-common-post: make PXE and DHCP boot targets optional Svyatoslav Ryhel
2023-06-23  5:55 ` [PATCH v7 3/7] ARM: tegra: add SoC UID calculation function Svyatoslav Ryhel
2023-06-23 11:24   ` Thierry Reding
2023-06-23 11:46     ` Svyatoslav Ryhel
2023-06-23 14:25       ` Thierry Reding
2023-06-23 14:45         ` Svyatoslav Ryhel
2023-06-23  5:55 ` [PATCH v7 4/7] board: asus: transformer: add ASUS Transformer T30 family support Svyatoslav Ryhel
2023-06-23 11:32   ` Thierry Reding [this message]
2023-06-23 11:51     ` Svyatoslav Ryhel
2023-06-23 14:11       ` Thierry Reding
2023-06-23 14:19         ` Svyatoslav Ryhel
2023-06-23 14:26           ` Thierry Reding
2023-06-23  5:55 ` [PATCH v7 5/7] board: asus: grouper: add Google Nexus 7 (2012) support Svyatoslav Ryhel
2023-06-23  5:55 ` [PATCH v7 6/7] board: lg: x3: add Optimus 4X HD and Optimus Vu support Svyatoslav Ryhel
2023-06-23  5:56 ` [PATCH v7 7/7] board: htc: endeavoru: add One X support Svyatoslav Ryhel
2023-06-27 15:15   ` Svyatoslav Ryhel

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=ZJWCziALx2Akx63y@orome \
    --to=thierry.reding@gmail.com \
    --cc=clamor95@gmail.com \
    --cc=jonasschwoebel@yahoo.de \
    --cc=sjg@chromium.org \
    --cc=treding@nvidia.com \
    --cc=trini@konsulko.com \
    --cc=twarren@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.