From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-6.6 133/133] drivers/media/platform/mediatek/vcodec/decoder/mtk_vcodec_dec_pm.c:233:6: warning: no previous prototype for 'mtk_vcodec_dec_enable_dvfs'
Date: Tue, 27 May 2025 11:31:19 +0800 [thread overview]
Message-ID: <202505271126.2PctcHm8-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-6.6
head: 00e2b7e08c550ff321daba7b9956795d281bdd98
commit: 622d2b38b47c46cd9c5d33e14c31ea3e36e996ed [133/133] CHROMIUM: mediatek: decoder: calling pm interface change freq and vol
config: arm64-randconfig-001-20250527 (https://download.01.org/0day-ci/archive/20250527/202505271126.2PctcHm8-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250527/202505271126.2PctcHm8-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/202505271126.2PctcHm8-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/media/platform/mediatek/vcodec/decoder/mtk_vcodec_dec_pm.c:233:6: warning: no previous prototype for 'mtk_vcodec_dec_enable_dvfs' [-Wmissing-prototypes]
void mtk_vcodec_dec_enable_dvfs(struct mtk_vcodec_dec_ctx *ctx, int hw_idx)
^~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/media/platform/mediatek/vcodec/decoder/mtk_vcodec_dec_pm.c:239:6: warning: no previous prototype for 'mtk_vcodec_dec_disable_dvfs' [-Wmissing-prototypes]
void mtk_vcodec_dec_disable_dvfs(struct mtk_vcodec_dec_ctx *ctx, int hw_idx)
^~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/mtk_vcodec_dec_enable_dvfs +233 drivers/media/platform/mediatek/vcodec/decoder/mtk_vcodec_dec_pm.c
232
> 233 void mtk_vcodec_dec_enable_dvfs(struct mtk_vcodec_dec_ctx *ctx, int hw_idx)
234 {
235 mtk_vdec_dvfs_begin_inst(ctx, hw_idx);
236 vcodec_pmqos_helper_update(ctx, hw_idx);
237 }
238
> 239 void mtk_vcodec_dec_disable_dvfs(struct mtk_vcodec_dec_ctx *ctx, int hw_idx)
240 {
241 mtk_vdec_dvfs_end_inst(ctx, hw_idx);
242 vcodec_pmqos_helper_update(ctx, hw_idx);
243 }
244
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-27 3: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=202505271126.2PctcHm8-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.