LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Samuel Ortiz <sameo@openedhand.com>
Cc: Liam Girdwood <lrg@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mfd: Core support for the WM8400 AudioPlus HiFi CODEC and PMU
Date: Fri, 12 Sep 2008 13:05:23 +0100 [thread overview]
Message-ID: <20080912120522.GA21720@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20080912105413.GA4999@localdomain>
On Fri, Sep 12, 2008 at 12:54:19PM +0200, Samuel Ortiz wrote:
> > +config MFD_WM8400
> > + tristate "Support Wolfson Microelectronics WM8400"
> > + select MFD_CORE
> It seems you're not using the mfd-core API currently.
> Maybe we could get rid of this select for now ?
Done, will be in the next version I push out.
> > --- /dev/null
> > +++ b/include/linux/mfd/wm8400-private.h
> Just a remark here: many chunks from this file are really wm8400 private and
> could live in drivers/mfd/wm8400.h.
Which chunks in particular? Note that I've not currently included the
audio driver - it will need much more interaction with the core than the
regulator support does and it doesn't feel right to have it peer into
drivers/mfd for things it needs. While I have split much of that into a
separate audio header file for the next submission there are several
areas which cross over multiple functions.
> I would also prefer to have one single wm8400.h file in include/linux/mfd/,
> containing both those definitions and the ones you're adding with the
> regulator patch.
The goal in splitting out wm8400.h from wm8400-private.h was to ensure
that the (fairly small) interface intended for use by clients of the
driver was clearly separated from the interfaces intended for use within
the WM8400 drivers themselves. I'd like to keep this separation since
it makes it clearer to users which interfaces they should be using and
having to include a separate file makes this very easy to spot on
review.
next prev parent reply other threads:[~2008-09-12 12:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 18:28 [PATCH 0/2] WM8400 support Mark Brown
2008-09-10 18:28 ` [PATCH 1/2] mfd: Core support for the WM8400 AudioPlus HiFi CODEC and PMU Mark Brown
2008-09-10 18:28 ` [PATCH 2/2] regulator: Add WM8400 regulator support Mark Brown
2008-09-10 18:39 ` Liam Girdwood
2008-09-10 19:40 ` Mark Brown
2008-09-10 19:58 ` Liam Girdwood
2008-09-10 18:47 ` [PATCH 1/2] mfd: Core support for the WM8400 AudioPlus HiFi CODEC and PMU Liam Girdwood
2008-09-10 19:13 ` Mark Brown
2008-09-10 19:38 ` Liam Girdwood
2008-09-11 10:02 ` Mark Brown
2008-09-12 10:54 ` Samuel Ortiz
2008-09-12 12:05 ` Mark Brown [this message]
2008-09-12 10:58 ` [PATCH 0/2] WM8400 support Samuel Ortiz
2008-09-16 9:42 [PATCH 0/2] WM8400 support v2 Mark Brown
2008-09-16 9:43 ` [PATCH 1/2] mfd: Core support for the WM8400 AudioPlus HiFi CODEC and PMU Mark Brown
2008-09-18 2:28 ` Andrew Morton
2008-09-18 10:29 ` Mark Brown
2008-09-22 18:33 ` Samuel Ortiz
2008-09-23 0:27 ` Liam Girdwood
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=20080912120522.GA21720@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@kernel.org \
--cc=sameo@openedhand.com \
--subject='Re: [PATCH 1/2] mfd: Core support for the WM8400 AudioPlus HiFi CODEC and PMU' \
/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
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).