Linux IIO development
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Hector Palacios <hector.palacios@digi.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Marek Vasut <marex@denx.de>,
	"fabio.estevam@freescale.com" <fabio.estevam@freescale.com>
Subject: Re: Accessing specific hardware features of mxs-lradc
Date: Tue, 02 Jul 2013 17:45:04 +0200	[thread overview]
Message-ID: <51D2F580.5070205@free-electrons.com> (raw)
In-Reply-To: <51D2EFDD.9000403@metafoo.de>

On 02/07/2013 17:21, Lars-Peter Clausen wrote:
>>>
>>> I was looking at that yesterday as I had to had a scale for the
>>> temperature sensors. You'll have to be careful because the maximum
>>> measured voltage when DIVIDE_BY_TWO is not set is 1.85V and when it is
>>> set, it becomes VDDIO - 50mv.
> 
> I had a quick peak at the datasheet and I think that's a typo. VDDIO is 3.3V.
> This sentence also doesn't make much sense if divide by two would actually
> lower the range. "For input channels (other than BATT, 5V, or VDDIO) with
> signals larger than 1.85 V, the divide-by-two option should be set."
> 

Yeah, what I think they meant is if !DIVIDE_BY_TWO : Vmax = 1.85V else
Vmax = 3.25V. So it may not be as easy as multiplying hte scale by two.
I couldn't test it, so I didn't implement it.

>>>
>>> Also, scaling for quite a lot of channels is fixed. You'll also get
>>> channels with a fixed divider that can take DIVIDE_BY_TWO. That is quite
>>> a mess ;)
>>
>> Thank you, I checked and it's easy to add custom sysfs attributes using
>> IIO_DEVICE_ATTR(). I was thinking whether adding a divide_by_two attribute per
>> channel:
>>
>>     divide_by_two0
>>     divide_by_two1
>>     ...
>>     divide_by_two7
>>
>> or a unique divide_by_two descriptor that admits a mask value for all channels.
>> I think the first approach (one per channel) is cleaner. Opinions?
> 
> Just use the scale attribute for this. That's the standard way to handle this,
> don't invent custom interfaces if there is already a generic one.
> 

Hector, you can have a look at what I did there:

http://marc.info/?l=linux-iio&m=137269905605960&w=2

Add IIO_CHAN_INFO_SCALE to .info_mask_separate in the MXS_ADC_CHAN
macro. Then, implement the scaling in the switch case in
mxs_lradc_read_raw and you'll probably also want to implement a write_raw.


-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2013-07-02 15:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 10:49 Accessing specific hardware features of mxs-lradc Hector Palacios
2013-07-02 12:06 ` Marek Vasut
2013-07-02 12:58 ` Lars-Peter Clausen
2013-07-02 13:28   ` Alexandre Belloni
2013-07-02 14:55     ` Hector Palacios
2013-07-02 15:21       ` Lars-Peter Clausen
2013-07-02 15:41         ` Lars-Peter Clausen
2013-07-02 15:45         ` Alexandre Belloni [this message]
2013-07-02 15:55           ` Lars-Peter Clausen

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=51D2F580.5070205@free-electrons.com \
    --to=alexandre.belloni@free-electrons.com \
    --cc=fabio.estevam@freescale.com \
    --cc=hector.palacios@digi.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=marex@denx.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