From: Manuel Lauss <manuel.lauss@googlemail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-input@vger.kernel.org
Subject: Re: WM9712 GPIO
Date: Wed, 12 May 2010 14:50:44 +0200 [thread overview]
Message-ID: <AANLkTimGhfLPxAIhtTYoUO-te1mUs86LEVEcYN7DgOtY@mail.gmail.com> (raw)
In-Reply-To: <20100512123026.GA8082@rakim.wolfsonmicro.main>
On Wed, May 12, 2010 at 2:30 PM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Wed, May 12, 2010 at 01:47:12PM +0200, Manuel Lauss wrote:
>
>> I'm playing with the GPIO interface on a WM9712G, specifically GPIO1
>> and 2 of the chip.
>> However I'm unable to get the chip to toggle any of these pins.
>
>> Setting a pin with
>> wm97xx_set_gpio(wm, WM97XX_GPIO_1, WM97XX_GPIO_HIGH);
>
>> reads back 0x0820 from GPIO status reg, sets bit 1,writes back 0x1044 (<<1),
>> but a read following immediately after yields 0x0820 again, and the pin
>> never changes.
>
>> Am I missing something?
>
> The WM9712 does not support this feature. It only supports setting the
> GPIO status by use of AC'97 slot 12 for which there's currently no
> standard glue on Linux. Setting slot 12 needs to be done in the AC'97
> controller.
Wonderful. Thanks for the info.
Manuel Lauss
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-05-12 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 11:47 WM9712 GPIO Manuel Lauss
2010-05-12 12:30 ` Mark Brown
2010-05-12 12:50 ` Manuel Lauss [this message]
2010-05-12 12:52 ` Mark Brown
2010-05-12 12:54 ` Manuel Lauss
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=AANLkTimGhfLPxAIhtTYoUO-te1mUs86LEVEcYN7DgOtY@mail.gmail.com \
--to=manuel.lauss@googlemail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-input@vger.kernel.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).