linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: kristina.martsenko@gmail.com, kernel@pengutronix.de,
	jic23@kernel.org, pawel.moll@arm.com, knaack.h@gmx.de,
	ijc+devicetree@hellion.org.uk, robh+dt@kernel.org,
	galak@codeaurora.org, festevam@gmail.com, mark.rutland@arm.com,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: mxs-lradc: check ranges of ts properties
Date: Wed, 24 Dec 2014 01:35:21 +0100	[thread overview]
Message-ID: <201412240135.21244.marex@denx.de> (raw)
In-Reply-To: <1197201553.616296.1419374759245.JavaMail.open-xchange@oxbaltgw02.schlund.de>

On Tuesday, December 23, 2014 at 11:45:59 PM, Stefan Wahren wrote:
> Hi Marek,

Hi!

> > Marek Vasut <marex@denx.de> hat am 23. Dezember 2014 um 14:37
> > geschrieben:
> > 
> > 
> > On Monday, December 22, 2014 at 01:14:36 PM, Stefan Wahren wrote:
> > [...]
> > 
> > Very minor coding style flub in this comment above. Multi-line comments
> > should start with /* and a newline after that ;-)
> 
> Thanks for your advice.

Sure, it's really a minor thing.

> > > + * from the datasheet:
> > > + * "The DELAY fields in HW_LRADC_DELAY0, HW_LRADC_DELAY1,
> > > + * HW_LRADC_DELAY2, and HW_LRADC_DELAY3 must be non-zero; otherwise,
> > > + * the LRADC will not trigger the delay group."
> > > + */
> > > mxs_lradc_reg_wrt(lradc, LRADC_DELAY_TRIGGER(1 << ch) |
> > > LRADC_DELAY_TRIGGER_DELAYS(0) |
> > > LRADC_DELAY_LOOP(lradc->over_sample_cnt - 1) |
> > > @@ -1495,20 +1501,38 @@ static int mxs_lradc_probe_touchscreen(struct
> > > mxs_lradc *lradc, return -EINVAL;
> > > }
> > > 
> > > - lradc->over_sample_cnt = 4;
> > > - ret = of_property_read_u32(lradc_node, "fsl,ave-ctrl", &adapt);
> > > - if (ret == 0)
> > > + if (of_property_read_u32(lradc_node, "fsl,ave-ctrl", &adapt)) {
> > > + lradc->over_sample_cnt = 4;
> > > + } else {
> > > + if (adapt < 1 || adapt > 32) {
> > 
> > This is just an idea, but do we not have some kind of a
> > "of_property_read_u32_range()" thingie, which would include this kind of
> > range checking ? Would it be worth implementing such thing ? What do you
> > think please ?
> 
> I never heard of such a function. I think it's not the best idea of mixing
> dt parsing and range checking in a general function.

It was just an idea, since it would trim down the code duplication a bit.

> But this code does nearly the same thing 3 times. How about defining an
> array of property range structures:
> 
> static const struct property_value_range mxs_lradc_properties[] = {
> 	{
> 		.name = "fsl,ave-ctrl",
> 		.min_value = 1,
> 		.max_value = 32,
> 		.default_value = 4,
> 	},
> 	{
> 		.name = "fsl,ave-delay",
> 		.min_value = 2,
> 		.max_value = LRADC_DELAY_DELAY_MASK+1,
> 		.default_value = 2,
> 	},
> 	{
> 		.name = "fsl,settling",
> 		.min_value = 1,
> 		.max_value = LRADC_DELAY_DELAY_MASK,
> 		.default_value = 10,
> 	},
> };
> 
> and a local validate function for these optional parameters.

That's becoming a bit too complex for such a simple task. I cannot tell right 
now, so I'd prefer of others chimed in.

Have a nice holiday!

  reply	other threads:[~2014-12-24  0:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22 12:14 [PATCH 0/2] iio: mxs-lradc: check ranges of ts properties Stefan Wahren
2014-12-22 12:14 ` [PATCH 1/2] DT: mxs-lradc: fix " Stefan Wahren
2014-12-22 12:14 ` [PATCH 2/2] iio: mxs-lradc: check " Stefan Wahren
2014-12-23 13:37   ` Marek Vasut
2014-12-23 22:45     ` Stefan Wahren
2014-12-24  0:35       ` Marek Vasut [this message]
2014-12-26  9:22         ` Jonathan Cameron
2014-12-26  9:23   ` Jonathan Cameron
2014-12-26 20:50     ` Stefan Wahren
2014-12-26 21:57       ` Jonathan Cameron

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=201412240135.21244.marex@denx.de \
    --to=marex@denx.de \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jic23@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=knaack.h@gmx.de \
    --cc=kristina.martsenko@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=stefan.wahren@i2se.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).