All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@linuxtv.org>
To: Steffen Barszus <steffenbpunkt@googlemail.com>
Cc: linux-media Mailing List <linux-media@vger.kernel.org>,
	James <bjlockie@lockie.ca>,
	Devin Heitmueller <dheitmueller@kernellabs.com>
Subject: Re: femon signal strength
Date: Mon, 07 Nov 2011 11:47:55 +0100	[thread overview]
Message-ID: <4EB7B75B.70004@linuxtv.org> (raw)
In-Reply-To: <20111106205907.47b9102b@grobi>

I didn't receive Devin's mail, so I'm replying to this one instead, see
below:

On 06.11.2011 20:59, Steffen Barszus wrote:
> On Sun, 6 Nov 2011 10:01:49 -0500
> Devin Heitmueller <dheitmueller@kernellabs.com> wrote:
> 
>> On Sunday, November 6, 2011, Steffen Barszus
>> <steffenbpunkt@googlemail.com> wrote:
>>>
>>> Any uniform
>>> scale is better, then whats there at the moment.

[...]

>> (and I've said on numerous occasions when discussing this
>> issue that any standard that is uniform is better than no standard at
>> all).  "Perfect is the enemy of good"

Quoting myself from three years ago, I propose to add an interface to
read SNR in units of db/100:

On 17.10.2008 11:55, Andreas Oberritter wrote:
> How about adding a new command instead (and a similar one for S2API)? 
> 
> /* Read SNR in units of dB/100 */
> #define FE_READ_SNR_DB _IOR('o', 74, __u16)
> 
> Then it's no problem to slowly migrate the drivers to this interface. The
> old interface can still stay for some time without changes. Applications
> can try this ioctl, and if it returns an error, then it is not implemented
> for the used device.

S2API currently implements none of the signal quality measurement
commands that v3 knows about. Nevertheless, it should be easy to add a
property:

/* SNR in units of dB/100 */
#define DTV_SNR		44

If a driver does not implement this property, the core should return an
error (i.e. set dtv_property.result to a non-zero value, e.g. -EOPNOTSUPP).

Regards,
Andreas

  reply	other threads:[~2011-11-07 10:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26  4:36 femon signal strength James
2011-10-26  8:15 ` Devin Heitmueller
2011-10-26 19:45   ` James
2011-10-26 19:49     ` Devin Heitmueller
2011-10-26 19:58       ` James
2011-11-05 10:10         ` Steffen Barszus
     [not found]           ` <CAGoCfiwC+7pkY6ZchySBYRkyY1XjFjKeJYQEPTc2ZiBN-pdoyw@mail.gmail.com>
2011-11-06 13:15             ` Steffen Barszus
     [not found]               ` <CAGoCfixoOwZumohwJrLVKhfpUNGYwbD9uSq7nM0GhqriOx0FxA@mail.gmail.com>
2011-11-06 19:59                 ` Steffen Barszus
2011-11-07 10:47                   ` Andreas Oberritter [this message]
2011-11-07 15:13                     ` Luca Olivetti
2011-11-07 19:16                       ` Andreas Oberritter

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=4EB7B75B.70004@linuxtv.org \
    --to=obi@linuxtv.org \
    --cc=bjlockie@lockie.ca \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=steffenbpunkt@googlemail.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 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.