From: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
To: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH 1/2] staging: iio: adc: ad7192: add device-tree support to driver
Date: Sun, 14 Jan 2018 10:53:54 +0000 [thread overview]
Message-ID: <20180114105354.7d4e71e6@archlinux> (raw)
In-Reply-To: <E2AE62E8D995114A80E27C874A28DB3C97C501@NWD2MBX7.ad.analog.com>
On Mon, 8 Jan 2018 07:51:08 +0000
"Ardelean, Alexandru" <alexandru.Ardelean@analog.com> wrote:
> ________________________________________
> From: Jonathan Cameron [jic23@jic23.retrosnub.co.uk]
> Sent: Saturday, January 06, 2018 2:58 PM
> To: Ardelean, Alexandru
> Cc: linux-iio@vger.kernel.org
> Subject: Re: [PATCH 1/2] staging: iio: adc: ad7192: add device-tree support to driver
>
> On Fri, 5 Jan 2018 17:21:32 +0200
> <alexandru.ardelean@analog.com> wrote:
>
> > From: Alexandru Ardelean <alexandru.ardelean@analog.com>
> >
> Say what the patch does before going into details of why
> you have done it the way you have.
>
> Ack
One more thing, if you can find an email client (or configure current one)
to keep to indenting quotes with >
Makes it easier to tell what you wrote!
Jonathan
>
> > Admittedly, this will always use up to
> > sizeof(struct ad7192_platform_data) bytes (~12 bytes at most)
> > on the stack, during the probing of the device.
>
> >
> > But this will maintain most of the other
> > init code unchanged.
> >
>
> I'm hopeful that you are going to also do any remaining work necessary
> to get this out of staging once and for all?
>
> Yep.
> Once I get the gist of sending patches to the kernel.
> So far, I've only sent to other smaller projects ; I'll make an effort to learn the rules here.
>
> Anyhow, comments inline.
> > Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
> > ---
> > drivers/staging/iio/adc/ad7192.c | 27 +++++++++++++++++++++++++--
> > 1 file changed, 25 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/staging/iio/adc/ad7192.c b/drivers/staging/iio/adc/ad7192.c
> > index cadfb96734ed..fca988330588 100644
> > --- a/drivers/staging/iio/adc/ad7192.c
> > +++ b/drivers/staging/iio/adc/ad7192.c
> > @@ -610,18 +610,41 @@ static const struct iio_chan_spec ad7193_channels[] = {
> > IIO_CHAN_SOFT_TIMESTAMP(14),
> > };
> >
> > +static void ad7192_parse_dt(struct device_node *np,
> > + struct ad7192_platform_data *pdata)
> > +{
> > + of_property_read_u16(np, "adi,reference-voltage-mv", &pdata->vref_mv);
> > + of_property_read_u8(np, "adi,clock-source-select", &pdata->clock_source_sel);
> > + of_property_read_u32(np, "adi,external-clock-Hz", &pdata->ext_clk_hz);
> > + pdata->refin2_en = of_property_read_bool(np, "adi,refin2-pins-enable");
> > + pdata->rej60_en = of_property_read_bool(np, "adi,rejection-60-Hz-enable");
> > + pdata->sinc3_en = of_property_read_bool(np, "adi,sinc3-filter-enable");
> > + pdata->chop_en = of_property_read_bool(np, "adi,chop-enable");
> > + pdata->buf_en = of_property_read_bool(np, "adi,buffer-enable");
> > + pdata->unipolar_en = of_property_read_bool(np, "adi,unipolar-enable");
> > + pdata->burnout_curr_en = of_property_read_bool(np, "adi,burnout-currents-enable");
>
> Error checking? No particular reason a devicetree must be right and have all of
> these.
>
> Ack.
>
> > +}
> > +
> > static int ad7192_probe(struct spi_device *spi)
> > {
> > const struct ad7192_platform_data *pdata = dev_get_platdata(&spi->dev);
> > + const struct device_node *of_node = dev_of_node(&spi->dev);
> > + struct ad7192_platform_data lpdata;
> > struct ad7192_state *st;
> > struct iio_dev *indio_dev;
> > int ret, voltage_uv = 0;
> >
> > - if (!pdata) {
> > - dev_err(&spi->dev, "no platform data?\n");
> > + if (!pdata && !of_node) {
> > + dev_err(&spi->dev, "no platform data or device tree configuration?\n");
> > return -ENODEV;
> > }
> >
> > + if (!pdata) {
> > + memset(&lpdata, 0, sizeof(lpdata));
> > + pdata = &lpdata;
> > + ad7192_parse_dt(of_node, pdata);
> > + }
> > +
> > if (!spi->irq) {
> > dev_err(&spi->dev, "no IRQ?\n");
> > return -ENODEV;
>
>
prev parent reply other threads:[~2018-01-14 10:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 15:21 [PATCH 1/2] staging: iio: adc: ad7192: add device-tree support to driver alexandru.ardelean
2018-01-05 15:21 ` [PATCH 2/2] staging:iio:docs: add ad7291 doc to detail dt usage alexandru.ardelean
2018-01-05 15:25 ` Ardelean, Alexandru
2018-01-05 15:40 ` [PATCH 1/2] staging: iio: adc: ad7192: add device-tree support to driver Ardelean, Alexandru
2018-01-06 12:58 ` Jonathan Cameron
2018-01-08 7:51 ` Ardelean, Alexandru
2018-01-14 10:53 ` 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=20180114105354.7d4e71e6@archlinux \
--to=jic23@jic23.retrosnub.co.uk \
--cc=alexandru.Ardelean@analog.com \
--cc=linux-iio@vger.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).