linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Lothar Rubusch <l.rubusch@gmail.com>
Cc: jic23@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
	andy@kernel.org, corbet@lwn.net, lucas.p.stankus@gmail.com,
	lars@metafoo.de, Michael.Hennerich@analog.com,
	bagasdotme@gmail.com, linux-iio@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 3/8] iio: accel: adxl313: add buffered FIFO watermark with interrupt handling
Date: Thu, 3 Jul 2025 17:36:41 +0300	[thread overview]
Message-ID: <aGaVeW4l6HkiMtql@smile.fi.intel.com> (raw)
In-Reply-To: <20250702230819.19353-4-l.rubusch@gmail.com>

On Wed, Jul 02, 2025 at 11:08:14PM +0000, Lothar Rubusch wrote:
> Cover the following tasks:
> - Add scan_mask and scan_index to the IIO channel configuration. The
> scan_index sets up buffer usage. According to the datasheet, the ADXL313
> uses a 13-bit wide data field in full-resolution mode. Set the
> signedness, number of storage bits, and endianness accordingly.
> 
> - Parse the devicetree for an optional interrupt line and configure the
> interrupt mapping based on its presence. If no interrupt line is
> specified, keep the FIFO in bypass mode as currently implemented.
> 
> - Set up the interrupt handler. Add register access to detect and
> evaluate interrupts. Implement functions to clear status registers and
> reset the FIFO.
> 
> - Implement FIFO watermark configuration and handling. Allow the
> watermark level to be set, evaluate the corresponding interrupt, read
> the FIFO contents, and push the data to the IIO channel.

...

> +err:

The rule of thumb for naming error labels is an answer to "what does code do
when I goto $LABEL?". In other words name should encode what will be done when
goto. In this case I would make it

err_fifo_reset:

The rationale is that reading the code won't require to "goto" to understand
what 'err' means.

> +	adxl313_fifo_reset(data);
> +
> +	return IRQ_HANDLED;

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-07-03 14:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02 23:08 [PATCH v7 0/8] iio: accel: adxl313: add power-save on activity/inactivity Lothar Rubusch
2025-07-02 23:08 ` [PATCH v7 1/8] iio: accel: adxl313: make use of regmap cache Lothar Rubusch
2025-07-02 23:08 ` [PATCH v7 2/8] iio: accel: adxl313: add function to enable measurement Lothar Rubusch
2025-07-02 23:08 ` [PATCH v7 3/8] iio: accel: adxl313: add buffered FIFO watermark with interrupt handling Lothar Rubusch
2025-07-03 14:36   ` Andy Shevchenko [this message]
2025-07-02 23:08 ` [PATCH v7 4/8] iio: accel: adxl313: add activity sensing Lothar Rubusch
2025-07-02 23:08 ` [PATCH v7 5/8] iio: accel: adxl313: add inactivity sensing Lothar Rubusch
2025-07-02 23:08 ` [PATCH v7 6/8] iio: accel: adxl313: implement power-save on inactivity Lothar Rubusch
2025-07-02 23:08 ` [PATCH v7 7/8] iio: accel: adxl313: add AC coupled activity/inactivity events Lothar Rubusch
2025-07-02 23:08 ` [PATCH v7 8/8] docs: iio: add ADXL313 accelerometer Lothar Rubusch
2025-07-03 14:40 ` [PATCH v7 0/8] iio: accel: adxl313: add power-save on activity/inactivity Andy Shevchenko
2025-07-06 12:03   ` Jonathan Cameron

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=aGaVeW4l6HkiMtql@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=l.rubusch@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.p.stankus@gmail.com \
    --cc=nuno.sa@analog.com \
    /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).