linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: "Hennerich, Michael" <Michael.Hennerich@analog.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"Device-drivers-devel@blackfin.uclinux.org"
	<Device-drivers-devel@blackfin.uclinux.org>,
	"manuel.stahl@iis.fraunhofer.de" <manuel.stahl@iis.fraunhofer.de>
Subject: Re: [RFC PATCH 0/2] IIO: Filtering - how to handle.
Date: Wed, 05 Oct 2011 09:38:48 +0100	[thread overview]
Message-ID: <4E8C1798.2070003@cam.ac.uk> (raw)
In-Reply-To: <544AC56F16B56944AEC3BD4E3D59177146E73435B5@LIMKCMBX1.ad.analog.com>

On 10/05/11 07:55, Hennerich, Michael wrote:
> Jonathan Cameron wrote on 2011-09-30:
>> Hi All,
>>
>> One big area we have pretty much glossed over so far is devices with
>> controllable hardware filters.  This RFC proposes one option for
>> how to handle this. For low pass filters at least, the 3db point
>> seems the obvious choice as it allows us to gloss over exactly
>> what type of filter it is whilst still capturing it's basic
>> property of what it lets through.
>>
>> What do people think?
> 
> Looks good. The 3dB cutoff or corner frequency is typically used to describe
> various types of filters: low, high or band (pass/stop).
> 
> Documentation?
Indeed. Naughty me ;)  Will add for new version.
> 
> 
>>
>> Jonathan
>>
>> Jonathan Cameron (2):
>>   staging:iio: filter description - low pass 3db frequency.
>>   staging:iio:imu:adis16400 add control of data filtering.
>>  drivers/staging/iio/iio.h                |    2 +
>>  drivers/staging/iio/imu/adis16400.h      |    2 +
>>  drivers/staging/iio/imu/adis16400_core.c |  177
>>  +++++++++++++++++++++++------ drivers/staging/iio/industrialio-core.c
>>  |    2 + 4 files changed, 146 insertions(+), 37 deletions(-)
> 
> Greetings,
> Michael
> 
> --
> Analog Devices GmbH      Wilhelm-Wagenfeld-Str. 6      80807 Muenchen
> Sitz der Gesellschaft: Muenchen; Registergericht: Muenchen HRB 40368;
> Geschaeftsfuehrer:Dr.Carsten Suckrow, Thomas Wessel, William A. Martin, Margaret Seif
> 
> 
> 
> 


  reply	other threads:[~2011-10-05  8:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30 10:17 [RFC PATCH 0/2] IIO: Filtering - how to handle Jonathan Cameron
2011-09-30 10:17 ` [PATCH 1/2] staging:iio: filter description - low pass 3db frequency Jonathan Cameron
2011-09-30 10:17 ` [PATCH 2/2] staging:iio:imu:adis16400 add control of data filtering Jonathan Cameron
2011-10-04 12:39 ` [RFC PATCH 0/2] IIO: Filtering - how to handle JohnLM
2011-10-04 14:23   ` Jonathan Cameron
2011-10-06 14:01     ` JohnLM
2011-10-06 14:25       ` Jonathan Cameron
2011-10-05  6:55 ` Hennerich, Michael
2011-10-05  8:38   ` Jonathan Cameron [this message]
2011-10-06 15:40     ` [PATCH] staging:iio:documentation: document filter_low_pass_3db_frequency Jonathan Cameron

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=4E8C1798.2070003@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=Device-drivers-devel@blackfin.uclinux.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=manuel.stahl@iis.fraunhofer.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 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).