From: Slawomir Stepien <sst@poczta.fm>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, matthew.weber@rockwellcollins.com,
maury.anderson@rockwellcollins.com, devicetree@vger.kernel.org,
Mark Rutland <Mark.Rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v3] iio: max5481: Add support for Maxim digital potentiometers
Date: Mon, 16 Jan 2017 18:10:26 +0100 [thread overview]
Message-ID: <20170116171026.GA1676@x220.localdomain> (raw)
In-Reply-To: <e48d9285-a077-36b3-b904-d9cf95c50a82@kernel.org>
On Jan 15, 2017 14:27, Jonathan Cameron wrote:
> A few more bits an pieces.
>
> Thanks,
Thanks for the review!
> Jonathan
> > ---
> > +static int max5481_write_cmd(struct max5481_data *data, u8 cmd, u16 val)
> > +{
> > + struct spi_device *spi = data->spi;
> > +
> > + data->msg[0] = cmd;
> > +
> > + switch (cmd) {
> > + case MAX5481_WRITE_WIPER:
> > + data->msg[1] = val >> 2;
> > + data->msg[2] = (val & 0x3) << 6;
> > + return spi_write(spi, data->msg, ARRAY_SIZE(data->msg));
> array_size will give you the number of elements in the array. Here that
> is fine, but inconsistent with the use of sizeof(data->msg[0]) below.
Yes, you are right.
Do you think that plain 3 and 1 below will be OK in this case? This is the way
the protocol is defined.
Or maybe ARRAY_SIZE above is OK, but below I will just write 1?
> > +
> > + case MAX5481_COPY_AB_TO_NV:
> > + case MAX5481_COPY_NV_TO_AB:
> > + return spi_write(spi, data->msg, sizeof(data->msg[0]));
> > +
> > + default:
> > + return -EIO;
> > + }
> > +}
> > +
> > (...)
> > +static int max5481_probe(struct spi_device *spi)
> > +{
> > + struct iio_dev *indio_dev;
> > + struct max5481_data *data;
> > + const struct spi_device_id *id = spi_get_device_id(spi);
> > + int ret;
> > +
> > + indio_dev = devm_iio_device_alloc(&spi->dev, sizeof(*data));
> > + if (!indio_dev)
> > + return -ENOMEM;
> > +
> > + dev_set_drvdata(&spi->dev, indio_dev);
> > + data = iio_priv(indio_dev);
> > +
> > + data->spi = spi;
> To use the of data you have below this will need different handling,
> specifically the use of of_match_device to get access to the data.
> See something like adc/max1363 for how to do this.
OK thanks!
> > + data->cfg = &max5481_cfg[id->driver_data];
> > +
> > + indio_dev->name = id->name;
> > + indio_dev->dev.parent = &spi->dev;
> > + indio_dev->modes = INDIO_DIRECT_MODE;
> > +
> > + /* variant specific configuration */
> > + indio_dev->info = &max5481_info;
> > + indio_dev->channels = max5481_channels;
> > + indio_dev->num_channels = ARRAY_SIZE(max5481_channels);
> > +
> > + /* restore wiper from NV */
> > + ret = max5481_write_cmd(data, MAX5481_COPY_NV_TO_AB, 0);
> > + if (ret < 0)
> > + return ret;
> > +
> > + return iio_device_register(indio_dev);
> > +}
> > (...)
> > +MODULE_AUTHOR("Maury Anderson <maury.anderson@rockwellcollins.com>");
> > +MODULE_DESCRIPTION("max5481 SPI driver");
> > +MODULE_LICENSE("GPL v2");
> >
> 1
Do you mean:
MODULE_LICENSE("GPL");
?
--
Slawomir Stepien
next prev parent reply other threads:[~2017-01-16 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 21:21 [PATCH v3] iio: max5481: Add support for Maxim digital potentiometers Slawomir Stepien
2017-01-15 14:27 ` Jonathan Cameron
2017-01-16 17:10 ` Slawomir Stepien [this message]
2017-01-19 13:09 ` Rob Herring
2017-01-19 19:35 ` Slawomir Stepien
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=20170116171026.GA1676@x220.localdomain \
--to=sst@poczta.fm \
--cc=Mark.Rutland@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=matthew.weber@rockwellcollins.com \
--cc=maury.anderson@rockwellcollins.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).