From: Lee Jones <lee.jones@linaro.org>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] ASoC: wm9713: add gpio chip
Date: Fri, 6 Nov 2015 09:29:13 +0000 [thread overview]
Message-ID: <20151106092913.GC3378@x1> (raw)
In-Reply-To: <87oaf9bls9.fsf@belgarion.home>
On Wed, 04 Nov 2015, Robert Jarzmik wrote:
> Charles Keepax <ckeepax@opensource.wolfsonmicro.com> writes:
>
> > On Wed, Nov 04, 2015 at 06:12:44PM +0100, Robert Jarzmik wrote:
> >> The Wolfson WM9713 provides 8 GPIOs. If the gpiolib is compiled in the
> >> kernel, declare a gpio chip.
> >>
> >> Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
> >> ---
> >
> > 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.
>
> I'd like to first have a confirmation from :
> - Mark (Brown)
> - and Lee (Jones)
>
> The confirmation I'm looking for states that :
> - the wm9713 should have a part in the mfd tree
> - the gpio part should be in drivers/gpio
> - the sound soc codecs will remain as is
> - if the future driver/mfd/wm9713.c is technically sound, it will be accepted
>
> I remember at least one example where the MFD approach was rejected from mfd
> tree for pxa gpios, so I won't work unless I have a confirmation from both
> maintainers.
I have no idea what you're talking about. Context please?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
Mark Brown <broonie@kernel.org>,
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: Fri, 6 Nov 2015 09:29:13 +0000 [thread overview]
Message-ID: <20151106092913.GC3378@x1> (raw)
In-Reply-To: <87oaf9bls9.fsf@belgarion.home>
On Wed, 04 Nov 2015, Robert Jarzmik wrote:
> Charles Keepax <ckeepax@opensource.wolfsonmicro.com> writes:
>
> > On Wed, Nov 04, 2015 at 06:12:44PM +0100, Robert Jarzmik wrote:
> >> The Wolfson WM9713 provides 8 GPIOs. If the gpiolib is compiled in the
> >> kernel, declare a gpio chip.
> >>
> >> Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
> >> ---
> >
> > 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.
>
> I'd like to first have a confirmation from :
> - Mark (Brown)
> - and Lee (Jones)
>
> The confirmation I'm looking for states that :
> - the wm9713 should have a part in the mfd tree
> - the gpio part should be in drivers/gpio
> - the sound soc codecs will remain as is
> - if the future driver/mfd/wm9713.c is technically sound, it will be accepted
>
> I remember at least one example where the MFD approach was rejected from mfd
> tree for pxa gpios, so I won't work unless I have a confirmation from both
> maintainers.
I have no idea what you're talking about. Context please?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-11-06 9:29 UTC|newest]
Thread overview: 15+ 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 18:33 ` Charles Keepax
2015-11-04 19:35 ` Robert Jarzmik
2015-11-04 19:35 ` Robert Jarzmik
2015-11-05 9:48 ` Charles Keepax
2015-11-05 9:48 ` Charles Keepax
2015-11-06 9:29 ` Lee Jones [this message]
2015-11-06 9:29 ` Lee Jones
2015-11-06 9:27 ` Charles Keepax
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
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=20151106092913.GC3378@x1 \
--to=lee.jones@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--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 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.