From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Angelo Dureghello <adureghello@baylibre.com>
Cc: <oe-kbuild-all@lists.linux.dev>, Nuno Sa <nuno.sa@analog.com>,
<linux-iio@vger.kernel.org>
Subject: Re: [jic23-iio:testing 23/47] drivers/iio/dac/adi-axi-dac.c:731 axi_dac_bus_set_io_mode() warn: always true condition '(mode >= 0) => (0-u32max >= 0)'
Date: Tue, 4 Feb 2025 08:57:44 +0000 [thread overview]
Message-ID: <20250204085744.000075d4@huawei.com> (raw)
In-Reply-To: <rhmmbt3yqfqhodivu2smuu4g2i77sqyzr3jjjxtvjsny7a6jgd@64bong6elaul>
On Tue, 4 Feb 2025 09:43:17 +0100
Angelo Dureghello <adureghello@baylibre.com> wrote:
> Hi Jonathan,
>
> On 04.02.2025 07:23, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git testing
> > head: 315198c0a370da031f5c3d504b99f771a0c545ab
> > commit: 493122c53af1915b4b5b5f47a8c446973ebff052 [23/47] iio: dac: adi-axi-dac: add bus mode setup
> > config: m68k-randconfig-r071-20250204 (https://download.01.org/0day-ci/archive/20250204/202502040758.DJqHqhLO-lkp@intel.com/config)
> > compiler: m68k-linux-gcc (GCC) 14.2.0
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202502040758.DJqHqhLO-lkp@intel.com/
> >
> > smatch warnings:
> > drivers/iio/dac/adi-axi-dac.c:731 axi_dac_bus_set_io_mode() warn: always true condition '(mode >= 0) => (0-u32max >= 0)'
> >
> > vim +731 drivers/iio/dac/adi-axi-dac.c
> >
> > 724
> > 725 static int axi_dac_bus_set_io_mode(struct iio_backend *back,
> > 726 enum ad3552r_io_mode mode)
> > 727 {
> > 728 struct axi_dac_state *st = iio_backend_get_priv(back);
> > 729 int ival, ret;
> > 730
> > > 731 if (!(mode >= AD3552R_IO_MODE_SPI && mode <= AD3552R_IO_MODE_QSPI))
> > 732
>
> not clear to me the reason of this warning, maybe because mode is an enum ?
> Should i take any action ?
Currently there are only a few modes in there and that range covers them all I think.
So warning is correct, but we perhaps want this check there as hardening against future
addition of more modes. Maybe an explicit switch with all modes listed and a default
will have same effect and be better defense anyway against future changes?
Jonathan
>
> return -EINVAL;
> > 733
> > 734 guard(mutex)(&st->lock);
> > 735
> > 736 ret = regmap_update_bits(st->regmap, AXI_DAC_CUSTOM_CTRL_REG,
> > 737 AXI_DAC_CUSTOM_CTRL_MULTI_IO_MODE,
> > 738 FIELD_PREP(AXI_DAC_CUSTOM_CTRL_MULTI_IO_MODE, mode));
> > 739 if (ret)
> > 740 return ret;
> > 741
> > 742 return regmap_read_poll_timeout(st->regmap, AXI_DAC_UI_STATUS_REG, ival,
> > 743 FIELD_GET(AXI_DAC_UI_STATUS_IF_BUSY, ival) == 0, 10,
> > 744 100 * KILO);
> > 745 }
> > 746
> >
> > --
> > 0-DAY CI Kernel Test Service
> > https://github.com/intel/lkp-tests/wiki
>
> Thanks,
> regards,
> angelo
next prev parent reply other threads:[~2025-02-04 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 23:23 [jic23-iio:testing 23/47] drivers/iio/dac/adi-axi-dac.c:731 axi_dac_bus_set_io_mode() warn: always true condition '(mode >= 0) => (0-u32max >= 0)' kernel test robot
2025-02-04 8:43 ` Angelo Dureghello
2025-02-04 8:57 ` Jonathan Cameron [this message]
2025-02-04 9:12 ` Angelo Dureghello
2025-02-04 19:27 ` Jonathan Cameron
2025-02-08 15:10 ` 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=20250204085744.000075d4@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=adureghello@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.