From: Jonathan Cameron <jic23@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v4 4/8] iio: adc: max1027: Prepare the introduction of different resolutions
Date: Sat, 12 Oct 2019 12:29:12 +0100 [thread overview]
Message-ID: <20191012122912.5882d2e7@archlinux> (raw)
In-Reply-To: <20191011144347.19146-5-miquel.raynal@bootlin.com>
On Fri, 11 Oct 2019 16:43:43 +0200
Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> Maxim's max1027/29/31 series returns the measured voltages with a
> resolution of 10 bits. There is a very similar series, max1227/29/31
> which works identically but uses a resolution of 12 bits. Prepare the
> support for these chips by turning the 'depth' into a macro parameter
> instead of hardcoding it everywhere. Also reorganize just a bit the
> macros at the top to avoid repeating tens of lines when adding support
> for a new chip.
>
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Applied.
Thanks,
Jonathan
> ---
> drivers/iio/adc/max1027.c | 74 +++++++++++++++++----------------------
> 1 file changed, 32 insertions(+), 42 deletions(-)
>
> diff --git a/drivers/iio/adc/max1027.c b/drivers/iio/adc/max1027.c
> index f9b473ee6711..8b449044bef5 100644
> --- a/drivers/iio/adc/max1027.c
> +++ b/drivers/iio/adc/max1027.c
> @@ -83,7 +83,7 @@ static const struct of_device_id max1027_adc_dt_ids[] = {
> MODULE_DEVICE_TABLE(of, max1027_adc_dt_ids);
> #endif
>
> -#define MAX1027_V_CHAN(index) \
> +#define MAX1027_V_CHAN(index, depth) \
> { \
> .type = IIO_VOLTAGE, \
> .indexed = 1, \
> @@ -93,7 +93,7 @@ MODULE_DEVICE_TABLE(of, max1027_adc_dt_ids);
> .scan_index = index + 1, \
> .scan_type = { \
> .sign = 'u', \
> - .realbits = 10, \
> + .realbits = depth, \
> .storagebits = 16, \
> .shift = 2, \
> .endianness = IIO_BE, \
> @@ -115,52 +115,42 @@ MODULE_DEVICE_TABLE(of, max1027_adc_dt_ids);
> }, \
> }
>
> +#define MAX1X27_CHANNELS(depth) \
> + MAX1027_T_CHAN, \
> + MAX1027_V_CHAN(0, depth), \
> + MAX1027_V_CHAN(1, depth), \
> + MAX1027_V_CHAN(2, depth), \
> + MAX1027_V_CHAN(3, depth), \
> + MAX1027_V_CHAN(4, depth), \
> + MAX1027_V_CHAN(5, depth), \
> + MAX1027_V_CHAN(6, depth), \
> + MAX1027_V_CHAN(7, depth)
> +
> +#define MAX1X29_CHANNELS(depth) \
> + MAX1X27_CHANNELS(depth), \
> + MAX1027_V_CHAN(8, depth), \
> + MAX1027_V_CHAN(9, depth), \
> + MAX1027_V_CHAN(10, depth), \
> + MAX1027_V_CHAN(11, depth)
> +
> +#define MAX1X31_CHANNELS(depth) \
> + MAX1X27_CHANNELS(depth), \
> + MAX1X29_CHANNELS(depth), \
> + MAX1027_V_CHAN(12, depth), \
> + MAX1027_V_CHAN(13, depth), \
> + MAX1027_V_CHAN(14, depth), \
> + MAX1027_V_CHAN(15, depth)
> +
> static const struct iio_chan_spec max1027_channels[] = {
> - MAX1027_T_CHAN,
> - MAX1027_V_CHAN(0),
> - MAX1027_V_CHAN(1),
> - MAX1027_V_CHAN(2),
> - MAX1027_V_CHAN(3),
> - MAX1027_V_CHAN(4),
> - MAX1027_V_CHAN(5),
> - MAX1027_V_CHAN(6),
> - MAX1027_V_CHAN(7)
> + MAX1X27_CHANNELS(10),
> };
>
> static const struct iio_chan_spec max1029_channels[] = {
> - MAX1027_T_CHAN,
> - MAX1027_V_CHAN(0),
> - MAX1027_V_CHAN(1),
> - MAX1027_V_CHAN(2),
> - MAX1027_V_CHAN(3),
> - MAX1027_V_CHAN(4),
> - MAX1027_V_CHAN(5),
> - MAX1027_V_CHAN(6),
> - MAX1027_V_CHAN(7),
> - MAX1027_V_CHAN(8),
> - MAX1027_V_CHAN(9),
> - MAX1027_V_CHAN(10),
> - MAX1027_V_CHAN(11)
> + MAX1X29_CHANNELS(10),
> };
>
> static const struct iio_chan_spec max1031_channels[] = {
> - MAX1027_T_CHAN,
> - MAX1027_V_CHAN(0),
> - MAX1027_V_CHAN(1),
> - MAX1027_V_CHAN(2),
> - MAX1027_V_CHAN(3),
> - MAX1027_V_CHAN(4),
> - MAX1027_V_CHAN(5),
> - MAX1027_V_CHAN(6),
> - MAX1027_V_CHAN(7),
> - MAX1027_V_CHAN(8),
> - MAX1027_V_CHAN(9),
> - MAX1027_V_CHAN(10),
> - MAX1027_V_CHAN(11),
> - MAX1027_V_CHAN(12),
> - MAX1027_V_CHAN(13),
> - MAX1027_V_CHAN(14),
> - MAX1027_V_CHAN(15)
> + MAX1X31_CHANNELS(10),
> };
>
> static const unsigned long max1027_available_scan_masks[] = {
> @@ -284,7 +274,7 @@ static int max1027_read_raw(struct iio_dev *indio_dev,
> break;
> case IIO_VOLTAGE:
> *val = 2500;
> - *val2 = 10;
> + *val2 = chan->scan_type.realbits;
> ret = IIO_VAL_FRACTIONAL_LOG2;
> break;
> default:
next prev parent reply other threads:[~2019-10-12 11:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 14:43 [PATCH v4 0/8] Introduce max12xx ADC support Miquel Raynal
2019-10-11 14:43 ` [PATCH v4 1/8] iio: adc: max1027: Add debugfs register read support Miquel Raynal
2019-10-12 11:25 ` Jonathan Cameron
2019-10-11 14:43 ` [PATCH v4 2/8] iio: adc: max1027: Make it optional to use interrupts Miquel Raynal
2019-10-12 11:34 ` Jonathan Cameron
2019-10-11 14:43 ` [PATCH v4 3/8] iio: adc: max1027: Reset the device at probe time Miquel Raynal
2019-10-12 11:28 ` Jonathan Cameron
2019-10-11 14:43 ` [PATCH v4 4/8] iio: adc: max1027: Prepare the introduction of different resolutions Miquel Raynal
2019-10-12 11:29 ` Jonathan Cameron [this message]
2019-10-11 14:43 ` [PATCH v4 5/8] iio: adc: max1027: Introduce 12-bit devices support Miquel Raynal
2019-10-12 11:30 ` Jonathan Cameron
2019-10-11 14:43 ` [PATCH v4 6/8] dt-bindings: iio: adc: max1027: Mark interrupts as optional Miquel Raynal
2019-10-12 11:31 ` Jonathan Cameron
2019-10-11 14:43 ` [PATCH v4 7/8] dt-bindings: Add 1027/1029/1031 SPI ADCs as trivial devices Miquel Raynal
2019-10-14 15:38 ` Rob Herring
2019-10-11 14:43 ` [PATCH v4 8/8] dt-bindings: Add max12xx SPI ADC series " Miquel Raynal
2019-10-12 11:32 ` Jonathan Cameron
2019-10-14 15:38 ` Rob Herring
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=20191012122912.5882d2e7@archlinux \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=miquel.raynal@bootlin.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.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).