From: kernel test robot <lkp@intel.com>
To: Manikandan Muralidharan <manikandan.m@microchip.com>,
sam@ravnborg.org, bbrezillon@kernel.org, airlied@gmail.com,
daniel@ffwll.ch, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, lee@kernel.org,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Balakrishnan.S@microchip.com,
Nayabbasha.Sayed@microchip.com,
Balamanikandan.Gunasundar@microchip.com,
Manikandan Muralidharan <manikandan.m@microchip.com>,
Varshini.Rajendran@microchip.com, Dharma.B@microchip.com,
Durai Manickam KR <durai.manickamkr@microchip.com>,
Hari.PrasathGE@microchip.com
Subject: Re: [PATCH v3 5/8] drm: atmel_hlcdc: Add support for XLCDC in atmel LCD driver
Date: Thu, 17 Aug 2023 23:13:51 +0800 [thread overview]
Message-ID: <202308172209.DZ2HgtVa-lkp@intel.com> (raw)
In-Reply-To: <20230817091250.225512-6-manikandan.m@microchip.com>
Hi Manikandan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on lee-mfd/for-mfd-next lee-leds/for-leds-next lee-mfd/for-mfd-fixes linus/master v6.5-rc6 next-20230817]
[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/Manikandan-Muralidharan/mfd-atmel-hlcdc-Add-compatible-for-sam9x75-XLCD-controller/20230817-172003
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20230817091250.225512-6-manikandan.m%40microchip.com
patch subject: [PATCH v3 5/8] drm: atmel_hlcdc: Add support for XLCDC in atmel LCD driver
config: arm-randconfig-r033-20230817 (https://download.01.org/0day-ci/archive/20230817/202308172209.DZ2HgtVa-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230817/202308172209.DZ2HgtVa-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/202308172209.DZ2HgtVa-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_plane.c:1013:6: warning: no previous prototype for 'hlcdc_irq_dbg' [-Wmissing-prototypes]
1013 | void hlcdc_irq_dbg(struct atmel_hlcdc_plane *plane,
| ^~~~~~~~~~~~~
>> drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_plane.c:1029:6: warning: no previous prototype for 'xlcdc_irq_dbg' [-Wmissing-prototypes]
1029 | void xlcdc_irq_dbg(struct atmel_hlcdc_plane *plane,
| ^~~~~~~~~~~~~
vim +/hlcdc_irq_dbg +1013 drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_plane.c
1012
> 1013 void hlcdc_irq_dbg(struct atmel_hlcdc_plane *plane,
1014 const struct atmel_hlcdc_layer_desc *desc)
1015 {
1016 u32 isr = atmel_hlcdc_layer_read_reg(&plane->layer, ATMEL_HLCDC_LAYER_ISR);
1017
1018 /*
1019 * There's not much we can do in case of overrun except informing
1020 * the user. However, we are in interrupt context here, hence the
1021 * use of dev_dbg().
1022 */
1023 if (isr &
1024 (ATMEL_HLCDC_LAYER_OVR_IRQ(0) | ATMEL_HLCDC_LAYER_OVR_IRQ(1) |
1025 ATMEL_HLCDC_LAYER_OVR_IRQ(2)))
1026 pr_warn("%s: overrun on plane %s\n", __func__, desc->name);
1027 }
1028
> 1029 void xlcdc_irq_dbg(struct atmel_hlcdc_plane *plane,
1030 const struct atmel_hlcdc_layer_desc *desc)
1031 {
1032 u32 isr = atmel_hlcdc_layer_read_reg(&plane->layer, ATMEL_XLCDC_LAYER_ISR);
1033
1034 /*
1035 * There's not much we can do in case of overrun except informing
1036 * the user. However, we are in interrupt context here, hence the
1037 * use of dev_dbg().
1038 */
1039 if (isr &
1040 (ATMEL_XLCDC_LAYER_OVR_IRQ(0) | ATMEL_XLCDC_LAYER_OVR_IRQ(1) |
1041 ATMEL_XLCDC_LAYER_OVR_IRQ(2)))
1042 pr_warn("%s: overrun on plane %s\n", __func__, desc->name);
1043 }
1044
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-17 15:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 9:12 [PATCH v3 0/8] Add support for XLCDC to sam9x7 SoC family Manikandan Muralidharan
2023-08-17 9:12 ` [PATCH v3 1/8] mfd: atmel-hlcdc: Add compatible for sam9x75 XLCD controller Manikandan Muralidharan
2023-08-17 9:12 ` [PATCH v3 2/8] drm: atmel-hlcdc: add flag to differentiate XLCDC and HLCDC IP Manikandan Muralidharan
2023-08-17 9:12 ` [PATCH v3 3/8] drm: atmel-hlcdc: add LCD controller layer definition for sam9x75 Manikandan Muralidharan
2023-08-17 9:12 ` [PATCH v3 4/8] drm: atmel-hlcdc: Define SAM9X7 SoC XLCDC specific registers Manikandan Muralidharan
2023-08-17 9:12 ` [PATCH v3 5/8] drm: atmel_hlcdc: Add support for XLCDC in atmel LCD driver Manikandan Muralidharan
2023-08-17 15:13 ` kernel test robot [this message]
2023-08-17 15:24 ` kernel test robot
2023-08-17 9:12 ` [PATCH v3 6/8] drm: atmel-hlcdc: add DPI mode support for XLCDC Manikandan Muralidharan
2023-08-17 9:12 ` [PATCH v3 7/8] drm: atmel-hlcdc: add vertical and horizontal scaling " Manikandan Muralidharan
2023-08-17 9:12 ` [PATCH v3 8/8] drm: atmel-hlcdc: add support for DSI output formats Manikandan Muralidharan
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=202308172209.DZ2HgtVa-lkp@intel.com \
--to=lkp@intel.com \
--cc=Balakrishnan.S@microchip.com \
--cc=Balamanikandan.Gunasundar@microchip.com \
--cc=Dharma.B@microchip.com \
--cc=Hari.PrasathGE@microchip.com \
--cc=Nayabbasha.Sayed@microchip.com \
--cc=Varshini.Rajendran@microchip.com \
--cc=airlied@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=bbrezillon@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=durai.manickamkr@microchip.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manikandan.m@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sam@ravnborg.org \
/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).