From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Tegra114: pinmux: Fix bad CAM_MCLK func 3 table entry
Date: Wed, 13 Mar 2013 17:26:28 -0600 [thread overview]
Message-ID: <51410B24.9080105@wwwdotorg.org> (raw)
In-Reply-To: <CA+m5__KeKWZkjiBMbbA_hQ4JXW609txXddB9pNfJKaC7fEkNyg@mail.gmail.com>
On 03/13/2013 04:55 PM, Tom Warren wrote:
> On Wed, Mar 13, 2013 at 3:34 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 03/13/2013 04:10 PM, Tom Warren wrote:
>>> This caused CAM_MCLK's pinmux reg to be locked out, since the
>>> table parsing code couldn't find a matching entry for VI_ALT3
>>> and wrote garbage to the register.
>>
>>> diff --git a/arch/arm/cpu/tegra114-common/pinmux.c b/arch/arm/cpu/tegra114-common/pinmux.c
>>
>>> @@ -239,7 +239,7 @@ const struct tegra_pingroup_desc tegra_soc_pingroups[PINGRP_COUNT] = {
>>
>>> - PINI(CAM_MCLK, CAM, VI, VI_ALT1, VI_ALT2, RSVD4),
>>> + PINI(CAM_MCLK, CAM, VI, VI_ALT1, VI_ALT3, RSVD4),
>>
>> This doesn't seem right; the "alt" settings should be assigned in order
>> non-alt, alt1, alt2, alt3.
>
> According to the TRM, CAM_MCLK takes the following 4 possible mux settings:
>
> 0 = VI
> 1 = VI_ALT1
> 2 = VI_ALT3
> 3 = RSVD3
>
> There is no VI_ALT2 in the Tegra114 TRM. There was in the T30 TRM.
Uggh, yes. The TRM is screwed up. Best to match it though I suppose.
So, the change is fine, and ends up matching the kernel's pinmux table
too. It might be a good idea to check for any other diffs.
prev parent reply other threads:[~2013-03-13 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 22:10 [U-Boot] [PATCH] Tegra114: pinmux: Fix bad CAM_MCLK func 3 table entry Tom Warren
2013-03-13 22:34 ` Stephen Warren
2013-03-13 22:55 ` Tom Warren
2013-03-13 23:26 ` Stephen Warren [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=51410B24.9080105@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