All of lore.kernel.org
 help / color / mirror / Atom feed
From: viresh.kumar@st.com (Viresh KUMAR)
To: linux-arm-kernel@lists.infradead.org
Subject: Query on direction_output fn of PL061 GPIO driver.
Date: Tue, 13 Apr 2010 17:10:41 +0530	[thread overview]
Message-ID: <4BC45839.1080902@st.com> (raw)
In-Reply-To: <20100413113237.GA2212@tarshish>

On 4/13/2010 5:02 PM, Baruch Siach wrote:
>> > In current implementation, firstly value of GPIO pin is modified and then its
>> > direction is set to OUT. In our SOCs (ST SPEAr), this implementation doesn't
>> > work correctly (we have pl061 in our soc). Suppose previously pin is in IN mode,
>> > now writing val to it doesn't change anything because it is in IN mode and we
>> > can write to a pin only when it is in OUT mode. Now if its direction is
>> > changed to OUT then also its value will remain same and will not be changed to
>> > what we wanted.
>> > 
>> > Am i missing something?
> Probably not. This is a design bug in the PL061 hardware. Changing the 
> direction before the value makes the output value of the GPIO undefined 
> (apparently 0) for a short period of time. This is bad news for some 
> applications.
> 

thanks for your prompt reply.
Ok. so this may cause problem on the board. 
Anyway if this is the issue, then writing value to val register has no effects.

> Anyway, the right thing to do here is to reverse do just that, since the 
> current way of doing things is broken.

I didn't get it completely. If i got it correctly, maybe myself or you can just
send a patch to reverse this, i.e. writing val and setting direction.
Am i correct?

regards,
viresh kumar.

  reply	other threads:[~2010-04-13 11:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13 10:50 Query on direction_output fn of PL061 GPIO driver Viresh KUMAR
2010-04-13 11:32 ` Baruch Siach
2010-04-13 11:40   ` Viresh KUMAR [this message]
2010-04-13 11:53     ` Baruch Siach
2010-04-13 18:57       ` Russell King - ARM Linux
2010-04-14  5:29         ` Baruch Siach
2010-04-15  4:14           ` Viresh KUMAR
2010-04-17 18:20             ` Baruch Siach

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=4BC45839.1080902@st.com \
    --to=viresh.kumar@st.com \
    --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 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.