From: Jelle van der Waa <jelle@vdwaa.nl>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Subject: Re: [PATCH v2] iio: accel: add support for the Domintech DMARD09 3-axis accelerometer
Date: Sun, 24 Jul 2016 16:11:08 +0200 [thread overview]
Message-ID: <20160724141107.GA3781@gmail.com> (raw)
In-Reply-To: <68c86474-aa4b-bb96-f412-38bafe3b9ff1@kernel.org>
On 07/24/16 at 02:25pm, Jonathan Cameron wrote:
> Hi Jelle,
>
> One quick process thing first. If you are sending a new version, please
> don't send it as a reply to the previous. I leads to convoluted
> and very deep threads where it isn't always clear which version
> is being replied to!
Thanks,
I'm quiet new to Linux kernel development. I hope to address the last
few comments today and send out a v3.
---
Jelle van der Waa
>
> Thanks,
>
> Jonathan
>
> On 18/07/16 21:54, Jelle van der Waa wrote:
> > This patch adds basic read_raw support for the DMARD09 3-axis accelerometer
> > which can be found in a q8 A33 Allwinner tablet. [0]
> >
> > The driver is based on the Android driver which can be found
> > on Github. [1]
> >
> > Unfortunately there is no datatsheet of the DMARD09 available online.
> >
> > [0] http://linux-sunxi.org/TZX-723Qa4
> > [1] https://github.com/JujuXIII/android_kernel_acer_v370_KK/tree/master/mediatek/custom/common/kernel/accelerometer/dmard09
> >
> > Changes in v2:
> > - Use ARRAY_SIZE instead of the #define DMARD09_AXES_NUM
> > - Use a function-like macro to generate the channel structs
> > - Remove duplicate 3-axis in driver description
> > - Don't initialize the u8 buf
> > - Use devm_iio_device_register and remove the now unrequired
> > dmard09_remove.
> > - Remove device from dmard09_data struct and use the client member to retrieve
> > the device.
> > - Describe the read strategy of the read_raw function
> > - Simplify reading the X, Y, Z axis, by introducing DMARD09_AXIS_N_OFFSET,
> > which removes the required if statements.
> > - Log the _STAT address in the dev_error in the dmard09_read_raw function.
> >
> >
> > Jelle van der Waa (1):
> > iio: accel: add support for the Domintech DMARD09 3-axis accelerometer
> >
> > .../devicetree/bindings/iio/accel/dmard09.txt | 13 ++
> > drivers/iio/accel/Kconfig | 10 ++
> > drivers/iio/accel/Makefile | 1 +
> > drivers/iio/accel/dmard09.c | 149 +++++++++++++++++++++
> > 4 files changed, 173 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/iio/accel/dmard09.txt
> > create mode 100644 drivers/iio/accel/dmard09.c
> >
>
next prev parent reply other threads:[~2016-07-24 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 19:51 [PATCH] Add support for the Domintech DMARD09 3-axis accelerometer Jelle van der Waa
2016-07-16 19:51 ` [PATCH] iio: accel: add " Jelle van der Waa
2016-07-17 16:12 ` Peter Meerwald-Stadler
2016-07-18 11:54 ` Lars-Peter Clausen
2016-07-18 17:01 ` Jonathan Cameron
2016-07-18 20:54 ` [PATCH v2] " Jelle van der Waa
2016-07-18 20:54 ` [PATCH] " Jelle van der Waa
2016-07-24 13:30 ` Jonathan Cameron
2016-07-24 13:25 ` [PATCH v2] " Jonathan Cameron
2016-07-24 14:11 ` Jelle van der Waa [this message]
2016-07-24 18:56 ` 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=20160724141107.GA3781@gmail.com \
--to=jelle@vdwaa.nl \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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).