All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	Eero Nurkkala <ext-eero.nurkkala@nokia.com>,
	Nils Faerber <nils.faerber@kernelconcepts.de>,
	Joni Lapilainen <joni.lapilainen@gmail.com>
Subject: Re: [PATCH] media: Add BCM2048 radio driver
Date: Sat, 26 Oct 2013 22:04:33 +0200	[thread overview]
Message-ID: <201310262204.33674@pali> (raw)
In-Reply-To: <201310172131.05106@pali>

[-- Attachment #1: Type: Text/Plain, Size: 2605 bytes --]

Hans, so can it be added to drivers/staging/media tree?

On Thursday 17 October 2013 21:31:04 Pali Rohár wrote:
> Hello,
> 
> so what do you suggest? Add it to staging for now (or not)?
> 
> On Tuesday 15 October 2013 17:08:39 Hans Verkuil wrote:
> > Hi Pali,
> > 
> > Thanks for the patch, but I am afraid it will need some work
> > to make this acceptable for inclusion into the kernel.
> > 
> > The main thing you need to do is to implement all the
> > controls using the control framework (see
> > Documentation/video4linux/v4l2-controls.txt). Most drivers
> > are by now converted to the control framework, so you will
> > find many examples of how to do this in drivers/media/radio.
> > 
> > The sysfs stuff should be replaced by controls as well. A
> > lot of the RDS support is now available as controls
> > (although there may well be some missing features, but that
> > is easy enough to add). Since the RDS data is actually
> > read() from the device I am not sure whether the RDS
> > properties/controls should be there at all.
> > 
> > Finally this driver should probably be split up into two
> > parts: one v4l2_subdev-based core driver and one platform
> > driver. See e.g. radio-si4713/si4713-i2c.c as a good
> > example. But I would wait with that until the rest of the
> > driver is cleaned up. Then I have a better idea of whether
> > this is necessary or not.
> > 
> > It's also very useful to run v4l2-compliance (available in
> > the v4l-utils.git repo on git.linuxtv.org). That does lots
> > of sanity checks.
> > 
> > Another option is to add the driver as-is to
> > drivers/staging/media, and clean it up bit by bit.
> > 
> > Regards,
> > 
> > 	Hans
> > 
> > On 10/15/2013 04:26 PM, Pali Rohár wrote:
> > > This adds support for the BCM2048 radio module found in
> > > Nokia N900
> > > 
> > > Signed-off-by: Eero Nurkkala <ext-eero.nurkkala@nokia.com>
> > > Signed-off-by: Nils Faerber
> > > <nils.faerber@kernelconcepts.de> Signed-off-by: Joni
> > > Lapilainen <joni.lapilainen@gmail.com> Signed-off-by:
> > > Pali Rohár <pali.rohar@gmail.com>
> > > ---
> > > 
> > >  drivers/media/radio/Kconfig         |   10 +
> > >  drivers/media/radio/Makefile        |    1 +
> > >  drivers/media/radio/radio-bcm2048.c | 2744
> > >  +++++++++++++++++++++++++++++++++++
> > >  include/media/radio-bcm2048.h       |   30 +
> > >  4 files changed, 2785 insertions(+)
> > >  create mode 100644 drivers/media/radio/radio-bcm2048.c
> > >  create mode 100644 include/media/radio-bcm2048.h

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-10-26 20:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 14:26 [PATCH] media: Add BCM2048 radio driver Pali Rohár
2013-10-15 15:08 ` Hans Verkuil
2013-10-17 19:31   ` Pali Rohár
2013-10-26 20:04     ` Pali Rohár [this message]
2013-10-26 20:22       ` Hans Verkuil
2013-10-26 20:45         ` Pali Rohár
2013-11-04 11:39           ` Hans Verkuil
2013-12-02 20:51             ` Pali Rohár
2013-12-05  7:52               ` Hans Verkuil
2013-12-05 13:20                 ` Pali Rohár
2013-12-05 13:57                   ` Sebastian Reichel
2013-12-05 14:03                     ` Nils Faerber
2013-12-05 20:03                       ` ext-eero.1.nurkkala
2013-12-05 20:03                         ` ext-eero.1.nurkkala

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=201310262204.33674@pali \
    --to=pali.rohar@gmail.com \
    --cc=ext-eero.nurkkala@nokia.com \
    --cc=hverkuil@xs4all.nl \
    --cc=joni.lapilainen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=nils.faerber@kernelconcepts.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.