From: kernel test robot <lkp@intel.com>
To: Pawel Laszczak <pawell@cadence.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: drivers/usb/cdns3/cdnsp-gadget.c:159:16: sparse: sparse: incorrect type in argument 1 (different base types)
Date: Thu, 08 Jan 2026 09:31:41 +0800 [thread overview]
Message-ID: <202601080940.6cYiaoCI-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: f0b9d8eb98dfee8d00419aa07543bdc2c1a44fb1
commit: 241e2ce88e5a494be7a5d44c0697592f1632fbee usb: cdnsp: Fix issue with resuming from L1
date: 8 months ago
config: loongarch-randconfig-r132-20260108 (https://download.01.org/0day-ci/archive/20260108/202601080940.6cYiaoCI-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260108/202601080940.6cYiaoCI-lkp@intel.com/reproduce)
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/202601080940.6cYiaoCI-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/usb/cdns3/cdnsp-gadget.c:157:16: sparse: sparse: cast to restricted __le32
>> drivers/usb/cdns3/cdnsp-gadget.c:159:16: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected unsigned int [usertype] value @@ got restricted __le32 [usertype] @@
drivers/usb/cdns3/cdnsp-gadget.c:159:16: sparse: expected unsigned int [usertype] value
drivers/usb/cdns3/cdnsp-gadget.c:159:16: sparse: got restricted __le32 [usertype]
vim +159 drivers/usb/cdns3/cdnsp-gadget.c
141
142 static void cdnsp_set_apb_timeout_value(struct cdnsp_device *pdev)
143 {
144 struct cdns *cdns = dev_get_drvdata(pdev->dev);
145 __le32 __iomem *reg;
146 void __iomem *base;
147 u32 offset = 0;
148 u32 val;
149
150 if (!cdns->override_apb_timeout)
151 return;
152
153 base = &pdev->cap_regs->hc_capbase;
154 offset = cdnsp_find_next_ext_cap(base, offset, D_XEC_PRE_REGS_CAP);
155 reg = base + offset + REG_CHICKEN_BITS_3_OFFSET;
156
> 157 val = le32_to_cpu(readl(reg));
158 val = CHICKEN_APB_TIMEOUT_SET(val, cdns->override_apb_timeout);
> 159 writel(cpu_to_le32(val), reg);
160 }
161
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-08 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 1:31 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-21 13:40 kernel test robot
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=202601080940.6cYiaoCI-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pawell@cadence.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
all inboxes | Powered by JetHome®