All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Valentin <eduardo.valentin@nokia.com>
To: ext Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	"Valentin Eduardo (Nokia-D/Helsinki)"
	<eduardo.valentin@nokia.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"Nurkkala Eero.An (EXT-Offcode/Oulu)"
	<ext-Eero.Nurkkala@nokia.com>
Subject: Re: [PATCH v2 1/7] v4l2: video device: Add V4L2_CTRL_CLASS_FMTX controls
Date: Wed, 13 May 2009 08:55:17 +0300	[thread overview]
Message-ID: <20090513055517.GJ4639@esdhcp037198.research.nokia.com> (raw)
In-Reply-To: <20090512072954.07e2b303@pedra.chehab.org>

On Tue, May 12, 2009 at 12:29:54PM +0200, ext Mauro Carvalho Chehab wrote:
> Em Tue, 12 May 2009 08:26:40 +0200
> Hans Verkuil <hverkuil@xs4all.nl> escreveu:
> 
> > The only reason why such a table might end up in the kernel is if there are 
> > legal requirements forcing strict control on what is allowed for an FM 
> > transmitter in each country, and in that case a similar mechanism as is 
> > used for wifi should be used. I know we discussed this earlier, but I've 
> > forgotten the exact name of that API.
> 
> If the usage of FM transmission is for very short range transmissions (for
> example, to listen to a phone call inside your car stereo, or to listen to your
> baby's room noises or to see him while you're in the kitchen), I doubt that
> there are any legal requirements. Such usage is called by the regulatory
> agencies as "secondary usage"[1]. The secondary usage for FM and for their
> adjacent frequencies (the TV range) should allow such domestic usage [2]. In
> general, the restriction for secondary usage is just the power level, to avoid
> interferences with the primary usage. In general, the secondary usage for TV
> and FM ranges are the same (and both ranges are adjacent).
> 
> On the other hand, for FM primary usage, e. g. a FM broadcaster, the
> restriction is that you should transmit _ONLY_ at the authorized frequency, at
> the specified maximum power (that may have a different max power during the day
> or during the night), using strict shapes for frequency shift, and for
> modulation levels. It also restricts the location of the FM station, and the
> characteristics of the antenna beams. Such constraints require application,
> infrastructure and hardware control that couldn't be done at kernel level.
> 
> So, I don't see how legal issues might affect this driver.
> 
> [1] Maybe the specific term may change from country to country, but the idea
> remains the same, since this concept exists on ITU-R regulations.
> 
> [2] I'm not aware of any country that forbids the usage of FM/TV ranges for
> domestic usage. Yet, if such country does exist, then the usage of this module
> should be forbidden at such country, no matter what frequency you're
> generating. So, again, it seems pointless to add such restriction in kernel.

Right. I've to agree that there is no need to have those in kernel. Better
to leave this role to user land, if some legal requirement is needed then.
I'll resend the patches without the region settings. It will export only
the device limits. I believe that user land can, on top of that, handle
the channel spacing and frequency limits. Of course, leaving a way to set/get
the preemphasis will be kept. But not bound to a region setting anymore.

> 
> Cheers,
> Mauro

Cheers,

-- 
Eduardo Valentin

  reply	other threads:[~2009-05-13  6:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11  9:31 [PATCH v2 0/7] [RFC] FM Transmitter (si4713) and another changes Eduardo Valentin
2009-05-11  9:31 ` [PATCH v2 1/7] v4l2: video device: Add V4L2_CTRL_CLASS_FMTX controls Eduardo Valentin
2009-05-11  9:31   ` [PATCH v2 2/7] v4l2: video device: Add FMTX controls default configurations Eduardo Valentin
2009-05-11  9:31     ` [PATCH v2 3/7] v4l2_subdev i2c: Add i2c board info to v4l2_i2c_new_subdev Eduardo Valentin
2009-05-11  9:31       ` [PATCH v2 4/7] FMTx: si4713: Add files to handle si4713 i2c device Eduardo Valentin
2009-05-11  9:31         ` [PATCH v2 5/7] FMTx: si4713: Add files to add radio interface for si4713 Eduardo Valentin
2009-05-11  9:31           ` [PATCH v2 6/7] FMTx: si4713: Add Kconfig and Makefile entries Eduardo Valentin
2009-05-11  9:31             ` [PATCH v2 7/7] FMTx: si4713: Add document file Eduardo Valentin
2009-05-12  5:15         ` [PATCH v2 4/7] FMTx: si4713: Add files to handle si4713 i2c device Eero Nurkkala
2009-05-12  5:22           ` Eero Nurkkala
2009-05-12  6:08             ` Eero Nurkkala
2009-05-12  2:12   ` [PATCH v2 1/7] v4l2: video device: Add V4L2_CTRL_CLASS_FMTX controls Mauro Carvalho Chehab
2009-05-12  6:12     ` Eduardo Valentin
2009-05-12  2:17   ` Mauro Carvalho Chehab
2009-05-12  6:10     ` Eduardo Valentin
2009-05-12  6:26       ` Hans Verkuil
2009-05-12 10:29         ` Mauro Carvalho Chehab
2009-05-13  5:55           ` Eduardo Valentin [this message]
2009-05-12  9:53       ` Mauro Carvalho Chehab
2009-05-12  4:49   ` Eero Nurkkala
2009-05-12  6:05     ` Eduardo Valentin
2009-05-12  7:03 ` [PATCH v2 0/7] [RFC] FM Transmitter (si4713) and another changes Hans Verkuil
2009-05-12  7:33   ` Eduardo Valentin
2009-05-12  7:35     ` Eduardo Valentin

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=20090513055517.GJ4639@esdhcp037198.research.nokia.com \
    --to=eduardo.valentin@nokia.com \
    --cc=ext-Eero.Nurkkala@nokia.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    /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.