From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12 0/2] sound/soc/codecs/ak4458.c:631:13: warning: 'ak4458_reset' defined but not used
Date: Tue, 17 Feb 2026 05:31:38 +0800 [thread overview]
Message-ID: <202602170556.dxLrrnSd-lkp@intel.com> (raw)
Hi Shengjiu,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android16-6.12
head: f2758f0da7bc5628c5fc4d3822976b07b3649b24
commit: 47c4976513f1dd9630c97b5d13a579ab68f908d1 [0/2] ASoC: ak4458: remove the reset operation in probe and remove
config: x86_64-randconfig-003-20260217 (https://download.01.org/0day-ci/archive/20260217/202602170556.dxLrrnSd-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260217/202602170556.dxLrrnSd-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/202602170556.dxLrrnSd-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> sound/soc/codecs/ak4458.c:631:13: warning: 'ak4458_reset' defined but not used [-Wunused-function]
631 | static void ak4458_reset(struct ak4458_priv *ak4458, bool active)
| ^~~~~~~~~~~~
vim +/ak4458_reset +631 sound/soc/codecs/ak4458.c
ee6047b8288814 Daniel Baluta 2019-01-04 630
e953daeb68b1ab Eliot Blennerhassett 2021-01-22 @631 static void ak4458_reset(struct ak4458_priv *ak4458, bool active)
08660086eff9e9 Cosmin-Gabriel Samoila 2018-02-14 632 {
1e0dff741b0a8a Shengjiu Wang 2024-07-03 633 if (!IS_ERR_OR_NULL(ak4458->reset)) {
8a0de73cf9dc04 Viorel Suman 2022-10-13 634 if (active)
8a0de73cf9dc04 Viorel Suman 2022-10-13 635 reset_control_assert(ak4458->reset);
8a0de73cf9dc04 Viorel Suman 2022-10-13 636 else
8a0de73cf9dc04 Viorel Suman 2022-10-13 637 reset_control_deassert(ak4458->reset);
8a0de73cf9dc04 Viorel Suman 2022-10-13 638 usleep_range(1000, 2000);
08660086eff9e9 Cosmin-Gabriel Samoila 2018-02-14 639 }
08660086eff9e9 Cosmin-Gabriel Samoila 2018-02-14 640 }
08660086eff9e9 Cosmin-Gabriel Samoila 2018-02-14 641
:::::: The code at line 631 was first introduced by commit
:::::: e953daeb68b1abd8a7d44902786349fdeef5c297 ASoC: ak4458: correct reset polarity
:::::: TO: Eliot Blennerhassett <eliot@blennerhassett.gen.nz>
:::::: CC: Mark Brown <broonie@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-16 21:32 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=202602170556.dxLrrnSd-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.