linux-kernel - Re: [PATCH v6 11/11] docs: iio: add documentation for adxl345 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]

Message-ID: <20250418193833.4abe05e7@jic23-huawei>
Date: Fri, 18 Apr 2025 19:38:33 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: Lothar Rubusch <l.rubusch@...il.com>
Cc: lars@...afoo.de, Michael.Hennerich@...log.com,
 linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org,
 eraretuya@...il.com
Subject: Re: [PATCH v6 11/11] docs: iio: add documentation for adxl345
 driver

On Mon, 14 Apr 2025 18:42:45 +0000
Lothar Rubusch <l.rubusch@...il.com> wrote:

> The documentation describes the ADXL345 driver, IIO interface,
> interface usage and configuration.
> 
> Signed-off-by: Lothar Rubusch <l.rubusch@...il.com>

This probably wants updating to reflect the subtle _all_ vs _any_
definitions for the various events.

> +When **activity** and **inactivity** events are enabled, the driver automatically
> +will implement its hysteresis solution by setting link bit and autosleep bit.
> +The link bit serially links the activity and inactivity functions. On the other
> +side, the autosleep function switches the sensor to sleep mode if the
> +inactivity function is enabled. This will reduce current consumption to the
> +sub-12.5Hz rate. Inactivity time can be configured between 1s and 255s. When 0
> +is configured as inactivity time, the driver will define a reasonable value
> +depending on a heuristic approach to optimize power consumption.

> +A **free fall** event will be detected if the signal goes below the configured
> +threshold, for the configured time [us].
> +
Also the examples later in the document will change with the introduction of
a pseudo channel for freefall (where there is only one set of parameters for
all channels). For activity / inactivity the per channel enables mean we keep
those on the individual channels.  It's always a bit odd to report an event
for a compound channel that doesn't have it to enable, but we've never found
a better way to handle that.

Jonathan