From: kernel test robot <lkp@intel.com>
To: Jianhua Lin <jianhua.lin@mediatek.com>,
daniel.almeida@collabora.com, mchehab@kernel.org,
angelogioacchino.delregno@collabora.com
Cc: oe-kbuild-all@lists.linux.dev, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
Jianhua Lin <jianhua.lin@mediatek.com>
Subject: Re: [PATCH v5 1/1] media: mediatek: jpeg: support 34bits
Date: Thu, 8 Aug 2024 08:42:29 +0800 [thread overview]
Message-ID: <202408080826.MtdkQQdh-lkp@intel.com> (raw)
In-Reply-To: <20240807130835.26739-1-jianhua.lin@mediatek.com>
Hi Jianhua,
kernel test robot noticed the following build errors:
[auto build test ERROR on media-tree/master]
[also build test ERROR on linuxtv-media-stage/master sailus-media-tree/master linus/master v6.11-rc2 next-20240807]
[cannot apply to sailus-media-tree/streams]
[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/Jianhua-Lin/media-mediatek-jpeg-support-34bits/20240807-211309
base: git://linuxtv.org/media_tree.git master
patch link: https://lore.kernel.org/r/20240807130835.26739-1-jianhua.lin%40mediatek.com
patch subject: [PATCH v5 1/1] media: mediatek: jpeg: support 34bits
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20240808/202408080826.MtdkQQdh-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240808/202408080826.MtdkQQdh-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/202408080826.MtdkQQdh-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/media/platform/mediatek/jpeg/mtk_jpeg_enc_hw.c: In function 'mtk_jpeg_set_enc_src':
>> drivers/media/platform/mediatek/jpeg/mtk_jpeg_enc_hw.c:104:39: error: implicit declaration of function 'FIELD_PREP' [-Werror=implicit-function-declaration]
104 | val = FIELD_PREP(MTK_JPEG_ADDR_MASK, upper);
| ^~~~~~~~~~
cc1: some warnings being treated as errors
--
drivers/media/platform/mediatek/jpeg/mtk_jpeg_dec_hw.c: In function 'mtk_jpeg_dec_set_dst_bank0':
>> drivers/media/platform/mediatek/jpeg/mtk_jpeg_dec_hw.c:294:23: error: implicit declaration of function 'FIELD_PREP' [-Werror=implicit-function-declaration]
294 | val = FIELD_PREP(MTK_JPEG_ADDR_MASK, upper_32_bits(addr_y));
| ^~~~~~~~~~
cc1: some warnings being treated as errors
vim +/FIELD_PREP +104 drivers/media/platform/mediatek/jpeg/mtk_jpeg_enc_hw.c
87
88 void mtk_jpeg_set_enc_src(struct mtk_jpeg_ctx *ctx, void __iomem *base,
89 struct vb2_buffer *src_buf)
90 {
91 int i;
92 dma_addr_t dma_addr;
93 u32 val;
94 u32 upper;
95 bool support_34bit = ctx->jpeg->variant->support_34bit;
96
97 for (i = 0; i < src_buf->num_planes; i++) {
98 dma_addr = vb2_dma_contig_plane_dma_addr(src_buf, i) +
99 src_buf->planes[i].data_offset;
100 if (!i) {
101 writel(dma_addr, base + JPEG_ENC_SRC_LUMA_ADDR);
102 if (support_34bit) {
103 upper = upper_32_bits(dma_addr);
> 104 val = FIELD_PREP(MTK_JPEG_ADDR_MASK, upper);
105 writel(val, base + JPEG_ENC_SRC_LUMA_ADDR_EXT);
106 }
107 } else {
108 writel(dma_addr, base + JPEG_ENC_SRC_CHROMA_ADDR);
109 if (support_34bit) {
110 upper = upper_32_bits(dma_addr);
111 val = FIELD_PREP(MTK_JPEG_ADDR_MASK, upper);
112 writel(val, base + JPEG_ENC_SRC_CHRO_ADDR_EXT);
113 }
114 }
115 }
116 }
117 EXPORT_SYMBOL_GPL(mtk_jpeg_set_enc_src);
118
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-08-08 0:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 13:08 Jianhua Lin
2024-08-07 22:18 ` kernel test robot
2024-08-08 0:42 ` 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=202408080826.MtdkQQdh-lkp@intel.com \
--to=lkp@intel.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel.almeida@collabora.com \
--cc=jianhua.lin@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mchehab@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®