From: Stefan Wahren <stefan.wahren@i2se.com>
To: jic23@kernel.org
Cc: festevam@gmail.com, kristina.martsenko@gmail.com,
knaack.h@gmx.de, marex@denx.de, kernel@pengutronix.de,
pawel.moll@arm.com, ijc+devicetree@hellion.org.uk,
robh+dt@kernel.org, galak@codeaurora.org, mark.rutland@arm.com,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: [PATCH V2 0/2] iio: mxs-lradc: check ranges of ts properties
Date: Mon, 29 Dec 2014 10:27:19 +0000 [thread overview]
Message-ID: <1419848841-12749-1-git-send-email-stefan.wahren@i2se.com> (raw)
These patch series fixes off-by-one issues of the touchscreen DT properties
and finally adds a range check during probe.
Only the range check has been tested by myself, because i don't have a
touchscreen. So a functional test is very welcome.
Changes since V1:
- fix format specifier in error message
- fix minor style issues
Changes since RFC:
- add fix for off-by-one issues
- first check DT properties and then assign a value
- adapt range check to better represent DT binding
- add important note from the reference manual as comment
Stefan Wahren (2):
DT: mxs-lradc: fix ranges of ts properties
iio: mxs-lradc: check ranges of ts properties
.../bindings/staging/iio/adc/mxs-lradc.txt | 4 +-
drivers/staging/iio/adc/mxs-lradc.c | 45 +++++++++++++++-----
2 files changed, 37 insertions(+), 12 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-12-29 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 10:27 Stefan Wahren [this message]
2014-12-29 10:27 ` [PATCH V2 1/2] DT: mxs-lradc: fix ranges of ts properties Stefan Wahren
2015-01-04 11:14 ` Jonathan Cameron
2014-12-29 10:27 ` [PATCH V2 2/2] iio: mxs-lradc: check " Stefan Wahren
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=1419848841-12749-1-git-send-email-stefan.wahren@i2se.com \
--to=stefan.wahren@i2se.com \
--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=marex@denx.de \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.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).