public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Felix Radensky <felix@embedded-sol.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] GPIO configuration on 460EX
Date: Thu, 16 Oct 2008 11:10:13 +0200	[thread overview]
Message-ID: <48F704F5.8040009@embedded-sol.com> (raw)
In-Reply-To: <200810160922.35491.sr@denx.de>

Hi, Stefan

Stefan Roese wrote:
> Hi Felix,
>
> On Thursday 16 October 2008, Felix Radensky wrote:
>   
>> I'm looking at GPIO setup code for Canyonlands, and
>> it looks like some initializations mentioned in the 460EX
>> manual are missing. When pin is configured as alternate
>> input, the corresponding bits in TSRL/H registers should
>> be set. U-Boot code sets TSRL/H registers only for output
>> pins.
>>
>> Am I missing something ?
>>     
>
> Looking again at the users manual I can't find that the TSR register should be 
> set for input functionality. Take a look at figure 35-1. Here you will see 
> that TSR is only involved for output functionality.
>
>   
I was looking at section 35.5.3 and Table 35-9 in user manual (Version 1.14)
TSR is involved in both input and output functionality. This indeed 
contradicts
the description you were referring to. Maybe AMCC guys reading this list can
clarify ?
> I assume that you are asking because of your Linux IRQ problem with the 
> external interrupt, correct? I'll take a look at the Linux thread and try to 
> give another answer there.
>   
Thanks a lot. Your suggestion in this thread indeed helped. I was using
wrong IRQ number in device tree.
> And feel free to test with TSR configured for input as well. If this gets your 
> interrupt working then this we need to change this GPIO config code of 
> course.
>
>   
I've tried that, but it didn't help.

Thanks a lot for you help.

Felix.

      reply	other threads:[~2008-10-16  9:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 23:46 [U-Boot] GPIO configuration on 460EX Felix Radensky
2008-10-16  7:22 ` Stefan Roese
2008-10-16  9:10   ` Felix Radensky [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=48F704F5.8040009@embedded-sol.com \
    --to=felix@embedded-sol.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox