From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: "Matti J. Aaltonen" <matti.j.aaltonen@nokia.com>,
alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com,
lrg@slimlogic.co.uk, hverkuil@xs4all.nl,
linux-media@vger.kernel.org
Subject: Re: WL1273 FM Radio driver...
Date: Wed, 02 Feb 2011 13:35:01 -0200 [thread overview]
Message-ID: <4D4979A5.1020000@redhat.com> (raw)
In-Reply-To: <20110130232358.GD2565@sortiz-mobl>
Em 30-01-2011 21:23, Samuel Ortiz escreveu:
> Hi Matti,
>
> On Tue, Jan 18, 2011 at 05:04:23PM +0200, Matti J. Aaltonen wrote:
>> Hello
>>
>> I have been trying to get the WL1273 FM radio driver into the kernel for
>> some time. It has been kind of difficult, one of the reasons is that I
>> didn't realize I should have tried to involve all relevant maintainers
>> to the discussion form the beginning (AsoC, Media and MFD). At Mark's
>> suggestion I'm trying to reopen the discussion now.
>>
>> The driver consists of an MFD core and two child drivers (the audio
>> codec and the V4L2 driver). And the question is mainly about the role of
>> the MFD driver: the original design had the IO functions in the core.
>> Currently the core is practically empty mainly because Mauro very
>> strongly wanted to have “everything” in the V4L2 driver.
> What was Mauro main concerns with having the IO part in the core ?
> A lot of MFD drivers are going that path already.
My concerns is that the V4L2-specific part of the code should be at drivers/media.
I prefer that the specific MFD I/O part to be at drivers/mfd, just like
the other drivers.
Cheers,
Mauro
next prev parent reply other threads:[~2011-02-02 15:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 15:04 WL1273 FM Radio driver Matti J. Aaltonen
2011-01-19 10:18 ` Mark Brown
2011-01-30 23:23 ` Samuel Ortiz
2011-02-02 15:35 ` Mauro Carvalho Chehab [this message]
2011-02-02 15:51 ` Mark Brown
2011-02-03 0:37 ` Samuel Ortiz
-- strict thread matches above, loose matches on Subject: below --
2011-02-07 10:52 Matti J. Aaltonen
2011-02-07 12:00 ` Mauro Carvalho Chehab
2011-02-07 12:02 ` Mark Brown
2011-02-07 12:48 ` Mauro Carvalho Chehab
2011-02-07 13:10 ` Mark Brown
2011-02-07 13:48 ` Mauro Carvalho Chehab
2011-02-07 13:52 ` Mark Brown
2011-02-07 14:17 ` Matti J. Aaltonen
2011-02-07 16:00 ` Mauro Carvalho Chehab
2011-02-08 9:15 ` Peter Ujfalusi
2011-02-08 10:09 ` [alsa-devel] " Bensaid, Selma
2011-02-08 11:02 ` Peter Ujfalusi
2011-02-08 13:47 ` [alsa-devel] " Bensaid, Selma
2011-02-09 7:14 ` Matti J. Aaltonen
2011-02-09 7:22 ` Matti J. Aaltonen
2011-02-10 9:35 ` Bensaid, Selma
2011-02-10 10:03 ` Matti J. Aaltonen
2011-02-10 11:02 ` [alsa-devel] " Mark Brown
2011-02-10 12:10 ` Matti J. Aaltonen
2011-02-10 12:28 ` Mark Brown
2011-02-10 12:57 ` Matti J. Aaltonen
2011-02-09 7:27 ` Matti J. Aaltonen
2011-02-09 8:47 ` Matti J. Aaltonen
2011-02-07 14:09 ` Matti J. Aaltonen
2011-02-07 15:57 ` Mauro Carvalho Chehab
2011-02-07 16:01 ` Mark Brown
2011-02-07 13:27 ` Matti J. Aaltonen
2011-02-07 13:28 ` Mark Brown
2011-02-07 13:34 ` Matti J. Aaltonen
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=4D4979A5.1020000@redhat.com \
--to=mchehab@redhat.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.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).