Linux IIO development
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/2] iio: imu: inv_icm42600: add WoM support
Date: Fri, 13 Jun 2025 15:53:36 +0300	[thread overview]
Message-ID: <aEwfUMgLTnQxOh_k@smile.fi.intel.com> (raw)
In-Reply-To: <FR3P281MB17578B82AC67F49552E24EB3CE77A@FR3P281MB1757.DEUP281.PROD.OUTLOOK.COM>

On Fri, Jun 13, 2025 at 12:46:46PM +0000, Jean-Baptiste Maneyrol wrote:
> >From: Andy Shevchenko <andriy.shevchenko@intel.com>
> >Sent: Friday, June 13, 2025 10:29
> >On Fri, Jun 13, 2025 at 09:34:26AM +0200, Jean-Baptiste Maneyrol via B4 Relay wrote:

...

> >> +	if (sleep_ms)
> >> +		msleep(sleep_ms);
> >
> >I still wonder if we can get rid of the conditional here.
> >Would the
> >
> >	fsleep(sleep_ms * USEC_PER_MSEC)
> >
> >actually work as expected?
> >
> >Ditto for other case(s) like this.
> 
> fsleep(0) would call udelay(0) which is architecture dependent. It seems like
> it may delay for a very little while, but I'm not able to check that.

Hmm... This is unfortunate. Somebody needs at least make it clear in the
documentation if not yet done.

...

> >Overall, looking to this patch again, I think it would be better to prepend it
> >by replacing *int*_t types by the respective uXX ones. Because in this patch
> >we add dozens of new ones which increases an unneeded churn in the future.
> >
> In my opinion, to respect the rule don't mix *int*_t and uXX types, it is better
> to keep *int*_t types. If it need to be changed, we can change afterward the
> whole driver types with a replace tool and send it in a separate patch.

It will be never ending story, sorry. We need someone to solve this tech debt.
And since this patch adds more than 3 new users of it, I think it's a candidate
to embrace the burden.

> Jonathan,
> what is your statement on this point?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-06-13 12:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13  7:34 [PATCH v4 0/2] Add support for WoM (Wake-on-Motion) feature Jean-Baptiste Maneyrol via B4 Relay
2025-06-13  7:34 ` [PATCH v4 1/2] iio: imu: inv_icm42600: add WoM support Jean-Baptiste Maneyrol via B4 Relay
2025-06-13  8:29   ` Andy Shevchenko
2025-06-13 12:46     ` Jean-Baptiste Maneyrol
2025-06-13 12:53       ` Andy Shevchenko [this message]
2025-06-13 12:54         ` Andy Shevchenko
2025-06-13 13:43           ` Jean-Baptiste Maneyrol
2025-06-13 14:41             ` Andy Shevchenko
2025-06-13 15:01               ` Andy Shevchenko
2025-06-13 17:14                 ` Jean-Baptiste Maneyrol
2025-06-13 21:02                   ` Andy Shevchenko
2025-06-14 12:41                     ` Jonathan Cameron
2025-06-14 12:53   ` Jonathan Cameron
2025-06-16  7:42     ` Jean-Baptiste Maneyrol
2025-06-21 17:07       ` Jonathan Cameron
2025-06-13  7:34 ` [PATCH v4 2/2] iio: imu: inv_icm42600: add wakeup functionality for Wake-on-Motion Jean-Baptiste Maneyrol via B4 Relay
2025-06-13  8:31   ` Andy Shevchenko
2025-06-13 11:42     ` Jean-Baptiste Maneyrol

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=aEwfUMgLTnQxOh_k@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=Jean-Baptiste.Maneyrol@tdk.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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