All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-kiwi-6.1 46/46] drivers/usb/cdns3/cdnsp-gadget.c:156:16: sparse: sparse: cast to restricted __le32
Date: Tue, 23 Dec 2025 16:17:43 +0800	[thread overview]
Message-ID: <202512231645.QE97S3sf-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android14-kiwi-6.1
head:   cb7f87cbf542550ff3ab5312b66ad42c860708ed
commit: 0554dade57dd6d657eba7303b63a8ed93498063d [46/46] usb: cdnsp: Fix issue with resuming from L1
config: x86_64-randconfig-r132-20251223 (https://download.01.org/0day-ci/archive/20251223/202512231645.QE97S3sf-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251223/202512231645.QE97S3sf-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/202512231645.QE97S3sf-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/usb/cdns3/cdnsp-gadget.c:156:16: sparse: sparse: cast to restricted __le32
>> drivers/usb/cdns3/cdnsp-gadget.c:158:16: sparse: sparse: incorrect type in argument 1 (different base types) @@     expected unsigned int val @@     got restricted __le32 [usertype] @@
   drivers/usb/cdns3/cdnsp-gadget.c:158:16: sparse:     expected unsigned int val
   drivers/usb/cdns3/cdnsp-gadget.c:158:16: sparse:     got restricted __le32 [usertype]

vim +156 drivers/usb/cdns3/cdnsp-gadget.c

   140	
   141	static void cdnsp_set_apb_timeout_value(struct cdnsp_device *pdev)
   142	{
   143		struct cdns *cdns = dev_get_drvdata(pdev->dev);
   144		__le32 __iomem *reg;
   145		void __iomem *base;
   146		u32 offset = 0;
   147		u32 val;
   148	
   149		if (!cdns->override_apb_timeout)
   150			return;
   151	
   152		base = &pdev->cap_regs->hc_capbase;
   153		offset = cdnsp_find_next_ext_cap(base, offset, D_XEC_PRE_REGS_CAP);
   154		reg = base + offset + REG_CHICKEN_BITS_3_OFFSET;
   155	
 > 156		val  = le32_to_cpu(readl(reg));
   157		val = CHICKEN_APB_TIMEOUT_SET(val, cdns->override_apb_timeout);
 > 158		writel(cpu_to_le32(val), reg);
   159	}
   160	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-12-23  8:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202512231645.QE97S3sf-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.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.