All of lore.kernel.org
 help / color / mirror / Atom feed
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: pxa27x: fix ac97 controller warm reset code
Date: Sun, 06 Jan 2013 15:00:25 +0100	[thread overview]
Message-ID: <87k3rqbedi.fsf@free.fr> (raw)
In-Reply-To: 50E92385.5020107@compulab.co.il

Igor Grinberg <grinberg@compulab.co.il> writes:

> On 01/04/13 22:34, Robert Jarzmik wrote:
>> This is not the original behaviour before commit
>> fb1bf8cd13bfa7ed0364ab0d82f717fc020d35f6.
>> 
>> The original behaviour was :
>>  - on = 1 => set GPIO as output GPIO, set to 1
>>  - on = 0 => set GPIO to the alternate function ac97reset, driven by PXA2xx AC97
>>  IP.
>> 
>> If you don't set the alternate function, the GCR register usage for reset is
>> useless, isn't it ? So why do you set the GPIO as "input" with on == 0 ?
>
> Well, I've made a quick patch for Mike to test if this works and
> since it works I will submit a proper one.
Mmm...

> To your question about setting the direction,
> I'd like us to be on a safe side and not drive the pin if AF is not GPIO.
> Although it should not meter and changing the AF to ac97reset should do the job,
> but just to be on the safe side, as I think GPDR/GPCR/GPSR settings are preserved
> even if you change the AF to something other than GPIO.

I think I was not clear enough.

My point is that if you program the GPIO as input, then the PXA will not drive
the pin anymore. If you have a resistor doing the "pullup", everything will work
(as I assume is the case in your board). If not, the AC97 codec (wm9713 and
co...) could have its reset line asserted (ie. #RESET line), and *this* bothers me.

So changing the AC97 #RESET line to "GPIO input" is incorrect, and I don't agree
with the patch.

Cheers.

-- 
Robert

  reply	other threads:[~2013-01-06 14:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 14:39 [PATCH v2] ARM: pxa27x: fix ac97 controller warm reset code Mike Dunn
2013-01-04  6:50 ` Igor Grinberg
2013-01-04 10:31   ` Igor Grinberg
2013-01-04 20:29     ` Mike Dunn
2013-01-04 20:34     ` Robert Jarzmik
2013-01-05 13:06       ` Mike Dunn
2013-01-06  7:11       ` Igor Grinberg
2013-01-06 14:00         ` Robert Jarzmik [this message]
2013-01-06 16:10           ` Igor Grinberg
2013-01-06 19:04           ` Mike Dunn
2013-01-06 19:13         ` Mike Dunn

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=87k3rqbedi.fsf@free.fr \
    --to=robert.jarzmik@free.fr \
    --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.