linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: michael.hennerich@analog.com
Cc: Jonathan Cameron <jic23@kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"device-drivers-devel@blackfin.uclinux.org"
	<device-drivers-devel@blackfin.uclinux.org>,
	Drivers <Drivers@analog.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [RFC] iio: amplifiers: New driver for AD8366 Dual-Digital Variable Gain Amplifier
Date: Tue, 08 May 2012 13:53:47 +0100	[thread overview]
Message-ID: <4FA9175B.6010206@cam.ac.uk> (raw)
In-Reply-To: <4FA7E78E.6050406@analog.com>

On 5/7/2012 4:17 PM, Michael Hennerich wrote:
> On 05/07/2012 05:00 PM, Michael Hennerich wrote:
>> On 03/22/2012 10:10 AM, Jonathan Cameron wrote:
>>> On 3/22/2012 8:52 AM, Michael Hennerich wrote:
>>>> On 03/21/2012 08:34 PM, Jonathan Cameron wrote:
>>>>> On 02/22/2012 12:36 PM, michael.hennerich@analog.com wrote:
>>>>>> From: Michael Hennerich<michael.hennerich@analog.com>
>>>>> Sorry for the slow response on this one. Been off sick...
>>>>>
>>>>> Anyhow, I'm still not sure what the right interface for this type
>>>>> of device is.
>>>>>
>>>>> The obvious options are:
>>>>>
>>>>> 1) Make gain an IIO type (doesn't make much sense as gain is only 
>>>>> going
>>>>> to be of one particular existing type).
>>>>> 2) Have it as an IIO_ALTVOLTAGE channel as you have here and use 
>>>>> extend
>>>>> name.  Any real reason for picking altvoltage rather than voltage?
>>>> I'm open for advice. Since I made the amplifier being an OUT type 
>>>> device
>>>> I chose IIO_ALTVOLTAGE analogous to our DDS/PLL drivers.
>>>> Some VGAs/PGAs work from DC, but typically VGAs are HF devices.
>>> Hmm.. Don't suppose it really matters but we ought to aim for 
>>> consistency
>>> (by review) at least.  This particular part is DC through to 600MHz.
>>>>> Clearly gain has the same meaning in either case (assuming it's 
>>>>> linear).
>>>>> 3) Make a change to core to allow a channel to have elements in
>>>>> info_mask but not actually to have a raw access.  Not entirely sure
>>>>> how we will do that cleanly.  Also it's not clear whether the gain
>>>>> would be an IN or an OUT channel type!
>>>> Well - having the ability for channels without raw access element
>>>> would be of interest.
>>> True enough.  Cleanest way to do this that I can think of is to make 
>>> a tree
>>> wide change to add the raw element to the info_mask.  We could allow 
>>> for
>>> a zero info_mask value actually being the equivalent of having only 
>>> a raw
>>> channel.  It's invasive but if we agreee it should be done now is
>>> probably the
>>> best time to do it (just post merge window etc).
>> Hi Jonathan,
>>
>> Thanks for getting this in place.
>>
>>>
>>> Whilst here, we clearly need way of destinguishing values in DB from 
>>> linear
>>> gains.  Could add a new return type for read_raw callbacks?
>>
>> Does something like this work for you?
>> Also wondering if we should introduce IIO_CHAN_INFO_GAIN
>> for amplifier type devices?
>
> Thinking about it a bit more - why not have iio_chan_type:IIO_GAIN?
Lack of consistency with other devices.  If we have a pga on the front
of an adc then the type is voltage and control is done via relevant info
element.
How is this any different?




  reply	other threads:[~2012-05-08 12:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 12:36 [RFC] iio: amplifiers: New driver for AD8366 Dual-Digital Variable Gain Amplifier michael.hennerich
2012-03-21 19:34 ` Jonathan Cameron
2012-03-21 19:59   ` Mark Brown
2012-03-22  9:05     ` Hennerich, Michael
2012-03-22  8:52   ` Michael Hennerich
2012-03-22  9:10     ` Jonathan Cameron
2012-03-22  9:53       ` Michael Hennerich
2012-03-22  9:59         ` Jonathan Cameron
2012-05-07 15:00       ` Michael Hennerich
2012-05-07 15:17         ` Michael Hennerich
2012-05-08 12:53           ` Jonathan Cameron [this message]
2012-05-08 13:26             ` Hennerich, Michael
2012-05-08 13:32               ` Jonathan Cameron
2012-05-08 14:48                 ` Michael Hennerich
2012-05-08 14:53                   ` Jonathan Cameron
2012-05-08 15:57                     ` Michael Hennerich

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=4FA9175B.6010206@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=Drivers@analog.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=device-drivers-devel@blackfin.uclinux.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=michael.hennerich@analog.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 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).