From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: Robert Jarzmik <robert.jarzmik@free.fr>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
patches@opensource.wolfsonmicro.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: wm9713: add gpio chip
Date: Thu, 5 Nov 2015 10:26:55 +0000 [thread overview]
Message-ID: <20151105102655.GN1717@sirena.org.uk> (raw)
In-Reply-To: <20151104183322.GD2549@ck-lbox>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
On Wed, Nov 04, 2015 at 06:33:22PM +0000, Charles Keepax wrote:
> You should probably make a seperate driver within GPIO for this
> and then tie the two together, using an MFD. I appreciate that is
> more work but it is likely a nicer solution overall.
GPIO chips are small and simple enough that we've not worried about it
historically. However my question here is why this is wm9713 specific -
the GPIO functionality is part of the AC'97 spec and present on many
AC'97 chips so it seems sensible to have something at the AC'97 level.
Unfortunately a quick check seems not to show anything indicating this
in the AC'97 capability information so we might want to make it opt in.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-11-05 10:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 17:12 [PATCH] ASoC: wm9713: add gpio chip Robert Jarzmik
2015-11-04 18:33 ` Charles Keepax
2015-11-04 19:35 ` Robert Jarzmik
2015-11-05 9:48 ` Charles Keepax
2015-11-06 9:29 ` Lee Jones
2015-11-06 9:27 ` Charles Keepax
2015-11-06 9:48 ` Lee Jones
2015-11-06 20:47 ` Robert Jarzmik
2015-11-06 21:22 ` Mark Brown
2015-11-05 10:26 ` Mark Brown [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=20151105102655.GN1717@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=perex@perex.cz \
--cc=robert.jarzmik@free.fr \
--cc=tiwai@suse.com \
/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).