All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hartmut Knaack <knaack.h@gmx.de>
To: Thomas.Betker@rohde-schwarz.com
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	linux-iio@vger.kernel.org,
	"Michal Simek" <michal.simek@xilinx.com>,
	"Sören Brinkmann" <soren.brinkmann@xilinx.com>
Subject: Re: [PATCH 3/5] iio: adc: xilinx: Fix VREFP scale
Date: Wed, 01 Jul 2015 20:30:08 +0200	[thread overview]
Message-ID: <559431B0.6050304@gmx.de> (raw)
In-Reply-To: <OF4F435CFE.EBD383ED-ONC1257E74.00350661-C1257E74.003C1F9E@rohde-schwarz.com>

Thomas.Betker@rohde-schwarz.com schrieb am 30.06.2015 um 12:56:
> Hello Hartmut:
> 
>>> The scaling factor for VREFP is 3.0/4096, not 1.0/4096; fix this to 
> get
>>> correct readings.
>>
>> I just had a look at the datasheet [1], table 3-1 on page 37, and 
>> get the feeling
>> that this scaling factor also applies to the VREFN channel. What is 
>> your opinion?
>>
>> [1] http://www.xilinx.com/support/documentation/user_guides/
>> ug480_7Series_XADC.pdf
> 
> The table provides the following references:
> - VREFP: Figure 2-10, transfer function 3*unsigned(code)/4096
> - VREFN: Figure 2-3, transfer function 1*unsigned(code)/4096
> 
> The table also says about VREFN: "The supply sensor is also used to 
> measure VREFN, thus 1 LSB = 3V/4096." I agree that this is not consistent 
> (by Figure 2-3, 1 LSB = 1V/4096), but I didn't have the means to check 
> which version is true as VREFN is close to 0V either way.
> 
> The situation is simpler for VREFP as UG480 is unambiguous here, and by 
> measuring the actual voltage we can tell 1.25V and 0.41V easily apart, 
> even when taking some measurement errors into account. In other words, we 
> have to use the factor 3 to get correct results for VREFP (thus the 
> patch), while either factor returns plausible results for VREFN.
> 
> I would suggest opening a webcase with Xilinx for clarification, and 
> adding another patch for VREFN if the factor 3 is confirmed. Can you do 
> this? If not, I can take care of it, but it may take a while as I am 
> pretty busy at the moment.
> 

Go ahead, whenever you find the time. I don't have a Xilinx device, just
reviewing the IIO patches and got a bit curious when reading through the
data sheet.

> Best regards,
> Thomas
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2015-07-01 18:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 19:11 [Patch 0/5] iio: adc: xilinx: Fix some minor issues Thomas Betker
2015-04-15 19:11 ` [PATCH 1/5] iio: adc: xilinx: Fix register addresses Thomas Betker
2015-04-19 12:48   ` Jonathan Cameron
2015-04-15 19:11 ` [PATCH 2/5] iio: adc: xilinx: Fix "vccaux" channel .address Thomas Betker
2015-04-19 12:51   ` Jonathan Cameron
2015-04-15 19:11 ` [PATCH 3/5] iio: adc: xilinx: Fix VREFP scale Thomas Betker
2015-04-19 12:51   ` Jonathan Cameron
2015-06-26 21:55   ` Hartmut Knaack
2015-06-30 10:56     ` Thomas.Betker
2015-07-01 18:30       ` Hartmut Knaack [this message]
2015-07-03  7:52         ` Thomas.Betker
2015-04-15 19:11 ` [PATCH 4/5] iio: adc: xilinx: Fix VREFN sign Thomas Betker
2015-04-19 12:52   ` Jonathan Cameron
2015-04-15 19:11 ` [PATCH 5/5] iio: adc: xilinx: Set .datasheet_name instead of .extend_name Thomas Betker
2015-04-15 20:54 ` [Patch 0/5] iio: adc: xilinx: Fix some minor issues Jonathan Cameron
2015-04-16  6:20   ` Lars-Peter Clausen
2015-04-16  8:03     ` Thomas.Betker
2015-04-16  7:53   ` Thomas.Betker
2015-04-18 19:26     ` Jonathan Cameron
2015-04-20  8:34       ` Thomas.Betker
2015-04-21 19:35         ` 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=559431B0.6050304@gmx.de \
    --to=knaack.h@gmx.de \
    --cc=Thomas.Betker@rohde-schwarz.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=soren.brinkmann@xilinx.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.