From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Matti J. Aaltonen" <matti.j.aaltonen@nokia.com>
Cc: alsa-devel@alsa-project.org, sameo@linux.intel.com,
ext Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: WL1273 FM radio: Access I2C IO functions through pointers.
Date: Thu, 13 Jan 2011 17:12:02 +0000 [thread overview]
Message-ID: <20110113171202.GG30351@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1294935501.6390.44.camel@masi.mnp.nokia.com>
On Thu, Jan 13, 2011 at 06:18:21PM +0200, Matti J. Aaltonen wrote:
> I'm not changing the MFD driver, the first version is hopefully going
> into the v. 2.6.38 kernel.
Oh, fail.
> At first I started to upstream all three parts of the driver at the same
> time, about a year ago. At first I sent all parts to the media list,
> there I was - quite reasonably - asked to send the codec to the alsa
> list. After some tuning and fine tuning the codec got accepted. But
> getting the rest of the driver in took much longer and in the process
> the MFD and V4L2 parts became incompatible with the codec.
This is something that should really have been brought up when making
changes. It's really bad to just go and make other bits of the kernel
fail to build.
While looking at this I also notice that it's surprisingly difficult to
actually build any of this stuff - the MFD core can't be enabled
directly, it's only available if you enable the V4L driver, and the core
V4L build appears to be rather large adding a noticable amount of time
to the build needed to get coverage of the CODECs. It'd be good if you
could fix this to remove the dependency, I'd really expect the MFD to be
able to build by itself.
> So we'll just wait until 2.6.38 is out and everything remains
> compilable... When 38 gets released the codec cannot be used with rest
> of the driver until this patch is applied, but that can be done when a
> suitable window opens, right?
*Ideally* we'd have this API change included as part of the MFD driver
merge or included in 2.6.37 since otherwise we cause build issues. ASoC
has already been sent to Linus for this merge window. As it is I guess
we have to apply this and send a fix later.
next prev parent reply other threads:[~2011-01-13 17:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 13:22 [PATCH] ASoC: WL1273 FM radio: Access I2C IO functions through pointers Matti J. Aaltonen
2011-01-13 13:34 ` Mark Brown
2011-01-13 13:35 ` Liam Girdwood
2011-01-13 14:17 ` Matti J. Aaltonen
2011-01-13 15:01 ` Mark Brown
2011-01-13 16:18 ` Matti J. Aaltonen
2011-01-13 17:12 ` Mark Brown [this message]
2011-01-14 7:43 ` Matti J. Aaltonen
2011-01-14 12:22 ` Mark Brown
2011-01-17 8:52 ` Matti J. Aaltonen
2011-01-17 13:56 ` Mark Brown
2011-01-17 14:58 ` Matti J. Aaltonen
2011-01-17 15:15 ` 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=20110113171202.GG30351@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=matti.j.aaltonen@nokia.com \
--cc=sameo@linux.intel.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).