From: Jonathan Cameron <jic23@kernel.org> To: Lars-Peter Clausen <lars@metafoo.de>, Gergely Imreh <imrehg@gmail.com> Cc: michal.simek@xilinx.com, linux-iio@vger.kernel.org, Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>, linux-kernel@vger.kernel.org, ola@adapteva.com Subject: Re: [PATCH 1/1] iio:adc: XADC: Set offset explicitly to zero on voltage channels Date: Sun, 14 Jun 2015 16:55:38 +0100 [thread overview] Message-ID: <557DA3FA.4050300@kernel.org> (raw) In-Reply-To: <557DA18F.5090805@metafoo.de> On 14/06/15 16:45, Lars-Peter Clausen wrote: > On 06/14/2015 05:15 AM, Gergely Imreh wrote: >> On 14 June 2015 at 02:30, Jonathan Cameron <jic23@kernel.org> wrote: >>> On 11/06/15 09:22, Gergely Imreh wrote: >>>> The Xilinx XADC driver has both a temperature channel and 8 voltage >>>> channels. The voltage channels have no offset, but actually were still >>>> set the same offset as the temperature channel. This did not cause >>>> problems in /sys/bus/iio/ but can cause problems with other drivers >>>> using iio data. For example iio-hwmon did return wrong voltage values >>>> because of the offset. >>>> >>>> Change tested with the Parallella board. >>>> >>>> Signed-off-by: Gergely Imreh <imrehg@gmail.com> >>> Well spotted on the bug, but I think we are better off fixing this at the >>> true source of the problem which is in drivers/iio/inkern.c >>> iio_convert_raw_to_processed_unlocked which does a call to >>> iio_channel_read(chan, &offset, NULL, IIO_CHAN_INFO_OFFSET) then uses >>> the error return to check if the offset parameter is available. It should >>> be checking that before making this call with a call to iio_channel_has_info. >>> >>> I don't suppose you could prepare a patch fixing that as you found the problem? >> >> I'll check it out, and send an updated patch! Thanks for the pointers >> to the core of the issue. > > The issue was already fixed a while ago, see this patch: > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=65de7654d39c70c2b942f801cea01590cf7e3458 > > Starting with that commit iio_channel_read() returns an error when > the attribute is not available, which causes > iio_convert_raw_to_processed_unlocked() to skip the offset if it is > not available. > oops. Good spot. I'd completely forgotten about that and failed to spot the check when looking at the code yesterday. Glad you were keeping an eagle eye on things ;) J > - Lars
WARNING: multiple messages have this Message-ID (diff)
From: jic23@kernel.org (Jonathan Cameron) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/1] iio:adc: XADC: Set offset explicitly to zero on voltage channels Date: Sun, 14 Jun 2015 16:55:38 +0100 [thread overview] Message-ID: <557DA3FA.4050300@kernel.org> (raw) In-Reply-To: <557DA18F.5090805@metafoo.de> On 14/06/15 16:45, Lars-Peter Clausen wrote: > On 06/14/2015 05:15 AM, Gergely Imreh wrote: >> On 14 June 2015 at 02:30, Jonathan Cameron <jic23@kernel.org> wrote: >>> On 11/06/15 09:22, Gergely Imreh wrote: >>>> The Xilinx XADC driver has both a temperature channel and 8 voltage >>>> channels. The voltage channels have no offset, but actually were still >>>> set the same offset as the temperature channel. This did not cause >>>> problems in /sys/bus/iio/ but can cause problems with other drivers >>>> using iio data. For example iio-hwmon did return wrong voltage values >>>> because of the offset. >>>> >>>> Change tested with the Parallella board. >>>> >>>> Signed-off-by: Gergely Imreh <imrehg@gmail.com> >>> Well spotted on the bug, but I think we are better off fixing this at the >>> true source of the problem which is in drivers/iio/inkern.c >>> iio_convert_raw_to_processed_unlocked which does a call to >>> iio_channel_read(chan, &offset, NULL, IIO_CHAN_INFO_OFFSET) then uses >>> the error return to check if the offset parameter is available. It should >>> be checking that before making this call with a call to iio_channel_has_info. >>> >>> I don't suppose you could prepare a patch fixing that as you found the problem? >> >> I'll check it out, and send an updated patch! Thanks for the pointers >> to the core of the issue. > > The issue was already fixed a while ago, see this patch: > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=65de7654d39c70c2b942f801cea01590cf7e3458 > > Starting with that commit iio_channel_read() returns an error when > the attribute is not available, which causes > iio_convert_raw_to_processed_unlocked() to skip the offset if it is > not available. > oops. Good spot. I'd completely forgotten about that and failed to spot the check when looking at the code yesterday. Glad you were keeping an eagle eye on things ;) J > - Lars
next prev parent reply other threads:[~2015-06-14 15:55 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-11 8:22 [PATCH 1/1] iio:adc: XADC: Set offset explicitly to zero on voltage channels Gergely Imreh 2015-06-11 8:22 ` Gergely Imreh 2015-06-13 18:30 ` Jonathan Cameron 2015-06-13 18:30 ` Jonathan Cameron 2015-06-14 3:15 ` Gergely Imreh 2015-06-14 3:15 ` Gergely Imreh 2015-06-14 15:45 ` Lars-Peter Clausen 2015-06-14 15:45 ` Lars-Peter Clausen 2015-06-14 15:55 ` Jonathan Cameron [this message] 2015-06-14 15:55 ` Jonathan Cameron 2015-06-15 2:07 ` Gergely Imreh 2015-06-15 2:07 ` Gergely Imreh
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=557DA3FA.4050300@kernel.org \ --to=jic23@kernel.org \ --cc=imrehg@gmail.com \ --cc=lars@metafoo.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-iio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=michal.simek@xilinx.com \ --cc=ola@adapteva.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: linkBe 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.