On Thursday 22 October 2009 02:13:11 ext Samuel Ortiz wrote:
As Mark noticed already, you dont really want users to explicitely select
this obscure mfd driver to get their audio and vibre driver selectable. It
should be the other way around, and I think you already agreed with that.
Yes, I
On Thu, Oct 22, 2009 at 09:04:32AM +0300, Peter Ujfalusi wrote:
I'll check, if the MFD patch applies to mfd-2.6:for-next also, but to have
the
soc codec changes the MFD patch should go to the sound-2.6 tree as well to
make
sure it is not braking things.
All-in-all, how these things can
On Thu, Oct 22, 2009 at 09:57:49AM +0200, Samuel Ortiz wrote:
It seems to me that this patchset is mostly an asoc one, even though all of
those patches depend on the MFD one. So I'd perfectly fine if they'd all go
through Mark's tree, and then I'd have to make sure I'm sending my 2.6.33
merge
On Thursday 22 October 2009 13:55:17 ext Mark Brown wrote:
On Thu, Oct 22, 2009 at 09:57:49AM +0200, Samuel Ortiz wrote:
It seems to me that this patchset is mostly an asoc one, even though all
of those patches depend on the MFD one. So I'd perfectly fine if they'd
all go through Mark's
Hi Peter,
On Mon, Oct 19, 2009 at 03:42:17PM +0300, Peter Ujfalusi wrote:
New MFD child to twl4030 MFD device.
This MFD device will be used by the drivers, which needs resources
from the twl4030 codec like audio and vibra.
The platform specific configuration data is passed along to the
On Mon, Oct 19, 2009 at 03:42:17PM +0300, Peter Ujfalusi wrote:
New MFD child to twl4030 MFD device.
This MFD device will be used by the drivers, which needs resources
from the twl4030 codec like audio and vibra.
The platform specific configuration data is passed along to the
child drivers
On Tuesday 20 October 2009 13:03:34 ext Mark Brown wrote:
On Mon, Oct 19, 2009 at 03:42:17PM +0300, Peter Ujfalusi wrote:
New MFD child to twl4030 MFD device.
This MFD device will be used by the drivers, which needs resources
from the twl4030 codec like audio and vibra.
The platform
New MFD child to twl4030 MFD device.
This MFD device will be used by the drivers, which needs resources
from the twl4030 codec like audio and vibra.
The platform specific configuration data is passed along to the
child drivers (audio, vibra).
Signed-off-by: Peter Ujfalusi
