devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Souradeep Chowdhury <quic_schowdhu@quicinc.com>,
	Andy Gross <agross@kernel.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh+dt@kernel.org>, Alex Elder <elder@ieee.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, Sibi Sankar <quic_sibis@quicinc.com>,
	Rajendra Nayak <quic_rjendra@quicinc.com>,
	Souradeep Chowdhury <quic_schowdhu@quicinc.com>
Subject: Re: [PATCH V1 2/3] drivers: misc: dcc: Add driver support for Data Capture and Compare unit(DCC)
Date: Tue, 18 Apr 2023 13:18:22 +0800	[thread overview]
Message-ID: <202304181327.0grVYsHS-lkp@intel.com> (raw)
In-Reply-To: <b1a9cbbcfefe133cc9047a71a2acdaa74239df29.1681480351.git.quic_schowdhu@quicinc.com>

Hi Souradeep,

kernel test robot noticed the following build warnings:

[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on char-misc/char-misc-next char-misc/char-misc-linus linus/master v6.3-rc7 next-20230417]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Souradeep-Chowdhury/dt-bindings-misc-qcom-dcc-Add-the-dtschema/20230414-220304
patch link:    https://lore.kernel.org/r/b1a9cbbcfefe133cc9047a71a2acdaa74239df29.1681480351.git.quic_schowdhu%40quicinc.com
patch subject: [PATCH V1 2/3] drivers: misc: dcc: Add driver support for Data Capture and Compare unit(DCC)
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20230418/202304181327.0grVYsHS-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project 9638da200e00bd069e6dd63604e14cbafede9324)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install arm64 cross compiling tool for clang build
        # apt-get install binutils-aarch64-linux-gnu
        # https://github.com/intel-lab-lkp/linux/commit/f3f73f6008e1ebca6fba848e260b1f938d91be95
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Souradeep-Chowdhury/dt-bindings-misc-qcom-dcc-Add-the-dtschema/20230414-220304
        git checkout f3f73f6008e1ebca6fba848e260b1f938d91be95
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 olddefconfig
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/misc/

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304181327.0grVYsHS-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/misc/dcc.c:217:14: warning: variable 'ret' is used uninitialized whenever 'for' loop exits because its condition is false [-Wsometimes-uninitialized]
           for (i = 0; i < drvdata->nr_link_list; i++) {
                       ^~~~~~~~~~~~~~~~~~~~~~~~~
   drivers/misc/dcc.c:238:9: note: uninitialized use occurs here
           return ret;
                  ^~~
   drivers/misc/dcc.c:217:14: note: remove the condition if it is always true
           for (i = 0; i < drvdata->nr_link_list; i++) {
                       ^~~~~~~~~~~~~~~~~~~~~~~~~
   drivers/misc/dcc.c:190:9: note: initialize the variable 'ret' to silence this warning
           int ret;
                  ^
                   = 0
   1 warning generated.


vim +217 drivers/misc/dcc.c

   186	
   187	static int dcc_sw_trigger(struct dcc_drvdata *drvdata)
   188	{
   189		void __iomem *addr;
   190		int ret;
   191		int i;
   192		u32 status;
   193		u32 ll_cfg;
   194		u32 tmp_ll_cfg;
   195		u32 val;
   196	
   197		mutex_lock(&drvdata->mutex);
   198	
   199		for (i = 0; i < drvdata->nr_link_list; i++) {
   200			if (!test_bit(i, drvdata->enable_bitmap))
   201				continue;
   202			ll_cfg = dcc_list_readl(drvdata, i, DCC_LL_CFG);
   203			tmp_ll_cfg = ll_cfg & ~DCC_TRIGGER_MASK;
   204			dcc_list_writel(drvdata, tmp_ll_cfg, i, DCC_LL_CFG);
   205			dcc_list_writel(drvdata, 1, i, DCC_LL_SW_TRIGGER);
   206			dcc_list_writel(drvdata, ll_cfg, i, DCC_LL_CFG);
   207		}
   208	
   209		addr = drvdata->base + DCC_STATUS(drvdata->mem_map_ver);
   210		if (readl_poll_timeout(addr, val, !FIELD_GET(DCC_STATUS_MASK, val),
   211				       1, STATUS_READY_TIMEOUT)) {
   212			dev_err(drvdata->dev, "DCC is busy after receiving sw trigger\n");
   213			ret = -EBUSY;
   214			goto out_unlock;
   215		}
   216	
 > 217		for (i = 0; i < drvdata->nr_link_list; i++) {
   218			if (!test_bit(i, drvdata->enable_bitmap))
   219				continue;
   220	
   221			status = dcc_list_readl(drvdata, i, DCC_LL_BUS_ACCESS_STATUS);
   222			if (!status)
   223				continue;
   224	
   225			dev_err(drvdata->dev, "Read access error for list %d err: 0x%x\n",
   226				i, status);
   227			ll_cfg = dcc_list_readl(drvdata, i, DCC_LL_CFG);
   228			tmp_ll_cfg = ll_cfg & ~DCC_TRIGGER_MASK;
   229			dcc_list_writel(drvdata, tmp_ll_cfg, i, DCC_LL_CFG);
   230			dcc_list_writel(drvdata, DCC_STATUS_MASK, i, DCC_LL_BUS_ACCESS_STATUS);
   231			dcc_list_writel(drvdata, ll_cfg, i, DCC_LL_CFG);
   232			ret = -ENODATA;
   233			break;
   234		}
   235	
   236	out_unlock:
   237		mutex_unlock(&drvdata->mutex);
   238		return ret;
   239	}
   240	

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

  parent reply	other threads:[~2023-04-18  5:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 13:59 [PATCH V1 0/3] Add Data Capture and Compare(DCC) driver to new location Souradeep Chowdhury
2023-04-14 13:59 ` [PATCH V1 1/3] dt-bindings: misc: qcom,dcc: Add the dtschema Souradeep Chowdhury
2023-04-14 13:59 ` [PATCH V1 2/3] drivers: misc: dcc: Add driver support for Data Capture and Compare unit(DCC) Souradeep Chowdhury
2023-04-15  5:39   ` Greg Kroah-Hartman
2023-04-17  6:01     ` Souradeep Chowdhury
2023-04-17  6:17       ` Greg Kroah-Hartman
2023-04-17  6:56         ` Souradeep Chowdhury
2023-04-17  7:41           ` Greg Kroah-Hartman
2023-04-17  8:50             ` Souradeep Chowdhury
2023-04-18  5:18   ` kernel test robot [this message]
2023-04-14 13:59 ` [PATCH V1 3/3] MAINTAINERS: Add the entry for DCC(Data Capture and Compare) driver support Souradeep Chowdhury

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=202304181327.0grVYsHS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=elder@ieee.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=quic_rjendra@quicinc.com \
    --cc=quic_schowdhu@quicinc.com \
    --cc=quic_sibis@quicinc.com \
    --cc=robh+dt@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).