From: Marek Vasut <marex@denx.de>
To: Robert Hodaszi <robert.hodaszi@digi.com>
Cc: jic23@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
alexandre.belloni@free-electrons.com, jbe@pengutronix.de,
hector.palacios@digi.com, fabio.estevam@freescale.com,
lars@metafoo.de
Subject: Re: [PATCH 2/2] iio: mxs-lradc: add ADC channel 9 as a copy of channel 8
Date: Wed, 11 Jun 2014 00:51:34 +0200 [thread overview]
Message-ID: <201406110051.34455.marex@denx.de> (raw)
In-Reply-To: <1402407695-2984-3-git-send-email-robert.hodaszi@digi.com>
On Tuesday, June 10, 2014 at 03:41:35 PM, Robert Hodaszi wrote:
> Commit c8231a9af8147f8a401fc55931ec44abfb937660 ("iio: mxs-lradc: compute
> temperature from channel 8 and 9") merged channel 8 and channel 9 to create
> an IIO_TEMP channel. It changed the number of LRADC channels, which could
> cause incompatibility with previous device-tree declarations, and also
> makes it illogical (e.g. channel 15 is <&lradc 14>).
>
> Add channel 9 as a copy of channel 8. Reading channel 9 has the same output
> as reading channel 8.
>
> Signed-off-by: Robert Hodaszi <robert.hodaszi@digi.com>
> ---
[...]
> static const struct iio_chan_spec mxs_lradc_chan_spec[] = {
> - MXS_ADC_CHAN(0, IIO_VOLTAGE),
> - MXS_ADC_CHAN(1, IIO_VOLTAGE),
> - MXS_ADC_CHAN(2, IIO_VOLTAGE),
> - MXS_ADC_CHAN(3, IIO_VOLTAGE),
> - MXS_ADC_CHAN(4, IIO_VOLTAGE),
> - MXS_ADC_CHAN(5, IIO_VOLTAGE),
> - MXS_ADC_CHAN(6, IIO_VOLTAGE),
> - MXS_ADC_CHAN(7, IIO_VOLTAGE), /* VBATT */
> + MXS_ADC_VOLTAGE_CHAN(0),
> + MXS_ADC_VOLTAGE_CHAN(1),
> + MXS_ADC_VOLTAGE_CHAN(2),
> + MXS_ADC_VOLTAGE_CHAN(3),
> + MXS_ADC_VOLTAGE_CHAN(4),
> + MXS_ADC_VOLTAGE_CHAN(5),
> + MXS_ADC_VOLTAGE_CHAN(6),
> + MXS_ADC_VOLTAGE_CHAN(7), /* VBATT */
> /* Combined Temperature sensors */
> - {
> - .type = IIO_TEMP,
> - .indexed = 1,
> - .scan_index = 8,
> - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW) |
> - BIT(IIO_CHAN_INFO_OFFSET) |
> - BIT(IIO_CHAN_INFO_SCALE),
> - .channel = 8,
> - .scan_type = {.sign = 'u', .realbits = 18, .storagebits = 32,},
> - },
I wonder, shouldn't the IIO framework handle this kind of a "hole" in the
iio_chan_spec structure, where one entry has .channel = N and the subsequent one
has .channel = N + 2 somehow ?
> - MXS_ADC_CHAN(10, IIO_VOLTAGE), /* VDDIO */
> - MXS_ADC_CHAN(11, IIO_VOLTAGE), /* VTH */
> - MXS_ADC_CHAN(12, IIO_VOLTAGE), /* VDDA */
> - MXS_ADC_CHAN(13, IIO_VOLTAGE), /* VDDD */
> - MXS_ADC_CHAN(14, IIO_VOLTAGE), /* VBG */
> - MXS_ADC_CHAN(15, IIO_VOLTAGE), /* VDD5V */
[...]
next prev parent reply other threads:[~2014-06-10 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 13:41 [PATCH 0/2] iio: mxs-lradc: fixes Robert Hodaszi
2014-06-10 13:41 ` [PATCH 1/2] iio: mxs-lradc: fix divider Robert Hodaszi
2014-06-10 15:19 ` Alexandre Belloni
2014-06-10 22:47 ` Marek Vasut
2014-06-14 14:01 ` Jonathan Cameron
2014-06-10 13:41 ` [PATCH 2/2] iio: mxs-lradc: add ADC channel 9 as a copy of channel 8 Robert Hodaszi
2014-06-10 15:19 ` Alexandre Belloni
2014-06-10 22:51 ` Marek Vasut [this message]
2014-06-14 13:58 ` 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=201406110051.34455.marex@denx.de \
--to=marex@denx.de \
--cc=alexandre.belloni@free-electrons.com \
--cc=fabio.estevam@freescale.com \
--cc=gregkh@linuxfoundation.org \
--cc=hector.palacios@digi.com \
--cc=jbe@pengutronix.de \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.hodaszi@digi.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).