linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Nickolay Goppen <setotau@yandex.ru>,
	Bjorn Andersson <andersson@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-arm-msm@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	Nickolay Goppen <setotau@yandex.ru>,
	Richard Acayan <mailingradian@gmail.com>
Subject: Re: [PATCH 3/3] pinctrl: qcom: Add SDM660 LPASS LPI TLMM
Date: Tue, 26 Aug 2025 14:01:15 +0800	[thread overview]
Message-ID: <202508261333.8hcdJOVB-lkp@intel.com> (raw)
In-Reply-To: <20250824-sdm660-lpass-lpi-v1-3-003d5cc28234@yandex.ru>

Hi Nickolay,

kernel test robot noticed the following build warnings:

[auto build test WARNING on 038d61fd642278bab63ee8ef722c50d10ab01e8f]

url:    https://github.com/intel-lab-lkp/linux/commits/Nickolay-Goppen/pinctrl-qcom-lpass-lpi-Introduce-pin_offset-callback/20250825-045348
base:   038d61fd642278bab63ee8ef722c50d10ab01e8f
patch link:    https://lore.kernel.org/r/20250824-sdm660-lpass-lpi-v1-3-003d5cc28234%40yandex.ru
patch subject: [PATCH 3/3] pinctrl: qcom: Add SDM660 LPASS LPI TLMM
config: microblaze-randconfig-r123-20250826 (https://download.01.org/0day-ci/archive/20250826/202508261333.8hcdJOVB-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 9.5.0
reproduce: (https://download.01.org/0day-ci/archive/20250826/202508261333.8hcdJOVB-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/202508261333.8hcdJOVB-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/pinctrl/qcom/pinctrl-sdm660-lpass-lpi.c:110:27: sparse: sparse: symbol 'sdm660_lpi_pinctrl_groups' was not declared. Should it be static?
>> drivers/pinctrl/qcom/pinctrl-sdm660-lpass-lpi.c:148:27: sparse: sparse: symbol 'sdm660_lpi_pinctrl_functions' was not declared. Should it be static?

vim +/sdm660_lpi_pinctrl_groups +110 drivers/pinctrl/qcom/pinctrl-sdm660-lpass-lpi.c

   109	
 > 110	const struct lpi_pingroup sdm660_lpi_pinctrl_groups[] = {
   111		LPI_PINGROUP(0, LPI_NO_SLEW, _, _, _, _),
   112		LPI_PINGROUP(1, LPI_NO_SLEW, _, _, _, _),
   113		LPI_PINGROUP(2, LPI_NO_SLEW, _, _, _, _),
   114		LPI_PINGROUP(3, LPI_NO_SLEW, _, _, _, _),
   115		LPI_PINGROUP(4, LPI_NO_SLEW, _, _, _, _),
   116		LPI_PINGROUP(5, LPI_NO_SLEW, _, _, _, _),
   117		LPI_PINGROUP(6, LPI_NO_SLEW, _, _, _, _),
   118		LPI_PINGROUP(7, LPI_NO_SLEW, _, _, _, _),
   119		LPI_PINGROUP(8, LPI_NO_SLEW, _, _, _, _),
   120		LPI_PINGROUP(9, LPI_NO_SLEW, _, _, _, _),
   121		LPI_PINGROUP(10, LPI_NO_SLEW, _, _, _, _),
   122		LPI_PINGROUP(11, LPI_NO_SLEW, _, _, _, _),
   123		LPI_PINGROUP(12, LPI_NO_SLEW, _, _, _, _),
   124		LPI_PINGROUP(13, LPI_NO_SLEW, _, _, _, _),
   125		LPI_PINGROUP(14, LPI_NO_SLEW, _, _, _, _),
   126		LPI_PINGROUP(15, LPI_NO_SLEW, _, _, _, _),
   127		LPI_PINGROUP(16, LPI_NO_SLEW, _, _, _, _),
   128		LPI_PINGROUP(17, LPI_NO_SLEW, _, _, _, _),
   129	
   130		/* The function names of the PDM GPIOs are derived from SDM670 */
   131		LPI_PINGROUP(18, LPI_NO_SLEW, pdm_clk, mclk0, _, _),
   132		LPI_PINGROUP(19, LPI_NO_SLEW, pdm_sync, _, _, _),
   133		LPI_PINGROUP(20, LPI_NO_SLEW, pdm_2_gpios, _, _, _),
   134		LPI_PINGROUP(21, LPI_NO_SLEW, pdm_rx, _, _, _),
   135		LPI_PINGROUP(22, LPI_NO_SLEW, comp_rx, _, _, _),
   136		LPI_PINGROUP(23, LPI_NO_SLEW, pdm_rx, _, _, _),
   137		LPI_PINGROUP(24, LPI_NO_SLEW, comp_rx, _, _, _),
   138		LPI_PINGROUP(25, LPI_NO_SLEW, pdm_rx, _, _, _),
   139		LPI_PINGROUP(26, LPI_NO_SLEW, dmic12, _, _, _),
   140		LPI_PINGROUP(27, LPI_NO_SLEW, dmic34, _, _, _),
   141		LPI_PINGROUP(28, LPI_NO_SLEW, dmic12, _, _, _),
   142		LPI_PINGROUP(29, LPI_NO_SLEW, dmic34, _, _, _),
   143	
   144		LPI_PINGROUP(30, LPI_NO_SLEW, _, _, _, _),
   145		LPI_PINGROUP(31, LPI_NO_SLEW, _, _, _, _),
   146	};
   147	
 > 148	const struct lpi_function sdm660_lpi_pinctrl_functions[] = {
   149		LPI_FUNCTION(comp_rx),
   150		LPI_FUNCTION(dmic12),
   151		LPI_FUNCTION(dmic34),
   152		LPI_FUNCTION(mclk0),
   153		LPI_FUNCTION(pdm_2_gpios),
   154		LPI_FUNCTION(pdm_clk),
   155		LPI_FUNCTION(pdm_rx),
   156		LPI_FUNCTION(pdm_sync),
   157	};
   158	

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

      parent reply	other threads:[~2025-08-26  6:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-24 20:42 [PATCH 0/3] Add SDM660 LPASS LPI TLMM Nickolay Goppen
2025-08-24 20:42 ` [PATCH 1/3] pinctrl: qcom: lpass-lpi: Introduce pin_offset callback Nickolay Goppen
2025-08-24 23:24   ` kernel test robot
2025-08-25  9:37   ` Dmitry Baryshkov
2025-08-24 20:42 ` [PATCH 2/3] dt-bindings: pinctrl: qcom: Add SDM660 LPI pinctrl Nickolay Goppen
2025-08-24 20:42 ` [PATCH 3/3] pinctrl: qcom: Add SDM660 LPASS LPI TLMM Nickolay Goppen
2025-08-25  9:48   ` Dmitry Baryshkov
2025-08-26  6:01   ` kernel test robot [this message]

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=202508261333.8hcdJOVB-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailingradian@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=setotau@yandex.ru \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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).