From: Jonathan Cameron <jic23@kernel.org>
To: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: "Natália Salvino André" <natalia.andre@ime.usp.br>,
andy@kernel.org, dlechner@baylibre.com, jikos@kernel.org,
nuno.sa@analog.com,
"Pietro Di Consolo Gregorio" <pietro.gregorio@usp.br>,
linux-iio@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH v3 2/6] iio: gyro: HID: hid-sensor-gyro-3d: Refactor channel initialization
Date: Sat, 16 May 2026 12:44:39 +0100 [thread overview]
Message-ID: <20260516124439.6ca0843f@jic23-huawei> (raw)
In-Reply-To: <873e576772dc7b283bb4f01b3c838894cc7a35de.camel@linux.intel.com>
On Fri, 15 May 2026 09:48:34 -0700
srinivas pandruvada <srinivas.pandruvada@linux.intel.com> wrote:
> On Mon, 2026-05-11 at 22:16 -0300, Natália Salvino André wrote:
> > Replace the local gyro_3d_adjust_channel_bit_mask() function with a
> > compound literal for scan_type initialization to improve code
> > readability.
> >
> > Signed-off-by: Natália Salvino André <natalia.andre@ime.usp.br>
> > Co-developed-by: Pietro Di Consolo Gregorio <pietro.gregorio@usp.br>
> > Signed-off-by: Pietro Di Consolo Gregorio <pietro.gregorio@usp.br>
> > ---
> > drivers/iio/gyro/hid-sensor-gyro-3d.c | 24 +++++++++---------------
> > 1 file changed, 9 insertions(+), 15 deletions(-)
> >
> > diff --git a/drivers/iio/gyro/hid-sensor-gyro-3d.c
> > b/drivers/iio/gyro/hid-sensor-gyro-3d.c
> > index c340cc899a7c..4cbe4d93a0a1 100644
> > --- a/drivers/iio/gyro/hid-sensor-gyro-3d.c
> > +++ b/drivers/iio/gyro/hid-sensor-gyro-3d.c
> > @@ -3,6 +3,7 @@
> > * HID Sensors Driver
> > * Copyright (c) 2012, Intel Corporation.
> > */
> > +#include <linux/bitops.h>
> > #include <linux/device.h>
> > #include <linux/platform_device.h>
> > #include <linux/module.h>
> > @@ -82,17 +83,6 @@ static const struct iio_chan_spec
> > gyro_3d_channels[] = {
> > IIO_CHAN_SOFT_TIMESTAMP(CHANNEL_SCAN_INDEX_TIMESTAMP)
> > };
> >
> > -/* Adjust channel real bits based on report descriptor */
> > -static void gyro_3d_adjust_channel_bit_mask(struct iio_chan_spec
> > *channels,
> > - int channel, int
> > size)
> > -{
> > - channels[channel].scan_type.sign = 's';
> > - /* Real storage bits will change based on the report desc.
> > */
> > - channels[channel].scan_type.realbits = size * 8;
> > - /* Maximum size of a sample to capture is u32 */
> > - channels[channel].scan_type.storagebits = sizeof(u32) * 8;
> > -}
> > -
> > /* Channel read_raw handler */
> > static int gyro_3d_read_raw(struct iio_dev *indio_dev,
> > struct iio_chan_spec const *chan,
> > @@ -251,16 +241,20 @@ static int gyro_3d_parse_report(struct
> > platform_device *pdev,
> > int i;
> >
> > for (i = 0; i <= CHANNEL_SCAN_INDEX_Z; ++i) {
> > + unsigned int ch = CHANNEL_SCAN_INDEX_X + i;
> > +
>
> When you do code change more than what you described, then you should
> add to commit description that you are also doing this at the same
> time.
Particularly true when it is less than ideal. Like in previous
patch the loop shouldbe from CHANNEL_SCAN_INDEX_X to CHANNEL_SCAN_INDEX_Z
not 0 (the value is 0 but if we assume that then the sum for ch makes little
sense!)
>
> Thanks,
> Srinivas
>
> > ret = sensor_hub_input_get_attribute_info(hsdev,
> > HID_INPUT_REPORT,
> > usage_id,
> > HID_USAGE_SENSOR_ANGL_VELOCITY_X_AXI
> > S + i,
> > - &st->gyro[CHANNEL_SCAN_INDEX_X +
> > i]);
> > + &st->gyro[ch]);
> > if (ret < 0)
> > break;
> > - gyro_3d_adjust_channel_bit_mask(channels,
> > - CHANNEL_SCAN_INDEX_X + i,
> > - st->gyro[CHANNEL_SCAN_INDEX_X +
> > i].size);
> > + channels[ch].scan_type = (struct iio_scan_type) {
> > + .format = 's',
> > + .realbits = BYTES_TO_BITS(st-
> > >gyro[ch].size),
> > + .storagebits = BITS_PER_TYPE(u32),
> > + };
> > }
> > dev_dbg(&pdev->dev, "gyro_3d %x:%x, %x:%x, %x:%x\n",
> > st->gyro[0].index,
>
next prev parent reply other threads:[~2026-05-16 11:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 1:16 [PATCH v3 0/6] iio: hid-sensor: standardize scan_type initialization Natália Salvino André
2026-05-12 1:16 ` [PATCH v3 1/6] iio: accel: HID: hid-sensor-accel-3d: Refactor channel initialization Natália Salvino André
2026-05-13 2:21 ` sashiko-bot
2026-05-12 1:16 ` [PATCH v3 2/6] iio: gyro: HID: hid-sensor-gyro-3d: " Natália Salvino André
2026-05-13 2:50 ` sashiko-bot
2026-05-15 16:48 ` srinivas pandruvada
2026-05-16 11:44 ` Jonathan Cameron [this message]
2026-05-12 1:16 ` [PATCH v3 3/6] iio: light: HID: hid-sensor-als: " Natália Salvino André
2026-05-13 3:00 ` sashiko-bot
2026-05-12 1:16 ` [PATCH v3 4/6] iio: light: HID: hid-sensor-prox: " Natália Salvino André
2026-05-13 3:10 ` sashiko-bot
2026-05-12 1:16 ` [PATCH v3 5/6] iio: magnetometer: HID: hid-sensor-magn-3d: " Natália Salvino André
2026-05-13 3:19 ` sashiko-bot
2026-05-12 1:16 ` [PATCH v3 6/6] iio: pressure: HID: hid-sensor-press: " Natália Salvino André
2026-05-13 3:30 ` sashiko-bot
2026-05-12 14:42 ` [PATCH v3 0/6] iio: hid-sensor: standardize scan_type initialization Jonathan Cameron
2026-05-12 20:21 ` Andy Shevchenko
2026-05-12 14:48 ` Jonathan Cameron
2026-05-13 3:27 ` Zhang, Lixu
2026-05-14 2:44 ` Zhang, Lixu
2026-05-15 16:50 ` srinivas pandruvada
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=20260516124439.6ca0843f@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=natalia.andre@ime.usp.br \
--cc=nuno.sa@analog.com \
--cc=pietro.gregorio@usp.br \
--cc=srinivas.pandruvada@linux.intel.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