:orphan:

.. title:: CONFIG_ADXL372_PEAK_DETECT_MODE

.. kconfig:: CONFIG_ADXL372_PEAK_DETECT_MODE

CONFIG_ADXL372_PEAK_DETECT_MODE
###############################

*Max Peak detect mode*

Type: ``bool``

Help
====

.. code-block:: none

    In most high-g applications, a single (3-axis) acceleration sample at
    the peak of an impact event contains sufficient information
    about the event, and the full acceleration history is not required.
    In this mode the device returns only the over threshold
    Peak Acceleration between two consecutive sample fetches.

Direct dependencies
===================

\ :ref:`<choice: Operating mode> <choice_331>`

*(Includes any dependencies from ifs and menus.)*

Kconfig definition
==================



At ``<Zephyr Driver>/sensor/adxl372/Kconfig:33``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:42`` → ``<Zephyr Driver>/Kconfig:64`` → ``<Zephyr Driver>/sensor/Kconfig:47``

Menu path: (Top) → Device Drivers → Sensor Drivers → ADXL372 Three Axis High-g I2C/SPI accelerometer → Operating mode

.. code-block:: kconfig

    config ADXL372_PEAK_DETECT_MODE
    	bool "Max Peak detect mode"
    	depends on <choice>
    	help
    	  In most high-g applications, a single (3-axis) acceleration sample at
    	  the peak of an impact event contains sufficient information
    	  about the event, and the full acceleration history is not required.
    	  In this mode the device returns only the over threshold
    	  Peak Acceleration between two consecutive sample fetches.

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*