All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 3/6] ARM: Tegra210: Add SoC code/include files for T210
Date: Wed, 22 Jul 2015 11:44:35 -0600	[thread overview]
Message-ID: <55AFD683.4000701@wwwdotorg.org> (raw)
In-Reply-To: <1437421844-5157-4-git-send-email-twarren@nvidia.com>

On 07/20/2015 01:50 PM, Tom Warren wrote:
> All based off of Tegra124. As a Tegra210 board is brought
> up, these may change a bit to match the HW more closely,
> but probably 90% of this is identical to T124.
>
> Note that since T210 is a 64-bit build, it has no SPL
> component, and hence no cpu.c for Tegra210.

> diff --git a/arch/arm/mach-tegra/tegra210/funcmux.c b/arch/arm/mach-tegra/tegra210/funcmux.c

> +int funcmux_select(enum periph_id id, int config)
> +{
> +	int bad_config = config != FUNCMUX_DEFAULT;
> +
> +	switch (id) {
> +	case PERIPH_ID_UART4:
> +		switch (config) {
> +		case FUNCMUX_UART4_GPIO: /* TXD,RXD,CTS,RTS */
> +			pinmux_set_func(PMUX_PINGRP_UART4_TX_PI4,
> +					PMUX_FUNC_UARTD);
> +			pinmux_set_func(PMUX_PINGRP_UART4_RX_PI5,
> +					PMUX_FUNC_UARTD);
> +			pinmux_set_func(PMUX_PINGRP_UART4_CTS_PI7,
> +					PMUX_FUNC_UARTD);
> +			pinmux_set_func(PMUX_PINGRP_UART4_RTS_PI6,
> +					PMUX_FUNC_UARTD);
...
> +	case PERIPH_ID_UART1:
> +		switch (config) {
> +		case FUNCMUX_UART1_KBC:
> +			pinmux_set_func(PMUX_PINGRP_UART1_TX_PU0,
> +					PMUX_FUNC_UARTA);
> +			pinmux_set_func(PMUX_PINGRP_UART1_RX_PU1,

Those are the wrong FUNCMUX_* enum names; they're supposed to be 
FUNCMUX_${hwblock}_${pinset}. ${hwblock} is correctly UART1/4 above. 
${pinset} doesn't look right to me; I see no GPIO or KBC pins being 
used. Rather, I'd expect FUNCMUX_UART4_UART4 and FUNCMUX_UART1_UART1.

  reply	other threads:[~2015-07-22 17:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 19:50 [U-Boot] [PATCH V2 0/6] Tegra210/P2571 initial support Tom Warren
2015-07-20 19:50 ` [U-Boot] [PATCH V2 1/6] Tegra210: Fix 64-bit build warning about save_boot_params_ret() Tom Warren
2015-07-20 19:50 ` [U-Boot] [PATCH V2 2/6] Tegra: Rework KConfig options to allow 64-bit builds (T210) Tom Warren
2015-07-22 17:40   ` Stephen Warren
2015-07-22 20:05     ` Tom Warren
2015-07-20 19:50 ` [U-Boot] [PATCH V2 3/6] ARM: Tegra210: Add SoC code/include files for T210 Tom Warren
2015-07-22 17:44   ` Stephen Warren [this message]
2015-07-23 15:34     ` Tom Warren
2015-07-20 19:50 ` [U-Boot] [PATCH V2 4/6] ARM: Tegra210: Add support to common Tegra source/config files Tom Warren
2015-07-22 17:52   ` Stephen Warren
2015-07-20 19:50 ` [U-Boot] [PATCH V2 5/6] P2571: dts: Add DT files for Tegra210/P2571 board Tom Warren
2015-07-22 17:57   ` Stephen Warren
2015-07-23 17:41     ` Tom Warren
2015-07-22 18:16   ` Stephen Warren
2015-07-23 17:44     ` Tom Warren
2015-07-23 17:59       ` Stephen Warren
2015-07-23 19:06         ` Tom Warren
2015-07-23 19:30           ` Stephen Warren
2015-07-20 19:50 ` [U-Boot] [PATCH V2 6/6] T210: Add support for 64-bit T210-based P2571 board Tom Warren
2015-07-22 18:04   ` Stephen Warren
2015-07-23 23:17     ` Tom Warren
2015-07-22 18:10 ` [U-Boot] [PATCH V2 0/6] Tegra210/P2571 initial support Stephen Warren
2015-07-22 20:35 ` Stephen Warren
2015-07-22 21:07   ` Tom Warren

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=55AFD683.4000701@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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.