From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]:48133 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754378Ab1BBPfX (ORCPT ); Wed, 2 Feb 2011 10:35:23 -0500 Message-ID: <4D4979A5.1020000@redhat.com> Date: Wed, 02 Feb 2011 13:35:01 -0200 From: Mauro Carvalho Chehab MIME-Version: 1.0 To: Samuel Ortiz CC: "Matti J. Aaltonen" , 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... References: <1295363063.25951.67.camel@masi.mnp.nokia.com> <20110130232358.GD2565@sortiz-mobl> In-Reply-To: <20110130232358.GD2565@sortiz-mobl> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit List-ID: Sender: 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