From: Jonathan Cameron <jic23@kernel.org>
To: William Breathitt Gray <william.gray@linaro.org>
Cc: lars@metafoo.de, linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: dac: cio-dac: Implement and utilize register structures
Date: Tue, 14 Jun 2022 12:26:18 +0100 [thread overview]
Message-ID: <20220614122618.68e2e9d1@jic23-huawei> (raw)
In-Reply-To: <44aec703753f930cceff448babd1c8e2959eebb0.1654118389.git.william.gray@linaro.org>
On Mon, 6 Jun 2022 10:15:18 -0400
William Breathitt Gray <william.gray@linaro.org> wrote:
> Reduce magic numbers and improve code readability by implementing and
> utilizing named register data structures.
>
> Signed-off-by: William Breathitt Gray <william.gray@linaro.org>
I'm unconvinced this one really helps readability seeing
as you are only indexing a straight forward array.
Simply using u16 __iomem *
would provide the main cleanup which is avoiding the indexing
via * 2.
Thanks,
Jonathan
> ---
> drivers/iio/dac/cio-dac.c | 24 ++++++++++++++++--------
> 1 file changed, 16 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/iio/dac/cio-dac.c b/drivers/iio/dac/cio-dac.c
> index 8080984dcb03..7860450ceaf3 100644
> --- a/drivers/iio/dac/cio-dac.c
> +++ b/drivers/iio/dac/cio-dac.c
> @@ -16,6 +16,7 @@
> #include <linux/isa.h>
> #include <linux/module.h>
> #include <linux/moduleparam.h>
> +#include <linux/types.h>
>
> #define CIO_DAC_NUM_CHAN 16
>
> @@ -34,14 +35,22 @@ static unsigned int num_cio_dac;
> module_param_hw_array(base, uint, ioport, &num_cio_dac, 0);
> MODULE_PARM_DESC(base, "Measurement Computing CIO-DAC base addresses");
>
> +/**
> + * struct cio_dac_reg - device register structure
> + * @da: D/A data
> + */
> +struct cio_dac_reg {
> + u16 da[CIO_DAC_NUM_CHAN];
> +};
> +
> /**
> * struct cio_dac_iio - IIO device private data structure
> * @chan_out_states: channels' output states
> - * @base: base port address of the IIO device
> + * @reg: I/O address offset for the device registers
> */
> struct cio_dac_iio {
> int chan_out_states[CIO_DAC_NUM_CHAN];
> - void __iomem *base;
> + struct cio_dac_reg __iomem *reg;
> };
>
> static int cio_dac_read_raw(struct iio_dev *indio_dev,
> @@ -61,7 +70,6 @@ static int cio_dac_write_raw(struct iio_dev *indio_dev,
> struct iio_chan_spec const *chan, int val, int val2, long mask)
> {
> struct cio_dac_iio *const priv = iio_priv(indio_dev);
> - const unsigned int chan_addr_offset = 2 * chan->channel;
>
> if (mask != IIO_CHAN_INFO_RAW)
> return -EINVAL;
> @@ -71,7 +79,7 @@ static int cio_dac_write_raw(struct iio_dev *indio_dev,
> return -EINVAL;
>
> priv->chan_out_states[chan->channel] = val;
> - iowrite16(val, priv->base + chan_addr_offset);
> + iowrite16(val, priv->reg->da + chan->channel);
>
> return 0;
> }
> @@ -106,8 +114,8 @@ static int cio_dac_probe(struct device *dev, unsigned int id)
> }
>
> priv = iio_priv(indio_dev);
> - priv->base = devm_ioport_map(dev, base[id], CIO_DAC_EXTENT);
> - if (!priv->base)
> + priv->reg = devm_ioport_map(dev, base[id], CIO_DAC_EXTENT);
> + if (!priv->reg)
> return -ENOMEM;
>
> indio_dev->info = &cio_dac_info;
> @@ -117,8 +125,8 @@ static int cio_dac_probe(struct device *dev, unsigned int id)
> indio_dev->name = dev_name(dev);
>
> /* initialize DAC outputs to 0V */
> - for (i = 0; i < 32; i += 2)
> - iowrite16(0, priv->base + i);
> + for (i = 0; i < CIO_DAC_NUM_CHAN; i++)
> + iowrite16(0, priv->reg->da + i);
>
> return devm_iio_device_register(dev, indio_dev);
> }
next prev parent reply other threads:[~2022-06-14 11:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 14:15 [PATCH 0/2] iio: Implement and utilize register structures for William Breathitt Gray
2022-06-06 14:15 ` [PATCH 1/2] iio: adc: stx104: Implement and utilize register structures William Breathitt Gray
2022-06-14 11:22 ` Jonathan Cameron
2022-06-14 16:12 ` William Breathitt Gray
2022-06-15 9:44 ` Andy Shevchenko
2022-06-15 11:55 ` William Breathitt Gray
2022-06-15 12:00 ` Andy Shevchenko
2022-06-15 12:19 ` William Breathitt Gray
2022-06-15 12:43 ` Andy Shevchenko
2022-06-16 13:27 ` Mark Brown
2022-06-06 14:15 ` [PATCH 2/2] iio: dac: cio-dac: " William Breathitt Gray
2022-06-14 11:26 ` Jonathan Cameron [this message]
2022-06-14 16:15 ` William Breathitt Gray
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=20220614122618.68e2e9d1@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=william.gray@linaro.org \
/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