All of lore.kernel.org
 help / color / mirror / Atom feed
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.3.y 53/59] drivers/gpu/drm/panel/panel-sitronix-st7701.c:546:13: warning: 'odroid_vu5s_gip_sequence' defined but not used
Date: Tue, 20 Oct 2026 23:39:16 +0200	[thread overview]
Message-ID: <202610202345.VlE9WaUV-lkp@intel.com> (raw)

tree:   https://github.com/tobetter/linux odroid-7.3.y
head:   c30cb664bead7336f81c7a7c7c82709ee1f803cf
commit: 9668f9aef9bdabc5f71819d776f07c1d904abdee [53/59] ODROID-M1/M1S: gpu/drm: add ODROID-Vu5S panel to ST7701 driver
config: powerpc-randconfig-r2202-20261020 (https://download.01.org/0day-ci/archive/20261020/202610202345.VlE9WaUV-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 12.5.0
smatch: v0.5.0-9187-g5189e3fb
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261020/202610202345.VlE9WaUV-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/202610202345.VlE9WaUV-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/panel/panel-sitronix-st7701.c:546:13: warning: 'odroid_vu5s_gip_sequence' defined but not used [-Wunused-function]
     546 | static void odroid_vu5s_gip_sequence(struct st7701 *st7701)
         |             ^~~~~~~~~~~~~~~~~~~~~~~~


vim +/odroid_vu5s_gip_sequence +546 drivers/gpu/drm/panel/panel-sitronix-st7701.c

   545	
 > 546	static void odroid_vu5s_gip_sequence(struct st7701 *st7701)
   547	{
   548		ST7701_WRITE(st7701, 0xE0, 0x00, 0x00, 0x02);
   549		ST7701_WRITE(st7701, 0xE1, 0x08, 0x00, 0x0A, 0x00, 0x07,
   550				0x00, 0x09, 0x00, 0x00, 0x33, 0x33);
   551		ST7701_WRITE(st7701, 0xE2, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
   552				0x00, 0x00, 0x00, 0x00, 0x00);
   553		ST7701_WRITE(st7701, 0xE3, 0x00, 0x00, 0x33, 0x33);
   554		ST7701_WRITE(st7701, 0xE4, 0x44, 0x44);
   555		ST7701_WRITE(st7701, 0xE5, 0x0E, 0x60, 0xA0, 0xA0, 0x10, 0x60, 0xA0, 0xA0,
   556				0x0A, 0x60, 0xA0, 0xA0, 0x0C, 0x60, 0xA0, 0xA0);
   557		ST7701_WRITE(st7701, 0xE6, 0x00, 0x00, 0x33, 0x33);
   558		ST7701_WRITE(st7701, 0xE7, 0x44, 0x44);
   559		ST7701_WRITE(st7701, 0xE8, 0x0D, 0x60, 0xA0, 0xA0, 0x0F, 0x60, 0xA0, 0xA0,
   560				0x09, 0x60, 0xA0, 0xA0, 0x0B, 0x60, 0xA0, 0xA0);
   561		ST7701_WRITE(st7701, 0xEB, 0x02, 0x01, 0xE4, 0xE4, 0x44, 0x00, 0x40);
   562		ST7701_WRITE(st7701, 0xEC, 0x02, 0x01);
   563		ST7701_WRITE(st7701, 0xED, 0xAB, 0x89, 0x76, 0x54, 0x01, 0xFF, 0xFF, 0xFF,
   564				0xFF, 0xFF, 0xFF, 0x10, 0x45, 0x67, 0x98, 0xBA);
   565	
   566		ST7701_WRITE(st7701, 0xCC, 0x10);
   567		ST7701_WRITE(st7701, 0xB9, 0x10);
   568	
   569		ST7701_WRITE(st7701, 0x3A, 0x70);
   570		ST7701_WRITE(st7701, 0x53, 0xEC);
   571		ST7701_WRITE(st7701, 0x55, 0xB3);
   572		ST7701_WRITE(st7701, 0x5E, 0xFF);
   573	}
   574	

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

                 reply	other threads:[~2026-10-20 21:40 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=202610202345.VlE9WaUV-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.