From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 6/6] T210: Add support for 64-bit T210-based P2571 board
Date: Wed, 29 Jul 2015 10:09:57 -0600 [thread overview]
Message-ID: <55B8FAD5.9060700@wwwdotorg.org> (raw)
In-Reply-To: <20150729110753.GC2398@ulmo.nvidia.com>
On 07/29/2015 05:07 AM, Thierry Reding wrote:
> On Tue, Jul 28, 2015 at 01:27:07PM -0600, Stephen Warren wrote:
>> On 07/24/2015 04:01 PM, Tom Warren wrote:
>>> Based on Venice2, incorporates Stephen Warren's
>>> latest P2571 pinmux table.
>>>
>>> With Thierry Reding's 64-bit build fixes, this
>>> will build and and boot in 64-bit on my P2571
>>> (when used with a 32-bit AVP loader).
>>
>>> diff --git a/board/nvidia/p2571/max77620_init.c b/board/nvidia/p2571/max77620_init.c
>>
>>> +void pmic_enable_cpu_vdd(void)
>>
>> This function is never called, or even linked into the binary. For previous
>> Tegra SoCs, it was called from the SPL before booting the CCPLEX. Since
>> there is no SPL for Tegra210, nothing calls this.
>>
>>> + debug("%s: Set LDO2 for VDDIO_SDMMC_AP power to 3.3V\n", __func__);
>>> + /* 0xF2 for 3.3v, enabled: bit7:6 = 11 = enable, bit5:0 = voltage */
>>> + reg = 0xF200 | MAX77620_CNFG1_L2_REG;
>>> + tegra_i2c_ll_write_addr(MAX77620_I2C_ADDR, 2);
>>> + tegra_i2c_ll_write_data(reg, I2C_SEND_2_BYTES);
>>> + udelay(10 * 1000);
>>
>> This explains why the SD card isn't working for me on p2371-2180; I guess
>> the PMIC OTP on that board has this regulator disabled, and since this code
>> never runs, it never gets turned on. If I manually turn it on using the i2c
>> command, then "mmc dev 1" works.
>>
>> For p2571, I think we should either delete this file entirely. Or, at least
>> strip it down so that it's not touching global PMIC configuration but rather
>> just enabling any non-CCPLEX rails that U-Boot might need such as SD card
>> and USB, then rename the function and arrange for it to be called from
>> somewhere. I'm not sure what a good name and call-site would be yet.
>
> Have you looked at my P2371 support patches? Specifically commit "ARM:
> tegra: Add NVIDIA P2371 support" has the board-level code that I've used
> to boot upstream on the device. There's a board_mmc_power_init()
> implementation which overrides the weak dummy provided in
> drivers/mmc/mmc.c.
Do you have a git repo and branch link?
I wasn't aware that U-Boot had been ported to either p2371, so I
re-created the support for those boards yesterday for L4T's U-Boot, and
I was planning to cherry-pick them into upstream U-Boot and retest that
today.
next prev parent reply other threads:[~2015-07-29 16:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 22:00 [U-Boot] [PATCH V3 0/6] Tegra210/P2571 initial support Tom Warren
2015-07-24 22:00 ` [U-Boot] [PATCH V3 1/6] Tegra210: Fix 64-bit build warning about save_boot_params_ret() Tom Warren
2015-07-24 22:00 ` [U-Boot] [PATCH V3 2/6] Tegra: Rework KConfig options to allow 64-bit builds (T210) Tom Warren
2015-07-24 22:00 ` [U-Boot] [PATCH V3 3/6] ARM: Tegra210: Add SoC code/include files for T210 Tom Warren
2015-07-27 17:52 ` Stephen Warren
2015-07-27 17:58 ` Tom Warren
2015-07-24 22:00 ` [U-Boot] [PATCH V3 4/6] ARM: Tegra210: Add support to common Tegra source/config files Tom Warren
2015-07-27 17:54 ` Stephen Warren
2015-07-27 17:59 ` Tom Warren
2015-07-24 22:00 ` [U-Boot] [PATCH V3 5/6] P2571: dts: Add DT file for Tegra210 P2571 board Tom Warren
2015-07-24 22:01 ` [U-Boot] [PATCH V3 6/6] T210: Add support for 64-bit T210-based " Tom Warren
2015-07-27 17:58 ` Stephen Warren
2015-07-28 19:27 ` Stephen Warren
2015-07-28 20:48 ` Tom Warren
2015-07-29 11:07 ` Thierry Reding
2015-07-29 15:57 ` Tom Warren
2015-07-29 16:09 ` Stephen Warren [this message]
2015-07-30 10:47 ` Thierry Reding
2015-07-27 18:00 ` [U-Boot] [PATCH V3 0/6] Tegra210/P2571 initial support Stephen Warren
2015-07-27 18:03 ` Tom Warren
2015-07-27 21:51 ` Tom Warren
2015-07-27 22:08 ` Tom Rini
2015-07-27 22:51 ` Tom Warren
2015-07-28 3:20 ` Stephen 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=55B8FAD5.9060700@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox