linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: DTS: OMAP4: Panda/SDP: twl6030: fix mux for IRQ pin and msecure line
Date: Fri, 24 May 2013 15:15:41 -0700	[thread overview]
Message-ID: <87ppwgdnxu.fsf@linaro.org> (raw)
In-Reply-To: <87a9nkf3mu.fsf@linaro.org> (Kevin Hilman's message of "Fri, 24 May 2013 14:51:21 -0700")

Kevin Hilman <khilman@linaro.org> writes:

> Nishanth Menon <nm@ti.com> writes:

[...]

>> Actually 2 things:
>>
>> a) patch seems to do the wrong thing for 4460 - 0x18 offset should
>> have been used instead of 0x14 which is correct for 4430?
>
> I see, thanks.  I'll double check the TRMs.
>
>> b) yes, I understand,  the current settings we did worked, but the
>> mode(0) we are setting to is real weird - we are setting it up for
>> clk0 out - I cant even think why it is even working in the first place
>> :( - is it because we are pumping out sysclkout and as a result we are
>> lucky that msecure is being sampled at the right point by twl6030
>> allowing rtc access? either way, IMHO, the configuration is wrong.
>
> Ah, yes.  Mode zero is definitely wrong.   When I did the original patch
> for legacy mode, I just duplicated the settings u-boot was using.  Guess
> it's a fluke that it works.

Actually, for legacy mode, it's set correctly in mode 2.  This line:

	omap_mux_init_signal("fref_clk0_out.sys_drm_msecure", OMAP_PIN_OUTPUT);

does the right thing based on the signal name.    But for DT boot, I
defintely screwed it up by setting it to mode (and putting it in the
wrong padconf section.)

Also, are you *really* sure about the offset difference between 4430 and
4460 here?  I don't have access to NDA docs anymore, so I cannot double
check this.

What I do know is that the legacy code is using 0x54 for both, and if I
simply comment out that 'sys_drm_msecure' line above, RTC wake stops
working (legacy boot) on both 4430 and 4460, so that seems like pretty
stront evidence that it's the same offset on both.

Kevin

  reply	other threads:[~2013-05-24 22:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 19:28 [PATCH] ARM: DTS: OMAP4: Panda/SDP: twl6030: fix mux for IRQ pin and msecure line Kevin Hilman
2013-05-24 20:09 ` Nishanth Menon
2013-05-24 20:32   ` Nishanth Menon
2013-05-24 21:19     ` Kevin Hilman
2013-05-24 21:25       ` Nishanth Menon
2013-05-24 21:51         ` Kevin Hilman
2013-05-24 22:15           ` Kevin Hilman [this message]
2013-05-26 17:35             ` Nishanth Menon
2013-05-28 18:33               ` Kevin Hilman
2013-05-29  8:36                 ` Grygorii Strashko
2013-05-29 16:12                   ` Kevin Hilman
2013-05-29  9:36                 ` Cousson, Benoit
2013-05-29  9:38           ` Cousson, Benoit
2013-05-29 14:03             ` Kevin Hilman
2013-05-29 14:23               ` Cousson, Benoit
     [not found]                 ` <CAGa+x85ZzfX400eEGmTGPzRiC21S83VRiHYj38cqsJLjDF3L7g@mail.gmail.com>
2013-05-29 16:02                   ` Cousson, Benoit
2013-05-29 16:13                     ` Kevin Hilman
2013-05-29 16:48                       ` Benoit Cousson

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=87ppwgdnxu.fsf@linaro.org \
    --to=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).