All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-next:master 4897/5417] drivers/i2c/busses/i2c-designware-amdpsp.c:165:25: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sat, 12 Feb 2022 05:24:05 +0800	[thread overview]
Message-ID: <202202120520.NbWJGvF2-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   6d9bd4ad4ca08b1114e814c2c42383b8b13be631
commit: 91560fe37f81ba8145427477a39cea88f4422385 [4897/5417] i2c: designware: Add AMD PSP I2C bus support
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220212/202202120520.NbWJGvF2-lkp(a)intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=91560fe37f81ba8145427477a39cea88f4422385
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 91560fe37f81ba8145427477a39cea88f4422385
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/i2c/busses/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)
>> drivers/i2c/busses/i2c-designware-amdpsp.c:165:25: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void const volatile [noderef] __iomem *addr @@     got unsigned int * @@
   drivers/i2c/busses/i2c-designware-amdpsp.c:165:25: sparse:     expected void const volatile [noderef] __iomem *addr
   drivers/i2c/busses/i2c-designware-amdpsp.c:165:25: sparse:     got unsigned int *

vim +165 drivers/i2c/busses/i2c-designware-amdpsp.c

   159	
   160	/* Helper to verify status returned by PSP */
   161	static int check_i2c_req_sts(struct psp_i2c_req *req)
   162	{
   163		int status;
   164	
 > 165		status = readl(&req->hdr.status);
   166	
   167		switch (status) {
   168		case PSP_I2C_REQ_STS_OK:
   169			return 0;
   170		case PSP_I2C_REQ_STS_BUS_BUSY:
   171			return -EBUSY;
   172		case PSP_I2C_REQ_STS_INV_PARAM:
   173		default:
   174			return -EIO;
   175		};
   176	}
   177	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Jan Dabros <jsd@semihalf.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Wolfram Sang <wsa-dev@sang-engineering.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [linux-next:master 4897/5417] drivers/i2c/busses/i2c-designware-amdpsp.c:165:25: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sat, 12 Feb 2022 05:24:05 +0800	[thread overview]
Message-ID: <202202120520.NbWJGvF2-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   6d9bd4ad4ca08b1114e814c2c42383b8b13be631
commit: 91560fe37f81ba8145427477a39cea88f4422385 [4897/5417] i2c: designware: Add AMD PSP I2C bus support
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220212/202202120520.NbWJGvF2-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=91560fe37f81ba8145427477a39cea88f4422385
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 91560fe37f81ba8145427477a39cea88f4422385
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/i2c/busses/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)
>> drivers/i2c/busses/i2c-designware-amdpsp.c:165:25: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void const volatile [noderef] __iomem *addr @@     got unsigned int * @@
   drivers/i2c/busses/i2c-designware-amdpsp.c:165:25: sparse:     expected void const volatile [noderef] __iomem *addr
   drivers/i2c/busses/i2c-designware-amdpsp.c:165:25: sparse:     got unsigned int *

vim +165 drivers/i2c/busses/i2c-designware-amdpsp.c

   159	
   160	/* Helper to verify status returned by PSP */
   161	static int check_i2c_req_sts(struct psp_i2c_req *req)
   162	{
   163		int status;
   164	
 > 165		status = readl(&req->hdr.status);
   166	
   167		switch (status) {
   168		case PSP_I2C_REQ_STS_OK:
   169			return 0;
   170		case PSP_I2C_REQ_STS_BUS_BUSY:
   171			return -EBUSY;
   172		case PSP_I2C_REQ_STS_INV_PARAM:
   173		default:
   174			return -EIO;
   175		};
   176	}
   177	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org


             reply	other threads:[~2022-02-11 21:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 21:24 kernel test robot [this message]
2022-02-11 21:24 ` [linux-next:master 4897/5417] drivers/i2c/busses/i2c-designware-amdpsp.c:165:25: sparse: sparse: incorrect type in argument 1 (different address spaces) kernel test robot
2022-02-14 12:27 ` Jan Dąbroś
2022-02-14 12:27   ` Jan Dąbroś
2022-02-14 13:27   ` Andy Shevchenko
2022-02-14 13:27     ` Andy Shevchenko
2022-02-14 13:59     ` Jan Dąbroś
2022-02-14 13:59       ` Jan Dąbroś
2022-02-14 14:43       ` Andy Shevchenko
2022-02-14 14:43         ` Andy Shevchenko
2022-02-16 14:06         ` Jan Dąbroś
2022-02-16 14:06           ` Jan Dąbroś

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=202202120520.NbWJGvF2-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /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.