linux-kernel - Re: [PATCH] iio: accel: mma8452: Bugfix to enbale and allow different events to work parallely.

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 for Android: free password hash cracker in your pocket

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

Date:   Fri, 18 Aug 2017 20:05:52 -0400
From:   Harinath Nampally <harinath922@...il.com>
To:     Jonathan Cameron <jic23@...nel.org>
Cc:     Martin Kepplinger <martink@...teo.de>,
        Peter Meerwald-Stadler <pmeerw@...erw.net>, knaack.h@....de,
        lars@...afoo.de, gregkh@...uxfoundation.org,
        linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org,
        amsfield22@...il.com
Subject: Re: [PATCH] iio: accel: mma8452: Bugfix to enbale and allow different
 events to work parallely.

> This patch fixes by detaching the event related information from
> chip_info struct,
>>> and based on channel type and event direction the corresponding
> event configuration registers
>>> are picked dynamically. Hence multiple events can be handled in
> read/write callbacks.
>> which chip can have which event(s)?
> I am planning to add 'supported events' field in
> One small point. Don't put the word bugfix in the title (and fix
> spelling of enable!).  I know this is obviously a false restriction
> on the driver, but it doesn't not work, it is just limited in features
> without this.
Sure, thanks for letting me know.


On 08/17/2017 10:40 AM, Jonathan Cameron wrote:
>>> This patch fixes by detaching the event related information from
>>> chip_info struct,
>>>>> and based on channel type and event direction the corresponding
>>> event configuration registers
>>>>> are picked dynamically. Hence multiple events can be handled in
>>> read/write callbacks.
>>>> which chip can have which event(s)?
>>> I am planning to add 'supported events' field in
> One small point. Don't put the word bugfix in the title (and fix
> spelling of enable!).  I know this is obviously a false restriction
> on the driver, but it doesn't not work, it is just limited in features
> without this.