linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Beniamin Bia <beniamin.bia@analog.com>
Cc: <lars@metafoo.de>, <Michael.Hennerich@analog.com>,
	<pmeerw@pmeerw.net>, <linux-iio@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <biabeniamin@outlook.com>,
	<knaack.h@gmx.de>
Subject: Re: [PATCH v2] iio: adc: ad7887: Cleanup channel assignment
Date: Sun, 1 Dec 2019 11:43:57 +0000	[thread overview]
Message-ID: <20191201114357.3c027077@archlinux> (raw)
In-Reply-To: <20191125132137.4753-1-beniamin.bia@analog.com>

On Mon, 25 Nov 2019 15:21:37 +0200
Beniamin Bia <beniamin.bia@analog.com> wrote:

> The channels specification assignment in chip info was simplified.
> This patch makes supporting other devices by this driver easier.
> 
> Signed-off-by: Beniamin Bia <beniamin.bia@analog.com>
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to play with it.

Thanks,

Jonathan

> ---
> Changes in v2:
> -separate iio_chan_spec for dual mode
> 
>  drivers/iio/adc/ad7887.c | 82 +++++++++++++++++++++-------------------
>  1 file changed, 43 insertions(+), 39 deletions(-)
> 
> diff --git a/drivers/iio/adc/ad7887.c b/drivers/iio/adc/ad7887.c
> index 6223043e432b..c6a3428e950a 100644
> --- a/drivers/iio/adc/ad7887.c
> +++ b/drivers/iio/adc/ad7887.c
> @@ -43,11 +43,17 @@ enum ad7887_channels {
>  /**
>   * struct ad7887_chip_info - chip specifc information
>   * @int_vref_mv:	the internal reference voltage
> - * @channel:		channel specification
> + * @channels:		channels specification
> + * @num_channels:	number of channels
> + * @dual_channels:	channels specification in dual mode
> + * @num_dual_channels:	number of channels in dual mode
>   */
>  struct ad7887_chip_info {
>  	u16				int_vref_mv;
> -	struct iio_chan_spec		channel[3];
> +	const struct iio_chan_spec	*channels;
> +	unsigned int			num_channels;
> +	const struct iio_chan_spec	*dual_channels;
> +	unsigned int			num_dual_channels;
>  };
>  
>  struct ad7887_state {
> @@ -183,45 +189,43 @@ static int ad7887_read_raw(struct iio_dev *indio_dev,
>  	return -EINVAL;
>  }
>  
> +#define AD7887_CHANNEL(x) { \
> +	.type = IIO_VOLTAGE, \
> +	.indexed = 1, \
> +	.channel = (x), \
> +	.info_mask_separate = BIT(IIO_CHAN_INFO_RAW), \
> +	.info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE), \
> +	.address = (x), \
> +	.scan_index = (x), \
> +	.scan_type = { \
> +		.sign = 'u', \
> +		.realbits = 12, \
> +		.storagebits = 16, \
> +		.shift = 0, \
> +		.endianness = IIO_BE, \
> +	}, \
> +}
> +
> +static const struct iio_chan_spec ad7887_channels[] = {
> +	AD7887_CHANNEL(0),
> +	IIO_CHAN_SOFT_TIMESTAMP(1),
> +};
> +
> +static const struct iio_chan_spec ad7887_dual_channels[] = {
> +	AD7887_CHANNEL(0),
> +	AD7887_CHANNEL(1),
> +	IIO_CHAN_SOFT_TIMESTAMP(2),
> +};
>  
>  static const struct ad7887_chip_info ad7887_chip_info_tbl[] = {
>  	/*
>  	 * More devices added in future
>  	 */
>  	[ID_AD7887] = {
> -		.channel[0] = {
> -			.type = IIO_VOLTAGE,
> -			.indexed = 1,
> -			.channel = 1,
> -			.info_mask_separate = BIT(IIO_CHAN_INFO_RAW),
> -			.info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE),
> -			.address = 1,
> -			.scan_index = 1,
> -			.scan_type = {
> -				.sign = 'u',
> -				.realbits = 12,
> -				.storagebits = 16,
> -				.shift = 0,
> -				.endianness = IIO_BE,
> -			},
> -		},
> -		.channel[1] = {
> -			.type = IIO_VOLTAGE,
> -			.indexed = 1,
> -			.channel = 0,
> -			.info_mask_separate = BIT(IIO_CHAN_INFO_RAW),
> -			.info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE),
> -			.address = 0,
> -			.scan_index = 0,
> -			.scan_type = {
> -				.sign = 'u',
> -				.realbits = 12,
> -				.storagebits = 16,
> -				.shift = 0,
> -				.endianness = IIO_BE,
> -			},
> -		},
> -		.channel[2] = IIO_CHAN_SOFT_TIMESTAMP(2),
> +		.channels = ad7887_channels,
> +		.num_channels = ARRAY_SIZE(ad7887_channels),
> +		.dual_channels = ad7887_dual_channels,
> +		.num_dual_channels = ARRAY_SIZE(ad7887_dual_channels),
>  		.int_vref_mv = 2500,
>  	},
>  };
> @@ -306,11 +310,11 @@ static int ad7887_probe(struct spi_device *spi)
>  		spi_message_init(&st->msg[AD7887_CH1]);
>  		spi_message_add_tail(&st->xfer[3], &st->msg[AD7887_CH1]);
>  
> -		indio_dev->channels = st->chip_info->channel;
> -		indio_dev->num_channels = 3;
> +		indio_dev->channels = st->chip_info->dual_channels;
> +		indio_dev->num_channels = st->chip_info->num_dual_channels;
>  	} else {
> -		indio_dev->channels = &st->chip_info->channel[1];
> -		indio_dev->num_channels = 2;
> +		indio_dev->channels = st->chip_info->channels;
> +		indio_dev->num_channels = st->chip_info->num_channels;
>  	}
>  
>  	ret = iio_triggered_buffer_setup(indio_dev, &iio_pollfunc_store_time,


      reply	other threads:[~2019-12-01 11:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 13:21 [PATCH v2] iio: adc: ad7887: Cleanup channel assignment Beniamin Bia
2019-12-01 11:43 ` Jonathan Cameron [this message]

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=20191201114357.3c027077@archlinux \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=beniamin.bia@analog.com \
    --cc=biabeniamin@outlook.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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).