linux-kernel - Re: [PATCH v2 0/8] iio: mma8452: support more devices and improve driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 03 Jul 2015 09:32:07 +0200
From:	Martin Kepplinger <martink@...teo.de>
To:	pmeerw@...erw.net, jic23@...nel.org,
	christoph.muellner@...obroma-systems.com
CC:	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-iio@...r.kernel.org
Subject: Re: [PATCH v2 0/8] iio: mma8452: support more devices and improve
 driver

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 linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/