From: Martin Kepplinger <martink-1KBjaw7Xf1+zQB+pC5nmwQ@public.gmane.org>
To: pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.org,
jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
christoph.muellner-SN7IsUiht6C/RdPyistoZJqQE7yCjDx5@public.gmane.org
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 0/8] iio: mma8452: support more devices and improve driver
Date: Fri, 03 Jul 2015 09:32:07 +0200 [thread overview]
Message-ID: <55963A77.5040202@posteo.de> (raw)
In-Reply-To: <1435738922-12580-1-git-send-email-martink-1KBjaw7Xf1+zQB+pC5nmwQ@public.gmane.org>
Am 2015-07-01 um 10:21 schrieb Martin Kepplinger:
> This is the 2nd version that adds support for motion interrupts and 3 more
> accelerometer chips, two of which use them because they don't support the
> until now included transient interrupt sources:
>
> MMA8453Q, MMA8652FC and MMA8653FC; datasheets are in the commit messages.
>
> The driver and module name remains the same, seperating it from the device
> names it now supports.
>
> On top of this, there are minor documentation additions, and more notably,
> the change of the existing iio event type from IIO_EV_TYPE_THRESH to
> IIO_EV_TYPE_MAG since it's the magnitude of the threshold that is relevant
> for these devices, not a signed value.
>
> Please review and test if you can. For MMA8452Q, other than the event type,
> nothing should have changed.
>
Any wishes, suggestions, objections about this change?
thanks,
martin
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-07-03 7:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 8:21 [PATCH v2 0/8] iio: mma8452: support more devices and improve driver Martin Kepplinger
[not found] ` <1435738922-12580-1-git-send-email-martink-1KBjaw7Xf1+zQB+pC5nmwQ@public.gmane.org>
2015-07-01 8:21 ` [PATCH 1/8] iio: mma8452: refactor for seperating chip specific data Martin Kepplinger
2015-07-01 8:21 ` [PATCH 2/8] iio: mma8452: add support for MMA8453Q accelerometer chip Martin Kepplinger
2015-07-01 8:21 ` [PATCH 3/8] iio: mma8452: add freefall / motion interrupt source Martin Kepplinger
2015-07-01 8:21 ` [PATCH 4/8] iio: mma8452: add support for MMA8652FC and MMA8653FC accelerometers Martin Kepplinger
2015-07-01 8:21 ` [PATCH 5/8] iio: mma8452: add devicetree documentation Martin Kepplinger
2015-07-01 8:22 ` [PATCH 6/8] iio: mma8452: add copyright notice comment Martin Kepplinger
2015-07-01 8:22 ` [PATCH 7/8] iio: mma8452: change iio event type to IIO_EV_TYPE_MAG Martin Kepplinger
2015-07-01 8:22 ` [PATCH 8/8] iio: mma8452: leave sysfs namings to the iio core Martin Kepplinger
2015-07-03 7:32 ` Martin Kepplinger [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=55963A77.5040202@posteo.de \
--to=martink-1kbjaw7xf1+zqb+pc5nmwq@public.gmane.org \
--cc=christoph.muellner-SN7IsUiht6C/RdPyistoZJqQE7yCjDx5@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.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).