From: kernel test robot <lkp@intel.com>
To: Dongjin Kim <tobetter@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, xiane <sangch.go@gmail.com>
Subject: [tobetter:odroid-7.1.y 64/64] drivers/gpu/drm/panel/panel-sitronix-st7701.c:545:13: warning: 'odroid_vu5s_gip_sequence' defined but not used
Date: Tue, 23 Jun 2026 08:22:03 +0800 [thread overview]
Message-ID: <202606230834.MiADlnH4-lkp@intel.com> (raw)
tree: https://github.com/tobetter/linux odroid-7.1.y
head: dbb4f6bd9fe8a1786673783249095632aff93442
commit: 6dc6d1337ee2e0b5ba85b9affd8ce10480dda8a7 [64/64] ODROID-M1/M1S: gpu/drm: add ODROID-Vu5S panel to ST7701 driver
config: nios2-allmodconfig (https://download.01.org/0day-ci/archive/20260623/202606230834.MiADlnH4-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260623/202606230834.MiADlnH4-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/202606230834.MiADlnH4-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/panel/panel-sitronix-st7701.c:545:13: warning: 'odroid_vu5s_gip_sequence' defined but not used [-Wunused-function]
545 | static void odroid_vu5s_gip_sequence(struct st7701 *st7701)
| ^~~~~~~~~~~~~~~~~~~~~~~~
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for COMMON_CLK_AXG_AUDIO
Depends on [n]: COMMON_CLK [=y] && (ARCH_MESON || COMPILE_TEST [=y]) && ARM64
Selected by [m]:
- SND_MESON_AXG_FIFO [=m] && SOUND [=m] && SND [=m] && SND_SOC [=m] && (ARCH_MESON || COMPILE_TEST [=y] && COMMON_CLK [=y])
vim +/odroid_vu5s_gip_sequence +545 drivers/gpu/drm/panel/panel-sitronix-st7701.c
544
> 545 static void odroid_vu5s_gip_sequence(struct st7701 *st7701)
546 {
547 ST7701_WRITE(st7701, 0xE0, 0x00, 0x00, 0x02);
548 ST7701_WRITE(st7701, 0xE1, 0x08, 0x00, 0x0A, 0x00, 0x07,
549 0x00, 0x09, 0x00, 0x00, 0x33, 0x33);
550 ST7701_WRITE(st7701, 0xE2, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
551 0x00, 0x00, 0x00, 0x00, 0x00);
552 ST7701_WRITE(st7701, 0xE3, 0x00, 0x00, 0x33, 0x33);
553 ST7701_WRITE(st7701, 0xE4, 0x44, 0x44);
554 ST7701_WRITE(st7701, 0xE5, 0x0E, 0x60, 0xA0, 0xA0, 0x10, 0x60, 0xA0, 0xA0,
555 0x0A, 0x60, 0xA0, 0xA0, 0x0C, 0x60, 0xA0, 0xA0);
556 ST7701_WRITE(st7701, 0xE6, 0x00, 0x00, 0x33, 0x33);
557 ST7701_WRITE(st7701, 0xE7, 0x44, 0x44);
558 ST7701_WRITE(st7701, 0xE8, 0x0D, 0x60, 0xA0, 0xA0, 0x0F, 0x60, 0xA0, 0xA0,
559 0x09, 0x60, 0xA0, 0xA0, 0x0B, 0x60, 0xA0, 0xA0);
560 ST7701_WRITE(st7701, 0xEB, 0x02, 0x01, 0xE4, 0xE4, 0x44, 0x00, 0x40);
561 ST7701_WRITE(st7701, 0xEC, 0x02, 0x01);
562 ST7701_WRITE(st7701, 0xED, 0xAB, 0x89, 0x76, 0x54, 0x01, 0xFF, 0xFF, 0xFF,
563 0xFF, 0xFF, 0xFF, 0x10, 0x45, 0x67, 0x98, 0xBA);
564
565 ST7701_WRITE(st7701, 0xCC, 0x10);
566 ST7701_WRITE(st7701, 0xB9, 0x10);
567
568 ST7701_WRITE(st7701, 0x3A, 0x70);
569 ST7701_WRITE(st7701, 0x53, 0xEC);
570 ST7701_WRITE(st7701, 0x55, 0xB3);
571 ST7701_WRITE(st7701, 0x5E, 0xFF);
572 }
573
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-06-23 0:22 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=202606230834.MiADlnH4-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sangch.go@gmail.com \
--cc=tobetter@gmail.com \
/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.