From: kernel test robot <lkp@intel.com>
To: Alex Lanzano <lanzano.alex@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Mehdi Djait <mehdi.djait@bootlin.com>
Cc: oe-kbuild-all@lists.linux.dev, christophe.jaillet@wanadoo.fr,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] drm/tiny: Add driver for Sharp Memory LCD
Date: Tue, 3 Sep 2024 23:46:41 +0800 [thread overview]
Message-ID: <202409032359.jHPOaDBF-lkp@intel.com> (raw)
In-Reply-To: <20240901201118.3179206-3-lanzano.alex@gmail.com>
Hi Alex,
kernel test robot noticed the following build errors:
[auto build test ERROR on robh/for-next]
[also build test ERROR on drm-misc/drm-misc-next linus/master v6.11-rc6 next-20240903]
[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/Alex-Lanzano/dt-bindings-display-Add-Sharp-Memory-LCD-bindings/20240902-041405
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20240901201118.3179206-3-lanzano.alex%40gmail.com
patch subject: [PATCH v5 2/2] drm/tiny: Add driver for Sharp Memory LCD
config: x86_64-randconfig-102-20240903 (https://download.01.org/0day-ci/archive/20240903/202409032359.jHPOaDBF-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240903/202409032359.jHPOaDBF-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/202409032359.jHPOaDBF-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/tiny/sharp-memory.c: In function 'sharp_memory_crtc_enable':
>> drivers/gpu/drm/tiny/sharp-memory.c:344:17: error: implicit declaration of function 'pwm_apply_state'; did you mean 'pwm_apply_args'? [-Werror=implicit-function-declaration]
344 | pwm_apply_state(smd->pwm_vcom_signal, &pwm_state);
| ^~~~~~~~~~~~~~~
| pwm_apply_args
cc1: some warnings being treated as errors
vim +344 drivers/gpu/drm/tiny/sharp-memory.c
318
319 static void sharp_memory_crtc_enable(struct drm_crtc *crtc,
320 struct drm_atomic_state *state)
321 {
322 struct pwm_state pwm_state;
323 struct sharp_memory_device *smd = drm_to_sharp_memory_device(crtc->dev);
324
325 sharp_memory_clear_display(smd);
326
327 if (smd->enable_gpio)
328 gpiod_set_value(smd->enable_gpio, 1);
329
330 switch (smd->vcom_mode) {
331 case SHARP_MEMORY_SOFTWARE_VCOM:
332 smd->sw_vcom_signal = kthread_run(sharp_memory_sw_vcom_signal_thread,
333 smd, "sw_vcom_signal");
334 break;
335
336 case SHARP_MEMORY_EXTERNAL_VCOM:
337 break;
338
339 case SHARP_MEMORY_PWM_VCOM:
340 pwm_get_state(smd->pwm_vcom_signal, &pwm_state);
341 pwm_state.period = 1000000000;
342 pwm_state.duty_cycle = 100000000;
343 pwm_state.enabled = true;
> 344 pwm_apply_state(smd->pwm_vcom_signal, &pwm_state);
345 break;
346 }
347 }
348
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-09-03 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 20:10 [PATCH v5 0/2] Add driver for Sharp Memory LCD Alex Lanzano
2024-09-01 20:10 ` [PATCH v5 1/2] dt-bindings: display: Add Sharp Memory LCD bindings Alex Lanzano
2024-09-01 20:10 ` [PATCH v5 2/2] drm/tiny: Add driver for Sharp Memory LCD Alex Lanzano
2024-09-03 15:46 ` 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=202409032359.jHPOaDBF-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk@kernel.org \
--cc=lanzano.alex@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mehdi.djait@bootlin.com \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=tzimmermann@suse.de \
/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