Re: [PATCH] drm/panthor: Lock XArray when getting entries for heap and VM
Hi Liviu,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on linus/master v6.12-rc6 next-20241106]
[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/Liviu-Dudau/drm-panthor-Lock-XArray-when-getting-entries-for-heap-and-VM/20241106-200841
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20241106120748.290697-1-liviu.dudau%40arm.com
patch subject: [PATCH] drm/panthor: Lock XArray when getting entries for heap
and VM
config: x86_64-buildonly-randconfig-002-20241106
(https://download.01.org/0day-ci/archive/20241107/202411070115.ypuba5qx-...@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project
ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241107/202411070115.ypuba5qx-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202411070115.ypuba5qx-...@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/panthor/panthor_heap.c:9:
In file included from drivers/gpu/drm/panthor/panthor_device.h:10:
In file included from include/linux/io-pgtable.h:6:
In file included from include/linux/iommu.h:10:
In file included from include/linux/scatterlist.h:8:
In file included from include/linux/mm.h:2213:
include/linux/vmstat.h:504:43: error: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Werror,-Wenum-enum-conversion]
504 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
505 |item];
|
include/linux/vmstat.h:511:43: error: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Werror,-Wenum-enum-conversion]
511 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
512 |NR_VM_NUMA_EVENT_ITEMS +
|~~
include/linux/vmstat.h:518:36: error: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Werror,-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
include/linux/vmstat.h:524:43: error: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Werror,-Wenum-enum-conversion]
524 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
525 |NR_VM_NUMA_EVENT_ITEMS +
|~~
>> drivers/gpu/drm/panthor/panthor_heap.c:354:57: error: declaration of 'struct
>> pathor_heap_pool' will not be visible outside of this function
>> [-Werror,-Wvisibility]
354 | static struct panthor_heap *panthor_heap_from_id(struct
pathor_heap_pool *pool, u32 id)
| ^
drivers/gpu/drm/panthor/panthor_heap.c:358:15: error: incomplete definition
of type 'struct pathor_heap_pool'
358 | xa_lock(&pool->xa);
| ^
include/linux/xarray.h:536:34: note: expanded from macro 'xa_lock'
536 | #define xa_lock(xa) spin_lock(&(xa)->xa_lock)
| ^~
drivers/gpu/drm/panthor/panthor_heap.c:354:57: note: forward declaration of
'struct pathor_heap_pool'
354 | static struct panthor_heap *panthor_heap_from_id(struct
pathor_heap_pool *pool, u32 id)
| ^
drivers/gpu/drm/panthor/panthor_heap.c:359:22: error: incomplete definition
of type 'struct pathor_heap_pool'
359 | heap = xa_load(&pool->xa, id);
| ^
drivers/gpu/drm/panthor/panthor_heap.c:354:57: note: forward declaration of
'struct pathor_heap_pool'
354 | static struct panthor_heap *panthor_heap_from_id(struct
pathor_heap_pool *pool, u32 id)
|
Re: [PATCH] drm/panthor: Lock XArray when getting entries for heap and VM
Hi Liviu, kernel test robot noticed the following build errors: [auto build test ERROR on drm-misc/drm-misc-next] [also build test ERROR on linus/master v6.12-rc6 next-20241106] [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/Liviu-Dudau/drm-panthor-Lock-XArray-when-getting-entries-for-heap-and-VM/20241106-200841 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20241106120748.290697-1-liviu.dudau%40arm.com patch subject: [PATCH] drm/panthor: Lock XArray when getting entries for heap and VM config: arc-allyesconfig (https://download.01.org/0day-ci/archive/20241107/202411070140.l4jawkvx-...@intel.com/config) compiler: arceb-elf-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241107/202411070140.l4jawkvx-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202411070140.l4jawkvx-...@intel.com/ All error/warnings (new ones prefixed by >>): >> drivers/gpu/drm/panthor/panthor_heap.c:354:57: warning: 'struct >> pathor_heap_pool' declared inside parameter list will not be visible outside >> of this definition or declaration 354 | static struct panthor_heap *panthor_heap_from_id(struct pathor_heap_pool *pool, u32 id) | ^~~~ In file included from include/linux/list_lru.h:14, from include/linux/fs.h:13, from include/linux/huge_mm.h:8, from include/linux/mm.h:1120, from include/linux/scatterlist.h:8, from include/linux/iommu.h:10, from include/linux/io-pgtable.h:6, from drivers/gpu/drm/panthor/panthor_device.h:10, from drivers/gpu/drm/panthor/panthor_heap.c:9: drivers/gpu/drm/panthor/panthor_heap.c: In function 'panthor_heap_from_id': >> drivers/gpu/drm/panthor/panthor_heap.c:358:22: error: invalid use of >> undefined type 'struct pathor_heap_pool' 358 | xa_lock(&pool->xa); | ^~ include/linux/xarray.h:536:45: note: in definition of macro 'xa_lock' 536 | #define xa_lock(xa) spin_lock(&(xa)->xa_lock) | ^~ drivers/gpu/drm/panthor/panthor_heap.c:359:29: error: invalid use of undefined type 'struct pathor_heap_pool' 359 | heap = xa_load(&pool->xa, id); | ^~ drivers/gpu/drm/panthor/panthor_heap.c:360:24: error: invalid use of undefined type 'struct pathor_heap_pool' 360 | xa_unlock(&pool->va); |^~ include/linux/xarray.h:537:47: note: in definition of macro 'xa_unlock' 537 | #define xa_unlock(xa) spin_unlock(&(xa)->xa_lock) | ^~ drivers/gpu/drm/panthor/panthor_heap.c: In function 'panthor_heap_return_chunk': >> drivers/gpu/drm/panthor/panthor_heap.c:389:37: error: passing argument 1 of >> 'panthor_heap_from_id' from incompatible pointer type >> [-Werror=incompatible-pointer-types] 389 | heap = panthor_heap_from_id(pool, heap_id); | ^~~~ | | | struct panthor_heap_pool * drivers/gpu/drm/panthor/panthor_heap.c:354:75: note: expected 'struct pathor_heap_pool *' but argument is of type 'struct panthor_heap_pool *' 354 | static struct panthor_heap *panthor_heap_from_id(struct pathor_heap_pool *pool, u32 id) | ~^~~~ drivers/gpu/drm/panthor/panthor_heap.c: In function 'panthor_heap_grow': drivers/gpu/drm/panthor/panthor_heap.c:452:37: error: passing argument 1 of 'panthor_heap_from_id' from incompatible pointer type [-Werror=incompatible-pointer-types] 452 | heap = panthor_heap_from_id(pool, heap_id); | ^~~~ | | | struct panthor_heap_pool * drivers/gpu/drm/panthor/panthor_heap.c:354:75: note: expected 'struct pathor_heap_pool *' but argument is of type &#
Re: [PATCH v2 3/4] drm/mode_object: add drm_mode_object_read_refcount()
Hi Luca,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 42f7652d3eb527d03665b09edac47f85fb600924]
url:
https://github.com/intel-lab-lkp/linux/commits/Luca-Ceresoli/drm-drm_mode_object-fix-typo-in-kerneldoc/20241106-185032
base: 42f7652d3eb527d03665b09edac47f85fb600924
patch link:
https://lore.kernel.org/r/20241106-drm-small-improvements-v2-3-f6e2aef86719%40bootlin.com
patch subject: [PATCH v2 3/4] drm/mode_object: add
drm_mode_object_read_refcount()
config: arc-randconfig-002-20241106
(https://download.01.org/0day-ci/archive/20241107/202411070038.tzjzi7nc-...@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241107/202411070038.tzjzi7nc-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202411070038.tzjzi7nc-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/drm_mode_object.c:228: warning: expecting prototype for
>> drm_mode_object_get(). Prototype was for drm_mode_object_read_refcount()
>> instead
vim +228 drivers/gpu/drm/drm_mode_object.c
219
220 /**
221 * drm_mode_object_get - read the refcount for a mode object
222 * @obj: DRM mode object
223 *
224 * This function returns the current object's refcount if it is a
225 * refcounted modeset object, or 0 on any other object.
226 */
227 unsigned int drm_mode_object_read_refcount(struct drm_mode_object *obj)
> 228 {
229 unsigned int refcount = 0;
230
231 if (obj->free_cb) {
232 refcount = kref_read(&obj->refcount);
233 DRM_DEBUG("OBJ ID: %d (%d)\n", obj->id, refcount);
234 }
235
236 return refcount;
237 }
238 EXPORT_SYMBOL(drm_mode_object_read_refcount);
239
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3 2/3] iommu/io-pgtable-arm-v7s: Remove split on unmap behavior
Hi Jason,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 8e929cb546ee42c9a61d24fae60605e9e3192354]
url:
https://github.com/intel-lab-lkp/linux/commits/Jason-Gunthorpe/iommu-io-pgtable-arm-Remove-split-on-unmap-behavior/20241106-021511
base: 8e929cb546ee42c9a61d24fae60605e9e3192354
patch link:
https://lore.kernel.org/r/2-v3-b3a5b5937f56%2B7bb-arm_no_split_jgg%40nvidia.com
patch subject: [PATCH v3 2/3] iommu/io-pgtable-arm-v7s: Remove split on unmap
behavior
config: arm-randconfig-004-20241106
(https://download.01.org/0day-ci/archive/20241106/202411061634.3etgzij8-...@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project
6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241106/202411061634.3etgzij8-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202411061634.3etgzij8-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/iommu/io-pgtable-arm-v7s.c:823:18: warning: variable 'loopnr' set
>> but not used [-Wunused-but-set-variable]
823 | unsigned int i, loopnr = 0;
| ^
1 warning generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for GET_FREE_REGION
Depends on [n]: SPARSEMEM [=n]
Selected by [y]:
- RESOURCE_KUNIT_TEST [=y] && RUNTIME_TESTING_MENU [=y] && KUNIT [=y]
vim +/loopnr +823 drivers/iommu/io-pgtable-arm-v7s.c
e5fc9753b1a831 Robin Murphy2016-01-26 810
e5fc9753b1a831 Robin Murphy2016-01-26 811 static int __init
arm_v7s_do_selftests(void)
e5fc9753b1a831 Robin Murphy2016-01-26 812 {
e5fc9753b1a831 Robin Murphy2016-01-26 813 struct io_pgtable_ops
*ops;
e5fc9753b1a831 Robin Murphy2016-01-26 814 struct io_pgtable_cfg
cfg = {
e5fc9753b1a831 Robin Murphy2016-01-26 815 .tlb =
&dummy_tlb_ops,
e5fc9753b1a831 Robin Murphy2016-01-26 816 .oas = 32,
e5fc9753b1a831 Robin Murphy2016-01-26 817 .ias = 32,
4f41845b340783 Will Deacon 2019-06-25 818 .coherent_walk
= true,
4f41845b340783 Will Deacon 2019-06-25 819 .quirks =
IO_PGTABLE_QUIRK_ARM_NS,
e5fc9753b1a831 Robin Murphy2016-01-26 820 .pgsize_bitmap
= SZ_4K | SZ_64K | SZ_1M | SZ_16M,
e5fc9753b1a831 Robin Murphy2016-01-26 821 };
76b8c2705cdd26 Jason Gunthorpe 2024-11-05 822 unsigned int iova, size;
e5fc9753b1a831 Robin Murphy2016-01-26 @823 unsigned int i, loopnr
= 0;
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 4/7] dt-bindings: display: panel: Add YLM-LBV0345001H-V2 panel
Hi Hironori, kernel test robot noticed the following build warnings: [auto build test WARNING on next-20241104] [also build test WARNING on v6.12-rc6] [cannot apply to robh/for-next linus/master v6.12-rc6 v6.12-rc5 v6.12-rc4] [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/Hironori-KIKUCHI/dt-bindings-display-panel-Rename-rg35xx-plus-panel-back-to-WL-355608-A8/20241105-135601 base: next-20241104 patch link: https://lore.kernel.org/r/20241105055239.1577275-5-kikuchan98%40gmail.com patch subject: [PATCH 4/7] dt-bindings: display: panel: Add YLM-LBV0345001H-V2 panel config: csky-randconfig-051-20241106 (https://download.01.org/0day-ci/archive/20241106/202411061425.qitk3g1q-...@intel.com/config) compiler: csky-linux-gcc (GCC) 14.2.0 dtschema version: 2024.10.dev6+g12c3cd5 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241106/202411061425.qitk3g1q-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202411061425.qitk3g1q-...@intel.com/ All warnings (new ones prefixed by >>): Documentation/devicetree/bindings/net/snps,dwmac.yaml: mac-mode: missing type definition >> Warning: Duplicate compatible "anbernic,rg35xx-h-panel" found in schemas >> matching "$id": http://devicetree.org/schemas/display/panel/anbernic,wl-355608-a8.yaml# http://devicetree.org/schemas/display/panel/anbernic,ylm-lbv0345001h-v2.yaml# >> Warning: Duplicate compatible "anbernic,rg35xx-sp-panel" found in schemas >> matching "$id": http://devicetree.org/schemas/display/panel/anbernic,wl-355608-a8.yaml# http://devicetree.org/schemas/display/panel/anbernic,ylm-lbv0345001h-v2.yaml# >> Warning: Duplicate compatible "anbernic,rg35xx-plus-panel" found in schemas >> matching "$id": http://devicetree.org/schemas/display/panel/anbernic,wl-355608-a8.yaml# http://devicetree.org/schemas/display/panel/anbernic,ylm-lbv0345001h-v2.yaml# >> Warning: Duplicate compatible "anbernic,rg35xx-2024-panel" found in schemas >> matching "$id": http://devicetree.org/schemas/display/panel/anbernic,wl-355608-a8.yaml# http://devicetree.org/schemas/display/panel/anbernic,ylm-lbv0345001h-v2.yaml# -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 2/6] drm/log: Introduce a new boot logger to draw the kmsg on the screen
Hi Jocelyn, kernel test robot noticed the following build errors: [auto build test ERROR on d78f0ee0406803cda8801fd5201746ccf89e5e4a] url: https://github.com/intel-lab-lkp/linux/commits/Jocelyn-Falempe/drm-panic-Move-drawing-functions-to-drm_draw/20241105-205432 base: d78f0ee0406803cda8801fd5201746ccf89e5e4a patch link: https://lore.kernel.org/r/20241105125109.226866-3-jfalempe%40redhat.com patch subject: [PATCH v6 2/6] drm/log: Introduce a new boot logger to draw the kmsg on the screen config: hexagon-randconfig-002-20241106 (https://download.01.org/0day-ci/archive/20241106/202411060951.mk9fi0fi-...@intel.com/config) compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241106/202411060951.mk9fi0fi-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202411060951.mk9fi0fi-...@intel.com/ All errors (new ones prefixed by >>): >> ld.lld: error: undefined symbol: drm_client_setup >>> referenced by komeda_drv.c:87 (drivers/gpu/drm/arm/display/komeda/komeda_drv.c:87) >>> drivers/gpu/drm/arm/display/komeda/komeda_drv.o:(komeda_platform_probe) in archive vmlinux.a >>> referenced by komeda_drv.c:87 (drivers/gpu/drm/arm/display/komeda/komeda_drv.c:87) >>> drivers/gpu/drm/arm/display/komeda/komeda_drv.o:(komeda_platform_probe) in archive vmlinux.a >>> referenced by vkms_drv.c:230 (drivers/gpu/drm/vkms/vkms_drv.c:230) >>> drivers/gpu/drm/vkms/vkms_drv.o:(vkms_init) in archive vmlinux.a >>> referenced 23 more times -- >> ld.lld: error: undefined symbol: drm_client_setup_with_fourcc >>> referenced by arcpgu.c:399 (drivers/gpu/drm/tiny/arcpgu.c:399) >>> drivers/gpu/drm/tiny/arcpgu.o:(arcpgu_probe) in archive vmlinux.a >>> referenced by arcpgu.c:399 (drivers/gpu/drm/tiny/arcpgu.c:399) >>> drivers/gpu/drm/tiny/arcpgu.o:(arcpgu_probe) in archive vmlinux.a -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 2/6] drm/log: Introduce a new boot logger to draw the kmsg on the screen
Hi Jocelyn,
kernel test robot noticed the following build errors:
[auto build test ERROR on d78f0ee0406803cda8801fd5201746ccf89e5e4a]
url:
https://github.com/intel-lab-lkp/linux/commits/Jocelyn-Falempe/drm-panic-Move-drawing-functions-to-drm_draw/20241105-205432
base: d78f0ee0406803cda8801fd5201746ccf89e5e4a
patch link:
https://lore.kernel.org/r/20241105125109.226866-3-jfalempe%40redhat.com
patch subject: [PATCH v6 2/6] drm/log: Introduce a new boot logger to draw the
kmsg on the screen
config: s390-randconfig-001-20241106
(https://download.01.org/0day-ci/archive/20241106/202411060804.hiqa1esz-...@intel.com/config)
compiler: s390-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241106/202411060804.hiqa1esz-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202411060804.hiqa1esz-...@intel.com/
All errors (new ones prefixed by >>):
s390-linux-ld: drivers/gpu/drm/arm/display/komeda/komeda_drv.o: in function
`komeda_platform_probe':
>> drivers/gpu/drm/arm/display/komeda/komeda_drv.c:87:(.text+0x18e): undefined
>> reference to `drm_client_setup'
s390-linux-ld: drivers/gpu/drm/radeon/radeon_drv.o: in function
`radeon_pci_probe':
>> drivers/gpu/drm/radeon/radeon_drv.c:336:(.text+0x594): undefined reference
>> to `drm_client_setup'
s390-linux-ld: drivers/gpu/drm/vkms/vkms_drv.o: in function `vkms_create':
>> drivers/gpu/drm/vkms/vkms_drv.c:230:(.text.unlikely+0x1b4): undefined
>> reference to `drm_client_setup'
s390-linux-ld: drivers/gpu/drm/nouveau/nouveau_drm.o: in function
`nouveau_drm_probe':
>> drivers/gpu/drm/nouveau/nouveau_drm.c:882:(.text+0x2c26): undefined
>> reference to `drm_client_setup'
s390-linux-ld: drivers/gpu/drm/ast/ast_drv.o: in function `ast_pci_probe':
>> drivers/gpu/drm/ast/ast_drv.c:365:(.text+0x916): undefined reference to
>> `drm_client_setup'
s390-linux-ld:
drivers/gpu/drm/qxl/qxl_drv.o:drivers/gpu/drm/qxl/qxl_drv.c:122: more undefined
references to `drm_client_setup' follow
vim +87 drivers/gpu/drm/arm/display/komeda/komeda_drv.c
ce3d99c8349584 Douglas Anderson 2023-09-01 55
4cfe5cc02e3f62 Faiz Abbas 2023-07-12 56 static
int komeda_platform_probe(struct platform_device *pdev)
26bd43a7599639 james qian wang (Arm Technology China 2019-01-03 57) {
4cfe5cc02e3f62 Faiz Abbas 2023-07-12 58 struct
device *dev = &pdev->dev;
26bd43a7599639 james qian wang (Arm Technology China 2019-01-03 59) struct
komeda_drv *mdrv;
26bd43a7599639 james qian wang (Arm Technology China 2019-01-03 60) int err;
26bd43a7599639 james qian wang (Arm Technology China 2019-01-03 61)
a918dcfecc36f8 Amjad Ouled-Ameur 2024-02-19 62 err =
dma_set_mask_and_coherent(dev, DMA_BIT_MASK(40));
a918dcfecc36f8 Amjad Ouled-Ameur 2024-02-19 63 if (err)
a918dcfecc36f8 Amjad Ouled-Ameur 2024-02-19 64
return dev_err_probe(dev, err, "DMA mask error\n");
a918dcfecc36f8 Amjad Ouled-Ameur 2024-02-19 65
26bd43a7599639 james qian wang (Arm Technology China 2019-01-03 66) mdrv =
devm_kzalloc(dev, sizeof(*mdrv), GFP_KERNEL);
26bd43a7599639 james qian wang (Arm Technology China 2019-01-03 67) if
(!mdrv)
26bd43a7599639 james qian wang (Arm Technology China 2019-01-03 68)
return -ENOMEM;
26bd43a7599639 james qian wang (Arm Technology China 2019-01-03 69)
26bd43a7599639 james qian wang (Arm Technology China 2019-01-03 70)
mdrv->mdev = komeda_dev_create(dev);
26bd43a7599639 james qian wang (Arm Technology China 2019-01-03 71) if
(IS_ERR(mdrv->mdev)) {
26bd43a7599639 james qian wang (Arm Technology China 2019-01-03 72)
err = PTR_ERR(mdrv->mdev);
26bd43a7599639 james qian wang (Arm Technology China 2019-01-03 73)
goto free_mdrv;
26bd43a7599639 james qian wang (Arm Technology China 2019-01-03 74) }
26bd43a7599639 james qian wang (Arm Technology China 2019-01-03 75)
efb46508851874 james qian wang (Arm Technology China 2019-12-12 76)
pm_runtime_enable(dev);
efb46508851874 james qian wang (Arm Technology China 2019-12-12 77) if
(!pm_runtime_enabled(dev))
efb46508851874 james qian wang (Arm Technology China 2019-12-12 78)
komeda_dev_resume(mdrv->mdev);
efb46508851874 james qian wang (Arm Technology China 2019-12-12 79)
61f1c4a8ab7575 james qian wang (Arm Technology China 2019-01-03 80)
mdrv->kms = komeda_kms_attach(mdrv->mdev);
61f1c4a8ab7575 james qian wang (Arm Technology China 2019-01-03 81) if
(IS
Re: [PATCH] drm/etnaviv: add optional reset support
Hi LECOINTRE,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm/drm-next]
[also build test ERROR on drm-exynos/exynos-drm-next drm-misc/drm-misc-next
linus/master drm-intel/for-linux-next drm-intel/for-linux-next-fixes
drm-tip/drm-tip v6.12-rc6]
[cannot apply to next-20241105]
[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/LECOINTRE-Philippe/drm-etnaviv-add-optional-reset-support/20241105-224118
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/0825fa6ad3954cda970b42c25b45fb0d%40thalesgroup.com
patch subject: [PATCH] drm/etnaviv: add optional reset support
config: i386-buildonly-randconfig-003-20241106
(https://download.01.org/0day-ci/archive/20241106/202411060610.iiidhxhp-...@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/20241106/202411060610.iiidhxhp-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202411060610.iiidhxhp-...@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/etnaviv/etnaviv_gpu.c: In function
'etnaviv_gpu_platform_probe':
>> drivers/gpu/drm/etnaviv/etnaviv_gpu.c:1900:9: error: implicit declaration of
>> function 'irq_set_status_flags' [-Werror=implicit-function-declaration]
1900 | irq_set_status_flags(gpu->irq, IRQ_NOAUTOEN);
| ^~~~
>> drivers/gpu/drm/etnaviv/etnaviv_gpu.c:1900:40: error: 'IRQ_NOAUTOEN'
>> undeclared (first use in this function); did you mean 'IRQF_NO_AUTOEN'?
1900 | irq_set_status_flags(gpu->irq, IRQ_NOAUTOEN);
|^~~~
|IRQF_NO_AUTOEN
drivers/gpu/drm/etnaviv/etnaviv_gpu.c:1900:40: note: each undeclared
identifier is reported only once for each function it appears in
cc1: all warnings being treated as errors
vim +/irq_set_status_flags +1900 drivers/gpu/drm/etnaviv/etnaviv_gpu.c
1874
1875 static int etnaviv_gpu_platform_probe(struct platform_device *pdev)
1876 {
1877 struct device *dev = &pdev->dev;
1878 struct etnaviv_gpu *gpu;
1879 int err;
1880
1881 gpu = devm_kzalloc(dev, sizeof(*gpu), GFP_KERNEL);
1882 if (!gpu)
1883 return -ENOMEM;
1884
1885 gpu->dev = &pdev->dev;
1886 mutex_init(&gpu->lock);
1887 mutex_init(&gpu->sched_lock);
1888
1889 /* Map registers: */
1890 gpu->mmio = devm_platform_ioremap_resource(pdev, 0);
1891 if (IS_ERR(gpu->mmio))
1892 return PTR_ERR(gpu->mmio);
1893
1894 /* Get Interrupt: */
1895 gpu->irq = platform_get_irq(pdev, 0);
1896 if (gpu->irq < 0)
1897 return gpu->irq;
1898
1899 /* Avoid enabling the interrupt until everything is ready */
> 1900 irq_set_status_flags(gpu->irq, IRQ_NOAUTOEN);
1901
1902 err = devm_request_irq(&pdev->dev, gpu->irq, irq_handler, 0,
1903 dev_name(gpu->dev), gpu);
1904 if (err) {
1905 dev_err(dev, "failed to request IRQ%u: %d\n", gpu->irq,
err);
1906 return err;
1907 }
1908
1909 /* Get Reset: */
1910 gpu->rst = devm_reset_control_get_optional(&pdev->dev, NULL);
1911 if (IS_ERR(gpu->rst))
1912 return dev_err_probe(dev, PTR_ERR(gpu->rst),
1913 "failed to get reset\n");
1914
1915 /* Get Clocks: */
1916 gpu->clk_reg = devm_clk_get_optional(&pdev->dev, "reg");
1917 DBG("clk_reg: %p", gpu->clk_reg);
1918 if (IS_ERR(gpu->clk_reg))
1919 return PTR_ERR(gpu->clk_reg);
1920
1921 gpu->clk_bus = devm_clk_get_optional(&pdev->dev, "bus");
1922 DBG("clk_bus: %p", gpu->clk_bus);
1923 if (IS_ERR(gpu->clk_bus))
1924 return PTR_ERR(gpu->clk_bus);
1925
1926 gpu->clk_core = devm_clk_get(&pdev->dev, "core");
1927 DBG("clk_core: %p", gpu->clk_core);
1928 if (
Re: [PATCH] drm/etnaviv: add optional reset support
Hi LECOINTRE,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm/drm-next]
[also build test ERROR on drm-exynos/exynos-drm-next drm-misc/drm-misc-next
linus/master drm-intel/for-linux-next drm-intel/for-linux-next-fixes
drm-tip/drm-tip v6.12-rc6]
[cannot apply to next-20241105]
[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/LECOINTRE-Philippe/drm-etnaviv-add-optional-reset-support/20241105-224118
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/0825fa6ad3954cda970b42c25b45fb0d%40thalesgroup.com
patch subject: [PATCH] drm/etnaviv: add optional reset support
config: i386-buildonly-randconfig-004-20241106
(https://download.01.org/0day-ci/archive/20241106/202411060619.p5ny0vzy-...@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project
ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241106/202411060619.p5ny0vzy-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202411060619.p5ny0vzy-...@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/etnaviv/etnaviv_gpu.c:11:
In file included from include/linux/dma-mapping.h:11:
In file included from include/linux/scatterlist.h:8:
In file included from include/linux/mm.h:2213:
include/linux/vmstat.h:518:36: warning: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
>> drivers/gpu/drm/etnaviv/etnaviv_gpu.c:1900:2: error: call to undeclared
>> function 'irq_set_status_flags'; ISO C99 and later do not support implicit
>> function declarations [-Wimplicit-function-declaration]
1900 | irq_set_status_flags(gpu->irq, IRQ_NOAUTOEN);
| ^
>> drivers/gpu/drm/etnaviv/etnaviv_gpu.c:1900:33: error: use of undeclared
>> identifier 'IRQ_NOAUTOEN'
1900 | irq_set_status_flags(gpu->irq, IRQ_NOAUTOEN);
|^
1 warning and 2 errors generated.
vim +/irq_set_status_flags +1900 drivers/gpu/drm/etnaviv/etnaviv_gpu.c
1874
1875 static int etnaviv_gpu_platform_probe(struct platform_device *pdev)
1876 {
1877 struct device *dev = &pdev->dev;
1878 struct etnaviv_gpu *gpu;
1879 int err;
1880
1881 gpu = devm_kzalloc(dev, sizeof(*gpu), GFP_KERNEL);
1882 if (!gpu)
1883 return -ENOMEM;
1884
1885 gpu->dev = &pdev->dev;
1886 mutex_init(&gpu->lock);
1887 mutex_init(&gpu->sched_lock);
1888
1889 /* Map registers: */
1890 gpu->mmio = devm_platform_ioremap_resource(pdev, 0);
1891 if (IS_ERR(gpu->mmio))
1892 return PTR_ERR(gpu->mmio);
1893
1894 /* Get Interrupt: */
1895 gpu->irq = platform_get_irq(pdev, 0);
1896 if (gpu->irq < 0)
1897 return gpu->irq;
1898
1899 /* Avoid enabling the interrupt until everything is ready */
> 1900 irq_set_status_flags(gpu->irq, IRQ_NOAUTOEN);
1901
1902 err = devm_request_irq(&pdev->dev, gpu->irq, irq_handler, 0,
1903 dev_name(gpu->dev), gpu);
1904 if (err) {
1905 dev_err(dev, "failed to request IRQ%u: %d\n", gpu->irq,
err);
1906 return err;
1907 }
1908
1909 /* Get Reset: */
1910 gpu->rst = devm_reset_control_get_optional(&pdev->dev, NULL);
1911 if (IS_ERR(gpu->rst))
1912 return dev_err_probe(dev, PTR_ERR(gpu->rst),
1913 "failed to get reset\n");
1914
1915 /* Get Clocks: */
1916 gpu->clk_reg = devm_clk_get_optional(&pdev->dev, "reg");
1917 DBG("clk_reg: %p", gpu->clk_reg);
1918 if (IS_ERR(gpu->clk_reg))
1919 return PTR_ERR(gpu->clk_reg);
1920
1921 gpu->clk_bus = devm_clk_get_optional(&pdev->dev, "bus");
1922 DBG("clk_bus: %p"
Re: [PATCH bpf-next 2/2] bpf: Switch bpf arena to use drm_mm instead of maple_tree
Hi Alexei,
kernel test robot noticed the following build errors:
[auto build test ERROR on bpf-next/master]
url:
https://github.com/intel-lab-lkp/linux/commits/Alexei-Starovoitov/drm-bpf-Move-drm_mm-c-to-lib-to-be-used-by-bpf-arena/20241102-075645
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link:
https://lore.kernel.org/r/20241101235453.63380-3-alexei.starovoitov%40gmail.com
patch subject: [PATCH bpf-next 2/2] bpf: Switch bpf arena to use drm_mm instead
of maple_tree
config: sparc-randconfig-r061-20241105
(https://download.01.org/0day-ci/archive/20241105/202411052322.genc72sg-...@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241105/202411052322.genc72sg-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202411052322.genc72sg-...@intel.com/
All errors (new ones prefixed by >>):
sparc64-linux-ld: lib/drm_mm.o: in function `drm_mm_takedown':
>> lib/drm_mm.c:135:(.text+0x470): undefined reference to `__drm_err'
>> sparc64-linux-ld: lib/drm_mm.c:129:(.text+0x4ac): undefined reference to
>> `__drm_err'
vim +135 lib/drm_mm.c
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 117
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 118 static
void show_leaks(struct drm_mm *mm)
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 119 {
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 120struct
drm_mm_node *node;
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 121char
*buf;
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 122
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 123buf =
kmalloc(BUFSZ, GFP_KERNEL);
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 124if
(!buf)
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 125
return;
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 126
2bc98c86517b08 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-12-22 127
list_for_each_entry(node, drm_mm_nodes(mm), node_list) {
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 128
if (!node->stack) {
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 @129
DRM_ERROR("node [%08llx + %08llx]: unknown owner\n",
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 130
node->start, node->size);
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 131
continue;
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 132
}
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 133
0f68d45ef41abb drivers/gpu/drm/drm_mm.c Imran Khan 2021-11-08 134
stack_depot_snprint(node->stack, buf, BUFSZ, 0);
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 @135
DRM_ERROR("node [%08llx + %08llx]: inserted at\n%s",
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 136
node->start, node->size, buf);
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 137}
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 138
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 139
kfree(buf);
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 140 }
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 141
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH bpf-next 2/2] bpf: Switch bpf arena to use drm_mm instead of maple_tree
Hi Alexei,
kernel test robot noticed the following build errors:
[auto build test ERROR on bpf-next/master]
url:
https://github.com/intel-lab-lkp/linux/commits/Alexei-Starovoitov/drm-bpf-Move-drm_mm-c-to-lib-to-be-used-by-bpf-arena/20241102-075645
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link:
https://lore.kernel.org/r/20241101235453.63380-3-alexei.starovoitov%40gmail.com
patch subject: [PATCH bpf-next 2/2] bpf: Switch bpf arena to use drm_mm instead
of maple_tree
config: i386-randconfig-003-20241104
(https://download.01.org/0day-ci/archive/20241105/202411051357.3xlbnpy3-...@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/20241105/202411051357.3xlbnpy3-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202411051357.3xlbnpy3-...@intel.com/
All errors (new ones prefixed by >>):
ld: lib/drm_mm.o: in function `show_leaks':
>> lib/drm_mm.c:135: undefined reference to `__drm_err'
>> ld: lib/drm_mm.c:129: undefined reference to `__drm_err'
vim +135 lib/drm_mm.c
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 117
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 118 static
void show_leaks(struct drm_mm *mm)
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 119 {
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 120struct
drm_mm_node *node;
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 121char
*buf;
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 122
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 123buf =
kmalloc(BUFSZ, GFP_KERNEL);
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 124if
(!buf)
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 125
return;
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 126
2bc98c86517b08 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-12-22 127
list_for_each_entry(node, drm_mm_nodes(mm), node_list) {
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 128
if (!node->stack) {
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 @129
DRM_ERROR("node [%08llx + %08llx]: unknown owner\n",
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 130
node->start, node->size);
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 131
continue;
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 132
}
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 133
0f68d45ef41abb drivers/gpu/drm/drm_mm.c Imran Khan 2021-11-08 134
stack_depot_snprint(node->stack, buf, BUFSZ, 0);
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 @135
DRM_ERROR("node [%08llx + %08llx]: inserted at\n%s",
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 136
node->start, node->size, buf);
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 137}
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 138
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 139
kfree(buf);
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 140 }
5705670d046342 drivers/gpu/drm/drm_mm.c Chris Wilson 2016-10-31 141
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 3/3] iommu: Add a kdoc to iommu_unmap()
Hi Jason,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 8e929cb546ee42c9a61d24fae60605e9e3192354]
url:
https://github.com/intel-lab-lkp/linux/commits/Jason-Gunthorpe/iommu-io-pgtable-arm-Remove-split-on-unmap-behavior/20241105-014356
base: 8e929cb546ee42c9a61d24fae60605e9e3192354
patch link:
https://lore.kernel.org/r/3-v2-fd55d00a60b2%2Bc69-arm_no_split_jgg%40nvidia.com
patch subject: [PATCH v2 3/3] iommu: Add a kdoc to iommu_unmap()
config: x86_64-rhel-8.3
(https://download.01.org/0day-ci/archive/20241105/202411051125.mlgewlem-...@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/20241105/202411051125.mlgewlem-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202411051125.mlgewlem-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/iommu/iommu.c:2605: warning: Function parameter or struct member
>> 'size' not described in 'iommu_unmap'
>> drivers/iommu/iommu.c:2605: warning: Excess function parameter 'len'
>> description in 'iommu_unmap'
vim +2605 drivers/iommu/iommu.c
add02cfdc9bc29 drivers/iommu/iommu.c Joerg Roedel2017-08-23 2588
6aa7e03e9dd8b5 drivers/iommu/iommu.c Jason Gunthorpe 2024-11-04 2589 /**
6aa7e03e9dd8b5 drivers/iommu/iommu.c Jason Gunthorpe 2024-11-04 2590 *
iommu_unmap() - Remove mappings from a range of IOVA
6aa7e03e9dd8b5 drivers/iommu/iommu.c Jason Gunthorpe 2024-11-04 2591 *
@domain: Domain to manipulate
6aa7e03e9dd8b5 drivers/iommu/iommu.c Jason Gunthorpe 2024-11-04 2592 *
@iova: IO virtual address to start
6aa7e03e9dd8b5 drivers/iommu/iommu.c Jason Gunthorpe 2024-11-04 2593 * @len:
Length of the range starting from @iova
6aa7e03e9dd8b5 drivers/iommu/iommu.c Jason Gunthorpe 2024-11-04 2594 *
6aa7e03e9dd8b5 drivers/iommu/iommu.c Jason Gunthorpe 2024-11-04 2595 *
iommu_unmap() will remove a translation created by iommu_map(). It cannot
6aa7e03e9dd8b5 drivers/iommu/iommu.c Jason Gunthorpe 2024-11-04 2596 *
subdivide a mapping created by iommu_map(), so it should be called with IOVA
6aa7e03e9dd8b5 drivers/iommu/iommu.c Jason Gunthorpe 2024-11-04 2597 *
ranges that match what was passed to iommu_map(). The range can aggregate
6aa7e03e9dd8b5 drivers/iommu/iommu.c Jason Gunthorpe 2024-11-04 2598 *
contiguous iommu_map() calls so long as no individual range is split.
6aa7e03e9dd8b5 drivers/iommu/iommu.c Jason Gunthorpe 2024-11-04 2599 *
6aa7e03e9dd8b5 drivers/iommu/iommu.c Jason Gunthorpe 2024-11-04 2600 *
Returns: Number of bytes of IOVA unmapped. iova + res will be the point
6aa7e03e9dd8b5 drivers/iommu/iommu.c Jason Gunthorpe 2024-11-04 2601 *
unmapping stopped.
6aa7e03e9dd8b5 drivers/iommu/iommu.c Jason Gunthorpe 2024-11-04 2602 */
add02cfdc9bc29 drivers/iommu/iommu.c Joerg Roedel2017-08-23 2603 size_t
iommu_unmap(struct iommu_domain *domain,
add02cfdc9bc29 drivers/iommu/iommu.c Joerg Roedel2017-08-23 2604
unsigned long iova, size_t size)
add02cfdc9bc29 drivers/iommu/iommu.c Joerg Roedel2017-08-23 @2605 {
a7d20dc19d9ea7 drivers/iommu/iommu.c Will Deacon 2019-07-02 2606 struct
iommu_iotlb_gather iotlb_gather;
a7d20dc19d9ea7 drivers/iommu/iommu.c Will Deacon 2019-07-02 2607 size_t
ret;
a7d20dc19d9ea7 drivers/iommu/iommu.c Will Deacon 2019-07-02 2608
a7d20dc19d9ea7 drivers/iommu/iommu.c Will Deacon 2019-07-02 2609
iommu_iotlb_gather_init(&iotlb_gather);
a7d20dc19d9ea7 drivers/iommu/iommu.c Will Deacon 2019-07-02 2610 ret =
__iommu_unmap(domain, iova, size, &iotlb_gather);
aae4c8e27bd756 drivers/iommu/iommu.c Tom Murphy 2020-08-17 2611
iommu_iotlb_sync(domain, &iotlb_gather);
a7d20dc19d9ea7 drivers/iommu/iommu.c Will Deacon 2019-07-02 2612
a7d20dc19d9ea7 drivers/iommu/iommu.c Will Deacon 2019-07-02 2613 return
ret;
add02cfdc9bc29 drivers/iommu/iommu.c Joerg Roedel2017-08-23 2614 }
cefc53c7f49424 drivers/base/iommu.c Joerg Roedel2010-01-08 2615
EXPORT_SYMBOL_GPL(iommu_unmap);
1460432cb513f0 drivers/iommu/iommu.c Alex Williamson 2011-10-21 2616
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH V3 drm-dp 2/4] drm/hisilicon/hibmc: add dp link moduel in hibmc
Hi Yongbang,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on linus/master v6.12-rc6 next-20241101]
[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/Yongbang-Shi/drm-hisilicon-hibmc-add-dp-aux-in-hibmc/20241101-185648
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20241101105028.2177274-3-shiyongbang%40huawei.com
patch subject: [PATCH V3 drm-dp 2/4] drm/hisilicon/hibmc: add dp link moduel in
hibmc
config: csky-randconfig-r121-20241103
(https://download.01.org/0day-ci/archive/20241104/202411041559.wifxrn6n-...@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.1.0
reproduce:
(https://download.01.org/0day-ci/archive/20241104/202411041559.wifxrn6n-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202411041559.wifxrn6n-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/hisilicon/hibmc/dp/dp_link.c:12:10: sparse: sparse: symbol
>> 'link_rate_map' was not declared. Should it be static?
vim +/link_rate_map +12 drivers/gpu/drm/hisilicon/hibmc/dp/dp_link.c
11
> 12 const u8 link_rate_map[] = {DP_LINK_BW_1_62, DP_LINK_BW_2_7,
13 DP_LINK_BW_5_4, DP_LINK_BW_8_1};
14
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 3/3] drm/panel: add LXD M9189A panel driver
Hi Rouven,
kernel test robot noticed the following build errors:
[auto build test ERROR on c2ee9f594da826bea183ed14f2cc029c719bf4da]
url:
https://github.com/intel-lab-lkp/linux/commits/Rouven-Czerwinski/dt-bindings-display-panel-add-YAML-schema-for-LXD-M9189A/20241025-221252
base: c2ee9f594da826bea183ed14f2cc029c719bf4da
patch link:
https://lore.kernel.org/r/20241025141130.3179166-3-r.czerwinski%40pengutronix.de
patch subject: [PATCH v2 3/3] drm/panel: add LXD M9189A panel driver
config: arm-randconfig-r062-20241102
(https://download.01.org/0day-ci/archive/20241102/202411020816.nb9aevto-...@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project
6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241102/202411020816.nb9aevto-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202411020816.nb9aevto-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/panel/panel-lxd-m9189a.c:173:29: error: variable 'ret' is
>> uninitialized when used here [-Werror,-Wuninitialized]
173 | return dev_err_probe(dev, ret, "Failed to get
regulator\n");
| ^~~
drivers/gpu/drm/panel/panel-lxd-m9189a.c:165:9: note: initialize the
variable 'ret' to silence this warning
165 | int ret;
|^
| = 0
1 error generated.
vim +/ret +173 drivers/gpu/drm/panel/panel-lxd-m9189a.c
160
161 static int lxd_m9189_probe(struct mipi_dsi_device *dsi)
162 {
163 struct device *dev = &dsi->dev;
164 struct m9189_panel *m9189;
165 int ret;
166
167 m9189 = devm_kzalloc(dev, sizeof(*m9189), GFP_KERNEL);
168 if (!m9189)
169 return -ENOMEM;
170
171 m9189->supply = devm_regulator_get(dev, "vdd");
172 if (IS_ERR(m9189->supply))
> 173 return dev_err_probe(dev, ret, "Failed to get
> regulator\n");
174
175 m9189->reset_gpio = devm_gpiod_get(dev, "reset", GPIOD_OUT_LOW);
176 if (IS_ERR(m9189->reset_gpio))
177 return dev_err_probe(dev, PTR_ERR(m9189->reset_gpio),
178 "Failed to get reset-gpios\n");
179
180 m9189->standby_gpio = devm_gpiod_get(dev, "standby",
GPIOD_OUT_LOW);
181 if (IS_ERR(m9189->standby_gpio))
182 return dev_err_probe(dev, PTR_ERR(m9189->standby_gpio),
183 "Failed to get standby-gpios\n");
184
185 m9189->dsi = dsi;
186 mipi_dsi_set_drvdata(dsi, m9189);
187
188 dsi->lanes = 4;
189 dsi->format = MIPI_DSI_FMT_RGB888;
190 dsi->mode_flags = MIPI_DSI_MODE_VIDEO |
MIPI_DSI_MODE_VIDEO_BURST;
191
192 drm_panel_init(&m9189->panel, dev, &m9189_panel_funcs,
193 DRM_MODE_CONNECTOR_DSI);
194 m9189->panel.prepare_prev_first = true;
195
196 ret = drm_panel_of_backlight(&m9189->panel);
197 if (ret)
198 return dev_err_probe(dev, ret, "Failed to get
backlight\n");
199
200 drm_panel_add(&m9189->panel);
201
202 ret = mipi_dsi_attach(dsi);
203 if (ret < 0) {
204 dev_err_probe(dev, ret, "Failed to attach to DSI
host\n");
205 drm_panel_remove(&m9189->panel);
206 return ret;
207 }
208
209 return 0;
210 }
211
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[linux-next:fs-next] [fs] 0eccf222d7: Oops:general_protection_fault, probably_for_non-canonical_address#:#[##]PREEMPT_SMP_KASAN_PTI
Hello,
for this commit but in linux-next/fs-next branch, we notice crash issue in
vm/booting tests
kernel test robot noticed
"Oops:general_protection_fault,probably_for_non-canonical_address#:#[##]PREEMPT_SMP_KASAN_PTI"
on:
commit: 0eccf222d798166ce42a4ed0da91a0cb14945c7a ("fs: port files to file_ref")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git fs-next
in testcase: boot
config: x86_64-rhel-8.3-kselftests
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+--+++
|
| 08ef26ea9a | 0eccf222d7 |
+--+++
| boot_successes
| 18 | 0 |
| boot_failures
| 0 | 18 |
|
Oops:general_protection_fault,probably_for_non-canonical_address#:#[##]PREEMPT_SMP_KASAN_PTI
| 0 | 18 |
| KASAN:null-ptr-deref_in_range[#-#]
| 0 | 18 |
| RIP:hook_file_free_security
| 0 | 18 |
| Kernel_panic-not_syncing:Fatal_exception
| 0 | 18 |
+--+++
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
| Closes:
https://lore.kernel.org/oe-lkp/202410301313.50e4d05c-oliver.s...@intel.com
[3.605271][T1] pci_bus :00: resource 8 [mem 0x44000-0x4bfff
window]
[3.608369][T1] pci :00:01.0: PIIX3: Enabling Passive Release
[3.609815][T1] pci :00:00.0: Limiting direct PCI/PCI transfers
[3.611533][T1] PCI: CLS 0 bytes, default 64
[3.615146][ T30] Trying to unpack rootfs image as initramfs...
[3.622946][T9] Oops: general protection fault, probably for
non-canonical address 0xdc01: [#1] PREEMPT SMP KASAN PTI
[3.623645][T9] KASAN: null-ptr-deref in range
[0x0008-0x000f]
[3.623645][T9] CPU: 0 UID: 0 PID: 9 Comm: kworker/0:1 Not tainted
6.12.0-rc2-3-g0eccf222d798 #1
[3.623645][T9] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[3.623645][T9] Workqueue: events delayed_fput
[ 3.623645][ T9] RIP: 0010:hook_file_free_security
(kbuild/src/consumer/security/landlock/fs.c:1662)
[ 3.623645][ T9] Code: b6 14 11 38 d0 7c 04 84 d2 75 2f 48 63 05 21 1f ae 02 48
01 c3 48 b8 00 00 00 00 00 fc ff df 48 8d 7b 08 48 89 fa 48 c1 ea 03 <80> 3c 02
00 75 1f 48 8b 7b 08 5b e9 25 d1 ff ff 48 c7 c7 e4 0c a1
All code
0: b6 14 mov$0x14,%dh
2: 11 38 adc%edi,(%rax)
4: d0 7c 04 84 sarb -0x7c(%rsp,%rax,1)
8: d2 75 2fshlb %cl,0x2f(%rbp)
b: 48 63 05 21 1f ae 02movslq 0x2ae1f21(%rip),%rax# 0x2ae1f33
12: 48 01 c3add%rax,%rbx
15: 48 b8 00 00 00 00 00movabs $0xdc00,%rax
1c: fc ff df
1f: 48 8d 7b 08 lea0x8(%rbx),%rdi
23: 48 89 famov%rdi,%rdx
26: 48 c1 ea 03 shr$0x3,%rdx
2a:* 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <--
trapping instruction
2e: 75 1f jne0x4f
30: 48 8b 7b 08 mov0x8(%rbx),%rdi
34: 5b pop%rbx
35: e9 25 d1 ff ff jmpq 0xd15f
3a: 48 rex.W
3b: c7 .byte 0xc7
3c: c7 (bad)
3d: e4 0c in $0xc,%al
3f: a1 .byte 0xa1
Code starting with the faulting instruction
===
0: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1)
4: 75 1f jne0x25
6: 48 8b 7b 08 mov0x8(%rbx),%rdi
a: 5b pop%rbx
b: e9 25 d1 ff ff jmpq 0xd135
10: 48 rex.W
11: c7 .byte 0xc7
12: c7 (bad)
13: e4 0c in $0xc,%al
15: a1 .byte 0xa1
[
Re: [PATCH] fbdev: udl: Make CONFIG_FB_DEVICE optional
Hi Gonzalo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-tip/drm-tip linus/master v6.12-rc5
next-20241028]
[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/Gonzalo-Silvalde-Blanco/fbdev-udl-Make-CONFIG_FB_DEVICE-optional/20241025-172653
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20241025092538.38339-1-gonzalo.silvalde%40gmail.com
patch subject: [PATCH] fbdev: udl: Make CONFIG_FB_DEVICE optional
config: riscv-randconfig-r073-20241029
(https://download.01.org/0day-ci/archive/20241029/202410290452.xkxqkwp1-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
5886454669c3c9026f7f27eab13509dd0241f2d6)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241029/202410290452.xkxqkwp1-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410290452.xkxqkwp1-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/video/fbdev/udlfb.c:19:
In file included from include/linux/usb.h:16:
In file included from include/linux/interrupt.h:22:
In file included from arch/riscv/include/asm/sections.h:9:
In file included from include/linux/mm.h:2213:
include/linux/vmstat.h:518:36: warning: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
>> drivers/video/fbdev/udlfb.c:1485:35: warning: unused variable 'edid_attr'
>> [-Wunused-const-variable]
1485 | static const struct bin_attribute edid_attr = {
| ^
>> drivers/video/fbdev/udlfb.c:1493:38: warning: unused variable
>> 'fb_device_attrs' [-Wunused-const-variable]
1493 | static const struct device_attribute fb_device_attrs[] = {
| ^~~
3 warnings generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for GET_FREE_REGION
Depends on [n]: SPARSEMEM [=n]
Selected by [m]:
- RESOURCE_KUNIT_TEST [=m] && RUNTIME_TESTING_MENU [=y] && KUNIT [=m]
vim +/edid_attr +1485 drivers/video/fbdev/udlfb.c
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1484
598b2eedfc3fbe drivers/video/fbdev/udlfb.c Bhumika Goyal 2017-08-18
@1485 static const struct bin_attribute edid_attr = {
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1486.attr.name = "edid",
8ef8cc4fca4a92 drivers/staging/udlfb/udlfb.c Bernie Thompson2010-09-05
1487.attr.mode = 0666,
b9f03a3cd06c6f drivers/video/udlfb.c Paul Mundt 2011-01-06
1488.size = EDID_LENGTH,
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1489.read = edid_show,
8ef8cc4fca4a92 drivers/staging/udlfb/udlfb.c Bernie Thompson2010-09-05
1490.write = edid_store
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1491 };
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1492
fa738a5c4b2a6b drivers/video/fbdev/udlfb.c Ladislav Michl 2018-01-16
@1493 static const struct device_attribute fb_device_attrs[] = {
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1494__ATTR_RO(metrics_bytes_rendered),
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1495__ATTR_RO(metrics_bytes_identical),
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1496__ATTR_RO(metrics_bytes_sent),
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1497__ATTR_RO(metrics_cpu_kcycles_used),
926c11151e3b82 drivers/staging/udlfb/udlfb.c Greg Kroah-Hartman 2010-11-18
1498__ATTR(metrics_reset, S_IWUSR, NULL, metrics_reset_store),
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1499 };
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1500
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH] fbdev: udl: Make CONFIG_FB_DEVICE optional
Hi Gonzalo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-tip/drm-tip linus/master v6.12-rc4
next-20241025]
[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/Gonzalo-Silvalde-Blanco/fbdev-udl-Make-CONFIG_FB_DEVICE-optional/20241025-172653
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20241025092538.38339-1-gonzalo.silvalde%40gmail.com
patch subject: [PATCH] fbdev: udl: Make CONFIG_FB_DEVICE optional
config: i386-randconfig-r121-20241027
(https://download.01.org/0day-ci/archive/20241028/202410280002.axteajwc-...@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/20241028/202410280002.axteajwc-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410280002.axteajwc-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/video/fbdev/udlfb.c:1493:38: warning: 'fb_device_attrs' defined but
>> not used [-Wunused-const-variable=]
1493 | static const struct device_attribute fb_device_attrs[] = {
| ^~~
>> drivers/video/fbdev/udlfb.c:1485:35: warning: 'edid_attr' defined but not
>> used [-Wunused-const-variable=]
1485 | static const struct bin_attribute edid_attr = {
| ^
vim +/fb_device_attrs +1493 drivers/video/fbdev/udlfb.c
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1484
598b2eedfc3fbe drivers/video/fbdev/udlfb.c Bhumika Goyal 2017-08-18
@1485 static const struct bin_attribute edid_attr = {
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1486.attr.name = "edid",
8ef8cc4fca4a92 drivers/staging/udlfb/udlfb.c Bernie Thompson2010-09-05
1487.attr.mode = 0666,
b9f03a3cd06c6f drivers/video/udlfb.c Paul Mundt 2011-01-06
1488.size = EDID_LENGTH,
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1489.read = edid_show,
8ef8cc4fca4a92 drivers/staging/udlfb/udlfb.c Bernie Thompson2010-09-05
1490.write = edid_store
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1491 };
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1492
fa738a5c4b2a6b drivers/video/fbdev/udlfb.c Ladislav Michl 2018-01-16
@1493 static const struct device_attribute fb_device_attrs[] = {
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1494__ATTR_RO(metrics_bytes_rendered),
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1495__ATTR_RO(metrics_bytes_identical),
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1496__ATTR_RO(metrics_bytes_sent),
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1497__ATTR_RO(metrics_cpu_kcycles_used),
926c11151e3b82 drivers/staging/udlfb/udlfb.c Greg Kroah-Hartman 2010-11-18
1498__ATTR(metrics_reset, S_IWUSR, NULL, metrics_reset_store),
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1499 };
7d9485e2c53caa drivers/staging/udlfb/udlfb.c Bernie Thompson2010-02-15
1500
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v8 1/4] drm: Introduce device wedged event
Hi Raag,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-xe/drm-xe-next]
[also build test ERROR on drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.12-rc4
next-20241025]
[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/Raag-Jadav/drm-Introduce-device-wedged-event/20241025-165119
base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link:
https://lore.kernel.org/r/20241025084817.144621-2-raag.jadav%40intel.com
patch subject: [PATCH v8 1/4] drm: Introduce device wedged event
config: arm-randconfig-002-20241026
(https://download.01.org/0day-ci/archive/20241026/202410261754.enck8cc6-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
5886454669c3c9026f7f27eab13509dd0241f2d6)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241026/202410261754.enck8cc6-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410261754.enck8cc6-...@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/drm_drv.c:36:
In file included from include/linux/pseudo_fs.h:4:
In file included from include/linux/fs_context.h:14:
In file included from include/linux/security.h:33:
In file included from include/linux/mm.h:2213:
include/linux/vmstat.h:518:36: warning: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
>> drivers/gpu/drm/drm_drv.c:81:3: error: expression is not an integer constant
>> expression
81 | [ffs(DRM_WEDGE_RECOVERY_REBIND) - 1]= "rebind",
| ^~
include/asm-generic/bitops/ffs.h:43:16: note: expanded from macro 'ffs'
43 | #define ffs(x) generic_ffs(x)
|^
drivers/gpu/drm/drm_drv.c:82:3: error: expression is not an integer constant
expression
82 | [ffs(DRM_WEDGE_RECOVERY_BUS_RESET) - 1] = "bus-reset",
| ^
include/asm-generic/bitops/ffs.h:43:16: note: expanded from macro 'ffs'
43 | #define ffs(x) generic_ffs(x)
|^
>> drivers/gpu/drm/drm_drv.c:84:15: error: invalid application of 'sizeof' to
>> an incomplete type 'const char *const[]'
84 | static_assert(ARRAY_SIZE(drm_wedge_recovery_opts) ==
ffs(DRM_WEDGE_RECOVERY_BUS_RESET));
|
~~^
include/linux/array_size.h:11:32: note: expanded from macro 'ARRAY_SIZE'
11 | #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) +
__must_be_array(arr))
|^
include/linux/build_bug.h:77:50: note: expanded from macro 'static_assert'
77 | #define static_assert(expr, ...) __static_assert(expr,
##__VA_ARGS__, #expr)
|
^~~
include/linux/build_bug.h:78:56: note: expanded from macro '__static_assert'
78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
|^~~~
drivers/gpu/drm/drm_drv.c:528:32: error: invalid application of 'sizeof' to
an incomplete type 'const char *const[]'
528 | unsigned int len, opt, size =
ARRAY_SIZE(drm_wedge_recovery_opts);
|
^~~
include/linux/array_size.h:11:32: note: expanded from macro 'ARRAY_SIZE'
11 | #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) +
__must_be_array(arr))
|^
1 warning and 4 errors generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for MODVERSIONS
Depends on [n]: MODULES [=y] && !COMPILE_TEST [=y]
Selected by [y]:
- RANDSTRUCT_FULL [=y] && (CC_HAS_RANDSTRUCT [=y] || GCC_PLUGINS [=n]) &&
MODULES [=y]
vim +81 drivers/gpu/drm/drm_drv.c
75
76 /*
77 * Available recovery methods for wedged device. To be sent along with
device
78 * wedged uevent.
79
Re: [PATCH v8 1/4] drm: Introduce device wedged event
Hi Raag,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-xe/drm-xe-next]
[also build test ERROR on drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.12-rc4
next-20241025]
[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/Raag-Jadav/drm-Introduce-device-wedged-event/20241025-165119
base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link:
https://lore.kernel.org/r/20241025084817.144621-2-raag.jadav%40intel.com
patch subject: [PATCH v8 1/4] drm: Introduce device wedged event
config: alpha-allmodconfig
(https://download.01.org/0day-ci/archive/20241026/202410261411.f8079sy8-...@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/20241026/202410261411.f8079sy8-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410261411.f8079sy8-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/drm_drv.c:81:10: error: nonconstant array index in
>> initializer
81 | [ffs(DRM_WEDGE_RECOVERY_REBIND) - 1]= "rebind",
| ^~~
drivers/gpu/drm/drm_drv.c:81:10: note: (near initialization for
'drm_wedge_recovery_opts')
drivers/gpu/drm/drm_drv.c:82:10: error: nonconstant array index in
initializer
82 | [ffs(DRM_WEDGE_RECOVERY_BUS_RESET) - 1] = "bus-reset",
| ^~~
drivers/gpu/drm/drm_drv.c:82:10: note: (near initialization for
'drm_wedge_recovery_opts')
In file included from drivers/gpu/drm/drm_drv.c:30:
>> drivers/gpu/drm/drm_drv.c:84:51: error: expression in static assertion is
>> not constant
84 | static_assert(ARRAY_SIZE(drm_wedge_recovery_opts) ==
ffs(DRM_WEDGE_RECOVERY_BUS_RESET));
include/linux/build_bug.h:78:56: note: in definition of macro
'__static_assert'
78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
|^~~~
drivers/gpu/drm/drm_drv.c:84:1: note: in expansion of macro 'static_assert'
84 | static_assert(ARRAY_SIZE(drm_wedge_recovery_opts) ==
ffs(DRM_WEDGE_RECOVERY_BUS_RESET));
| ^
vim +81 drivers/gpu/drm/drm_drv.c
75
76 /*
77 * Available recovery methods for wedged device. To be sent along with
device
78 * wedged uevent.
79 */
80 static const char *const drm_wedge_recovery_opts[] = {
> 81 [ffs(DRM_WEDGE_RECOVERY_REBIND) - 1]= "rebind",
82 [ffs(DRM_WEDGE_RECOVERY_BUS_RESET) - 1] = "bus-reset",
83 };
> 84 static_assert(ARRAY_SIZE(drm_wedge_recovery_opts) ==
ffs(DRM_WEDGE_RECOVERY_BUS_RESET));
85
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 22/37] drm/vc4: txp: Add BCM2712 MOPLET support
Hi Dave,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 91e21479c81dd4e9e22a78d7446f92f6b96a7284]
url:
https://github.com/intel-lab-lkp/linux/commits/Dave-Stevenson/drm-vc4-Limit-max_bpc-to-8-on-Pi0-3/20241024-005239
base: 91e21479c81dd4e9e22a78d7446f92f6b96a7284
patch link:
https://lore.kernel.org/r/20241023-drm-vc4-2712-support-v1-22-1cc2d5594907%40raspberrypi.com
patch subject: [PATCH 22/37] drm/vc4: txp: Add BCM2712 MOPLET support
config: arc-randconfig-r111-20241025
(https://download.01.org/0day-ci/archive/20241025/202410251938.rnvciesu-...@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce:
(https://download.01.org/0day-ci/archive/20241025/202410251938.rnvciesu-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410251938.rnvciesu-...@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/gpu/drm/vc4/vc4_txp.c:513:27: sparse: sparse: symbol
'bcm2712_mop_data' was not declared. Should it be static?
>> drivers/gpu/drm/vc4/vc4_txp.c:527:27: sparse: sparse: symbol
>> 'bcm2712_moplet_data' was not declared. Should it be static?
vim +/bcm2712_moplet_data +527 drivers/gpu/drm/vc4/vc4_txp.c
526
> 527 const struct vc4_txp_data bcm2712_moplet_data = {
528 .base = {
529 .name = "moplet",
530 .debugfs_name = "moplet_regs",
531 .hvs_available_channels = BIT(1),
532 .hvs_output = 4,
533 },
534 .encoder_type = VC4_ENCODER_TYPE_TXP1,
535 .high_addr_ptr_reg = TXP_DST_PTR_HIGH_MOPLET,
536 .size_minus_one = true,
537 .supports_40bit_addresses = true,
538 };
539
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 21/37] drm/vc4: txp: Add support for BCM2712 MOP
Hi Dave,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 91e21479c81dd4e9e22a78d7446f92f6b96a7284]
url:
https://github.com/intel-lab-lkp/linux/commits/Dave-Stevenson/drm-vc4-Limit-max_bpc-to-8-on-Pi0-3/20241024-005239
base: 91e21479c81dd4e9e22a78d7446f92f6b96a7284
patch link:
https://lore.kernel.org/r/20241023-drm-vc4-2712-support-v1-21-1cc2d5594907%40raspberrypi.com
patch subject: [PATCH 21/37] drm/vc4: txp: Add support for BCM2712 MOP
config: arc-randconfig-r111-20241025
(https://download.01.org/0day-ci/archive/20241025/202410251725.zqplkjrl-...@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce:
(https://download.01.org/0day-ci/archive/20241025/202410251725.zqplkjrl-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410251725.zqplkjrl-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/vc4/vc4_txp.c:513:27: sparse: sparse: symbol
>> 'bcm2712_mop_data' was not declared. Should it be static?
vim +/bcm2712_mop_data +513 drivers/gpu/drm/vc4/vc4_txp.c
512
> 513 const struct vc4_txp_data bcm2712_mop_data = {
514 .base = {
515 .name = "mop",
516 .debugfs_name = "mop_regs",
517 .hvs_available_channels = BIT(2),
518 .hvs_output = 2,
519 },
520 .encoder_type = VC4_ENCODER_TYPE_TXP0,
521 .high_addr_ptr_reg = TXP_DST_PTR_HIGH_MOP,
522 .has_byte_enable = true,
523 .size_minus_one = true,
524 .supports_40bit_addresses = true,
525 };
526
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH V2 drm-dp 3/4] drm/hisilicon/hibmc: add dp hw moduel in hibmc
Hi Yongbang, kernel test robot noticed the following build errors: [auto build test ERROR on drm-misc/drm-misc-next] [also build test ERROR on linus/master v6.12-rc4 next-20241024] [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/Yongbang-Shi/drm-hisilicon-hibmc-add-dp-aux-in-hibmc/20241022-204925 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20241022124148.1952761-4-shiyongbang%40huawei.com patch subject: [PATCH V2 drm-dp 3/4] drm/hisilicon/hibmc: add dp hw moduel in hibmc config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20241025/202410250931.udq9s66h-...@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/20241025/202410250931.udq9s66h-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410250931.udq9s66h-...@intel.com/ All errors (new ones prefixed by >>, old ones prefixed by <<): WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/gpu/drm/bridge/imx/imx-legacy-bridge.o >> ERROR: modpost: "__divdi3" [drivers/gpu/drm/hisilicon/hibmc/hibmc-drm.ko] >> undefined! ERROR: modpost: "__udivdi3" [drivers/gpu/drm/hisilicon/hibmc/hibmc-drm.ko] undefined! Kconfig warnings: (for reference only) WARNING: unmet direct dependencies detected for GET_FREE_REGION Depends on [n]: SPARSEMEM [=n] Selected by [m]: - RESOURCE_KUNIT_TEST [=m] && RUNTIME_TESTING_MENU [=y] && KUNIT [=m] -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH 2/2] drm: remove driver date from struct drm_driver and all drivers
Hi Jani,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on next-20241024]
[cannot apply to drm-exynos/exynos-drm-next shawnguo/for-next
drm-xe/drm-xe-next linus/master v6.12-rc4]
[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/Jani-Nikula/drm-remove-driver-date-from-struct-drm_driver-and-all-drivers/20241025-002344
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20241024162240.2398664-2-jani.nikula%40intel.com
patch subject: [PATCH 2/2] drm: remove driver date from struct drm_driver and
all drivers
config: s390-allmodconfig
(https://download.01.org/0day-ci/archive/20241025/202410251345.na1ihu0x-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
5886454669c3c9026f7f27eab13509dd0241f2d6)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241025/202410251345.na1ihu0x-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410251345.na1ihu0x-...@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/accel/qaic/qaic_drv.c:7:
In file included from include/linux/dma-mapping.h:8:
In file included from include/linux/device.h:32:
In file included from include/linux/device/driver.h:21:
In file included from include/linux/module.h:19:
In file included from include/linux/elf.h:6:
In file included from arch/s390/include/asm/elf.h:181:
In file included from arch/s390/include/asm/mmu_context.h:11:
In file included from arch/s390/include/asm/pgalloc.h:18:
In file included from include/linux/mm.h:2213:
include/linux/vmstat.h:504:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
504 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
505 |item];
|
include/linux/vmstat.h:511:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
511 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
512 |NR_VM_NUMA_EVENT_ITEMS +
|~~
include/linux/vmstat.h:518:36: warning: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
include/linux/vmstat.h:524:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
524 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
525 |NR_VM_NUMA_EVENT_ITEMS +
|~~
In file included from drivers/accel/qaic/qaic_drv.c:7:
In file included from include/linux/dma-mapping.h:11:
In file included from include/linux/scatterlist.h:9:
In file included from arch/s390/include/asm/io.h:93:
include/asm-generic/io.h:548:31: warning: performing pointer arithmetic on a
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
548 | val = __raw_readb(PCI_IOBASE + addr);
| ~~ ^
include/asm-generic/io.h:561:61: warning: performing pointer arithmetic on a
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
561 | val = __le16_to_cpu((__le16 __force)__raw_readw(PCI_IOBASE +
addr));
| ~~ ^
include/uapi/linux/byteorder/big_endian.h:37:59: note: expanded from macro
'__le16_to_cpu'
37 | #define __le16_to_cpu(x) __swab16((__force __u16)(__le16)(x))
| ^
include/uapi/linux/swab.h:102:54: note: expanded from macro '__swab16'
102 | #define __swab16(x) (__u16)__builtin_bswap16((__u16)(x))
| ^
In file included from drivers/accel/qa
Re: [PATCH 11/37] drm/vc4: hvs: Add support for BCM2712 HVS
Hi Dave, kernel test robot noticed the following build errors: [auto build test ERROR on 91e21479c81dd4e9e22a78d7446f92f6b96a7284] url: https://github.com/intel-lab-lkp/linux/commits/Dave-Stevenson/drm-vc4-Limit-max_bpc-to-8-on-Pi0-3/20241024-005239 base: 91e21479c81dd4e9e22a78d7446f92f6b96a7284 patch link: https://lore.kernel.org/r/20241023-drm-vc4-2712-support-v1-11-1cc2d5594907%40raspberrypi.com patch subject: [PATCH 11/37] drm/vc4: hvs: Add support for BCM2712 HVS config: um-allmodconfig (https://download.01.org/0day-ci/archive/20241025/202410250541.6acfkd5k-...@intel.com/config) compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 5886454669c3c9026f7f27eab13509dd0241f2d6) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241025/202410250541.6acfkd5k-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410250541.6acfkd5k-...@intel.com/ All error/warnings (new ones prefixed by >>): In file included from drivers/gpu/drm/vc4/vc4_kms.c:17: In file included from include/drm/drm_atomic.h:31: In file included from include/drm/drm_crtc.h:32: In file included from include/drm/drm_modes.h:33: In file included from include/drm/drm_connector.h:32: In file included from include/drm/drm_util.h:35: In file included from include/linux/interrupt.h:11: In file included from include/linux/hardirq.h:11: In file included from arch/um/include/asm/hardirq.h:5: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:14: In file included from arch/um/include/asm/io.h:24: include/asm-generic/io.h:548:31: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 548 | val = __raw_readb(PCI_IOBASE + addr); | ~~ ^ include/asm-generic/io.h:561:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 561 | val = __le16_to_cpu((__le16 __force)__raw_readw(PCI_IOBASE + addr)); | ~~ ^ include/uapi/linux/byteorder/little_endian.h:37:51: note: expanded from macro '__le16_to_cpu' 37 | #define __le16_to_cpu(x) ((__force __u16)(__le16)(x)) | ^ In file included from drivers/gpu/drm/vc4/vc4_kms.c:17: In file included from include/drm/drm_atomic.h:31: In file included from include/drm/drm_crtc.h:32: In file included from include/drm/drm_modes.h:33: In file included from include/drm/drm_connector.h:32: In file included from include/drm/drm_util.h:35: In file included from include/linux/interrupt.h:11: In file included from include/linux/hardirq.h:11: In file included from arch/um/include/asm/hardirq.h:5: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:14: In file included from arch/um/include/asm/io.h:24: include/asm-generic/io.h:574:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 574 | val = __le32_to_cpu((__le32 __force)__raw_readl(PCI_IOBASE + addr)); | ~~ ^ include/uapi/linux/byteorder/little_endian.h:35:51: note: expanded from macro '__le32_to_cpu' 35 | #define __le32_to_cpu(x) ((__force __u32)(__le32)(x)) | ^ In file included from drivers/gpu/drm/vc4/vc4_kms.c:17: In file included from include/drm/drm_atomic.h:31: In file included from include/drm/drm_crtc.h:32: In file included from include/drm/drm_modes.h:33: In file included from include/drm/drm_connector.h:32: In file included from include/drm/drm_util.h:35: In file included from include/linux/interrupt.h:11: In file included from include/linux/hardirq.h:11: In file included from arch/um/include/asm/hardirq.h:5: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:14: In file included from arch/um/include/asm/io.h:24: include/asm-generic/io.h:585:33: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 585 | __raw_writeb(value, PCI_IOBASE + addr); | ~~ ^ include/asm-generic/io.h:595:59: warning: performing pointer arithmetic on a null pointer has undefined behavior
Re: [PATCH 1/7] kernel/cgroup: Add "dev" memory accounting cgroup
Hi Maarten,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-exynos/exynos-drm-next linus/master v6.12-rc4
next-20241024]
[cannot apply to tj-cgroup/for-next drm-xe/drm-xe-next akpm-mm/mm-everything
drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next
drm-tip/drm-tip]
[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/Maarten-Lankhorst/kernel-cgroup-Add-dev-memory-accounting-cgroup/20241023-155504
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20241023075302.27194-2-maarten.lankhorst%40linux.intel.com
patch subject: [PATCH 1/7] kernel/cgroup: Add "dev" memory accounting cgroup
config: i386-randconfig-061-20241025
(https://download.01.org/0day-ci/archive/20241025/202410251311.olenabod-...@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/20241025/202410251311.olenabod-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410251311.olenabod-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/cgroup/dev.c:423:9: sparse: sparse: incompatible types in comparison
>> expression (different address spaces):
kernel/cgroup/dev.c:423:9: sparse:struct list_head [noderef] __rcu *
kernel/cgroup/dev.c:423:9: sparse:struct list_head *
>> kernel/cgroup/dev.c:423:9: sparse: sparse: incompatible types in comparison
>> expression (different address spaces):
kernel/cgroup/dev.c:423:9: sparse:struct list_head [noderef] __rcu *
kernel/cgroup/dev.c:423:9: sparse:struct list_head *
kernel/cgroup/dev.c: note: in included file (through include/linux/smp.h,
include/linux/lockdep.h, include/linux/spinlock.h, ...):
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates
to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates
to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates
to true
vim +423 kernel/cgroup/dev.c
400
401 /**
402 * dev_cgroup_unregister_device() - Unregister a previously registered
device.
403 * @cgdev: The device to unregister.
404 *
405 * This function undoes dev_cgroup_register_device.
406 */
407 void dev_cgroup_unregister_device(struct dev_cgroup_device *cgdev)
408 {
409 struct devcg_device *dev;
410 struct list_head *entry;
411
412 if (!cgdev || !cgdev->priv)
413 return;
414
415 dev = cgdev->priv;
416 cgdev->priv = NULL;
417
418 spin_lock(&devcg_lock);
419
420 /* Remove from global device list */
421 list_del_rcu(&dev->dev_node);
422
> 423 list_for_each_rcu(entry, &dev->pools) {
424 struct dev_cgroup_pool_state *pool =
425 container_of(entry, typeof(*pool), dev_node);
426
427 list_del_rcu(&pool->css_node);
428 }
429
430 /*
431 * Ensure any RCU based lookups fail. Additionally,
432 * no new pools should be added to the dead device
433 * by get_cg_pool_unlocked.
434 */
435 dev->unregistered = true;
436 spin_unlock(&devcg_lock);
437
438 kref_put(&dev->ref, devcg_free_device);
439 }
440 EXPORT_SYMBOL_GPL(dev_cgroup_unregister_device);
441
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 2/2] drm: remove driver date from struct drm_driver and all drivers
Hi Jani,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on next-20241024]
[cannot apply to drm-exynos/exynos-drm-next shawnguo/for-next
drm-xe/drm-xe-next linus/master v6.12-rc4]
[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/Jani-Nikula/drm-remove-driver-date-from-struct-drm_driver-and-all-drivers/20241025-002344
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20241024162240.2398664-2-jani.nikula%40intel.com
patch subject: [PATCH 2/2] drm: remove driver date from struct drm_driver and
all drivers
config: i386-buildonly-randconfig-004-20241025
(https://download.01.org/0day-ci/archive/20241025/202410251351.r16zfufe-...@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/20241025/202410251351.r16zfufe-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410251351.r16zfufe-...@intel.com/
All warnings (new ones prefixed by >>):
drivers/accel/qaic/qaic_drv.c:211:10: error: 'const struct drm_driver' has
no member named 'date'
211 | .date = "20190618",
| ^~~~
>> drivers/accel/qaic/qaic_drv.c:211:35: warning: initialization of 'unsigned
>> int' from 'char *' makes integer from pointer without a cast
>> [-Wint-conversion]
211 | .date = "20190618",
| ^~
drivers/accel/qaic/qaic_drv.c:211:35: note: (near initialization for
'qaic_accel_driver.driver_features')
drivers/accel/qaic/qaic_drv.c:211:35: warning: initialized field overwritten
[-Woverride-init]
drivers/accel/qaic/qaic_drv.c:211:35: note: (near initialization for
'qaic_accel_driver.driver_features')
vim +211 drivers/accel/qaic/qaic_drv.c
c501ca23a6a306 Jeffrey Hugo 2023-03-27 205
c501ca23a6a306 Jeffrey Hugo 2023-03-27 206 static const struct drm_driver
qaic_accel_driver = {
c501ca23a6a306 Jeffrey Hugo 2023-03-27 207 .driver_features=
DRIVER_GEM | DRIVER_COMPUTE_ACCEL,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 208
c501ca23a6a306 Jeffrey Hugo 2023-03-27 209 .name =
QAIC_NAME,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 210 .desc =
QAIC_DESC,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 @211 .date =
"20190618",
c501ca23a6a306 Jeffrey Hugo 2023-03-27 212
c501ca23a6a306 Jeffrey Hugo 2023-03-27 213 .fops =
&qaic_accel_fops,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 214 .open =
qaic_open,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 215 .postclose =
qaic_postclose,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 216
c501ca23a6a306 Jeffrey Hugo 2023-03-27 217 .ioctls =
qaic_drm_ioctls,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 218 .num_ioctls =
ARRAY_SIZE(qaic_drm_ioctls),
c501ca23a6a306 Jeffrey Hugo 2023-03-27 219 .gem_prime_import =
qaic_gem_prime_import,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 220 };
c501ca23a6a306 Jeffrey Hugo 2023-03-27 221
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 2/2] drm: remove driver date from struct drm_driver and all drivers
Hi Jani,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on next-20241024]
[cannot apply to drm-exynos/exynos-drm-next shawnguo/for-next
drm-xe/drm-xe-next linus/master v6.12-rc4]
[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/Jani-Nikula/drm-remove-driver-date-from-struct-drm_driver-and-all-drivers/20241025-002344
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20241024162240.2398664-2-jani.nikula%40intel.com
patch subject: [PATCH 2/2] drm: remove driver date from struct drm_driver and
all drivers
config: loongarch-allmodconfig
(https://download.01.org/0day-ci/archive/20241025/202410251306.cos7w98u-...@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241025/202410251306.cos7w98u-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410251306.cos7w98u-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/accel/qaic/qaic_drv.c:211:10: error: 'const struct drm_driver' has
>> no member named 'date'
211 | .date = "20190618",
| ^~~~
>> drivers/accel/qaic/qaic_drv.c:211:35: error: initialization of 'unsigned
>> int' from 'char *' makes integer from pointer without a cast
>> [-Wint-conversion]
211 | .date = "20190618",
| ^~
drivers/accel/qaic/qaic_drv.c:211:35: note: (near initialization for
'qaic_accel_driver.driver_features')
>> drivers/accel/qaic/qaic_drv.c:211:35: error: initializer element is not
>> computable at load time
drivers/accel/qaic/qaic_drv.c:211:35: note: (near initialization for
'qaic_accel_driver.driver_features')
vim +211 drivers/accel/qaic/qaic_drv.c
c501ca23a6a306 Jeffrey Hugo 2023-03-27 205
c501ca23a6a306 Jeffrey Hugo 2023-03-27 206 static const struct drm_driver
qaic_accel_driver = {
c501ca23a6a306 Jeffrey Hugo 2023-03-27 207 .driver_features=
DRIVER_GEM | DRIVER_COMPUTE_ACCEL,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 208
c501ca23a6a306 Jeffrey Hugo 2023-03-27 209 .name =
QAIC_NAME,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 210 .desc =
QAIC_DESC,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 @211 .date =
"20190618",
c501ca23a6a306 Jeffrey Hugo 2023-03-27 212
c501ca23a6a306 Jeffrey Hugo 2023-03-27 213 .fops =
&qaic_accel_fops,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 214 .open =
qaic_open,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 215 .postclose =
qaic_postclose,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 216
c501ca23a6a306 Jeffrey Hugo 2023-03-27 217 .ioctls =
qaic_drm_ioctls,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 218 .num_ioctls =
ARRAY_SIZE(qaic_drm_ioctls),
c501ca23a6a306 Jeffrey Hugo 2023-03-27 219 .gem_prime_import =
qaic_gem_prime_import,
c501ca23a6a306 Jeffrey Hugo 2023-03-27 220 };
c501ca23a6a306 Jeffrey Hugo 2023-03-27 221
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH V2 drm-dp 4/4] drm/hisilicon/hibmc: add dp module in hibmc
Hi Yongbang, kernel test robot noticed the following build errors: [auto build test ERROR on drm-misc/drm-misc-next] [also build test ERROR on linus/master v6.12-rc4 next-20241024] [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/Yongbang-Shi/drm-hisilicon-hibmc-add-dp-aux-in-hibmc/20241022-204925 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20241022124148.1952761-5-shiyongbang%40huawei.com patch subject: [PATCH V2 drm-dp 4/4] drm/hisilicon/hibmc: add dp module in hibmc config: powerpc-randconfig-003-20241024 (https://download.01.org/0day-ci/archive/20241025/202410251136.1m7blr68-...@intel.com/config) compiler: powerpc-linux-gcc (GCC) 14.1.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241025/202410251136.1m7blr68-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410251136.1m7blr68-...@intel.com/ All errors (new ones prefixed by >>): powerpc-linux-ld: drivers/gpu/drm/hisilicon/hibmc/dp/dp_hw.o: in function `dp_link_cfg': >> dp_hw.c:(.text.dp_link_cfg+0x250): undefined reference to `__udivdi3' >> powerpc-linux-ld: dp_hw.c:(.text.dp_link_cfg+0x340): undefined reference to >> `__udivdi3' powerpc-linux-ld: dp_hw.c:(.text.dp_link_cfg+0x384): undefined reference to `__udivdi3' -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH 02/37] drm/vc4: Use of_device_get_match_data to set generation
Hi Dave,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 91e21479c81dd4e9e22a78d7446f92f6b96a7284]
url:
https://github.com/intel-lab-lkp/linux/commits/Dave-Stevenson/drm-vc4-Limit-max_bpc-to-8-on-Pi0-3/20241024-005239
base: 91e21479c81dd4e9e22a78d7446f92f6b96a7284
patch link:
https://lore.kernel.org/r/20241023-drm-vc4-2712-support-v1-2-1cc2d5594907%40raspberrypi.com
patch subject: [PATCH 02/37] drm/vc4: Use of_device_get_match_data to set
generation
config: um-allmodconfig
(https://download.01.org/0day-ci/archive/20241025/202410250459.oqaldqvp-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
5886454669c3c9026f7f27eab13509dd0241f2d6)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241025/202410250459.oqaldqvp-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410250459.oqaldqvp-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/gpu/drm/vc4/vc4_drv.c:27:
In file included from include/linux/dma-mapping.h:11:
In file included from include/linux/scatterlist.h:8:
In file included from include/linux/mm.h:2213:
include/linux/vmstat.h:518:36: warning: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
In file included from drivers/gpu/drm/vc4/vc4_drv.c:27:
In file included from include/linux/dma-mapping.h:11:
In file included from include/linux/scatterlist.h:9:
In file included from arch/um/include/asm/io.h:24:
include/asm-generic/io.h:548:31: warning: performing pointer arithmetic on a
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
548 | val = __raw_readb(PCI_IOBASE + addr);
| ~~ ^
include/asm-generic/io.h:561:61: warning: performing pointer arithmetic on a
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
561 | val = __le16_to_cpu((__le16 __force)__raw_readw(PCI_IOBASE +
addr));
| ~~ ^
include/uapi/linux/byteorder/little_endian.h:37:51: note: expanded from
macro '__le16_to_cpu'
37 | #define __le16_to_cpu(x) ((__force __u16)(__le16)(x))
| ^
In file included from drivers/gpu/drm/vc4/vc4_drv.c:27:
In file included from include/linux/dma-mapping.h:11:
In file included from include/linux/scatterlist.h:9:
In file included from arch/um/include/asm/io.h:24:
include/asm-generic/io.h:574:61: warning: performing pointer arithmetic on a
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
574 | val = __le32_to_cpu((__le32 __force)__raw_readl(PCI_IOBASE +
addr));
| ~~ ^
include/uapi/linux/byteorder/little_endian.h:35:51: note: expanded from
macro '__le32_to_cpu'
35 | #define __le32_to_cpu(x) ((__force __u32)(__le32)(x))
| ^
In file included from drivers/gpu/drm/vc4/vc4_drv.c:27:
In file included from include/linux/dma-mapping.h:11:
In file included from include/linux/scatterlist.h:9:
In file included from arch/um/include/asm/io.h:24:
include/asm-generic/io.h:585:33: warning: performing pointer arithmetic on a
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
585 | __raw_writeb(value, PCI_IOBASE + addr);
| ~~ ^
include/asm-generic/io.h:595:59: warning: performing pointer arithmetic on a
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
595 | __raw_writew((u16 __force)cpu_to_le16(value), PCI_IOBASE +
addr);
| ~~ ^
include/asm-generic/io.h:605:59: warning: performing pointer arithmetic on a
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
605 | __raw_writel((u32 __force)cpu_to_le32(value), PCI_IOBASE +
addr);
| ~~ ^
include/asm-generic/io.h:693:20: warning: performing pointer arithmetic on a
null pointer has undefined behavior [-Wnull-pointer-arithmetic]
693 | readsb(PCI_IOBASE + addr, buffer, count);
|~~ ^
include/asm-generic/io.h:701:20: warning: performing pointer arithmetic on a
null pointer has undefined behavior [-Wnull-
Re: [PATCH 2/7] drm/drv: Add drmm cgroup registration for dev cgroups.
Hi Maarten,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm/drm-next]
[also build test ERROR on drm-exynos/exynos-drm-next next-20241024]
[cannot apply to tj-cgroup/for-next drm-xe/drm-xe-next akpm-mm/mm-everything
drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next
drm-tip/drm-tip linus/master v6.12-rc4]
[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/Maarten-Lankhorst/kernel-cgroup-Add-dev-memory-accounting-cgroup/20241023-155504
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20241023075302.27194-3-maarten.lankhorst%40linux.intel.com
patch subject: [PATCH 2/7] drm/drv: Add drmm cgroup registration for dev
cgroups.
config: arm64-randconfig-002-20241024
(https://download.01.org/0day-ci/archive/20241024/202410242324.adtg6g0w-...@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241024/202410242324.adtg6g0w-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410242324.adtg6g0w-...@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/drm_drv.c:29:
include/linux/cgroup_dev.h:61:12: error: two or more data types in
declaration specifiers
61 | static int int dev_cgroup_try_charge(struct dev_cgroup_device *cgdev,
|^~~
include/linux/cgroup_dev.h:65:1: error: expected identifier or '(' before
'{' token
65 | {
| ^
>> include/linux/cgroup_dev.h:61:16: error: 'dev_cgroup_try_charge' declared
>> 'static' but never defined [-Werror=unused-function]
61 | static int int dev_cgroup_try_charge(struct dev_cgroup_device *cgdev,
|^
cc1: all warnings being treated as errors
vim +61 include/linux/cgroup_dev.h
487073b1855ef4 Maarten Lankhorst 2024-10-23 60
487073b1855ef4 Maarten Lankhorst 2024-10-23 @61 static int int
dev_cgroup_try_charge(struct dev_cgroup_device *cgdev,
487073b1855ef4 Maarten Lankhorst 2024-10-23 62
u32 index, u64 size,
487073b1855ef4 Maarten Lankhorst 2024-10-23 63
struct dev_cgroup_pool_state **ret_pool,
487073b1855ef4 Maarten Lankhorst 2024-10-23 64
struct dev_cgroup_pool_state **ret_limit_pool);
487073b1855ef4 Maarten Lankhorst 2024-10-23 65 {
487073b1855ef4 Maarten Lankhorst 2024-10-23 66 *ret_pool = NULL;
487073b1855ef4 Maarten Lankhorst 2024-10-23 67
487073b1855ef4 Maarten Lankhorst 2024-10-23 68 if (ret_limit_pool)
487073b1855ef4 Maarten Lankhorst 2024-10-23 69 *ret_limit_pool
= NULL;
487073b1855ef4 Maarten Lankhorst 2024-10-23 70
487073b1855ef4 Maarten Lankhorst 2024-10-23 71 return 0;
487073b1855ef4 Maarten Lankhorst 2024-10-23 72 }
487073b1855ef4 Maarten Lankhorst 2024-10-23 73
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH V2 drm-dp 1/4] drm/hisilicon/hibmc: add dp aux in hibmc
Hi Yongbang,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on linus/master v6.12-rc4 next-20241024]
[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/Yongbang-Shi/drm-hisilicon-hibmc-add-dp-aux-in-hibmc/20241022-204925
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20241022124148.1952761-2-shiyongbang%40huawei.com
patch subject: [PATCH V2 drm-dp 1/4] drm/hisilicon/hibmc: add dp aux in hibmc
config: arm64-randconfig-004-20241024
(https://download.01.org/0day-ci/archive/20241025/202410250305.uhkdhtxy-...@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241025/202410250305.uhkdhtxy-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410250305.uhkdhtxy-...@intel.com/
All errors (new ones prefixed by >>):
aarch64-linux-ld: drivers/gpu/drm/hisilicon/hibmc/dp/dp_aux.o: in function
`dp_aux_init':
>> drivers/gpu/drm/hisilicon/hibmc/dp/dp_aux.c:154: multiple definition of
>> `dp_aux_init'; drivers/gpu/drm/msm/dp/dp_aux.o:dp_aux.c:(.text+0x8a0): first
>> defined here
vim +154 drivers/gpu/drm/hisilicon/hibmc/dp/dp_aux.c
152
153 void dp_aux_init(struct dp_dev *dp)
> 154 {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 2/7] drm/drv: Add drmm cgroup registration for dev cgroups.
Hi Maarten,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm/drm-next]
[also build test ERROR on drm-exynos/exynos-drm-next next-20241024]
[cannot apply to tj-cgroup/for-next drm-xe/drm-xe-next akpm-mm/mm-everything
drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next
drm-tip/drm-tip linus/master v6.12-rc4]
[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/Maarten-Lankhorst/kernel-cgroup-Add-dev-memory-accounting-cgroup/20241023-155504
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20241023075302.27194-3-maarten.lankhorst%40linux.intel.com
patch subject: [PATCH 2/7] drm/drv: Add drmm cgroup registration for dev
cgroups.
config: x86_64-rhel-8.3
(https://download.01.org/0day-ci/archive/20241024/202410241806.p6u3fcgs-...@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/20241024/202410241806.p6u3fcgs-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410241806.p6u3fcgs-...@intel.com/
All error/warnings (new ones prefixed by >>):
In file included from drivers/gpu/drm/drm_drv.c:29:
>> include/linux/cgroup_dev.h:61:12: error: two or more data types in
>> declaration specifiers
61 | static int int dev_cgroup_try_charge(struct dev_cgroup_device *cgdev,
|^~~
>> include/linux/cgroup_dev.h:65:1: error: expected identifier or '(' before
>> '{' token
65 | {
| ^
>> include/linux/cgroup_dev.h:61:16: warning: 'dev_cgroup_try_charge' declared
>> 'static' but never defined [-Wunused-function]
61 | static int int dev_cgroup_try_charge(struct dev_cgroup_device *cgdev,
|^
vim +61 include/linux/cgroup_dev.h
487073b1855ef4 Maarten Lankhorst 2024-10-23 60
487073b1855ef4 Maarten Lankhorst 2024-10-23 @61 static int int
dev_cgroup_try_charge(struct dev_cgroup_device *cgdev,
487073b1855ef4 Maarten Lankhorst 2024-10-23 62
u32 index, u64 size,
487073b1855ef4 Maarten Lankhorst 2024-10-23 63
struct dev_cgroup_pool_state **ret_pool,
487073b1855ef4 Maarten Lankhorst 2024-10-23 64
struct dev_cgroup_pool_state **ret_limit_pool);
487073b1855ef4 Maarten Lankhorst 2024-10-23 @65 {
487073b1855ef4 Maarten Lankhorst 2024-10-23 66 *ret_pool = NULL;
487073b1855ef4 Maarten Lankhorst 2024-10-23 67
487073b1855ef4 Maarten Lankhorst 2024-10-23 68 if (ret_limit_pool)
487073b1855ef4 Maarten Lankhorst 2024-10-23 69 *ret_limit_pool
= NULL;
487073b1855ef4 Maarten Lankhorst 2024-10-23 70
487073b1855ef4 Maarten Lankhorst 2024-10-23 71 return 0;
487073b1855ef4 Maarten Lankhorst 2024-10-23 72 }
487073b1855ef4 Maarten Lankhorst 2024-10-23 73
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 5/5] drm/xe/pt: Add an additional check for dmabuf BOs while updating PTEs
Hi Vivek,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-xe/drm-xe-next]
[also build test ERROR on drm/drm-next drm-exynos/exynos-drm-next
drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next
drm-tip/drm-tip linus/master v6.12-rc4 next-20241022]
[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/Vivek-Kasireddy/PCI-P2PDMA-Don-t-enforce-ACS-check-for-functions-of-same-device/20241021-134804
base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link:
https://lore.kernel.org/r/20241021052236.1820329-6-vivek.kasireddy%40intel.com
patch subject: [PATCH v2 5/5] drm/xe/pt: Add an additional check for dmabuf BOs
while updating PTEs
config: i386-buildonly-randconfig-003-20241022
(https://download.01.org/0day-ci/archive/20241022/202410222048.8ihss8ie-...@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/20241022/202410222048.8ihss8ie-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410222048.8ihss8ie-...@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/xe/xe_pt.c: In function 'xe_pt_stage_bind':
>> drivers/gpu/drm/xe/xe_pt.c:682:25: error: implicit declaration of function
>> 'xe_res_first_dma'; did you mean 'xe_res_first_sg'?
>> [-Werror=implicit-function-declaration]
682 | xe_res_first_dma(bo->dma_addr,
xe_vma_bo_offset(vma),
| ^~~~
| xe_res_first_sg
cc1: some warnings being treated as errors
vim +682 drivers/gpu/drm/xe/xe_pt.c
583
584 /**
585 * xe_pt_stage_bind() - Build a disconnected page-table tree for a
given address
586 * range.
587 * @tile: The tile we're building for.
588 * @vma: The vma indicating the address range.
589 * @entries: Storage for the update entries used for connecting the
tree to
590 * the main tree at commit time.
591 * @num_entries: On output contains the number of @entries used.
592 *
593 * This function builds a disconnected page-table tree for a given
address
594 * range. The tree is connected to the main vm tree for the gpu using
595 * xe_migrate_update_pgtables() and for the cpu using
xe_pt_commit_bind().
596 * The function builds xe_vm_pgtable_update structures for already
existing
597 * shared page-tables, and non-existing shared and non-shared
page-tables
598 * are built and populated directly.
599 *
600 * Return 0 on success, negative error code on error.
601 */
602 static int
603 xe_pt_stage_bind(struct xe_tile *tile, struct xe_vma *vma,
604 struct xe_vm_pgtable_update *entries, u32 *num_entries)
605 {
606 struct xe_device *xe = tile_to_xe(tile);
607 struct xe_bo *bo = xe_vma_bo(vma);
608 bool is_devmem = !xe_vma_is_userptr(vma) && bo &&
609 (xe_bo_is_vram(bo) || xe_bo_is_stolen_devmem(bo));
610 struct xe_res_cursor curs;
611 struct xe_pt_stage_bind_walk xe_walk = {
612 .base = {
613 .ops = &xe_pt_stage_bind_ops,
614 .shifts = xe_normal_pt_shifts,
615 .max_level = XE_PT_HIGHEST_LEVEL,
616 },
617 .vm = xe_vma_vm(vma),
618 .tile = tile,
619 .curs = &curs,
620 .va_curs_start = xe_vma_start(vma),
621 .vma = vma,
622 .wupd.entries = entries,
623 .needs_64K = (xe_vma_vm(vma)->flags & XE_VM_FLAG_64K)
&& is_devmem,
624 };
625 struct xe_pt *pt = xe_vma_vm(vma)->pt_root[tile->id];
626 int ret;
627
628 /**
629 * Default atomic expectations for different allocation
scenarios are as follows:
630 *
631 * 1. Traditional API: When the VM is not in LR mode:
632 *- Device atomics are expected to function with all
allocations.
633 *
634 * 2. Compute/SVM API: When the VM is in LR mode:
635 *- Device atomics are the default behavior when the bo is
placed in a single region.
636 *- In all other cases device atomics will be di
Re: [PATCH v2 4/5] drm/xe/bo: Create new dma_addr array for dmabuf BOs associated with VFs
Hi Vivek, kernel test robot noticed the following build errors: [auto build test ERROR on drm-xe/drm-xe-next] [also build test ERROR on drm/drm-next drm-exynos/exynos-drm-next drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip linus/master v6.12-rc4 next-20241021] [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/Vivek-Kasireddy/PCI-P2PDMA-Don-t-enforce-ACS-check-for-functions-of-same-device/20241021-134804 base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next patch link: https://lore.kernel.org/r/20241021052236.1820329-5-vivek.kasireddy%40intel.com patch subject: [PATCH v2 4/5] drm/xe/bo: Create new dma_addr array for dmabuf BOs associated with VFs config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20241022/202410221832.r04dr21j-...@intel.com/config) compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241022/202410221832.r04dr21j-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410221832.r04dr21j-...@intel.com/ All errors (new ones prefixed by >>): >> drivers/gpu/drm/xe/xe_bo.c:591:15: error: subscript of pointer to incomplete >> type 'struct drm_pagemap_dma_addr' 591 | bo->dma_addr[i] = drm_pagemap_dma_addr_encode(addr, | ^ drivers/gpu/drm/xe/xe_bo_types.h:78:9: note: forward declaration of 'struct drm_pagemap_dma_addr' 78 | struct drm_pagemap_dma_addr *dma_addr; |^ >> drivers/gpu/drm/xe/xe_bo.c:591:21: error: call to undeclared function >> 'drm_pagemap_dma_addr_encode'; ISO C99 and later do not support implicit >> function declarations [-Wimplicit-function-declaration] 591 | bo->dma_addr[i] = drm_pagemap_dma_addr_encode(addr, | ^ >> drivers/gpu/drm/xe/xe_bo.c:592:7: error: use of undeclared identifier >> 'DRM_INTERCONNECT_DRIVER' 592 | DRM_INTERCONNECT_DRIVER, | ^ >> drivers/gpu/drm/xe/xe_bo.c:626:48: error: invalid application of 'sizeof' to >> an incomplete type 'struct drm_pagemap_dma_addr' 626 | bo->dma_addr = kmalloc_array(sg->nents, sizeof(*bo->dma_addr), | ^~~ include/linux/slab.h:925:63: note: expanded from macro 'kmalloc_array' 925 | #define kmalloc_array(...) alloc_hooks(kmalloc_array_noprof(__VA_ARGS__)) | ^~~ include/linux/alloc_tag.h:210:31: note: expanded from macro 'alloc_hooks' 210 | alloc_hooks_tag(&_alloc_tag, _do_alloc); \ | ^ include/linux/alloc_tag.h:202:9: note: expanded from macro 'alloc_hooks_tag' 202 | typeof(_do_alloc) _res = _do_alloc; \ |^ drivers/gpu/drm/xe/xe_bo_types.h:78:9: note: forward declaration of 'struct drm_pagemap_dma_addr' 78 | struct drm_pagemap_dma_addr *dma_addr; |^ >> drivers/gpu/drm/xe/xe_bo.c:626:48: error: invalid application of 'sizeof' to >> an incomplete type 'struct drm_pagemap_dma_addr' 626 | bo->dma_addr = kmalloc_array(sg->nents, sizeof(*bo->dma_addr), | ^~~ include/linux/slab.h:925:63: note: expanded from macro 'kmalloc_array' 925 | #define kmalloc_array(...) alloc_hooks(kmalloc_array_noprof(__VA_ARGS__)) | ^~~ include/linux/alloc_tag.h:210:31: note: expanded from macro 'alloc_hooks' 210 | alloc_hooks_tag(&_alloc_tag, _do_alloc); \ | ^ include/linux/alloc_tag.h:202:27: note: expanded from macro 'alloc_hooks_tag' 202 | typeof(_do_allo
Re: [PATCH v2 4/5] drm/xe/bo: Create new dma_addr array for dmabuf BOs associated with VFs
Hi Vivek, kernel test robot noticed the following build errors: [auto build test ERROR on drm-xe/drm-xe-next] [also build test ERROR on drm/drm-next drm-exynos/exynos-drm-next drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip linus/master v6.12-rc4 next-20241021] [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/Vivek-Kasireddy/PCI-P2PDMA-Don-t-enforce-ACS-check-for-functions-of-same-device/20241021-134804 base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next patch link: https://lore.kernel.org/r/20241021052236.1820329-5-vivek.kasireddy%40intel.com patch subject: [PATCH v2 4/5] drm/xe/bo: Create new dma_addr array for dmabuf BOs associated with VFs config: i386-buildonly-randconfig-003-20241022 (https://download.01.org/0day-ci/archive/20241022/202410221702.flgkndgm-...@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/20241022/202410221702.flgkndgm-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410221702.flgkndgm-...@intel.com/ All errors (new ones prefixed by >>): drivers/gpu/drm/xe/xe_bo.c: In function 'xe_bo_translate_iova_to_dpa': >> drivers/gpu/drm/xe/xe_bo.c:591:29: error: invalid use of undefined type >> 'struct drm_pagemap_dma_addr' 591 | bo->dma_addr[i] = drm_pagemap_dma_addr_encode(addr, | ^ >> drivers/gpu/drm/xe/xe_bo.c:591:35: error: implicit declaration of function >> 'drm_pagemap_dma_addr_encode' [-Werror=implicit-function-declaration] 591 | bo->dma_addr[i] = drm_pagemap_dma_addr_encode(addr, | ^~~ >> drivers/gpu/drm/xe/xe_bo.c:592:49: error: 'DRM_INTERCONNECT_DRIVER' >> undeclared (first use in this function) 592 | DRM_INTERCONNECT_DRIVER, | ^~~ drivers/gpu/drm/xe/xe_bo.c:592:49: note: each undeclared identifier is reported only once for each function it appears in drivers/gpu/drm/xe/xe_bo.c:591:33: error: invalid use of undefined type 'struct drm_pagemap_dma_addr' 591 | bo->dma_addr[i] = drm_pagemap_dma_addr_encode(addr, | ^ In file included from include/linux/percpu.h:5, from arch/x86/include/asm/msr.h:15, from arch/x86/include/asm/tsc.h:10, from arch/x86/include/asm/timex.h:6, from include/linux/timex.h:67, from include/linux/time32.h:13, from include/linux/time.h:60, from include/linux/jiffies.h:10, from include/linux/ktime.h:25, from include/linux/timer.h:6, from include/linux/workqueue.h:9, from include/linux/mm_types.h:19, from include/linux/mmzone.h:22, from include/linux/gfp.h:7, from include/linux/mm.h:7, from include/linux/pagemap.h:8, from include/drm/ttm/ttm_tt.h:30, from drivers/gpu/drm/xe/xe_bo.h:9, from drivers/gpu/drm/xe/xe_bo.c:6: drivers/gpu/drm/xe/xe_bo.c: In function 'xe_bo_sg_to_dma_addr_array': >> drivers/gpu/drm/xe/xe_bo.c:626:55: error: invalid application of 'sizeof' to >> incomplete type 'struct drm_pagemap_dma_addr' 626 | bo->dma_addr = kmalloc_array(sg->nents, sizeof(*bo->dma_addr), | ^ include/linux/alloc_tag.h:202:16: note: in definition of macro 'alloc_hooks_tag' 202 | typeof(_do_alloc) _res = _do_alloc; \ |^ include/linux/slab.h:925:49: note: in expansion of macro 'alloc_hooks' 925 | #define kmalloc_array(...) alloc_hooks(kmalloc_array_noprof(__VA_ARGS__)) | ^~~ drivers/gpu/drm/xe/xe_bo.c:626:24: note: in expansion of macro 'kmalloc_array' 626 | bo->dma_addr = kmalloc_array(sg->nents, sizeof(*bo->dma_addr), |
Re: [PATCH v6 03/10] drm/bridge: it6505: add AUX operation for HDCP KSV list read
Hi Hermes,
kernel test robot noticed the following build errors:
[auto build test ERROR on b8128f7815ff135f0333c1b46dcdf1543c41b860]
url:
https://github.com/intel-lab-lkp/linux/commits/Hermes-Wu-via-B4-Relay/drm-bridge-it6505-Change-definition-of-AUX_FIFO_MAX_SIZE/20241016-155607
base: b8128f7815ff135f0333c1b46dcdf1543c41b860
patch link:
https://lore.kernel.org/r/20241016-upstream-v6-v6-3-4d93a0c46de1%40ite.com.tw
patch subject: [PATCH v6 03/10] drm/bridge: it6505: add AUX operation for HDCP
KSV list read
config: m68k-allmodconfig
(https://download.01.org/0day-ci/archive/20241020/202410200624.sr8sf1ya-...@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241020/202410200624.sr8sf1ya-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410200624.sr8sf1ya-...@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/bridge/ite-it6505.c: In function 'it6505_aux_operation':
>> drivers/gpu/drm/bridge/ite-it6505.c:1004:47: error: implicit declaration of
>> function 'FIELD_GET' [-Wimplicit-function-declaration]
1004 | it6505_write(it6505, REG_AUX_CMD_REQ,
FIELD_GET(M_AUX_REQ_CMD, cmd));
| ^
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for GET_FREE_REGION
Depends on [n]: SPARSEMEM [=n]
Selected by [m]:
- RESOURCE_KUNIT_TEST [=m] && RUNTIME_TESTING_MENU [=y] && KUNIT [=m]
vim +/FIELD_GET +1004 drivers/gpu/drm/bridge/ite-it6505.c
956
957 static ssize_t it6505_aux_operation(struct it6505 *it6505,
958 enum aux_cmd_type cmd,
959 unsigned int address, u8 *buffer,
960 size_t size, enum aux_cmd_reply
*reply)
961 {
962 int i, ret;
963 bool aux_write_check = false;
964
965 if (!it6505_get_sink_hpd_status(it6505))
966 return -EIO;
967
968 /* set AUX user mode */
969 it6505_set_bits(it6505, REG_AUX_CTRL, AUX_USER_MODE,
AUX_USER_MODE);
970
971 aux_op_start:
972 /* HW AUX FIFO supports only EDID and DCPD KSV FIFO area */
973 if (cmd == CMD_AUX_I2C_EDID_READ || cmd ==
CMD_AUX_GET_KSV_LIST) {
974 /* AUX EDID FIFO has max length of AUX_FIFO_MAX_SIZE
bytes. */
975 size = min_t(size_t, size, AUX_FIFO_MAX_SIZE);
976 /* Enable AUX FIFO read back and clear FIFO */
977 it6505_set_bits(it6505, REG_AUX_CTRL,
978 AUX_EN_FIFO_READ | CLR_EDID_FIFO,
979 AUX_EN_FIFO_READ | CLR_EDID_FIFO);
980
981 it6505_set_bits(it6505, REG_AUX_CTRL,
982 AUX_EN_FIFO_READ | CLR_EDID_FIFO,
983 AUX_EN_FIFO_READ);
984 } else {
985 /* The DP AUX transmit buffer has 4 bytes. */
986 size = min_t(size_t, size, 4);
987 it6505_set_bits(it6505, REG_AUX_CTRL, AUX_NO_SEGMENT_WR,
988 AUX_NO_SEGMENT_WR);
989 }
990
991 /* Start Address[7:0] */
992 it6505_write(it6505, REG_AUX_ADR_0_7, (address >> 0) & 0xFF);
993 /* Start Address[15:8] */
994 it6505_write(it6505, REG_AUX_ADR_8_15, (address >> 8) & 0xFF);
995 /* WriteNum[3:0]+StartAdr[19:16] */
996 it6505_write(it6505, REG_AUX_ADR_16_19,
997 ((address >> 16) & 0x0F) | ((size - 1) << 4));
998
999 if (cmd == CMD_AUX_NATIVE_WRITE)
1000 regmap_bulk_write(it6505->regmap, REG_AUX_OUT_DATA0,
buffer,
1001size);
1002
1003 /* Aux Fire */
> 1004 it6505_write(it6505, REG_AUX_CMD_REQ, FIELD_GET(M_AUX_REQ_CMD,
> cmd));
1005
1006 ret = it6505_aux_wait(it6505);
1007 if (ret < 0)
1008 goto aux_op_err;
1009
1010 ret = it6505_read(it6505, REG_AUX_ERROR_STS);
1011 if (ret < 0)
1012 goto aux_op_err;
1013
1014 switch ((ret >> 6) & 0x3) {
1015 case 0:
1016 *reply = REPLY_ACK;
1017 break;
1018 case 1:
1019 *reply = REPLY_DEFER;
1020 ret = -EAGAIN;
1021 goto aux_op_e
Re: [PATCH v6 03/10] drm/bridge: it6505: add AUX operation for HDCP KSV list read
Hi Hermes, kernel test robot noticed the following build errors: [auto build test ERROR on b8128f7815ff135f0333c1b46dcdf1543c41b860] url: https://github.com/intel-lab-lkp/linux/commits/Hermes-Wu-via-B4-Relay/drm-bridge-it6505-Change-definition-of-AUX_FIFO_MAX_SIZE/20241016-155607 base: b8128f7815ff135f0333c1b46dcdf1543c41b860 patch link: https://lore.kernel.org/r/20241016-upstream-v6-v6-3-4d93a0c46de1%40ite.com.tw patch subject: [PATCH v6 03/10] drm/bridge: it6505: add AUX operation for HDCP KSV list read config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20241020/202410200756.klsple8a-...@intel.com/config) compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project bfe84f7085d82d06d61c632a7bad1e692fd159e4) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241020/202410200756.klsple8a-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410200756.klsple8a-...@intel.com/ All errors (new ones prefixed by >>): In file included from drivers/gpu/drm/bridge/ite-it6505.c:13: In file included from include/linux/i2c.h:19: In file included from include/linux/regulator/consumer.h:35: In file included from include/linux/suspend.h:5: In file included from include/linux/swap.h:9: In file included from include/linux/memcontrol.h:13: In file included from include/linux/cgroup.h:26: In file included from include/linux/kernel_stat.h:8: In file included from include/linux/interrupt.h:11: In file included from include/linux/hardirq.h:11: In file included from ./arch/hexagon/include/generated/asm/hardirq.h:1: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:14: In file included from arch/hexagon/include/asm/io.h:328: include/asm-generic/io.h:548:31: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 548 | val = __raw_readb(PCI_IOBASE + addr); | ~~ ^ include/asm-generic/io.h:561:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 561 | val = __le16_to_cpu((__le16 __force)__raw_readw(PCI_IOBASE + addr)); | ~~ ^ include/uapi/linux/byteorder/little_endian.h:37:51: note: expanded from macro '__le16_to_cpu' 37 | #define __le16_to_cpu(x) ((__force __u16)(__le16)(x)) | ^ In file included from drivers/gpu/drm/bridge/ite-it6505.c:13: In file included from include/linux/i2c.h:19: In file included from include/linux/regulator/consumer.h:35: In file included from include/linux/suspend.h:5: In file included from include/linux/swap.h:9: In file included from include/linux/memcontrol.h:13: In file included from include/linux/cgroup.h:26: In file included from include/linux/kernel_stat.h:8: In file included from include/linux/interrupt.h:11: In file included from include/linux/hardirq.h:11: In file included from ./arch/hexagon/include/generated/asm/hardirq.h:1: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:14: In file included from arch/hexagon/include/asm/io.h:328: include/asm-generic/io.h:574:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 574 | val = __le32_to_cpu((__le32 __force)__raw_readl(PCI_IOBASE + addr)); | ~~ ^ include/uapi/linux/byteorder/little_endian.h:35:51: note: expanded from macro '__le32_to_cpu' 35 | #define __le32_to_cpu(x) ((__force __u32)(__le32)(x)) | ^ In file included from drivers/gpu/drm/bridge/ite-it6505.c:13: In file included from include/linux/i2c.h:19: In file included from include/linux/regulator/consumer.h:35: In file included from include/linux/suspend.h:5: In file included from include/linux/swap.h:9: In file included from include/linux/memcontrol.h:13: In file included from include/linux/cgroup.h:26: In file included from include/linux/kernel_stat.h:8: In file included from include/linux/interrupt.h:11: In file included from include/linux/hardirq.h:11: In file included from ./arch/hexagon/include/generated/asm/hardirq.h:1: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include
Re: [PATCH v1 5/5] i2c: i2c-qcom-geni: Add Block event interrupt support
Hi Jyothi, kernel test robot noticed the following build errors: [auto build test ERROR on 55bcd2e0d04c1171d382badef1def1fd04ef66c5] url: https://github.com/intel-lab-lkp/linux/commits/Jyothi-Kumar-Seerapu/dt-bindings-dmaengine-qcom-gpi-Add-additional-arg-to-dma-cell-property/20241015-202637 base: 55bcd2e0d04c1171d382badef1def1fd04ef66c5 patch link: https://lore.kernel.org/r/20241015120750.21217-6-quic_jseerapu%40quicinc.com patch subject: [PATCH v1 5/5] i2c: i2c-qcom-geni: Add Block event interrupt support config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20241019/202410191055.bi1pwtay-...@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/20241019/202410191055.bi1pwtay-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410191055.bi1pwtay-...@intel.com/ All errors (new ones prefixed by >>, old ones prefixed by <<): >> ERROR: modpost: "gpi_multi_desc_process" >> [drivers/i2c/busses/i2c-qcom-geni.ko] undefined! Kconfig warnings: (for reference only) WARNING: unmet direct dependencies detected for GET_FREE_REGION Depends on [n]: SPARSEMEM [=n] Selected by [m]: - RESOURCE_KUNIT_TEST [=m] && RUNTIME_TESTING_MENU [=y] && KUNIT [=m] WARNING: unmet direct dependencies detected for OMAP2PLUS_MBOX Depends on [n]: MAILBOX [=y] && (ARCH_OMAP2PLUS || ARCH_K3) Selected by [m]: - TI_K3_M4_REMOTEPROC [=m] && REMOTEPROC [=y] && (ARCH_K3 || COMPILE_TEST [=y]) -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v1 5/5] i2c: i2c-qcom-geni: Add Block event interrupt support
Hi Jyothi,
kernel test robot noticed the following build errors:
[auto build test ERROR on 55bcd2e0d04c1171d382badef1def1fd04ef66c5]
url:
https://github.com/intel-lab-lkp/linux/commits/Jyothi-Kumar-Seerapu/dt-bindings-dmaengine-qcom-gpi-Add-additional-arg-to-dma-cell-property/20241015-202637
base: 55bcd2e0d04c1171d382badef1def1fd04ef66c5
patch link:
https://lore.kernel.org/r/20241015120750.21217-6-quic_jseerapu%40quicinc.com
patch subject: [PATCH v1 5/5] i2c: i2c-qcom-geni: Add Block event interrupt
support
config: x86_64-allyesconfig
(https://download.01.org/0day-ci/archive/20241019/202410190549.hgafbyqg-...@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project
3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241019/202410190549.hgafbyqg-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410190549.hgafbyqg-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/i2c/busses/i2c-qcom-geni.c:562:8: error: incompatible pointer to
>> integer conversion passing 'dma_addr_t *' (aka 'unsigned long long *') to
>> parameter of type 'dma_addr_t' (aka 'unsigned long long'); dereference with
>> * [-Wint-conversion]
562 |tx_multi_xfer->dma_addr[wr_idx],
NULL, NULL);
|^~~
|*
drivers/i2c/busses/i2c-qcom-geni.c:519:36: note: passing argument to
parameter 'tx_addr' here
519 |void *tx_buf, dma_addr_t tx_addr,
| ^
>> drivers/i2c/busses/i2c-qcom-geni.c:562:47: error: incompatible pointer to
>> integer conversion passing 'void *' to parameter of type 'dma_addr_t' (aka
>> 'unsigned long long') [-Wint-conversion]
562 |tx_multi_xfer->dma_addr[wr_idx],
NULL, NULL);
|
^~~~
include/linux/stddef.h:8:14: note: expanded from macro 'NULL'
8 | #define NULL ((void *)0)
| ^~~
drivers/i2c/busses/i2c-qcom-geni.c:520:36: note: passing argument to
parameter 'rx_addr' here
520 |void *rx_buf, dma_addr_t rx_addr)
| ^
>> drivers/i2c/busses/i2c-qcom-geni.c:586:7: error: incompatible pointer to
>> integer conversion assigning to 'dma_addr_t' (aka 'unsigned long long') from
>> 'dma_addr_t *' (aka 'unsigned long long *'); dereference with *
>> [-Wint-conversion]
586 | addr = gi2c_gpi_xfer->dma_addr[gi2c_gpi_xfer->buf_idx];
| ^ ~~~
|*
3 errors generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for OMAP2PLUS_MBOX
Depends on [n]: MAILBOX [=y] && (ARCH_OMAP2PLUS || ARCH_K3)
Selected by [y]:
- TI_K3_M4_REMOTEPROC [=y] && REMOTEPROC [=y] && (ARCH_K3 || COMPILE_TEST
[=y])
vim +562 drivers/i2c/busses/i2c-qcom-geni.c
532
533 /**
534 * gpi_i2c_multi_desc_unmap() - unmaps the buffers post multi message
TX transfers
535 * @dev: pointer to the corresponding dev node
536 * @gi2c: i2c dev handle
537 * @msgs: i2c messages array
538 * @peripheral: pointer to the gpi_i2c_config
539 */
540 static void gpi_i2c_multi_desc_unmap(struct geni_i2c_dev *gi2c, struct
i2c_msg msgs[],
541 struct gpi_i2c_config *peripheral)
542 {
543 u32 msg_xfer_cnt, wr_idx = 0;
544 struct gpi_multi_xfer *tx_multi_xfer = &peripheral->multi_xfer;
545
546 /*
547 * In error case, need to unmap all messages based on the
msg_idx_cnt.
548 * Non-error case unmap all the processed messages.
549 */
550 if (gi2c->err)
551 msg_xfer_cnt = tx_multi_xfer->msg_idx_cnt;
552 else
553 msg_xfer_cnt = tx_multi_xfer->irq_cnt *
NUM_MSGS_PER_IRQ;
554
555 /* Unmap the processed DMA buffers based on the received
interrupt count */
556 for (; tx_multi_xfer->unmap_msg_cnt < msg_xfer_cnt;
tx_multi_xfer->unmap_msg_cnt++) {
557
Re: [PATCH 1/3] drm/connector: hdmi: Fix memory leak in drm_display_mode_from_cea_vic()
Hi Jinjie, kernel test robot noticed the following build warnings: [auto build test WARNING on drm-misc/drm-misc-next] [also build test WARNING on linus/master v6.12-rc3 next-20241017] [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/Jinjie-Ruan/drm-connector-hdmi-Fix-memory-leak-in-drm_display_mode_from_cea_vic/20241014-152022 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20241014071632.989108-2-ruanjinjie%40huawei.com patch subject: [PATCH 1/3] drm/connector: hdmi: Fix memory leak in drm_display_mode_from_cea_vic() config: arc-randconfig-002-20241017 (https://download.01.org/0day-ci/archive/20241018/202410180830.oitxtsov-...@intel.com/config) compiler: arc-elf-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241018/202410180830.oitxtsov-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410180830.oitxtsov-...@intel.com/ All warnings (new ones prefixed by >>): drivers/gpu/drm/tests/drm_connector_test.c: In function 'drm_test_drm_hdmi_compute_mode_clock_rgb': >> drivers/gpu/drm/tests/drm_connector_test.c:1008:31: warning: passing >> argument 2 of 'drm_mode_destroy' discards 'const' qualifier from pointer >> target type [-Wdiscarded-qualifiers] 1008 | drm_mode_destroy(drm, mode); | ^~~~ In file included from drivers/gpu/drm/tests/drm_connector_test.c:13: include/drm/drm_modes.h:456:72: note: expected 'struct drm_display_mode *' but argument is of type 'const struct drm_display_mode *' 456 | void drm_mode_destroy(struct drm_device *dev, struct drm_display_mode *mode); | ~^~~~ drivers/gpu/drm/tests/drm_connector_test.c: In function 'drm_test_drm_hdmi_compute_mode_clock_rgb_10bpc': drivers/gpu/drm/tests/drm_connector_test.c:1031:31: warning: passing argument 2 of 'drm_mode_destroy' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] 1031 | drm_mode_destroy(drm, mode); | ^~~~ include/drm/drm_modes.h:456:72: note: expected 'struct drm_display_mode *' but argument is of type 'const struct drm_display_mode *' 456 | void drm_mode_destroy(struct drm_device *dev, struct drm_display_mode *mode); | ~^~~~ drivers/gpu/drm/tests/drm_connector_test.c: In function 'drm_test_drm_hdmi_compute_mode_clock_rgb_10bpc_vic_1': drivers/gpu/drm/tests/drm_connector_test.c:1051:31: warning: passing argument 2 of 'drm_mode_destroy' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] 1051 | drm_mode_destroy(drm, mode); | ^~~~ include/drm/drm_modes.h:456:72: note: expected 'struct drm_display_mode *' but argument is of type 'const struct drm_display_mode *' 456 | void drm_mode_destroy(struct drm_device *dev, struct drm_display_mode *mode); | ~^~~~ drivers/gpu/drm/tests/drm_connector_test.c: In function 'drm_test_drm_hdmi_compute_mode_clock_rgb_12bpc': drivers/gpu/drm/tests/drm_connector_test.c:1074:31: warning: passing argument 2 of 'drm_mode_destroy' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] 1074 | drm_mode_destroy(drm, mode); | ^~~~ include/drm/drm_modes.h:456:72: note: expected 'struct drm_display_mode *' but argument is of type 'const struct drm_display_mode *' 456 | void drm_mode_destroy(struct drm_device *dev, struct drm_display_mode *mode); | ~^~~~ drivers/gpu/drm/tests/drm_connector_test.c: In function 'drm_test_drm_hdmi_compute_mode_clock_rgb_12bpc_vic_1': drivers/gpu/drm/tests/drm_connector_test.c:1094:31: warning: passing argument 2 of 'drm_mode_destroy' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] 1094 | drm_mode_destroy(drm, mode);
[linux-next:master] [drm/tests] 2735d5e406: WARNING:at_drivers/gpu/drm/drm_framebuffer.c:#drm_framebuffer_init[drm]
Hello,
kernel test robot noticed
"WARNING:at_drivers/gpu/drm/drm_framebuffer.c:#drm_framebuffer_init[drm]" on:
commit: 2735d5e4060960c7bd06698b0a1990c7d42c762e ("drm/tests: Add test for
drm_framebuffer_init()")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 15e7d45e786a62a211dd0098fee7c57f84f8c681]
in testcase: kunit
version:
with following parameters:
group: group-00
config: x86_64-rhel-8.3-kunit
compiler: gcc-12
test machine: 4 threads 1 sockets Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (Ivy
Bridge) with 8G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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
| Closes: https://lore.kernel.org/oe-lkp/202410171619.be977af4-...@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20241017/202410171619.be977af4-...@intel.com
kern :warn : [ 111.593780] [ cut here ]
kern :warn : [ 111.593995] WARNING: CPU: 0 PID: 4859 at
drivers/gpu/drm/drm_framebuffer.c:867 drm_framebuffer_init+0x40/0x380 [drm]
kern :warn : [ 111.594323] Modules linked in: drm_framebuffer_test
drm_kunit_helpers linear_ranges intel_rapl_msr intel_rapl_common
x86_pkg_temp_thermal intel_powerclamp btrfs coretemp kvm_intel kvm
blake2b_generic xor raid6_pq libcrc32c crct10dif_pclmul crc32_generic
crc32_pclmul crc32c_intel ghash_clmulni_intel sd_mod sha512_ssse3 sg rapl
ipmi_devintf intel_cstate ipmi_msghandler i915 ahci intel_uncore mei_me ttm
intel_gtt libahci mei drm_display_helper libata drm_kms_helper drm_buddy video
wmi drm fuse ip_tables [last unloaded: drm_format_test]
kern :warn : [ 111.595499] CPU: 0 UID: 0 PID: 4859 Comm: kunit_try_catch
Tainted: G S BN 6.11.0-rc7-01410-g2735d5e40609 #1
kern :warn : [ 111.595716] Tainted: [S]=CPU_OUT_OF_SPEC, [B]=BAD_PAGE,
[N]=TEST
kern :warn : [ 111.595842] Hardware name: Hewlett-Packard p6-1451cx/2ADA,
BIOS 8.15 02/05/2013
kern :warn : [ 111.595990] RIP: 0010:drm_framebuffer_init+0x40/0x380 [drm]
kern :warn : [ 111.596223] Code: 56 41 55 49 89 d5 48 89 f2 41 54 48 c1 ea
03 55 48 89 fd 53 48 89 f3 48 83 ec 10 80 3c 02 00 0f 85 54 02 00 00 48 39 2b
74 1e <0f> 0b 41 bc ea ff ff ff 48 83 c4 10 44 89 e0 5b 5d 41 5c 41 5d 41
kern :warn : [ 111.596572] RSP: 0018:c9edfbd0 EFLAGS: 00210246
kern :warn : [ 111.596689] RAX: dc00 RBX: c9edfcc0 RCX:
kern :warn : [ 111.596835] RDX: 1920001dbfa1 RSI: c9edfcc0 RDI:
c9edfd08
kern :warn : [ 111.596979] RBP: 888103087000 R08: 888103087000 R09:
888217ec9100
kern :warn : [ 111.597126] R10: 0003 R11: 00657361656c6572 R12:
1920001dbfc0
kern :warn : [ 111.597272] R13: c9edfc40 R14: R15:
c9edfe40
kern :warn : [ 111.597416] FS: ()
GS:8881c0e0() knlGS:
kern :warn : [ 111.597592] CS: 0010 DS: ES: CR0: 80050033
kern :warn : [ 111.597714] CR2: f7293000 CR3: 0001310c6001 CR4:
001706f0
kern :warn : [ 111.597859] DR0: 874243e0 DR1: 874243e1 DR2:
874243e3
kern :warn : [ 111.598004] DR3: 874243e5 DR6: 0ff0 DR7:
0600
kern :warn : [ 111.598149] Call Trace:
kern :warn : [ 111.598217]
kern :warn : [ 111.598278] ? __warn+0xcc/0x260
kern :warn : [ 111.598365] ? drm_framebuffer_init+0x40/0x380 [drm]
kern :warn : [ 111.598594] ? report_bug+0x261/0x2c0
kern :warn : [ 111.598686] ? handle_bug+0x3c/0x70
kern :warn : [ 111.598773] ? exc_invalid_op+0x17/0x40
kern :warn : [ 111.598867] ? asm_exc_invalid_op+0x1a/0x20
kern :warn : [ 111.598969] ? drm_framebuffer_init+0x40/0x380 [drm]
kern :warn : [ 111.599186] ? _raw_spin_lock_irqsave+0x8b/0xf0
kern :warn : [ 111.599291] drm_test_framebuffer_init_bad_format+0xf0/0x220
[drm_framebuffer_test]
kern :warn : [ 111.599451] ? __drmm_add_action+0x14b/0x280 [drm]
kern :warn : [ 111.599678] ?
__pfx_drm_test_framebuffer_init_bad_format+0x10/0x10 [drm_framebuffer_test]
kern :warn : [ 111.599849] ? __pfx_drm_mode_config_init_release+0x10/0x10
[drm]
kern :warn : [ 111.600082] ? __drmm_add_action+0x1a1/0x280 [drm]
kern :warn : [ 111.600295] ? __pfx_drm_mode_config_init_release+0x10/0x10
[drm]
kern :warn : [ 111.600543] ? __schedule+0x7ec/0x1950
kern :warn : [ 111.600635] ? __pfx_read_tsc+0x10/0x10
kern :warn : [ 111.600728] ? ktime_get_ts64+0x82/0x230
kern :warn : [ 111.600823] kunit_try_run_case+0x1b3/0x490
kern :warn : [ 111.600923] ? __pfx_kunit_try_run_case+0x10/0x10
kern :warn : [ 111.601031] ? set_cpus_allowed_ptr+0x85/0xc0
ke
Re: [PATCH 1/3] drm/connector: hdmi: Fix memory leak in drm_display_mode_from_cea_vic()
Hi Jinjie, kernel test robot noticed the following build warnings: [auto build test WARNING on drm-misc/drm-misc-next] [also build test WARNING on linus/master v6.12-rc3 next-20241017] [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/Jinjie-Ruan/drm-connector-hdmi-Fix-memory-leak-in-drm_display_mode_from_cea_vic/20241014-152022 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20241014071632.989108-2-ruanjinjie%40huawei.com patch subject: [PATCH 1/3] drm/connector: hdmi: Fix memory leak in drm_display_mode_from_cea_vic() config: x86_64-randconfig-121-20241017 (https://download.01.org/0day-ci/archive/20241018/202410180045.ubklh7fi-...@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/20241018/202410180045.ubklh7fi-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410180045.ubklh7fi-...@intel.com/ sparse warnings: (new ones prefixed by >>) >> drivers/gpu/drm/tests/drm_connector_test.c:1008:31: sparse: sparse: >> incorrect type in argument 2 (different modifiers) @@ expected struct >> drm_display_mode *mode @@ got struct drm_display_mode const *[assigned] >> mode @@ drivers/gpu/drm/tests/drm_connector_test.c:1008:31: sparse: expected struct drm_display_mode *mode drivers/gpu/drm/tests/drm_connector_test.c:1008:31: sparse: got struct drm_display_mode const *[assigned] mode drivers/gpu/drm/tests/drm_connector_test.c:1031:31: sparse: sparse: incorrect type in argument 2 (different modifiers) @@ expected struct drm_display_mode *mode @@ got struct drm_display_mode const *[assigned] mode @@ drivers/gpu/drm/tests/drm_connector_test.c:1031:31: sparse: expected struct drm_display_mode *mode drivers/gpu/drm/tests/drm_connector_test.c:1031:31: sparse: got struct drm_display_mode const *[assigned] mode drivers/gpu/drm/tests/drm_connector_test.c:1051:31: sparse: sparse: incorrect type in argument 2 (different modifiers) @@ expected struct drm_display_mode *mode @@ got struct drm_display_mode const *[assigned] mode @@ drivers/gpu/drm/tests/drm_connector_test.c:1051:31: sparse: expected struct drm_display_mode *mode drivers/gpu/drm/tests/drm_connector_test.c:1051:31: sparse: got struct drm_display_mode const *[assigned] mode drivers/gpu/drm/tests/drm_connector_test.c:1074:31: sparse: sparse: incorrect type in argument 2 (different modifiers) @@ expected struct drm_display_mode *mode @@ got struct drm_display_mode const *[assigned] mode @@ drivers/gpu/drm/tests/drm_connector_test.c:1074:31: sparse: expected struct drm_display_mode *mode drivers/gpu/drm/tests/drm_connector_test.c:1074:31: sparse: got struct drm_display_mode const *[assigned] mode drivers/gpu/drm/tests/drm_connector_test.c:1094:31: sparse: sparse: incorrect type in argument 2 (different modifiers) @@ expected struct drm_display_mode *mode @@ got struct drm_display_mode const *[assigned] mode @@ drivers/gpu/drm/tests/drm_connector_test.c:1094:31: sparse: expected struct drm_display_mode *mode drivers/gpu/drm/tests/drm_connector_test.c:1094:31: sparse: got struct drm_display_mode const *[assigned] mode drivers/gpu/drm/tests/drm_connector_test.c:1117:31: sparse: sparse: incorrect type in argument 2 (different modifiers) @@ expected struct drm_display_mode *mode @@ got struct drm_display_mode const *[assigned] mode @@ drivers/gpu/drm/tests/drm_connector_test.c:1117:31: sparse: expected struct drm_display_mode *mode drivers/gpu/drm/tests/drm_connector_test.c:1117:31: sparse: got struct drm_display_mode const *[assigned] mode drivers/gpu/drm/tests/drm_connector_test.c:1142:31: sparse: sparse: incorrect type in argument 2 (different modifiers) @@ expected struct drm_display_mode *mode @@ got struct drm_display_mode const *[assigned] mode @@ drivers/gpu/drm/tests/drm_connector_test.c:1142:31: sparse: expected struct drm_display_mode *mode drivers/gpu/drm/tests/drm_connector_test.c:1142:31: sparse: got struct drm_display_mode const *[assigned] mode drivers/gpu/drm/tests/drm_connector_test.c:1182:31: sparse: sparse: incorrect type in argument 2 (different modifiers) @@ expected struct drm_display_mode *mode @@ got struct drm_display_mode const *[assigned] mode @@ drivers/gpu/drm/tests/drm_connector_test.c:1182:31: sparse: expected struct drm_dis
Re: [PATCH 1/3] drm/connector: hdmi: Fix memory leak in drm_display_mode_from_cea_vic()
Hi Jinjie, kernel test robot noticed the following build errors: [auto build test ERROR on drm-misc/drm-misc-next] [also build test ERROR on linus/master v6.12-rc3 next-20241017] [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/Jinjie-Ruan/drm-connector-hdmi-Fix-memory-leak-in-drm_display_mode_from_cea_vic/20241014-152022 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20241014071632.989108-2-ruanjinjie%40huawei.com patch subject: [PATCH 1/3] drm/connector: hdmi: Fix memory leak in drm_display_mode_from_cea_vic() config: arm-randconfig-002-20241017 (https://download.01.org/0day-ci/archive/20241017/202410172046.2w97yglm-...@intel.com/config) compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241017/202410172046.2w97yglm-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410172046.2w97yglm-...@intel.com/ All errors (new ones prefixed by >>): >> drivers/gpu/drm/tests/drm_connector_test.c:1008:24: error: passing 'const >> struct drm_display_mode *' to parameter of type 'struct drm_display_mode *' >> discards qualifiers >> [-Werror,-Wincompatible-pointer-types-discards-qualifiers] drm_mode_destroy(drm, mode); ^~~~ include/drm/drm_modes.h:456:72: note: passing argument to parameter 'mode' here void drm_mode_destroy(struct drm_device *dev, struct drm_display_mode *mode); ^ drivers/gpu/drm/tests/drm_connector_test.c:1031:24: error: passing 'const struct drm_display_mode *' to parameter of type 'struct drm_display_mode *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers] drm_mode_destroy(drm, mode); ^~~~ include/drm/drm_modes.h:456:72: note: passing argument to parameter 'mode' here void drm_mode_destroy(struct drm_device *dev, struct drm_display_mode *mode); ^ drivers/gpu/drm/tests/drm_connector_test.c:1051:24: error: passing 'const struct drm_display_mode *' to parameter of type 'struct drm_display_mode *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers] drm_mode_destroy(drm, mode); ^~~~ include/drm/drm_modes.h:456:72: note: passing argument to parameter 'mode' here void drm_mode_destroy(struct drm_device *dev, struct drm_display_mode *mode); ^ drivers/gpu/drm/tests/drm_connector_test.c:1074:24: error: passing 'const struct drm_display_mode *' to parameter of type 'struct drm_display_mode *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers] drm_mode_destroy(drm, mode); ^~~~ include/drm/drm_modes.h:456:72: note: passing argument to parameter 'mode' here void drm_mode_destroy(struct drm_device *dev, struct drm_display_mode *mode); ^ drivers/gpu/drm/tests/drm_connector_test.c:1094:24: error: passing 'const struct drm_display_mode *' to parameter of type 'struct drm_display_mode *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers] drm_mode_destroy(drm, mode); ^~~~ include/drm/drm_modes.h:456:72: note: passing argument to parameter 'mode' here void drm_mode_destroy(struct drm_device *dev, struct drm_display_mode *mode); ^ drivers/gpu/drm/tests/drm_connector_test.c:1117:24: error: passing 'const struct drm_display_mode *' to parameter of type 'struct drm_display_mode *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers] drm_mode_destroy(drm, mode); ^~~~ include/drm/drm_modes.h:456:72: note: passing argument to parameter 'mode' here void drm_mode_destroy(struct drm_device *dev, struct drm_display_mode *mode);
[linux-next:master] [drm/tests] d219425604: WARNING:at_drivers/gpu/drm/drm_framebuffer.c:#drm_framebuffer_free[drm]
Hello,
kernel test robot noticed
"WARNING:at_drivers/gpu/drm/drm_framebuffer.c:#drm_framebuffer_free[drm]" on:
commit: d2194256049910d286cd6c308c2689df521d8842 ("drm/tests: Add test for
drm_framebuffer_free()")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 15e7d45e786a62a211dd0098fee7c57f84f8c681]
in testcase: kunit
version:
with following parameters:
group: group-00
config: x86_64-rhel-8.3-kunit
compiler: gcc-12
test machine: 4 threads 1 sockets Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (Ivy
Bridge) with 8G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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
| Closes:
https://lore.kernel.org/oe-lkp/202410171515.c79582d2-oliver.s...@intel.com
kern :warn : [ 111.096210] [ cut here ]
kern :warn : [ 111.096421] drm-kunit-mock-device
drm_test_framebuffer_free.drm-kunit-mock-device: [drm]
drm_WARN_ON(!list_empty(&fb->filp_head))
kern :warn : [ 111.096523] WARNING: CPU: 1 PID: 4862 at
drivers/gpu/drm/drm_framebuffer.c:832 drm_framebuffer_free
(drivers/gpu/drm/drm_framebuffer.c:832) drm
kern :warn : [ 111.097075] Modules linked in: drm_framebuffer_test
drm_kunit_helpers linear_ranges btrfs intel_rapl_msr intel_rapl_common
x86_pkg_temp_thermal intel_powerclamp coretemp blake2b_generic xor kvm_intel
raid6_pq libcrc32c kvm crct10dif_pclmul crc32_generic crc32_pclmul crc32c_intel
ghash_clmulni_intel sd_mod sg sha512_ssse3 rapl i915 intel_cstate ipmi_devintf
ipmi_msghandler ahci libahci intel_uncore ttm intel_gtt libata mei_me
drm_display_helper drm_kms_helper mei drm_buddy video wmi drm fuse ip_tables
[last unloaded: drm_format_test]
kern :warn : [ 111.098045] CPU: 1 UID: 0 PID: 4862 Comm: kunit_try_catch
Tainted: G S BN 6.11.0-rc7-01411-gd21942560499 #1
kern :warn : [ 111.098262] Tainted: [S]=CPU_OUT_OF_SPEC, [B]=BAD_PAGE,
[N]=TEST
kern :warn : [ 111.098389] Hardware name: Hewlett-Packard p6-1451cx/2ADA,
BIOS 8.15 02/05/2013
kern :warn : [ 111.098555] RIP: 0010:drm_framebuffer_free
(drivers/gpu/drm/drm_framebuffer.c:832) drm
kern :warn : [ 111.098795] Code: 8b 74 24 50 4d 85 f6 74 28 4c 89 e7 e8 af a2
96 c2 48 c7 c1 e0 d8 3e c0 4c 89 f2 48 c7 c7 40 d9 3e c0 48 89 c6 e8 66 ca eb
c0 <0f> 0b e9 2e ff ff ff 48 b8 00 00 00 00 00 fc ff df 4c 89 e2 48 c1
All code
0: 8b 74 24 50 mov0x50(%rsp),%esi
4: 4d 85 f6test %r14,%r14
7: 74 28 je 0x31
9: 4c 89 e7mov%r12,%rdi
c: e8 af a2 96 c2 call 0xc296a2c0
11: 48 c7 c1 e0 d8 3e c0mov$0xc03ed8e0,%rcx
18: 4c 89 f2mov%r14,%rdx
1b: 48 c7 c7 40 d9 3e c0mov$0xc03ed940,%rdi
22: 48 89 c6mov%rax,%rsi
25: e8 66 ca eb c0 call 0xc0ebca90
2a:* 0f 0b ud2 <-- trapping instruction
2c: e9 2e ff ff ff jmp0xff5f
31: 48 b8 00 00 00 00 00movabs $0xdc00,%rax
38: fc ff df
3b: 4c 89 e2mov%r12,%rdx
3e: 48 rex.W
3f: c1 .byte 0xc1
Code starting with the faulting instruction
===
0: 0f 0b ud2
2: e9 2e ff ff ff jmp0xff35
7: 48 b8 00 00 00 00 00movabs $0xdc00,%rax
e: fc ff df
11: 4c 89 e2mov%r12,%rdx
14: 48 rex.W
15: c1 .byte 0xc1
kern :warn : [ 111.099136] RSP: 0018:c9b8fc08 EFLAGS: 00010286
kern :warn : [ 111.099253] RAX: RBX: c9b8fcc8 RCX:
0027
kern :warn : [ 111.099400] RDX: 0027 RSI: 0004 RDI:
8881c0eb0b08
kern :warn : [ 111.099560] RBP: c9b8fca0 R08: 0001 R09:
ed10381d6161
kern :warn : [ 111.099707] R10: 8881c0eb0b0b R11: 0001 R12:
888122f04000
kern :warn : [ 111.099852] R13: 88821e36b000 R14: 888130ed8e80 R15:
c9a1f920
kern :warn : [ 111.06] FS: ()
GS:8881c0e8() knlGS:
kern :warn : [ 111.100158] CS: 0010 DS: ES: CR0: 80050033
kern :warn : [ 111.100280] CR2: f7203009 CR3: 0001047ee005 CR4:
001706f0
kern :warn : [ 111.100426] DR0: 874243e0 DR1: 874243e1 DR2:
874243e3
kern :warn : [ 111.100581] DR3: 874243e5 DR6: 0ff0 DR7:
0600
kern :warn : [ 111.100726] Call Trace:
kern :warn : [ 111.100793]
kern :warn : [ 111.100853] ? __w
Re: [PATCH 3/3] drm/panthor: Rreset device and load FW after failed PM suspend
Hi Adrián,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on linus/master v6.12-rc3 next-20241016]
[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/Adri-n-Larumbe/drm-panthor-Retry-OPP-transition-to-suspension-state-a-few-times/20241012-070112
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20241011225906.3789965-3-adrian.larumbe%40collabora.com
patch subject: [PATCH 3/3] drm/panthor: Rreset device and load FW after failed
PM suspend
config: i386-buildonly-randconfig-001-20241016
(https://download.01.org/0day-ci/archive/20241016/202410161634.8yjhtqm2-...@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project
3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241016/202410161634.8yjhtqm2-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410161634.8yjhtqm2-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/panthor/panthor_sched.c:3104:29: error: no member named
>> 'runtime_error' in 'struct dev_pm_info'
3104 | if (ptdev->base.dev->power.runtime_error) {
| ~~ ^
include/linux/compiler.h:55:47: note: expanded from macro 'if'
55 | #define if(cond, ...) if ( __trace_if_var( !!(cond , ## __VA_ARGS__)
) )
| ^~~~
include/linux/compiler.h:57:52: note: expanded from macro '__trace_if_var'
57 | #define __trace_if_var(cond) (__builtin_constant_p(cond) ? (cond) :
__trace_if_value(cond))
|^~~~
>> drivers/gpu/drm/panthor/panthor_sched.c:3104:29: error: no member named
>> 'runtime_error' in 'struct dev_pm_info'
3104 | if (ptdev->base.dev->power.runtime_error) {
| ~~ ^
include/linux/compiler.h:55:47: note: expanded from macro 'if'
55 | #define if(cond, ...) if ( __trace_if_var( !!(cond , ## __VA_ARGS__)
) )
| ^~~~
include/linux/compiler.h:57:61: note: expanded from macro '__trace_if_var'
57 | #define __trace_if_var(cond) (__builtin_constant_p(cond) ? (cond) :
__trace_if_value(cond))
| ^~~~
>> drivers/gpu/drm/panthor/panthor_sched.c:3104:29: error: no member named
>> 'runtime_error' in 'struct dev_pm_info'
3104 | if (ptdev->base.dev->power.runtime_error) {
| ~~ ^
include/linux/compiler.h:55:47: note: expanded from macro 'if'
55 | #define if(cond, ...) if ( __trace_if_var( !!(cond , ## __VA_ARGS__)
) )
| ^~~~
include/linux/compiler.h:57:86: note: expanded from macro '__trace_if_var'
57 | #define __trace_if_var(cond) (__builtin_constant_p(cond) ? (cond) :
__trace_if_value(cond))
|
^~~~
include/linux/compiler.h:68:3: note: expanded from macro '__trace_if_value'
68 | (cond) ?\
| ^~~~
3 errors generated.
vim +3104 drivers/gpu/drm/panthor/panthor_sched.c
3081
3082 static struct dma_fence *
3083 queue_run_job(struct drm_sched_job *sched_job)
3084 {
3085 struct panthor_job *job = container_of(sched_job, struct
panthor_job, base);
3086 struct panthor_group *group = job->group;
3087 struct panthor_queue *queue = group->queues[job->queue_idx];
3088 struct panthor_device *ptdev = group->ptdev;
3089 struct panthor_scheduler *sched = ptdev->scheduler;
3090 struct panthor_job_ringbuf_instrs instrs;
3091 struct panthor_job_cs_params cs_params;
3092 struct dma_fence *done_fence;
3093 int ret;
3094
3095 /* Stream size is zero, nothing to do except making sure all
previously
3096 * submitted jobs are done before we signal the
3097 * drm_sched_job::s_fence::finished fence.
3098 */
3099 if (!job->call_info.si
[linux-next:master] [fs] d91ea8195e: stress-ng.ring-pipe.ops_per_sec -5.1% regression (stress-ng.ring-pipe.pipe_read+write_calls_per_sec 7.3% improvement)
Hello,
kernel test robot noticed a -5.1% regression of stress-ng.ring-pipe.ops_per_sec
(but also a 7.3% improvement of
stress-ng.ring-pipe.pipe_read+write_calls_per_sec
in "miscellaneous metrics" part of the same test) on:
commit: d91ea8195ed416365007d83d2967985dc6d8f882 ("fs: port files to file_ref")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
testcase: stress-ng
config: x86_64-rhel-8.3
compiler: gcc-12
test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480CTDX
(Sapphire Rapids) with 256G memory
parameters:
nr_threads: 100%
testtime: 60s
test: ring-pipe
cpufreq_governor: performance
In addition to that, the commit also has significant impact on the following
tests:
+--+---+
| testcase: change | stress-ng: stress-ng.io-uring.ops_per_sec 27.5%
improvement |
| test machine | 256 threads 2 sockets GENUINE INTEL(R) XEON(R) (Sierra
Forest) with 128G memory |
| test parameters | cpufreq_governor=performance
|
| | nr_threads=100%
|
| | test=io-uring
|
| | testtime=60s
|
+--+---+
at the same time, we also observed
"dmesg.WARNING:at_fs/file.c:#__file_ref_put"
"dmesg.WARNING:at_fs/open.c:#filp_flush"
"RIP:aa_file_perm"
then kernel crash issues for stress-ng getdent tests as below part [1]
similar to what we reported in
https://lore.kernel.org/all/202410151043.5d224a27-oliver.s...@intel.com/
Details are as below:
-->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20241015/202410151611.f4cd71f2-oliver.s...@intel.com
=
compiler/cpufreq_governor/kconfig/nr_threads/rootfs/tbox_group/test/testcase/testtime:
gcc-12/performance/x86_64-rhel-8.3/100%/debian-12-x86_64-20240206.cgz/lkp-spr-r02/ring-pipe/stress-ng/60s
commit:
bef236c3c0 ("fs: add file_ref")
d91ea8195e ("fs: port files to file_ref")
bef236c3c0fea5fc d91ea8195ed416365007d83d296
---
%stddev %change %stddev
\ |\
170804 ± 23% -42.3% 98511 ± 9% cpuidle..usage
1.17 ± 2% -0.11.05mpstat.cpu.all.irq%
444333 ± 6% -25.7% 330133 ± 10% numa-meminfo.node1.Active
444317 ± 6% -25.7% 330117 ± 10% numa-meminfo.node1.Active(anon)
111455 ± 5% -26.0% 82465 ± 9% numa-vmstat.node1.nr_active_anon
111454 ± 5% -26.0% 82465 ± 9%
numa-vmstat.node1.nr_zone_active_anon
2.53 ± 32% -48.3% 1.31 ± 55%
perf-sched.sch_delay.max.ms.__x64_sys_pause.do_syscall_64.entry_SYSCALL_64_after_hwframe.[unknown]
136.17 ± 5% -13.8% 117.33 ± 11%
perf-sched.wait_and_delay.count.__cond_resched.mutex_lock.pipe_write.vfs_write.ksys_write
159.37 ± 10% +18.0% 188.02 ± 8%
sched_debug.cfs_rq:/.runnable_avg.stddev
0.01 ±223%+500.0% 0.03
sched_debug.rt_rq:.rt_nr_running.stddev
454317 ± 5% -26.2% 335215 ± 9% meminfo.Active
454285 ± 5% -26.2% 335183 ± 9% meminfo.Active(anon)
1124528 ± 2% +11.5%1254390 ± 2% meminfo.Inactive
1124315 ± 2% +11.6%1254176 ± 2% meminfo.Inactive(anon)
2705+7.3% 2902
stress-ng.ring-pipe.MB_per_sec_data_pipe_write
2.091e+09-5.1% 1.985e+09stress-ng.ring-pipe.ops
34851569-5.1% 33080540stress-ng.ring-pipe.ops_per_sec
692730+7.3% 743014
stress-ng.ring-pipe.pipe_read+write_calls_per_sec
708.08-7.6% 653.93stress-ng.time.user_time
112900 ± 7% -26.8% 82615 ± 10% proc-vmstat.nr_active_anon
281903 ± 2% +11.4% 314032 ± 2% proc-vmstat.nr_inactive_anon
112900 ± 7% -26.8% 82615 ± 10% proc-vmstat.nr_zone_active_anon
281903 ± 2% +11.4% 314032 ± 2% proc-vmstat.nr_zone_inactive_anon
1.433e+09-5.1% 1.36e+09proc-vmstat.numa_hit
1.432e+09-5.1% 1.36e+09proc-vmstat.numa_local
1.431e+09-5.1% 1.358e+09proc-vmstat.pgalloc_normal
1
Re: [PATCH v4 3/7] drm/log: Introduce a new boot logger to draw the kmsg on the screen
Hi Jocelyn,
kernel test robot noticed the following build errors:
[auto build test ERROR on 33c255312660653cf54f8019896b5dca28e3c580]
url:
https://github.com/intel-lab-lkp/linux/commits/Jocelyn-Falempe/drm-client-squash-of-drm-client-pending-series/20241011-225715
base: 33c255312660653cf54f8019896b5dca28e3c580
patch link:
https://lore.kernel.org/r/20241011105526.615812-4-jfalempe%40redhat.com
patch subject: [PATCH v4 3/7] drm/log: Introduce a new boot logger to draw the
kmsg on the screen
config: i386-allmodconfig
(https://download.01.org/0day-ci/archive/20241016/202410160342.rkkekxwk-...@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/20241016/202410160342.rkkekxwk-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410160342.rkkekxwk-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/drm_log.c:347:6: error: redefinition of 'drm_log_register'
347 | void drm_log_register(struct drm_device *dev)
| ^~~~
In file included from drivers/gpu/drm/drm_log.c:21:
drivers/gpu/drm/drm_log.h:8:20: note: previous definition of
'drm_log_register' with type 'void(struct drm_device *)'
8 | static inline void drm_log_register(struct drm_device *dev) {}
|^~~~
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for MODVERSIONS
Depends on [n]: MODULES [=y] && !COMPILE_TEST [=y]
Selected by [y]:
- RANDSTRUCT_FULL [=y] && (CC_HAS_RANDSTRUCT [=n] || GCC_PLUGINS [=y]) &&
MODULES [=y]
WARNING: unmet direct dependencies detected for GET_FREE_REGION
Depends on [n]: SPARSEMEM [=n]
Selected by [m]:
- RESOURCE_KUNIT_TEST [=m] && RUNTIME_TESTING_MENU [=y] && KUNIT [=m]
vim +/drm_log_register +347 drivers/gpu/drm/drm_log.c
342
343 /**
344 * drm_log_register() - Register a drm device to drm_log
345 * @dev: the drm device to register.
346 */
> 347 void drm_log_register(struct drm_device *dev)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH] drm/i915/lspcon: do not hardcode settle timeout
Hi Giedrius,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.12-rc3 next-20241015]
[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/Giedrius-Statkevi-ius/drm-i915-lspcon-do-not-hardcode-settle-timeout/20241014-174131
base: linus/master
patch link:
https://lore.kernel.org/r/20241014093914.109162-1-giedriuswork%40gmail.com
patch subject: [PATCH] drm/i915/lspcon: do not hardcode settle timeout
config: x86_64-defconfig
(https://download.01.org/0day-ci/archive/20241015/202410151813.hw9octae-...@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241015/202410151813.hw9octae-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410151813.hw9octae-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/display/drm_dp_dual_mode_helper.c:495: warning: Function
>> parameter or struct member 'time_out' not described in 'drm_lspcon_set_mode'
vim +495 drivers/gpu/drm/display/drm_dp_dual_mode_helper.c
056996b9568632 drivers/gpu/drm/drm_dp_dual_mode_helper.c Shashank
Sharma 2016-10-17 482
056996b9568632 drivers/gpu/drm/drm_dp_dual_mode_helper.c Shashank
Sharma 2016-10-17 483 /**
613a308159e5dd drivers/gpu/drm/drm_dp_dual_mode_helper.c Jani Nikula
2016-10-19 484 * drm_lspcon_set_mode: Change LSPCON's mode of
operation by
613a308159e5dd drivers/gpu/drm/drm_dp_dual_mode_helper.c Jani Nikula
2016-10-19 485 * writing offset (0x80, 0x40)
318fbd7dfedd67 drivers/gpu/drm/drm_dp_dual_mode_helper.c Lyude Paul
2021-04-23 486 * @dev: &drm_device to use
613a308159e5dd drivers/gpu/drm/drm_dp_dual_mode_helper.c Jani Nikula
2016-10-19 487 * @adapter: I2C-over-aux adapter
613a308159e5dd drivers/gpu/drm/drm_dp_dual_mode_helper.c Jani Nikula
2016-10-19 488 * @mode: required mode of operation
056996b9568632 drivers/gpu/drm/drm_dp_dual_mode_helper.c Shashank
Sharma 2016-10-17 489 *
056996b9568632 drivers/gpu/drm/drm_dp_dual_mode_helper.c Shashank
Sharma 2016-10-17 490 * Returns:
056996b9568632 drivers/gpu/drm/drm_dp_dual_mode_helper.c Shashank
Sharma 2016-10-17 491 * 0 on success, -error on failure/timeout
056996b9568632 drivers/gpu/drm/drm_dp_dual_mode_helper.c Shashank
Sharma 2016-10-17 492 */
318fbd7dfedd67 drivers/gpu/drm/drm_dp_dual_mode_helper.c Lyude Paul
2021-04-23 493 int drm_lspcon_set_mode(const struct drm_device *dev,
struct i2c_adapter *adapter,
3d7a1094af9e7e drivers/gpu/drm/display/drm_dp_dual_mode_helper.c Giedrius
Statkevičius 2024-10-14 494 enum drm_lspcon_mode
mode, int time_out)
056996b9568632 drivers/gpu/drm/drm_dp_dual_mode_helper.c Shashank
Sharma 2016-10-17 @495 {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 6/9] drm/bridge: Add ITE IT6263 LVDS to HDMI converter
Hi Liu,
kernel test robot noticed the following build warnings:
[auto build test WARNING on shawnguo/for-next]
[also build test WARNING on arm64/for-next/core drm/drm-next
drm-exynos/exynos-drm-next drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip
linus/master v6.12-rc3 next-20241014]
[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/Liu-Ying/arm64-dts-imx8mp-skov-revb-mi1010ait-1cp1-Add-panel-timing-node-to-panel-node/20241012-154239
base: https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git
for-next
patch link:
https://lore.kernel.org/r/20241012073543.1388069-7-victor.liu%40nxp.com
patch subject: [PATCH v2 6/9] drm/bridge: Add ITE IT6263 LVDS to HDMI converter
config: i386-randconfig-052-20241015
(https://download.01.org/0day-ci/archive/20241015/202410151230.dwfmnfo5-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410151230.dwfmnfo5-...@intel.com/
cocci warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/bridge/ite-it6263.c:683:57-62: WARNING: conversion to bool
>> not needed here
vim +683 drivers/gpu/drm/bridge/ite-it6263.c
655
656 static void
657 it6263_bridge_atomic_enable(struct drm_bridge *bridge,
658 struct drm_bridge_state *old_bridge_state)
659 {
660 struct drm_atomic_state *state = old_bridge_state->base.state;
661 struct it6263 *it = bridge_to_it6263(bridge);
662 const struct drm_crtc_state *crtc_state;
663 struct regmap *regmap = it->hdmi_regmap;
664 const struct drm_display_mode *mode;
665 struct drm_connector *connector;
666 bool is_stable = false;
667 struct drm_crtc *crtc;
668 unsigned int val;
669 bool pclk_high;
670 int i, ret;
671
672 connector = drm_atomic_get_new_connector_for_encoder(state,
673
bridge->encoder);
674 crtc = drm_atomic_get_new_connector_state(state,
connector)->crtc;
675 crtc_state = drm_atomic_get_new_crtc_state(state, crtc);
676 mode = &crtc_state->adjusted_mode;
677
678 regmap_write(regmap, HDMI_REG_HDMI_MODE, TX_HDMI_MODE);
679
680 it6263_hdmi_avi_infoframe_configure(it, connector, mode);
681
682 /* HDMI AFE setup */
> 683 pclk_high = mode->clock > HIGH_PIXEL_CLOCK_KHZ ? true : false;
684 regmap_write(regmap, HDMI_REG_AFE_DRV_CTRL, AFE_DRV_RST);
685 if (pclk_high)
686 regmap_write(regmap, HDMI_REG_AFE_XP_CTRL,
687 AFE_XP_GAINBIT | AFE_XP_RESETB);
688 else
689 regmap_write(regmap, HDMI_REG_AFE_XP_CTRL,
690 AFE_XP_ER0 | AFE_XP_RESETB);
691 regmap_write(regmap, HDMI_REG_AFE_ISW_CTRL, 0x10);
692 if (pclk_high)
693 regmap_write(regmap, HDMI_REG_AFE_IP_CTRL,
694 AFE_IP_GAINBIT | AFE_IP_RESETB);
695 else
696 regmap_write(regmap, HDMI_REG_AFE_IP_CTRL,
697 AFE_IP_ER0 | AFE_IP_RESETB);
698
699 /* HDMI software video reset */
700 regmap_write_bits(regmap, HDMI_REG_SW_RST, SOFTV_RST,
SOFTV_RST);
701 fsleep(1000);
702 regmap_write_bits(regmap, HDMI_REG_SW_RST, SOFTV_RST, 0);
703
704 /* reconfigure LVDS and retry several times in case video is
instable */
705 for (i = 0; i < 3; i++) {
706 ret = regmap_read_poll_timeout(regmap,
HDMI_REG_SYS_STATUS, val,
707 val & TXVIDSTABLE,
708 2, 50);
709 if (!ret) {
710 is_stable = true;
711 break;
712 }
713
714 it6263_lvds_config(it);
715 }
716
717 if (!is_stable)
718 dev_warn(it->dev, "failed to wait for video stable\n");
719
720 /* HDMI AFE reset release and power up */
721 regmap_write(regmap, HDMI_REG_AFE_DRV_CTRL, 0);
722
723 regmap_write_bits(regmap, HDMI_REG_GCP, AVMUTE, 0);
724
[linux-next:master] [drm/ast] 4e29cc7c5c: WARNING:at_drivers/gpu/drm/ast/ast_dp.c:#ast_dp_set_enable[ast]
Hello,
kernel test robot noticed
"WARNING:at_drivers/gpu/drm/ast/ast_dp.c:#ast_dp_set_enable[ast]" on:
commit: 4e29cc7c5c673299cfbaf4982fc8b6a72c9f706f ("drm/ast: astdp: Replace
ast_dp_set_on_off()")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master d61a00525464bfc5fe92c6ad713350988e492b88]
in testcase: lkvs
version: lkvs-x86_64-8e3b482-1_20241008
with following parameters:
test: rapl-server
config: x86_64-rhel-8.3-func
compiler: gcc-12
test machine: 384 threads 4 sockets GENUINE INTEL(R) XEON(R) (Granite Rapids)
with 128G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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
| Closes: https://lore.kernel.org/oe-lkp/202410151028.f9a3ee37-...@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20241015/202410151028.f9a3ee37-...@intel.com
kern :err : [ 234.161306] ast :2d:00.0: [drm] *ERROR* Link training
failed
kern :warn : [ 234.375338] [ cut here ]
kern :warn : [ 234.375347] ast :2d:00.0: [drm]
drm_WARN_ON(!__ast_dp_wait_enable(ast, enabled))
kern :warn : [ 234.375489] WARNING: CPU: 0 PID: 8 at
drivers/gpu/drm/ast/ast_dp.c:221 ast_dp_set_enable+0x153/0x1c0 [ast]
kern :warn : [ 234.375541] Modules linked in: intel_uncore_frequency_tpmi
ast(+) nvme intel_uncore_frequency_common intel_cstate intel_vsec_tpmi
drm_shmem_helper intel_uncore dax_hmem drm_kms_helper qat_4xxx intel_th_gth
nvme_core intel_qat dh_generic idxd intel_th_pci crc8 i2c_i801 intel_vsec
i2c_smbus intel_th authenc idxd_bus wmi ipmi_ssif joydev acpi_ipmi ipmi_si
ipmi_devintf ipmi_msghandler binfmt_misc loop fuse drm dm_mod ip_tables
kern :warn : [ 234.375610] CPU: 0 UID: 0 PID: 8 Comm: kworker/0:0 Not
tainted 6.11.0-rc7-01434-g4e29cc7c5c67 #1
kern :warn : [ 234.375622] Workqueue: events work_for_cpu_fn
kern :warn : [ 234.375657] RIP: 0010:ast_dp_set_enable+0x153/0x1c0 [ast]
kern :warn : [ 234.375667] Code: 48 8b 6b 50 48 85 ed 74 32 48 89 df e8 f6
73 1f bd 48 c7 c1 20 e4 80 c5 48 89 ea 48 c7 c7 80 e4 80 c5 48 89 c6 e8 6d a2
9e bb <0f> 0b 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc 48 b8 00 00 00
kern :warn : [ 234.375675] RSP: 0018:ffa000f87480 EFLAGS: 00010286
kern :warn : [ 234.375684] RAX: RBX: ff110910893960c8 RCX:
0027
kern :warn : [ 234.375687] RDX: 0027 RSI: 0004 RDI:
ff1100081d030b08
kern :warn : [ 234.375692] RBP: ff110910898e8e40 R08: 0001 R09:
ffe21c0103a06161
kern :warn : [ 234.375696] R10: ff1100081d030b0b R11: 0016 R12:
0010
kern :warn : [ 234.375699] R13: ff1100017149 R14: ffe21c002e2920c4 R15:
ff11000171490620
kern :warn : [ 234.375702] FS: ()
GS:ff1100081d00() knlGS:
kern :warn : [ 234.375706] CS: 0010 DS: ES: CR0: 80050033
kern :warn : [ 234.375708] CR2: 7f5f08e5e423 CR3: 00017b5a2002 CR4:
00f71ef0
kern :warn : [ 234.375710] DR0: DR1: DR2:
kern :warn : [ 234.375712] DR3: DR6: fffe07f0 DR7:
0400
kern :warn : [ 234.375714] PKRU: 5554
kern :warn : [ 234.375716] Call Trace:
kern :warn : [ 234.375722]
kern :warn : [ 234.375727] ? __warn+0xcc/0x260
kern :warn : [ 234.375740] ? ast_dp_set_enable+0x153/0x1c0 [ast]
kern :warn : [ 234.375749] ? report_bug+0x261/0x2c0
kern :warn : [ 234.375772] ? handle_bug+0x3c/0x70
kern :warn : [ 234.375789] ? exc_invalid_op+0x17/0x40
kern :warn : [ 234.375793] ? asm_exc_invalid_op+0x1a/0x20
kern :warn : [ 234.375813] ? ast_dp_set_enable+0x153/0x1c0 [ast]
kern :warn : [ 234.375822]
ast_astdp_encoder_helper_atomic_enable+0x215/0x280 [ast]
kern :warn : [ 234.375831] ?
__pfx_ast_astdp_encoder_helper_atomic_enable+0x10/0x10 [ast]
kern :warn : [ 234.375841]
drm_atomic_helper_commit_modeset_enables+0x52a/0xb20 [drm_kms_helper]
kern :warn : [ 234.375891] ?
drm_atomic_helper_wait_for_dependencies+0x45f/0x7d0 [drm_kms_helper]
kern :warn : [ 234.375912] drm_atomic_helper_commit_tail+0x72/0xd0
[drm_kms_helper]
kern :warn : [ 234.375934]
ast_mode_config_helper_atomic_commit_tail+0x44/0x60 [ast]
kern :warn : [ 234.375945] commit_tail+0x227/0x4b0 [drm_kms_helper]
kern :warn : [ 234.375969] drm_atomic_helper_commit+0x1ff/0x280
[drm_kms_helper]
kern :warn : [ 234.375991] ? __pfx_drm_atomic_helper_commit+0x10/0x10
[drm_kms_helper]
kern :warn : [ 234.376014] drm_atomic_commit+0x1ec/0x2b0 [drm]
kern :warn : [ 234.376114] ? __drm_atomic_helper_set_config+0x49f/0x6c0
[drm]
kern :warn : [ 234.376164]
Re: [PATCH 1/2] drm/sched: adding a new scheduling policy
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-exynos/exynos-drm-next]
[also build test ERROR on drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip
linus/master v6.12-rc2 next-20241011]
[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/jesse-zhang-amd-com/drm-amdgpu-add-the-ring-id-schedule-module-parameter-for-amdgpu/20241011-142247
base: https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git
exynos-drm-next
patch link:
https://lore.kernel.org/r/20241011062136.1019695-1-jesse.zhang%40amd.com
patch subject: [PATCH 1/2] drm/sched: adding a new scheduling policy
config: i386-randconfig-141-20241012
(https://download.01.org/0day-ci/archive/20241012/202410121939.czrbiako-...@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/20241012/202410121939.czrbiako-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410121939.czrbiako-...@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/xe/xe_sched_job.c: In function 'xe_sched_job_arm':
>> drivers/gpu/drm/xe/xe_sched_job.c:284:9: error: too few arguments to
>> function 'drm_sched_job_arm'
284 | drm_sched_job_arm(&job->drm);
| ^
In file included from drivers/gpu/drm/xe/xe_sched_job_types.h:11,
from drivers/gpu/drm/xe/xe_sched_job.h:9,
from drivers/gpu/drm/xe/xe_sched_job.c:6:
include/drm/gpu_scheduler.h:556:6: note: declared here
556 | void drm_sched_job_arm(struct drm_sched_job *job, int ring);
| ^
vim +/drm_sched_job_arm +284 drivers/gpu/drm/xe/xe_sched_job.c
dd08ebf6c3525a Matthew Brost 2023-03-30 239
dd08ebf6c3525a Matthew Brost 2023-03-30 240 void
xe_sched_job_arm(struct xe_sched_job *job)
dd08ebf6c3525a Matthew Brost 2023-03-30 241 {
4fc4899e86f7af Thomas Hellström 2024-03-27 242struct
xe_exec_queue *q = job->q;
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 243struct
dma_fence *fence, *prev;
4fc4899e86f7af Thomas Hellström 2024-03-27 244struct xe_vm
*vm = q->vm;
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 245u64 seqno = 0;
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 246int i;
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 247
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 248/* Migration
and kernel engines have their own locking */
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 249if
(IS_ENABLED(CONFIG_LOCKDEP) &&
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 250!(q->flags
& (EXEC_QUEUE_FLAG_KERNEL | EXEC_QUEUE_FLAG_VM))) {
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 251
lockdep_assert_held(&q->vm->lock);
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 252if
(!xe_vm_in_lr_mode(q->vm))
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 253
xe_vm_assert_held(q->vm);
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 254}
4fc4899e86f7af Thomas Hellström 2024-03-27 255
4fc4899e86f7af Thomas Hellström 2024-03-27 256if (vm &&
!xe_sched_job_is_migration(q) && !xe_vm_in_lr_mode(vm) &&
4fc4899e86f7af Thomas Hellström 2024-03-27 257
(vm->batch_invalidate_tlb || vm->tlb_flush_seqno != q->tlb_flush_seqno)) {
4fc4899e86f7af Thomas Hellström 2024-03-27 258
xe_vm_assert_held(vm);
4fc4899e86f7af Thomas Hellström 2024-03-27 259
q->tlb_flush_seqno = vm->tlb_flush_seqno;
4fc4899e86f7af Thomas Hellström 2024-03-27 260
job->ring_ops_flush_tlb = true;
4fc4899e86f7af Thomas Hellström 2024-03-27 261}
4fc4899e86f7af Thomas Hellström 2024-03-27 262
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 263/* Arm the
pre-allocated fences */
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 264for (i = 0; i <
q->width; prev = fence, ++i) {
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 265struct
dma_fence_chain *chain;
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 266
0ac7a2c745e8a4 Thomas Hellström 2024-05-27 267
Re: [PATCH 1/2] drm/sched: adding a new scheduling policy
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-exynos/exynos-drm-next]
[also build test ERROR on drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip
linus/master v6.12-rc2 next-20241011]
[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/jesse-zhang-amd-com/drm-amdgpu-add-the-ring-id-schedule-module-parameter-for-amdgpu/20241011-142247
base: https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git
exynos-drm-next
patch link:
https://lore.kernel.org/r/20241011062136.1019695-1-jesse.zhang%40amd.com
patch subject: [PATCH 1/2] drm/sched: adding a new scheduling policy
config: sparc64-randconfig-r073-20241012
(https://download.01.org/0day-ci/archive/20241012/202410121817.hue5mn9d-...@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241012/202410121817.hue5mn9d-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410121817.hue5mn9d-...@intel.com/
All error/warnings (new ones prefixed by >>):
drivers/gpu/drm/panthor/panthor_drv.c: In function
'panthor_submit_ctx_add_deps_and_arm_jobs':
>> drivers/gpu/drm/panthor/panthor_drv.c:674:17: error: too few arguments to
>> function 'drm_sched_job_arm'
674 | drm_sched_job_arm(ctx->jobs[i].job);
| ^
In file included from drivers/gpu/drm/panthor/panthor_drv.c:20:
include/drm/gpu_scheduler.h:556:6: note: declared here
556 | void drm_sched_job_arm(struct drm_sched_job *job, int ring);
| ^
--
drivers/gpu/drm/scheduler/sched_main.c:405: warning: Function parameter or
struct member 'result' not described in 'drm_sched_job_done'
>> drivers/gpu/drm/scheduler/sched_main.c:828: warning: Function parameter or
>> struct member 'ring' not described in 'drm_sched_job_arm'
vim +/drm_sched_job_arm +674 drivers/gpu/drm/panthor/panthor_drv.c
4bdca11507928a Boris Brezillon 2024-02-29 655
4bdca11507928a Boris Brezillon 2024-02-29 656 /**
4bdca11507928a Boris Brezillon 2024-02-29 657 *
panthor_submit_ctx_add_deps_and_arm_jobs() - Add jobs dependencies and arm jobs
4bdca11507928a Boris Brezillon 2024-02-29 658 * @ctx: Submit context.
4bdca11507928a Boris Brezillon 2024-02-29 659 *
4bdca11507928a Boris Brezillon 2024-02-29 660 * Must be called after the
resv preparation has been taken care of.
4bdca11507928a Boris Brezillon 2024-02-29 661 *
4bdca11507928a Boris Brezillon 2024-02-29 662 * Return: 0 on success, a
negative error code otherwise.
4bdca11507928a Boris Brezillon 2024-02-29 663 */
4bdca11507928a Boris Brezillon 2024-02-29 664 static int
4bdca11507928a Boris Brezillon 2024-02-29 665
panthor_submit_ctx_add_deps_and_arm_jobs(struct panthor_submit_ctx *ctx)
4bdca11507928a Boris Brezillon 2024-02-29 666 {
4bdca11507928a Boris Brezillon 2024-02-29 667 for (u32 i = 0; i <
ctx->job_count; i++) {
4bdca11507928a Boris Brezillon 2024-02-29 668 int ret;
4bdca11507928a Boris Brezillon 2024-02-29 669
4bdca11507928a Boris Brezillon 2024-02-29 670 ret =
panthor_submit_ctx_add_sync_deps_to_job(ctx, i);
4bdca11507928a Boris Brezillon 2024-02-29 671 if (ret)
4bdca11507928a Boris Brezillon 2024-02-29 672 return
ret;
4bdca11507928a Boris Brezillon 2024-02-29 673
4bdca11507928a Boris Brezillon 2024-02-29 @674
drm_sched_job_arm(ctx->jobs[i].job);
4bdca11507928a Boris Brezillon 2024-02-29 675
4bdca11507928a Boris Brezillon 2024-02-29 676 ret =
panthor_submit_ctx_update_job_sync_signal_fences(ctx, i);
4bdca11507928a Boris Brezillon 2024-02-29 677 if (ret)
4bdca11507928a Boris Brezillon 2024-02-29 678 return
ret;
4bdca11507928a Boris Brezillon 2024-02-29 679 }
4bdca11507928a Boris Brezillon 2024-02-29 680
4bdca11507928a Boris Brezillon 2024-02-29 681 return 0;
4bdca11507928a Boris Brezillon 2024-02-29 682 }
4bdca11507928a Boris Brezillon 2024-02-29 683
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v12 13/15] drm/vkms: Create KUnit tests for YUV conversions
Hi Louis, kernel test robot noticed the following build errors: [auto build test ERROR on 82fe69e63d2b5a5e86ea94c7361c833d3848ab69] url: https://github.com/intel-lab-lkp/linux/commits/Louis-Chauvet/drm-vkms-Code-formatting/20241008-001316 base: 82fe69e63d2b5a5e86ea94c7361c833d3848ab69 patch link: https://lore.kernel.org/r/20241007-yuv-v12-13-01c1ada6fec8%40bootlin.com patch subject: [PATCH v12 13/15] drm/vkms: Create KUnit tests for YUV conversions config: i386-randconfig-013-20241010 (https://download.01.org/0day-ci/archive/20241011/202410110407.ehvadsaf-...@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/20241011/202410110407.ehvadsaf-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410110407.ehvadsaf-...@intel.com/ All errors (new ones prefixed by >>, old ones prefixed by <<): WARNING: modpost: missing MODULE_DESCRIPTION() in lib/slub_kunit.o >> ERROR: modpost: "drm_get_color_range_name" >> [drivers/gpu/drm/vkms/tests/vkms_format_test.ko] undefined! >> ERROR: modpost: "drm_get_color_encoding_name" >> [drivers/gpu/drm/vkms/tests/vkms_format_test.ko] undefined! >> ERROR: modpost: "get_conversion_matrix_to_argb_u16" >> [drivers/gpu/drm/vkms/tests/vkms_format_test.ko] undefined! Kconfig warnings: (for reference only) WARNING: unmet direct dependencies detected for GET_FREE_REGION Depends on [n]: SPARSEMEM [=n] Selected by [m]: - RESOURCE_KUNIT_TEST [=m] && RUNTIME_TESTING_MENU [=y] && KUNIT [=y] -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH] drm/vblank: Require a driver register vblank support for 0 or all CRTCs
Hello,
kernel test robot noticed "BUG:kernel_NULL_pointer_dereference,address" on:
commit: 8e1a430cf308254a61a2317a0dfc4d8f4b3e13cb ("[PATCH] drm/vblank: Require
a driver register vblank support for 0 or all CRTCs")
url:
https://github.com/intel-lab-lkp/linux/commits/Lyude-Paul/drm-vblank-Require-a-driver-register-vblank-support-for-0-or-all-CRTCs/20240928-044210
patch link:
https://lore.kernel.org/all/20240927203946.695934-2-ly...@redhat.com/
patch subject: [PATCH] drm/vblank: Require a driver register vblank support for
0 or all CRTCs
in testcase: boot
compiler: gcc-12
test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+-+++
| | 22512c3ee0 | 8e1a430cf3 |
+-+++
| boot_successes | 12 | 0 |
| boot_failures | 0 | 12 |
| BUG:kernel_NULL_pointer_dereference,address | 0 | 12 |
| Oops:Oops:#[##] | 0 | 12 |
| EIP:drm_vblank_init | 0 | 12 |
| Kernel_panic-not_syncing:Fatal_exception| 0 | 12 |
+-+++
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
| Closes: https://lore.kernel.org/oe-lkp/202410101418.5704b4a5-...@intel.com
[4.727010][T1] BUG: kernel NULL pointer dereference, address: 0188
[4.728324][T1] #PF: supervisor read access in kernel mode
[4.729456][T1] #PF: error_code(0x) - not-present page
[4.729853][T1] *pdpt = *pde = f000ff53f000ff53
[4.729853][T1] Oops: Oops: [#1]
[4.729853][T1] CPU: 0 UID: 0 PID: 1 Comm: swapper Tainted: G
T 6.11.0-rc7-01372-g8e1a430cf308 #1
577dd3e1adc1bccd6f381550d3179686c5f157a0
[4.729853][T1] Tainted: [T]=RANDSTRUCT
[4.729853][T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 4.729853][ T1] EIP: drm_vblank_init (drivers/gpu/drm/drm_vblank.c:534)
[ 4.729853][ T1] Code: 89 c6 53 83 ec 08 89 55 ec 8b 90 64 05 00 00 39 d1 74 56
8d 42 f8 eb 12 90 8b 5a 04 85 db 74 17 8b 50 08 8d 42 f8 39 d1 74 3f <8b> 90 90
01 00 00 8b 7a 08 85 ff 75 e2 8b 40 10 85 f6 74 03 8b 76
All code
0: 89 c6 mov%eax,%esi
2: 53 push %rbx
3: 83 ec 08sub$0x8,%esp
6: 89 55 ecmov%edx,-0x14(%rbp)
9: 8b 90 64 05 00 00 mov0x564(%rax),%edx
f: 39 d1 cmp%edx,%ecx
11: 74 56 je 0x69
13: 8d 42 f8lea-0x8(%rdx),%eax
16: eb 12 jmp0x2a
18: 90 nop
19: 8b 5a 04mov0x4(%rdx),%ebx
1c: 85 db test %ebx,%ebx
1e: 74 17 je 0x37
20: 8b 50 08mov0x8(%rax),%edx
23: 8d 42 f8lea-0x8(%rdx),%eax
26: 39 d1 cmp%edx,%ecx
28: 74 3f je 0x69
2a:* 8b 90 90 01 00 00 mov0x190(%rax),%edx <-- trapping
instruction
30: 8b 7a 08mov0x8(%rdx),%edi
33: 85 ff test %edi,%edi
35: 75 e2 jne0x19
37: 8b 40 10mov0x10(%rax),%eax
3a: 85 f6 test %esi,%esi
3c: 74 03 je 0x41
3e: 8b .byte 0x8b
3f: 76 .byte 0x76
Code starting with the faulting instruction
===
0: 8b 90 90 01 00 00 mov0x190(%rax),%edx
6: 8b 7a 08mov0x8(%rdx),%edi
9: 85 ff test %edi,%edi
b: 75 e2 jne0xffef
d: 8b 40 10mov0x10(%rax),%eax
10: 85 f6 test %esi,%esi
12: 74 03 je 0x17
14: 8b .byte 0x8b
15: 76 .byte 0x76
[4.729853][T1] EAX: fff8 EBX: 86802000 ECX: 86802564 EDX:
[4.729853][T1] ESI: 86802000 EDI: 86813400 EBP: 85e1fe90 ESP: 85e1fe7c
[4.729853][T1] DS: 007b ES: 007b FS: GS: SS: 0068 EFLAGS:
00010282
[4.729853][T1] CR0: 80050033 CR2: 0188 CR3: 05182000 CR4: 000406b0
[4.729853][T1] DR0: DR1: DR2: DR3:
[4.729853][T1] DR6: fffe0ff0 DR7: 0
Re: [PATCH 4/8] drm/client: Make copies of modes
hi, Ville Syrjala,
we noticed there is a v2 for this commit
https://lore.kernel.org/all/20241003181553.8891-1-ville.syrj...@linux.intel.com/
but bot failed to analyze the patch mail structure and re-assemble it with
other patches in this serial to form a new branch (which need manual efforts).
so we just made this report out FYI. in case you are sure the issue should be
addressed by v2, please just ignore. if you want us to test v2, please let us
know. thanks
Hello,
kernel test robot noticed
"Oops:general_protection_fault,probably_for_non-canonical_address#:#[##]PREEMPT_SMP_KASAN_PTI"
on:
commit: 2cc919cccbb5d887534545618d696db4ec5fb691 ("[PATCH 4/8] drm/client: Make
copies of modes")
url:
https://github.com/intel-lab-lkp/linux/commits/Ville-Syrjala/drm-client-Constify-modes/20241004-061843
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/all/20241003113304.11700-5-ville.syrj...@linux.intel.com/
patch subject: [PATCH 4/8] drm/client: Make copies of modes
in testcase: boot
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+--+++
|
| 40327b7031 | 2cc919cccb |
+--+++
| boot_successes
| 15 | 0 |
| boot_failures
| 0 | 16 |
|
Oops:general_protection_fault,probably_for_non-canonical_address#:#[##]PREEMPT_SMP_KASAN_PTI
| 0 | 16 |
| KASAN:null-ptr-deref_in_range[#-#]
| 0 | 16 |
| RIP:drm_mode_copy[drm]
| 0 | 16 |
| Kernel_panic-not_syncing:Fatal_exception
| 0 | 16 |
+--+++
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
| Closes:
https://lore.kernel.org/oe-lkp/202410091649.1353a717-oliver.s...@intel.com
[ 12.729071][ T116] bochs-drm :00:02.0: vgaarb: deactivate vga console
[ 12.733522][ T116] Console: switching to colour dummy device 80x25
[ 12.738211][ T116] [drm] Found bochs VGA, ID 0xb0c5.
[ 12.738603][ T116] [drm] Framebuffer size 16384 kB @ 0xfd00, mmio @
0xfebf.
[ 12.742172][ T116] [drm] Initialized bochs-drm 1.0.0 for :00:02.0 on
minor 0
[ 12.744751][ T116] Oops: general protection fault, probably for
non-canonical address 0xdc00: [#1] PREEMPT SMP KASAN PTI
[ 12.745622][ T116] KASAN: null-ptr-deref in range
[0x-0x0007]
[ 12.746193][ T116] CPU: 1 UID: 0 PID: 116 Comm: udevd Not tainted
6.12.0-rc1-00311-g2cc919cccbb5 #2
[ 12.746817][ T116] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 12.747510][ T116] RIP: 0010:drm_mode_copy
(kbuild/src/consumer/drivers/gpu/drm/drm_modes.c:1422) drm
[ 12.748000][ T116] Code: 40 84 c6 0f 85 01 01 00 00 84 c9 0f 95 c2 0f 9e c0 84
c2 0f 85 f1 00 00 00 48 ba 00 00 00 00 00 fc ff df 48 89 e8 48 c1 e8 03 <0f> b6
0c 10 48 8d 45 77 48 89 c6 83 e0 07 48 c1 ee 03 0f b6 14 16
All code
0: 40 84 c6test %al,%sil
3: 0f 85 01 01 00 00 jne0x10a
9: 84 c9 test %cl,%cl
b: 0f 95 c2setne %dl
e: 0f 9e c0setle %al
11: 84 c2 test %al,%dl
13: 0f 85 f1 00 00 00 jne0x10a
19: 48 ba 00 00 00 00 00movabs $0xdc00,%rdx
20: fc ff df
23: 48 89 e8mov%rbp,%rax
26: 48 c1 e8 03 shr$0x3,%rax
2a:* 0f b6 0c 10 movzbl (%rax,%rdx,1),%ecx <--
trapping instruction
2e: 48 8d 45 77 lea0x77(%rbp),%rax
32: 48 89 c6mov%rax,%rsi
35: 83 e0 07and$0x7,%eax
38: 48 c1 ee 03 shr$0x3,%rsi
3c: 0f b6 14 16 movzbl (%rsi,%rdx,1),%edx
Code starting with the faulting instruction
===
0: 0f b6 0c 10 movzbl (%rax,%rdx,1),%ecx
4: 48 8d 45 77 lea0x77(%rbp),%rax
8: 48 89 c6
Re: [PATCH v6 1/3] drm/mipi-dsi: add mipi_dsi_compression_mode_multi
Hi Dzmitry,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 58ca61c1a866bfdaa5e19fb19a2416764f847d75]
url:
https://github.com/intel-lab-lkp/linux/commits/Dzmitry-Sankouski/drm-mipi-dsi-add-mipi_dsi_compression_mode_multi/20241007-022151
base: 58ca61c1a866bfdaa5e19fb19a2416764f847d75
patch link:
https://lore.kernel.org/r/20241006-starqltechn_integration_upstream-v6-1-8336b9cd6c34%40gmail.com
patch subject: [PATCH v6 1/3] drm/mipi-dsi: add mipi_dsi_compression_mode_multi
config: x86_64-rhel-8.3
(https://download.01.org/0day-ci/archive/20241009/202410092245.tfsuulll-...@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/20241009/202410092245.tfsuulll-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410092245.tfsuulll-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/drm_mipi_dsi.c:1533: warning: Function parameter or struct
>> member 'ctx' not described in 'mipi_dsi_compression_mode_multi'
>> drivers/gpu/drm/drm_mipi_dsi.c:1533: warning: Excess function parameter
>> 'dsi' description in 'mipi_dsi_compression_mode_multi'
vim +1533 drivers/gpu/drm/drm_mipi_dsi.c
1522
1523 /**
1524 * mipi_dsi_compression_mode_multi() - enable/disable DSC on the
peripheral
1525 * @dsi: DSI peripheral device
1526 * @enable: Whether to enable or disable the DSC
1527 *
1528 * Enable or disable Display Stream Compression on the peripheral using
the
1529 * default Picture Parameter Set and VESA DSC 1.1 algorithm.
1530 */
1531 void mipi_dsi_compression_mode_multi(struct mipi_dsi_multi_context *ctx,
1532 bool enable)
> 1533 {
1534 return mipi_dsi_compression_mode_ext_multi(ctx, enable,
1535
MIPI_DSI_COMPRESSION_DSC, 0);
1536 }
1537 EXPORT_SYMBOL(mipi_dsi_compression_mode_multi);
1538
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 3/5] perf: Add pmu get/put
Hi Lucas,
kernel test robot noticed the following build warnings:
[auto build test WARNING on perf-tools-next/perf-tools-next]
[cannot apply to tip/perf/core perf-tools/perf-tools acme/perf/core
linus/master v6.12-rc2 next-20241008]
[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/Lucas-De-Marchi/perf-Add-dummy-pmu-module/20241009-023728
base:
https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git
perf-tools-next
patch link:
https://lore.kernel.org/r/20241008183501.1354695-4-lucas.demarchi%40intel.com
patch subject: [PATCH 3/5] perf: Add pmu get/put
config: x86_64-kexec
(https://download.01.org/0day-ci/archive/20241009/202410091848.aruorwwd-...@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project
3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241009/202410091848.aruorwwd-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410091848.aruorwwd-...@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/events/core.c:5235:17: warning: unused variable 'module'
>> [-Wunused-variable]
5235 | struct module *module;
|^~
1 warning generated.
vim +/module +5235 kernel/events/core.c
5232
5233 static void _free_event(struct perf_event *event)
5234 {
> 5235 struct module *module;
5236
5237 irq_work_sync(&event->pending_irq);
5238 irq_work_sync(&event->pending_disable_irq);
5239 perf_pending_task_sync(event);
5240
5241 unaccount_event(event);
5242
5243 security_perf_event_free(event);
5244
5245 if (event->rb) {
5246 /*
5247 * Can happen when we close an event with re-directed
output.
5248 *
5249 * Since we have a 0 refcount, perf_mmap_close() will
skip
5250 * over us; possibly making our ring_buffer_put() the
last.
5251 */
5252 mutex_lock(&event->mmap_mutex);
5253 ring_buffer_attach(event, NULL);
5254 mutex_unlock(&event->mmap_mutex);
5255 }
5256
5257 if (is_cgroup_event(event))
5258 perf_detach_cgroup(event);
5259
5260 if (!event->parent) {
5261 if (event->attr.sample_type & PERF_SAMPLE_CALLCHAIN)
5262 put_callchain_buffers();
5263 }
5264
5265 perf_event_free_bpf_prog(event);
5266 perf_addr_filters_splice(event, NULL);
5267 kfree(event->addr_filter_ranges);
5268
5269 if (event->destroy)
5270 event->destroy(event);
5271
5272 /*
5273 * Must be after ->destroy(), due to uprobe_perf_close() using
5274 * hw.target.
5275 */
5276 if (event->hw.target)
5277 put_task_struct(event->hw.target);
5278
5279 if (event->pmu_ctx)
5280 put_pmu_ctx(event->pmu_ctx);
5281
5282 /*
5283 * perf_event_free_task() relies on put_ctx() being 'last', in
particular
5284 * all task references must be cleaned up.
5285 */
5286 if (event->ctx)
5287 put_ctx(event->ctx);
5288
5289 exclusive_event_destroy(event);
5290
5291 pmu_module_put(&event->pmu);
5292
5293 call_rcu(&event->rcu_head, free_event_rcu);
5294 }
5295
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH RESEND] locking/ww_mutex: Adjust to lockdep nest_lock requirements
Hello,
kernel test robot noticed "WARNING:at_kernel/locking/lockdep.c:#__lock_acquire"
on:
commit: d417c66b8b12b5706c9df4ddf5367af540f195c6 ("[PATCH RESEND]
locking/ww_mutex: Adjust to lockdep nest_lock requirements")
url:
https://github.com/intel-lab-lkp/linux/commits/Thomas-Hellstr-m/locking-ww_mutex-Adjust-to-lockdep-nest_lock-requirements/20241002-205818
base: https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git
d00b83d416e73bc3fa4d21b14bec920e88b70ce6
patch link:
https://lore.kernel.org/all/20241002125611.361001-1-thomas.hellst...@linux.intel.com/
patch subject: [PATCH RESEND] locking/ww_mutex: Adjust to lockdep nest_lock
requirements
in testcase: kernel-selftests
version: kernel-selftests-x86_64-977d51cf-1_20240508
with following parameters:
group: locking
compiler: gcc-12
test machine: 4 threads Intel(R) Xeon(R) CPU E3-1225 v5 @ 3.30GHz (Skylake)
with 16G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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
| Closes:
https://lore.kernel.org/oe-lkp/202410091542.f6c4a438-oliver.s...@intel.com
[ 63.327071][ T246] [ cut here ]
[ 63.332388][ T246] DEBUG_LOCKS_WARN_ON(hlock->references < references)
[ 63.332410][ T246] WARNING: CPU: 2 PID: 246 at kernel/locking/lockdep.c:5058
__lock_acquire (kernel/locking/lockdep.c:5058 (discriminator 9))
[ 63.348622][ T246] Modules linked in: test_ww_mutex(+) openvswitch
nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 psample btrfs
blake2b_generic xor zstd_compress raid6_pq libcrc32c intel_rapl_msr
intel_rapl_common x86_pkg_temp_thermal intel_powerclamp sd_mod coretemp sg
kvm_intel ipmi_devintf ipmi_msghandler i915 kvm binfmt_misc drm_buddy intel_gtt
drm_display_helper crct10dif_pclmul crc32_pclmul crc32c_intel mei_wdt
ghash_clmulni_intel ttm wmi_bmof sha512_ssse3 ahci rapl drm_kms_helper libahci
video intel_cstate intel_uncore serio_raw libata mei_me i2c_i801 mei i2c_smbus
intel_pch_thermal ie31200_edac wmi acpi_pad tpm_infineon loop fuse drm dm_mod
ip_tables sch_fq_codel
[ 63.409553][ T246] CPU: 2 PID: 246 Comm: kworker/u16:5 Tainted: G S
6.10.0-04481-gd417c66b8b12 #1
[ 63.419907][ T246] Hardware name: HP HP Z238 Microtower Workstation/8183,
BIOS N51 Ver. 01.63 10/05/2017
[ 63.429471][ T246] Workqueue: test-ww_mutex stress_inorder_work
[test_ww_mutex]
[ 63.436889][ T246] RIP: 0010:__lock_acquire (kernel/locking/lockdep.c:5058
(discriminator 9))
[ 63.442284][ T246] Code: d2 0f 85 15 0c 00 00 44 8b 0d 7d df c7 04 45 85 c9 0f
85 d0 fe ff ff 48 c7 c6 c0 c1 2a 84 48 c7 c7 00 91 2a 84 e8 8d 39 e5 ff <0f> 0b
e9 b6 fe ff ff 41 be 02 00 00 00 e9 11 f7 ff ff 31 db e9 bb
All code
0: d2 0f rorb %cl,(%rdi)
2: 85 15 0c 00 00 44 test %edx,0x440c(%rip)# 0x4414
8: 8b 0d 7d df c7 04 mov0x4c7df7d(%rip),%ecx# 0x4c7df8b
e: 45 85 c9test %r9d,%r9d
11: 0f 85 d0 fe ff ff jne0xfee7
17: 48 c7 c6 c0 c1 2a 84mov$0x842ac1c0,%rsi
1e: 48 c7 c7 00 91 2a 84mov$0x842a9100,%rdi
25: e8 8d 39 e5 ff callq 0xffe539b7
2a:* 0f 0b ud2 <-- trapping instruction
2c: e9 b6 fe ff ff jmpq 0xfee7
31: 41 be 02 00 00 00 mov$0x2,%r14d
37: e9 11 f7 ff ff jmpq 0xf74d
3c: 31 db xor%ebx,%ebx
3e: e9 .byte 0xe9
3f: bb .byte 0xbb
Code starting with the faulting instruction
===
0: 0f 0b ud2
2: e9 b6 fe ff ff jmpq 0xfebd
7: 41 be 02 00 00 00 mov$0x2,%r14d
d: e9 11 f7 ff ff jmpq 0xf723
12: 31 db xor%ebx,%ebx
14: e9 .byte 0xe9
15: bb .byte 0xbb
[ 63.461748][ T246] RSP: 0018:c9000141f7a8 EFLAGS: 00010086
[ 63.467683][ T246] RAX: RBX: 0001 RCX:
0027
[ 63.475525][ T246] RDX: 0027 RSI: 0004 RDI:
8883b5330c48
[ 63.483354][ T246] RBP: 888430688000 R08: 0001 R09:
ed1076a66189
[ 63.491172][ T246] R10: 8883b5330c4b R11: 0001 R12:
888430688f58
[ 63.499015][ T246] R13: 00a0 R14: 88841d5b1f28 R15:
[ 63.506860][ T246] FS: () GS:8883b530()
knlGS:
[ 63.515659][ T246] CS: 0010 DS: ES: CR0: 80050033
[ 63.522116][ T246] CR2: 5566d67bd842 CR3: 00043b67e002 CR4:
Re: [PATCH v1 1/4] misc: fastrpc: Add CRC support using invokeV2 request
Hi Ekansh,
kernel test robot noticed the following build warnings:
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on char-misc/char-misc-next char-misc/char-misc-linus
linus/master v6.12-rc2 next-20241008]
[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/Ekansh-Gupta/misc-fastrpc-Add-CRC-support-using-invokeV2-request/20241007-164734
base: char-misc/char-misc-testing
patch link:
https://lore.kernel.org/r/20241007084518.3649876-2-quic_ekangupt%40quicinc.com
patch subject: [PATCH v1 1/4] misc: fastrpc: Add CRC support using invokeV2
request
config: alpha-randconfig-r112-20241008
(https://download.01.org/0day-ci/archive/20241009/202410090402.lospefvz-...@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.3.0
reproduce:
(https://download.01.org/0day-ci/archive/20241009/202410090402.lospefvz-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410090402.lospefvz-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/misc/fastrpc.c:1696:19: sparse: sparse: incorrect type in assignment
>> (different base types) @@ expected unsigned long long [usertype] args @@
>> got struct fastrpc_invoke_args *[assigned] args @@
drivers/misc/fastrpc.c:1696:19: sparse: expected unsigned long long
[usertype] args
drivers/misc/fastrpc.c:1696:19: sparse: got struct fastrpc_invoke_args
*[assigned] args
>> drivers/misc/fastrpc.c:1716:18: sparse: sparse: incorrect type in argument 1
>> (different base types) @@ expected void const *objp @@ got unsigned
>> long long [addressable] [usertype] args @@
drivers/misc/fastrpc.c:1716:18: sparse: expected void const *objp
drivers/misc/fastrpc.c:1716:18: sparse: got unsigned long long
[addressable] [usertype] args
drivers/misc/fastrpc.c:1734:23: sparse: sparse: incorrect type in argument 1
(different base types) @@ expected void const *objp @@ got unsigned
long long [addressable] [usertype] args @@
drivers/misc/fastrpc.c:1734:23: sparse: expected void const *objp
drivers/misc/fastrpc.c:1734:23: sparse: got unsigned long long
[addressable] [usertype] args
drivers/misc/fastrpc.c: note: in included file (through
include/linux/swait.h, include/linux/completion.h):
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates
to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates
to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates
to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates
to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates
to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates
to true
vim +1696 drivers/misc/fastrpc.c
1677
1678 static int fastrpc_copy_args(struct fastrpc_invoke *inv)
1679 {
1680 struct fastrpc_invoke_args *args = NULL;
1681 u32 nscalars;
1682
1683 /* nscalars is truncated here to max supported value */
1684 nscalars = REMOTE_SCALARS_LENGTH(inv->sc);
1685 if (nscalars) {
1686 args = kcalloc(nscalars, sizeof(*args), GFP_KERNEL);
1687 if (!args)
1688 return -ENOMEM;
1689
1690 if (copy_from_user(args, (void __user
*)(uintptr_t)inv->args,
1691 nscalars * sizeof(*args))) {
1692 kfree(args);
1693 return -EFAULT;
1694 }
1695 }
> 1696 inv->args = args;
1697
1698 return 0;
1699 }
1700
1701 static int fastrpc_invoke(struct fastrpc_user *fl, char __user *argp)
1702 {
1703 struct fastrpc_invoke_v2 ioctl = {0};
1704 struct fastrpc_invoke inv;
1705 int err;
1706
1707 if (copy_from_user(&inv, argp, sizeof(inv)))
1708 return -EFAULT;
1709
1710 err = fastrpc_copy_args(&inv);
1711 if (err)
1712 return err;
1713
1714 ioctl.inv = inv;
1715 err = fastrpc_internal_invoke(fl, false, &ioctl);
> 1716 kfree(inv.args);
1717
1718 return err;
1719 }
1720
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v1 1/4] misc: fastrpc: Add CRC support using invokeV2 request
Hi Ekansh,
kernel test robot noticed the following build errors:
[auto build test ERROR on char-misc/char-misc-testing]
[also build test ERROR on char-misc/char-misc-next char-misc/char-misc-linus
linus/master v6.12-rc2 next-20241004]
[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/Ekansh-Gupta/misc-fastrpc-Add-CRC-support-using-invokeV2-request/20241007-164734
base: char-misc/char-misc-testing
patch link:
https://lore.kernel.org/r/20241007084518.3649876-2-quic_ekangupt%40quicinc.com
patch subject: [PATCH v1 1/4] misc: fastrpc: Add CRC support using invokeV2
request
config: loongarch-allmodconfig
(https://download.01.org/0day-ci/archive/20241008/202410081016.nuyub4xk-...@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241008/202410081016.nuyub4xk-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410081016.nuyub4xk-...@intel.com/
All errors (new ones prefixed by >>):
drivers/misc/fastrpc.c: In function 'fastrpc_copy_args':
>> drivers/misc/fastrpc.c:1696:19: error: assignment to '__u64' {aka 'long long
>> unsigned int'} from 'struct fastrpc_invoke_args *' makes integer from
>> pointer without a cast [-Wint-conversion]
1696 | inv->args = args;
| ^
drivers/misc/fastrpc.c: In function 'fastrpc_invoke':
>> drivers/misc/fastrpc.c:1716:18: error: passing argument 1 of 'kfree' makes
>> pointer from integer without a cast [-Wint-conversion]
1716 | kfree(inv.args);
| ~~~^
| |
| __u64 {aka long long unsigned int}
In file included from include/linux/fs.h:45,
from arch/loongarch/include/asm/elf.h:9,
from include/linux/elf.h:6,
from include/linux/module.h:19,
from include/linux/device/driver.h:21,
from include/linux/device.h:32,
from drivers/misc/fastrpc.c:6:
include/linux/slab.h:446:24: note: expected 'const void *' but argument is
of type '__u64' {aka 'long long unsigned int'}
446 | void kfree(const void *objp);
|^~~~
drivers/misc/fastrpc.c: In function 'fastrpc_invokev2':
drivers/misc/fastrpc.c:1734:23: error: passing argument 1 of 'kfree' makes
pointer from integer without a cast [-Wint-conversion]
1734 | kfree(inv2.inv.args);
| ^
| |
| __u64 {aka long long unsigned int}
include/linux/slab.h:446:24: note: expected 'const void *' but argument is
of type '__u64' {aka 'long long unsigned int'}
446 | void kfree(const void *objp);
|^~~~
vim +1696 drivers/misc/fastrpc.c
1677
1678 static int fastrpc_copy_args(struct fastrpc_invoke *inv)
1679 {
1680 struct fastrpc_invoke_args *args = NULL;
1681 u32 nscalars;
1682
1683 /* nscalars is truncated here to max supported value */
1684 nscalars = REMOTE_SCALARS_LENGTH(inv->sc);
1685 if (nscalars) {
1686 args = kcalloc(nscalars, sizeof(*args), GFP_KERNEL);
1687 if (!args)
1688 return -ENOMEM;
1689
1690 if (copy_from_user(args, (void __user
*)(uintptr_t)inv->args,
1691 nscalars * sizeof(*args))) {
1692 kfree(args);
1693 return -EFAULT;
1694 }
1695 }
> 1696 inv->args = args;
1697
1698 return 0;
1699 }
1700
1701 static int fastrpc_invoke(struct fastrpc_user *fl, char __user *argp)
1702 {
1703 struct fastrpc_invoke_v2 ioctl = {0};
1704 struct fastrpc_invoke inv;
1705 int err;
1706
1707 if (copy_from_user(&inv, argp, sizeof(inv)))
1708 return -EFAULT;
1709
1710 err = fastrpc_copy_args(&inv);
1711 if (err)
1712 return err;
1713
1714 ioctl.inv = inv;
1715 err = fastrpc_internal_invoke(fl, false, &ioctl);
> 1716 kfree(inv.args);
1717
1718 return err;
1719 }
1720
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v1 1/4] misc: fastrpc: Add CRC support using invokeV2 request
Hi Ekansh,
kernel test robot noticed the following build errors:
[auto build test ERROR on char-misc/char-misc-testing]
[also build test ERROR on char-misc/char-misc-next char-misc/char-misc-linus
linus/master v6.12-rc2 next-20241004]
[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/Ekansh-Gupta/misc-fastrpc-Add-CRC-support-using-invokeV2-request/20241007-164734
base: char-misc/char-misc-testing
patch link:
https://lore.kernel.org/r/20241007084518.3649876-2-quic_ekangupt%40quicinc.com
patch subject: [PATCH v1 1/4] misc: fastrpc: Add CRC support using invokeV2
request
config: arm-randconfig-002-20241008
(https://download.01.org/0day-ci/archive/20241008/202410080940.s7rar8zi-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
fef3566a25ff0e34fb87339ba5e13eca17cec00f)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241008/202410080940.s7rar8zi-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410080940.s7rar8zi-...@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/misc/fastrpc.c:7:
In file included from include/linux/dma-buf.h:19:
In file included from include/linux/scatterlist.h:8:
In file included from include/linux/mm.h:2213:
include/linux/vmstat.h:518:36: warning: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
>> drivers/misc/fastrpc.c:1696:12: error: incompatible pointer to integer
>> conversion assigning to '__u64' (aka 'unsigned long long') from 'struct
>> fastrpc_invoke_args *' [-Wint-conversion]
1696 | inv->args = args;
| ^
>> drivers/misc/fastrpc.c:1716:8: error: incompatible integer to pointer
>> conversion passing '__u64' (aka 'unsigned long long') to parameter of type
>> 'const void *' [-Wint-conversion]
1716 | kfree(inv.args);
| ^~~~
include/linux/slab.h:446:24: note: passing argument to parameter 'objp' here
446 | void kfree(const void *objp);
|^
drivers/misc/fastrpc.c:1734:8: error: incompatible integer to pointer
conversion passing '__u64' (aka 'unsigned long long') to parameter of type
'const void *' [-Wint-conversion]
1734 | kfree(inv2.inv.args);
| ^
include/linux/slab.h:446:24: note: passing argument to parameter 'objp' here
446 | void kfree(const void *objp);
|^
1 warning and 3 errors generated.
vim +1696 drivers/misc/fastrpc.c
1677
1678 static int fastrpc_copy_args(struct fastrpc_invoke *inv)
1679 {
1680 struct fastrpc_invoke_args *args = NULL;
1681 u32 nscalars;
1682
1683 /* nscalars is truncated here to max supported value */
1684 nscalars = REMOTE_SCALARS_LENGTH(inv->sc);
1685 if (nscalars) {
1686 args = kcalloc(nscalars, sizeof(*args), GFP_KERNEL);
1687 if (!args)
1688 return -ENOMEM;
1689
1690 if (copy_from_user(args, (void __user
*)(uintptr_t)inv->args,
1691 nscalars * sizeof(*args))) {
1692 kfree(args);
1693 return -EFAULT;
1694 }
1695 }
> 1696 inv->args = args;
1697
1698 return 0;
1699 }
1700
1701 static int fastrpc_invoke(struct fastrpc_user *fl, char __user *argp)
1702 {
1703 struct fastrpc_invoke_v2 ioctl = {0};
1704 struct fastrpc_invoke inv;
1705 int err;
1706
1707 if (copy_from_user(&inv, argp, sizeof(inv)))
1708 return -EFAULT;
1709
1710 err = fastrpc_copy_args(&inv);
1711 if (err)
1712 return err;
1713
1714 ioctl.inv = inv;
1715 err = fastrpc_internal_invoke(fl, false, &ioctl);
> 1716 kfree(inv.args);
1717
1718 return err;
1719 }
1720
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v1 1/4] misc: fastrpc: Add CRC support using invokeV2 request
Hi Ekansh,
kernel test robot noticed the following build warnings:
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on char-misc/char-misc-next char-misc/char-misc-linus
linus/master v6.12-rc2 next-20241004]
[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/Ekansh-Gupta/misc-fastrpc-Add-CRC-support-using-invokeV2-request/20241007-164734
base: char-misc/char-misc-testing
patch link:
https://lore.kernel.org/r/20241007084518.3649876-2-quic_ekangupt%40quicinc.com
patch subject: [PATCH v1 1/4] misc: fastrpc: Add CRC support using invokeV2
request
config: arc-randconfig-001-20241008
(https://download.01.org/0day-ci/archive/20241008/202410080906.2kcmky5c-...@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241008/202410080906.2kcmky5c-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410080906.2kcmky5c-...@intel.com/
All warnings (new ones prefixed by >>):
drivers/misc/fastrpc.c: In function 'fastrpc_context_alloc':
>> drivers/misc/fastrpc.c:584:16: warning: cast to pointer from integer of
>> different size [-Wint-to-pointer-cast]
584 | args = (struct fastrpc_invoke_args *)inv2->inv.args;
|^
drivers/misc/fastrpc.c: In function 'fastrpc_init_create_static_process':
>> drivers/misc/fastrpc.c:1331:26: warning: cast from pointer to integer of
>> different size [-Wpointer-to-int-cast]
1331 | ioctl.inv.args = (u64)args;
| ^
drivers/misc/fastrpc.c: In function 'fastrpc_init_create_process':
drivers/misc/fastrpc.c:1464:26: warning: cast from pointer to integer of
different size [-Wpointer-to-int-cast]
1464 | ioctl.inv.args = (u64)args;
| ^
drivers/misc/fastrpc.c: In function 'fastrpc_release_current_dsp_process':
drivers/misc/fastrpc.c:1527:26: warning: cast from pointer to integer of
different size [-Wpointer-to-int-cast]
1527 | ioctl.inv.args = (u64)args;
| ^
drivers/misc/fastrpc.c: In function 'fastrpc_init_attach':
drivers/misc/fastrpc.c:1674:26: warning: cast from pointer to integer of
different size [-Wpointer-to-int-cast]
1674 | ioctl.inv.args = (u64)args;
| ^
drivers/misc/fastrpc.c: In function 'fastrpc_copy_args':
>> drivers/misc/fastrpc.c:1696:19: warning: assignment to '__u64' {aka 'long
>> long unsigned int'} from 'struct fastrpc_invoke_args *' makes integer from
>> pointer without a cast [-Wint-conversion]
1696 | inv->args = args;
| ^
drivers/misc/fastrpc.c: In function 'fastrpc_invoke':
>> drivers/misc/fastrpc.c:1716:18: warning: passing argument 1 of 'kfree' makes
>> pointer from integer without a cast [-Wint-conversion]
1716 | kfree(inv.args);
| ~~~^
| |
| __u64 {aka long long unsigned int}
In file included from include/linux/mm.h:33,
from include/linux/scatterlist.h:8,
from include/linux/dma-buf.h:19,
from drivers/misc/fastrpc.c:7:
include/linux/slab.h:446:24: note: expected 'const void *' but argument is
of type '__u64' {aka 'long long unsigned int'}
446 | void kfree(const void *objp);
|^~~~
drivers/misc/fastrpc.c: In function 'fastrpc_invokev2':
drivers/misc/fastrpc.c:1734:23: warning: passing argument 1 of 'kfree' makes
pointer from integer without a cast [-Wint-conversion]
1734 | kfree(inv2.inv.args);
| ^
| |
| __u64 {aka long long unsigned int}
include/linux/slab.h:446:24: note: expected 'const void *' but argument is
of type '__u64' {aka 'long long unsigned int'}
446 | void kfree(const void *objp);
|^~~~
drivers/misc/fastrpc.c: In function 'fastrpc_get_info_from_dsp':
drivers/misc/fastrpc.c:1762:26: warning: cast from pointer to integer of
different size [-Wpointer-to-int-cast]
1762 | ioctl.inv.args =
Re: [PATCH v2] fbdev: sstfb: Make CONFIG_FB_DEVICE optional
Hi Gonzalo,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on linus/master v6.12-rc2 next-20241004]
[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/Gonzalo-Silvalde-Blanco/fbdev-sstfb-Make-CONFIG_FB_DEVICE-optional/20241004-232658
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20241004152429.4329-1-gonzalo.silvalde%40gmail.com
patch subject: [PATCH v2] fbdev: sstfb: Make CONFIG_FB_DEVICE optional
config: i386-allyesconfig
(https://download.01.org/0day-ci/archive/20241007/202410072022.orquf7dt-...@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/20241007/202410072022.orquf7dt-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410072022.orquf7dt-...@intel.com/
All errors (new ones prefixed by >>):
drivers/video/fbdev/sstfb.c: In function 'sstfb_probe':
>> drivers/video/fbdev/sstfb.c:1439:2: error: invalid preprocessing directive
>> #fdef; did you mean #ifdef?
1439 | #fdef CONFIG_FB_DEVICE
| ^~~~
| ifdef
drivers/video/fbdev/sstfb.c:1442:2: error: #endif without #if
1442 | #endif
| ^
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for MODVERSIONS
Depends on [n]: MODULES [=y] && !COMPILE_TEST [=y]
Selected by [y]:
- RANDSTRUCT_FULL [=y] && (CC_HAS_RANDSTRUCT [=n] || GCC_PLUGINS [=y]) &&
MODULES [=y]
WARNING: unmet direct dependencies detected for GET_FREE_REGION
Depends on [n]: SPARSEMEM [=n]
Selected by [y]:
- RESOURCE_KUNIT_TEST [=y] && RUNTIME_TESTING_MENU [=y] && KUNIT [=y]
vim +1439 drivers/video/fbdev/sstfb.c
1320
1321 static int sstfb_probe(struct pci_dev *pdev, const struct pci_device_id
*id)
1322 {
1323 struct fb_info *info;
1324 struct fb_fix_screeninfo *fix;
1325 struct sstfb_par *par;
1326 struct sst_spec *spec;
1327 int err;
1328
1329 err = aperture_remove_conflicting_pci_devices(pdev, "sstfb");
1330 if (err)
1331 return err;
1332
1333 /* Enable device in PCI config. */
1334 if ((err=pci_enable_device(pdev))) {
1335 printk(KERN_ERR "cannot enable device\n");
1336 return err;
1337 }
1338
1339 /* Allocate the fb and par structures. */
1340 info = framebuffer_alloc(sizeof(struct sstfb_par), &pdev->dev);
1341 if (!info)
1342 return -ENOMEM;
1343
1344 pci_set_drvdata(pdev, info);
1345
1346 par = info->par;
1347 fix = &info->fix;
1348
1349 par->type = id->driver_data;
1350 spec = &voodoo_spec[par->type];
1351 f_ddprintk("found device : %s\n", spec->name);
1352
1353 par->dev = pdev;
1354 par->revision = pdev->revision;
1355
1356 fix->mmio_start = pci_resource_start(pdev,0);
1357 fix->mmio_len = 0x40;
1358 fix->smem_start = fix->mmio_start + 0x40;
1359
1360 if (!request_mem_region(fix->mmio_start, fix->mmio_len, "sstfb
MMIO")) {
1361 printk(KERN_ERR "sstfb: cannot reserve mmio memory\n");
1362 goto fail_mmio_mem;
1363 }
1364
1365 if (!request_mem_region(fix->smem_start, 0x40,"sstfb FB")) {
1366 printk(KERN_ERR "sstfb: cannot reserve fb memory\n");
1367 goto fail_fb_mem;
1368 }
1369
1370 par->mmio_vbase = ioremap(fix->mmio_start,
1371 fix->mmio_len);
1372 if (!par->mmio_vbase) {
1373 printk(KERN_ERR "sstfb: cannot remap register area
%#lx\n",
1374 fix->mmio_start);
1375 goto fail_mmio_remap;
1376 }
1377 info->screen_base = ioremap(fix->smem_start, 0x40);
1378 if (!info->screen_base) {
1379 printk(KERN_ERR "sstfb: cannot remap framebuffer
%#lx\n",
1380 fix->smem_start);
1381
Re: [PATCH v2] fbdev: sstfb: Make CONFIG_FB_DEVICE optional
Hi Gonzalo,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on drm-tip/drm-tip linus/master v6.12-rc2 next-20241004]
[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/Gonzalo-Silvalde-Blanco/fbdev-sstfb-Make-CONFIG_FB_DEVICE-optional/20241004-232658
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20241004152429.4329-1-gonzalo.silvalde%40gmail.com
patch subject: [PATCH v2] fbdev: sstfb: Make CONFIG_FB_DEVICE optional
config: x86_64-allyesconfig
(https://download.01.org/0day-ci/archive/20241007/202410071957.gjrykfof-...@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project
3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241007/202410071957.gjrykfof-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410071957.gjrykfof-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/video/fbdev/sstfb.c:1439:2: error: invalid preprocessing directive
1439 | #fdef CONFIG_FB_DEVICE
| ^
>> drivers/video/fbdev/sstfb.c:1442:2: error: #endif without #if
1442 | #endif
| ^
2 errors generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for MODVERSIONS
Depends on [n]: MODULES [=y] && !COMPILE_TEST [=y]
Selected by [y]:
- RANDSTRUCT_FULL [=y] && (CC_HAS_RANDSTRUCT [=y] || GCC_PLUGINS [=n]) &&
MODULES [=y]
vim +1439 drivers/video/fbdev/sstfb.c
1320
1321 static int sstfb_probe(struct pci_dev *pdev, const struct pci_device_id
*id)
1322 {
1323 struct fb_info *info;
1324 struct fb_fix_screeninfo *fix;
1325 struct sstfb_par *par;
1326 struct sst_spec *spec;
1327 int err;
1328
1329 err = aperture_remove_conflicting_pci_devices(pdev, "sstfb");
1330 if (err)
1331 return err;
1332
1333 /* Enable device in PCI config. */
1334 if ((err=pci_enable_device(pdev))) {
1335 printk(KERN_ERR "cannot enable device\n");
1336 return err;
1337 }
1338
1339 /* Allocate the fb and par structures. */
1340 info = framebuffer_alloc(sizeof(struct sstfb_par), &pdev->dev);
1341 if (!info)
1342 return -ENOMEM;
1343
1344 pci_set_drvdata(pdev, info);
1345
1346 par = info->par;
1347 fix = &info->fix;
1348
1349 par->type = id->driver_data;
1350 spec = &voodoo_spec[par->type];
1351 f_ddprintk("found device : %s\n", spec->name);
1352
1353 par->dev = pdev;
1354 par->revision = pdev->revision;
1355
1356 fix->mmio_start = pci_resource_start(pdev,0);
1357 fix->mmio_len = 0x40;
1358 fix->smem_start = fix->mmio_start + 0x40;
1359
1360 if (!request_mem_region(fix->mmio_start, fix->mmio_len, "sstfb
MMIO")) {
1361 printk(KERN_ERR "sstfb: cannot reserve mmio memory\n");
1362 goto fail_mmio_mem;
1363 }
1364
1365 if (!request_mem_region(fix->smem_start, 0x40,"sstfb FB")) {
1366 printk(KERN_ERR "sstfb: cannot reserve fb memory\n");
1367 goto fail_fb_mem;
1368 }
1369
1370 par->mmio_vbase = ioremap(fix->mmio_start,
1371 fix->mmio_len);
1372 if (!par->mmio_vbase) {
1373 printk(KERN_ERR "sstfb: cannot remap register area
%#lx\n",
1374 fix->mmio_start);
1375 goto fail_mmio_remap;
1376 }
1377 info->screen_base = ioremap(fix->smem_start, 0x40);
1378 if (!info->screen_base) {
1379 printk(KERN_ERR "sstfb: cannot remap framebuffer
%#lx\n",
1380 fix->smem_start);
1381 goto fail_fb_remap;
1382 }
1383
1384 if (!sst_init(info, par)) {
1385 printk(KERN_ERR "sstfb: Init failed\n");
1386 goto fail;
1387
Re: [PATCH v2 05/10] drm/armada: Allow build with COMPILE_TEST=y
Hi Ville,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20241003]
[cannot apply to shawnguo/for-next linus/master rmk-arm/drm-armada-devel
rmk-arm/drm-armada-fixes v6.12-rc1 v6.11 v6.11-rc7 v6.12-rc2]
[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/Ville-Syrjala/drm-tilcdc-Allow-build-without-__iowmb/20241003-192043
base: next-20241003
patch link:
https://lore.kernel.org/r/20241003111851.10453-6-ville.syrjala%40linux.intel.com
patch subject: [PATCH v2 05/10] drm/armada: Allow build with COMPILE_TEST=y
config: csky-randconfig-r121-20241006
(https://download.01.org/0day-ci/archive/20241007/202410070736.gtekje6r-...@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.1.0
reproduce:
(https://download.01.org/0day-ci/archive/20241007/202410070736.gtekje6r-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410070736.gtekje6r-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/armada/armada_gem.c:63:37: sparse: sparse: incorrect type in
>> argument 1 (different address spaces) @@ expected void volatile
>> [noderef] __iomem *addr @@ got void *addr @@
drivers/gpu/drm/armada/armada_gem.c:63:37: sparse: expected void
volatile [noderef] __iomem *addr
drivers/gpu/drm/armada/armada_gem.c:63:37: sparse: got void *addr
drivers/gpu/drm/armada/armada_gem.c:185:28: sparse: sparse: incorrect type
in assignment (different address spaces) @@ expected void *addr @@ got
void [noderef] __iomem * @@
drivers/gpu/drm/armada/armada_gem.c:185:28: sparse: expected void *addr
drivers/gpu/drm/armada/armada_gem.c:185:28: sparse: got void [noderef]
__iomem *
vim +63 drivers/gpu/drm/armada/armada_gem.c
96f60e37dc6609 Russell King2012-08-15 40
96f60e37dc6609 Russell King2012-08-15 41 void
armada_gem_free_object(struct drm_gem_object *obj)
96f60e37dc6609 Russell King2012-08-15 42 {
96f60e37dc6609 Russell King2012-08-15 43 struct armada_gem_object *dobj
= drm_to_armada_gem(obj);
dad75a5208ec88 Simona Vetter 2020-09-04 44 struct armada_private *priv =
drm_to_armada_dev(obj->dev);
96f60e37dc6609 Russell King2012-08-15 45
96f60e37dc6609 Russell King2012-08-15 46 DRM_DEBUG_DRIVER("release obj
%p\n", dobj);
96f60e37dc6609 Russell King2012-08-15 47
96f60e37dc6609 Russell King2012-08-15 48
drm_gem_free_mmap_offset(&dobj->obj);
96f60e37dc6609 Russell King2012-08-15 49
0b8ebeacf5ef43 Simona Vetter 2015-11-24 50 might_lock(&priv->linear_lock);
0b8ebeacf5ef43 Simona Vetter 2015-11-24 51
96f60e37dc6609 Russell King2012-08-15 52 if (dobj->page) {
96f60e37dc6609 Russell King2012-08-15 53 /* page backed memory */
96f60e37dc6609 Russell King2012-08-15 54 unsigned int order =
get_order(dobj->obj.size);
96f60e37dc6609 Russell King2012-08-15 55
__free_pages(dobj->page, order);
96f60e37dc6609 Russell King2012-08-15 56 } else if (dobj->linear) {
96f60e37dc6609 Russell King2012-08-15 57 /* linear backed memory
*/
0b8ebeacf5ef43 Simona Vetter 2015-11-24 58
mutex_lock(&priv->linear_lock);
96f60e37dc6609 Russell King2012-08-15 59
drm_mm_remove_node(dobj->linear);
0b8ebeacf5ef43 Simona Vetter 2015-11-24 60
mutex_unlock(&priv->linear_lock);
96f60e37dc6609 Russell King2012-08-15 61 kfree(dobj->linear);
96f60e37dc6609 Russell King2012-08-15 62 if (dobj->addr)
96f60e37dc6609 Russell King2012-08-15 @63
iounmap(dobj->addr);
96f60e37dc6609 Russell King2012-08-15 64 }
96f60e37dc6609 Russell King2012-08-15 65
96f60e37dc6609 Russell King2012-08-15 66 if (dobj->obj.import_attach) {
96f60e37dc6609 Russell King2012-08-15 67 /* We only ever display
imported data */
0481c8c47f5e85 Russell King2015-06-15 68 if (dobj->sgt)
e4ea542846d0ef Dmitry Osipenko 2022-10-17 69
dma_buf_unmap_attachment_unlocked(dobj->obj.import_attach,
0481c8c47f5e85 Russell King2015-06-15 70
dobj->sgt, DMA_TO_DEVICE);
96f60e37dc6609 Russell King2012-08-15 71
drm_prime_gem_destroy(&dobj->obj, NULL);
96f60e37dc6609 Russell King2012-08-15 72 }
96f60e37dc6609 Russell King2012-08-15 73
96f60e37dc6609 Russell King2012-08-15 74
drm_gem_object_release(&
Re: [PATCH] gpu/drm: set gamma_lut or degamma_lut based on HW in setcmap_atomic
Hi Vamsi, kernel test robot noticed the following build errors: [auto build test ERROR on 7ec462100ef9142344ddbf86f2c3008b97acddbe] url: https://github.com/intel-lab-lkp/linux/commits/Vamsi-Krishna-Brahmajosyula/gpu-drm-set-gamma_lut-or-degamma_lut-based-on-HW-in-setcmap_atomic/20241003-200835 base: 7ec462100ef9142344ddbf86f2c3008b97acddbe patch link: https://lore.kernel.org/r/20241003120655.53663-1-vamsikrishna.brahmajosyula%40gmail.com patch subject: [PATCH] gpu/drm: set gamma_lut or degamma_lut based on HW in setcmap_atomic config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20241006/202410060802.ln9ygpuy-...@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/20241006/202410060802.ln9ygpuy-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410060802.ln9ygpuy-...@intel.com/ All errors (new ones prefixed by >>, old ones prefixed by <<): >> ERROR: modpost: "drm_mode_obj_find_prop_id" >> [drivers/gpu/drm/drm_kms_helper.ko] undefined! -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 29/44] drm/amd/display: Add support for sRGB EOTF in BLND block
Hi Harry,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm/drm-next]
[also build test ERROR on drm-exynos/exynos-drm-next drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip
linus/master v6.12-rc1 next-20241004]
[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/Harry-Wentland/drm-Add-helper-for-conversion-from-signed-magnitude/20241004-040629
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20241003200129.1732122-30-harry.wentland%40amd.com
patch subject: [PATCH v6 29/44] drm/amd/display: Add support for sRGB EOTF in
BLND block
config: x86_64-randconfig-122-20241005
(https://download.01.org/0day-ci/archive/20241005/202410052207.g19vlhrt-...@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project
3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241005/202410052207.g19vlhrt-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410052207.g19vlhrt-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_color.c:1296:46:
>> error: variable 'blend_size' is uninitialized when used here
>> [-Werror,-Wuninitialized]
1296 | return __set_input_tf(NULL, tf, blend_lut,
blend_size);
|^~
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_color.c:1278:21:
note: initialize the variable 'blend_size' to silence this warning
1278 | uint32_t blend_size;
|^
| = 0
1 error generated.
vim +/blend_size +1296
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_color.c
1273
1274 struct dc_transfer_func *tf = &dc_plane_state->blend_tf;
1275 struct drm_colorop *colorop = colorop_state->colorop;
1276 struct drm_device *drm = colorop->dev;
1277 const struct drm_color_lut *blend_lut;
1278 uint32_t blend_size;
1279
1280 if (colorop->type != DRM_COLOROP_1D_CURVE &&
1281 colorop_state->curve_1d_type !=
DRM_COLOROP_1D_CURVE_SRGB_EOTF)
1282 return -EINVAL;
1283
1284 if (colorop_state->bypass) {
1285 tf->type = TF_TYPE_BYPASS;
1286 tf->tf = TRANSFER_FUNCTION_LINEAR;
1287 return 0;
1288 }
1289
1290 drm_dbg(drm, "Blend colorop with ID: %d\n", colorop->base.id);
1291
1292 if (colorop->type == DRM_COLOROP_1D_CURVE) {
1293 tf->type = TF_TYPE_DISTRIBUTED_POINTS;
1294 tf->tf =
amdgpu_colorop_tf_to_dc_tf(colorop_state->curve_1d_type);
1295 tf->sdr_ref_white_level = SDR_WHITE_LEVEL_INIT_VALUE;
> 1296 return __set_input_tf(NULL, tf, blend_lut, blend_size);
1297 }
1298
1299 return -EINVAL;
1300 }
1301
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 29/44] drm/amd/display: Add support for sRGB EOTF in BLND block
Hi Harry,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-exynos/exynos-drm-next drm-misc/drm-misc-next
linus/master v6.12-rc1 next-20241004]
[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/Harry-Wentland/drm-Add-helper-for-conversion-from-signed-magnitude/20241004-040629
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20241003200129.1732122-30-harry.wentland%40amd.com
patch subject: [PATCH v6 29/44] drm/amd/display: Add support for sRGB EOTF in
BLND block
config: x86_64-allyesconfig
(https://download.01.org/0day-ci/archive/20241005/202410052046.3g21jba1-...@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project
3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241005/202410052046.3g21jba1-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410052046.3g21jba1-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_color.c:1296:46:
>> warning: variable 'blend_size' is uninitialized when used here
>> [-Wuninitialized]
1296 | return __set_input_tf(NULL, tf, blend_lut,
blend_size);
|^~
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_color.c:1278:21:
note: initialize the variable 'blend_size' to silence this warning
1278 | uint32_t blend_size;
|^
| = 0
1 warning generated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for MODVERSIONS
Depends on [n]: MODULES [=y] && !COMPILE_TEST [=y]
Selected by [y]:
- RANDSTRUCT_FULL [=y] && (CC_HAS_RANDSTRUCT [=y] || GCC_PLUGINS [=n]) &&
MODULES [=y]
vim +/blend_size +1296
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_color.c
1273
1274 struct dc_transfer_func *tf = &dc_plane_state->blend_tf;
1275 struct drm_colorop *colorop = colorop_state->colorop;
1276 struct drm_device *drm = colorop->dev;
1277 const struct drm_color_lut *blend_lut;
1278 uint32_t blend_size;
1279
1280 if (colorop->type != DRM_COLOROP_1D_CURVE &&
1281 colorop_state->curve_1d_type !=
DRM_COLOROP_1D_CURVE_SRGB_EOTF)
1282 return -EINVAL;
1283
1284 if (colorop_state->bypass) {
1285 tf->type = TF_TYPE_BYPASS;
1286 tf->tf = TRANSFER_FUNCTION_LINEAR;
1287 return 0;
1288 }
1289
1290 drm_dbg(drm, "Blend colorop with ID: %d\n", colorop->base.id);
1291
1292 if (colorop->type == DRM_COLOROP_1D_CURVE) {
1293 tf->type = TF_TYPE_DISTRIBUTED_POINTS;
1294 tf->tf =
amdgpu_colorop_tf_to_dc_tf(colorop_state->curve_1d_type);
1295 tf->sdr_ref_white_level = SDR_WHITE_LEVEL_INIT_VALUE;
> 1296 return __set_input_tf(NULL, tf, blend_lut, blend_size);
1297 }
1298
1299 return -EINVAL;
1300 }
1301
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 36/44] drm/amd/display: add 3x4 matrix colorop
Hi Harry,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm/drm-next]
[also build test ERROR on drm-exynos/exynos-drm-next drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip
linus/master v6.12-rc1 next-20241004]
[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/Harry-Wentland/drm-Add-helper-for-conversion-from-signed-magnitude/20241004-040629
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20241003200129.1732122-37-harry.wentland%40amd.com
patch subject: [PATCH v6 36/44] drm/amd/display: add 3x4 matrix colorop
config: i386-randconfig-063-20241005
(https://download.01.org/0day-ci/archive/20241005/202410051812.tvvprkdr-...@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/20241005/202410051812.tvvprkdr-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410051812.tvvprkdr-...@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/device.h:15,
from include/drm/drm_print.h:31,
from drivers/gpu/drm/amd/amdgpu/../amdgpu/amdgpu_ring.h:29,
from drivers/gpu/drm/amd/amdgpu/../amdgpu/amdgpu_ctx.h:29,
from drivers/gpu/drm/amd/amdgpu/../amdgpu/amdgpu.h:43,
from
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_color.c:25:
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_color.c: In
function '__set_dm_plane_colorop_3x4_matrix':
>> drivers/gpu/drm/amd/amdgpu/../amdgpu/amdgpu.h:41:22: error: format '%lu'
>> expects argument of type 'long unsigned int', but argument 3 has type
>> 'size_t' {aka 'unsigned int'} [-Werror=format=]
41 | #define dev_fmt(fmt) "amdgpu: " fmt
| ^~
include/linux/dev_printk.h:110:30: note: in definition of macro
'dev_printk_index_wrap'
110 | _p_func(dev, fmt, ##__VA_ARGS__);
\
| ^~~
include/linux/dev_printk.h:156:61: note: in expansion of macro 'dev_fmt'
156 | dev_printk_index_wrap(_dev_warn, KERN_WARNING, dev,
dev_fmt(fmt), ##__VA_ARGS__)
| ^~~
include/drm/drm_print.h:522:9: note: in expansion of macro 'dev_warn'
522 | dev_##level##type((drm) ? (drm)->dev : NULL, "[drm] " fmt,
##__VA_ARGS__)
| ^~~~
include/drm/drm_print.h:532:9: note: in expansion of macro '__drm_printk'
532 | __drm_printk((drm), warn,, fmt, ##__VA_ARGS__)
| ^~~~
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_color.c:1247:25:
note: in expansion of macro 'drm_warn'
1247 | drm_warn(dev, "blob->length (%lu) isn't
equal to drm_color_ctm_3x4 (%lu)\n",
| ^~~~
>> drivers/gpu/drm/amd/amdgpu/../amdgpu/amdgpu.h:41:22: error: format '%lu'
>> expects argument of type 'long unsigned int', but argument 4 has type
>> 'unsigned int' [-Werror=format=]
41 | #define dev_fmt(fmt) "amdgpu: " fmt
| ^~
include/linux/dev_printk.h:110:30: note: in definition of macro
'dev_printk_index_wrap'
110 | _p_func(dev, fmt, ##__VA_ARGS__);
\
| ^~~
include/linux/dev_printk.h:156:61: note: in expansion of macro 'dev_fmt'
156 | dev_printk_index_wrap(_dev_warn, KERN_WARNING, dev,
dev_fmt(fmt), ##__VA_ARGS__)
| ^~~
include/drm/drm_print.h:522:9: note: in expansion of macro 'dev_warn'
522 | dev_##level##type((drm) ? (drm)->dev : NULL, "[drm] " fmt,
##__VA_ARGS__)
| ^~~~
include/drm/drm_print.h:532:9: note: in expansion of macro '__drm_printk'
532 | __drm_printk((drm), warn,, fmt, ##__VA_ARGS__)
| ^~~~
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_color.c:1247:25:
note: in expansion of macro 'drm_warn'
1247 | d
Re: [PATCH v6 21/44] drm/vkms: Add tests for CTM handling
Hi Harry,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-exynos/exynos-drm-next drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip
linus/master v6.12-rc1 next-20241004]
[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/Harry-Wentland/drm-Add-helper-for-conversion-from-signed-magnitude/20241004-040629
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20241003200129.1732122-22-harry.wentland%40amd.com
patch subject: [PATCH v6 21/44] drm/vkms: Add tests for CTM handling
config: csky-randconfig-r112-20241005
(https://download.01.org/0day-ci/archive/20241005/202410051850.cgjobkkg-...@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.1.0
reproduce:
(https://download.01.org/0day-ci/archive/20241005/202410051850.cgjobkkg-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410051850.cgjobkkg-...@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/gpu/drm/vkms/tests/vkms_color_test.c:34:29: sparse: sparse: symbol
'test_linear_lut' was not declared. Should it be static?
>> drivers/gpu/drm/vkms/tests/vkms_color_test.c:193:32: sparse: sparse: symbol
>> 'test_matrix_3x4_50_desat' was not declared. Should it be static?
>> drivers/gpu/drm/vkms/tests/vkms_color_test.c:259:32: sparse: sparse: symbol
>> 'test_matrix_3x4_bt709_enc' was not declared. Should it be static?
vim +/test_matrix_3x4_50_desat +193 drivers/gpu/drm/vkms/tests/vkms_color_test.c
192
> 193 const struct drm_color_ctm_3x4 test_matrix_3x4_50_desat = { {
194 FIXPT_HALF, FIXPT_QUARTER, FIXPT_QUARTER, 0,
195 FIXPT_QUARTER, FIXPT_HALF, FIXPT_QUARTER, 0,
196 FIXPT_QUARTER, FIXPT_QUARTER, FIXPT_HALF, 0
197 } };
198
199 static void vkms_color_ctm_3x4_50_desat(struct kunit *test)
200 {
201 struct pixel_argb_s32 ref, out;
202
203 /* full white */
204 ref.a = 0x;
205 ref.r = 0x;
206 ref.g = 0x;
207 ref.b = 0x;
208
209 memcpy(&out, &ref, sizeof(out));
210 apply_3x4_matrix(&out, &test_matrix_3x4_50_desat);
211
212 KUNIT_EXPECT_MEMEQ(test, &ref, &out, sizeof(out));
213
214 /* full black */
215 ref.a = 0x;
216 ref.r = 0x0;
217 ref.g = 0x0;
218 ref.b = 0x0;
219
220 memcpy(&out, &ref, sizeof(out));
221 apply_3x4_matrix(&out, &test_matrix_3x4_50_desat);
222
223 KUNIT_EXPECT_MEMEQ(test, &ref, &out, sizeof(out));
224
225 /* 50% grey */
226 ref.a = 0x;
227 ref.r = 0x8000;
228 ref.g = 0x8000;
229 ref.b = 0x8000;
230
231 memcpy(&out, &ref, sizeof(out));
232 apply_3x4_matrix(&out, &test_matrix_3x4_50_desat);
233
234 KUNIT_EXPECT_MEMEQ(test, &ref, &out, sizeof(out));
235
236 /* full red to 50% desat */
237 ref.a = 0x;
238 ref.r = 0x8000;
239 ref.g = 0x4000;
240 ref.b = 0x4000;
241
242 out.a = 0x;
243 out.r = 0x;
244 out.g = 0x0;
245 out.b = 0x0;
246
247 apply_3x4_matrix(&out, &test_matrix_3x4_50_desat);
248
249 KUNIT_EXPECT_MEMEQ(test, &ref, &out, sizeof(out));
250 }
251
252 /*
253 * BT.709 encoding matrix
254 *
255 * Values printed from within IGT when converting
256 * igt_matrix_3x4_bt709_enc to the fixed-point format expected
257 * by DRM/KMS.
258 */
> 259 const struct drm_color_ctm_3x4 test_matrix_3x4_bt709_enc = { {
260 0x366cf400ull, 0xb7175900ull,
0x000127bb300ull, 0,
261 0x80001993b3a0ull, 0x80005609fe80ull,
0x6f9db200ull, 0,
262 0x9d70a400ull, 0x80008f011100ull,
0x8e6f9330ull, 0
263 } };
264
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 03/44] drm/vkms: Add kunit tests for VKMS LUT handling
Hi Harry,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-exynos/exynos-drm-next drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip
linus/master v6.12-rc1 next-20241004]
[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/Harry-Wentland/drm-Add-helper-for-conversion-from-signed-magnitude/20241004-040629
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20241003200129.1732122-4-harry.wentland%40amd.com
patch subject: [PATCH v6 03/44] drm/vkms: Add kunit tests for VKMS LUT handling
config: csky-randconfig-r112-20241005
(https://download.01.org/0day-ci/archive/20241005/202410051655.9wef2chw-...@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.1.0
reproduce:
(https://download.01.org/0day-ci/archive/20241005/202410051655.9wef2chw-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410051655.9wef2chw-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/vkms/tests/vkms_color_test.c:33:29: sparse: sparse: symbol
>> 'test_linear_lut' was not declared. Should it be static?
vim +/test_linear_lut +33 drivers/gpu/drm/vkms/tests/vkms_color_test.c
32
> 33 const struct vkms_color_lut test_linear_lut = {
34 .base = test_linear_array,
35 .lut_length = TEST_LUT_SIZE,
36 .channel_value2index_ratio = 0xf000fll
37 };
38
39
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 15/44] drm/vkms: Add kunit tests for linear and sRGB LUTs
Hi Harry, kernel test robot noticed the following build errors: [auto build test ERROR on drm/drm-next] [also build test ERROR on drm-exynos/exynos-drm-next drm-misc/drm-misc-next linus/master v6.12-rc1 next-20241004] [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/Harry-Wentland/drm-Add-helper-for-conversion-from-signed-magnitude/20241004-040629 base: git://anongit.freedesktop.org/drm/drm drm-next patch link: https://lore.kernel.org/r/20241003200129.1732122-16-harry.wentland%40amd.com patch subject: [PATCH v6 15/44] drm/vkms: Add kunit tests for linear and sRGB LUTs config: x86_64-randconfig-101-20241005 (https://download.01.org/0day-ci/archive/20241005/202410051303.vy1ejqpj-...@intel.com/config) compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241005/202410051303.vy1ejqpj-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410051303.vy1ejqpj-...@intel.com/ All errors (new ones prefixed by >>, old ones prefixed by <<): WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/gpu/drm/vkms/tests/vkms_color_test.o >> ERROR: modpost: "srgb_eotf" [drivers/gpu/drm/vkms/tests/vkms_color_test.ko] >> undefined! >> ERROR: modpost: "srgb_inv_eotf" >> [drivers/gpu/drm/vkms/tests/vkms_color_test.ko] undefined! >> ERROR: modpost: "linear_eotf" >> [drivers/gpu/drm/vkms/tests/vkms_color_test.ko] undefined! -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 10/11] drm/client: Make client support optional
Hi Thomas,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20241002]
[cannot apply to drm-xe/drm-xe-next drm/drm-next drm-exynos/exynos-drm-next
drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next
drm-tip/drm-tip linus/master v6.12-rc1 v6.11 v6.11-rc7 v6.12-rc1]
[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/Thomas-Zimmermann/drm-i915-Select-DRM_CLIENT_SELECTION/20241002-211520
base: next-20241002
patch link:
https://lore.kernel.org/r/20241002131306.288618-11-tzimmermann%40suse.de
patch subject: [PATCH v2 10/11] drm/client: Make client support optional
config: nios2-randconfig-r051-20241005
(https://download.01.org/0day-ci/archive/20241005/202410050927.hgk0kazl-...@intel.com/config)
compiler: nios2-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241005/202410050927.hgk0kazl-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410050927.hgk0kazl-...@intel.com/
All errors (new ones prefixed by >>):
nios2-linux-ld: drivers/gpu/drm/drm_debugfs.o: in function
`drm_debugfs_dev_register':
>> drivers/gpu/drm/drm_debugfs.c:313:(.text+0x1240): undefined reference to
>> `drm_client_debugfs_init'
>> drivers/gpu/drm/drm_debugfs.c:313:(.text+0x1240): relocation truncated to
>> fit: R_NIOS2_CALL26 against `drm_client_debugfs_init'
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for GET_FREE_REGION
Depends on [n]: SPARSEMEM [=n]
Selected by [y]:
- RESOURCE_KUNIT_TEST [=y] && RUNTIME_TESTING_MENU [=y] && KUNIT [=y]
vim +313 drivers/gpu/drm/drm_debugfs.c
0b30d57acafcaa Christian König 2023-08-29 306
0b30d57acafcaa Christian König 2023-08-29 307 void
drm_debugfs_dev_register(struct drm_device *dev)
0b30d57acafcaa Christian König 2023-08-29 308 {
0b30d57acafcaa Christian König 2023-08-29 309
drm_debugfs_add_files(dev, drm_debugfs_list, DRM_DEBUGFS_ENTRIES);
0b30d57acafcaa Christian König 2023-08-29 310
0b30d57acafcaa Christian König 2023-08-29 311 if
(drm_core_check_feature(dev, DRIVER_MODESET)) {
0b30d57acafcaa Christian König 2023-08-29 312
drm_framebuffer_debugfs_init(dev);
0b30d57acafcaa Christian König 2023-08-29 @313
drm_client_debugfs_init(dev);
0b30d57acafcaa Christian König 2023-08-29 314 }
d0b3c318e04cc6 Dmitry Baryshkov 2023-12-03 315 if
(drm_drv_uses_atomic_modeset(dev))
0b30d57acafcaa Christian König 2023-08-29 316
drm_atomic_debugfs_init(dev);
0b30d57acafcaa Christian König 2023-08-29 317 }
0b30d57acafcaa Christian König 2023-08-29 318
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/8] drm/client: Constify modes
Hi Ville,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on next-20241004]
[cannot apply to drm-intel/for-linux-next drm-intel/for-linux-next-fixes
drm/drm-next drm-exynos/exynos-drm-next linus/master v6.12-rc1]
[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/Ville-Syrjala/drm-client-Constify-modes/20241004-061843
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20241003113304.11700-2-ville.syrjala%40linux.intel.com
patch subject: [PATCH 1/8] drm/client: Constify modes
config: alpha-allyesconfig
(https://download.01.org/0day-ci/archive/20241005/202410050841.rws2vip5-...@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/20241005/202410050841.rws2vip5-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410050841.rws2vip5-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/gpu/drm/drm_client_modeset.c:1266:
drivers/gpu/drm/tests/drm_client_modeset_test.c: In function
'drm_test_pick_cmdline_res_1920_1080_60':
>> drivers/gpu/drm/tests/drm_client_modeset_test.c:108:14: warning: assignment
>> discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
108 | mode = drm_connector_pick_cmdline_mode(connector);
| ^
vim +/const +108 drivers/gpu/drm/tests/drm_client_modeset_test.c
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 84
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 85 static void
drm_test_pick_cmdline_res_1920_1080_60(struct kunit *test)
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 86 {
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 87struct
drm_client_modeset_test_priv *priv = test->priv;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 88struct drm_device *drm =
priv->drm;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 89struct drm_connector *connector
= &priv->connector;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 90struct drm_cmdline_mode
*cmdline_mode = &connector->cmdline_mode;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 91struct drm_display_mode
*expected_mode, *mode;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 92const char *cmdline =
"1920x1080@60";
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 93int ret;
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 94
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 95expected_mode =
drm_mode_find_dmt(priv->drm, 1920, 1080, 60, false);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 96KUNIT_ASSERT_NOT_NULL(test,
expected_mode);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 97
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 98KUNIT_ASSERT_TRUE(test,
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 99
drm_mode_parse_command_line_for_connector(cmdline,
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 100
connector,
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 101
cmdline_mode));
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 102
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 103
mutex_lock(&drm->mode_config.mutex);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 104ret =
drm_helper_probe_single_connector_modes(connector, 1920, 1080);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 105
mutex_unlock(&drm->mode_config.mutex);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 106KUNIT_ASSERT_GT(test, ret, 0);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 107
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 @108mode =
drm_connector_pick_cmdline_mode(connector);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 109KUNIT_ASSERT_NOT_NULL(test,
mode);
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 110
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 111KUNIT_EXPECT_TRUE(test,
drm_mode_equal(expected_mode, mode));
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 112 }
8fc0380f6ba7e9 Maxime Ripard 2022-11-14 113
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/8] drm/client: Constify modes
Hi Ville,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on next-20241004]
[cannot apply to drm-intel/for-linux-next drm-intel/for-linux-next-fixes
drm/drm-next drm-exynos/exynos-drm-next linus/master v6.12-rc1]
[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/Ville-Syrjala/drm-client-Constify-modes/20241004-061843
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20241003113304.11700-2-ville.syrjala%40linux.intel.com
patch subject: [PATCH 1/8] drm/client: Constify modes
config: i386-buildonly-randconfig-002-20241005
(https://download.01.org/0day-ci/archive/20241005/202410050750.i0ivowt8-...@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project
3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241005/202410050750.i0ivowt8-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410050750.i0ivowt8-...@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/drm_client_modeset.c:1266:
>> drivers/gpu/drm/tests/drm_client_modeset_test.c:108:7: error: assigning to
>> 'struct drm_display_mode *' from 'const struct drm_display_mode *' discards
>> qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
108 | mode = drm_connector_pick_cmdline_mode(connector);
| ^ ~~
1 error generated.
vim +108 drivers/gpu/drm/tests/drm_client_modeset_test.c
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 84
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 85 static void
drm_test_pick_cmdline_res_1920_1080_60(struct kunit *test)
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 86 {
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 87 struct
drm_client_modeset_test_priv *priv = test->priv;
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 88 struct drm_device *drm =
priv->drm;
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 89 struct drm_connector *connector
= &priv->connector;
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 90 struct drm_cmdline_mode
*cmdline_mode = &connector->cmdline_mode;
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 91 struct drm_display_mode
*expected_mode, *mode;
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 92 const char *cmdline =
"1920x1080@60";
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 93 int ret;
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 94
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 95 expected_mode =
drm_mode_find_dmt(priv->drm, 1920, 1080, 60, false);
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 96 KUNIT_ASSERT_NOT_NULL(test,
expected_mode);
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 97
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 98 KUNIT_ASSERT_TRUE(test,
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 99
drm_mode_parse_command_line_for_connector(cmdline,
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 100
connector,
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 101
cmdline_mode));
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 102
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 103
mutex_lock(&drm->mode_config.mutex);
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 104 ret =
drm_helper_probe_single_connector_modes(connector, 1920, 1080);
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 105
mutex_unlock(&drm->mode_config.mutex);
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 106 KUNIT_ASSERT_GT(test, ret, 0);
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 107
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 @108 mode =
drm_connector_pick_cmdline_mode(connector);
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 109 KUNIT_ASSERT_NOT_NULL(test,
mode);
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 110
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 111 KUNIT_EXPECT_TRUE(test,
drm_mode_equal(expected_mode, mode));
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 112 }
8fc0380f6ba7e94 Maxime Ripard 2022-11-14 113
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 03/11] drm/fbdev: Select fbdev I/O helpers from modules that require them
Hi Thomas,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20241002]
[also build test ERROR on v6.12-rc1]
[cannot apply to drm-xe/drm-xe-next drm/drm-next drm-exynos/exynos-drm-next
drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next
drm-tip/drm-tip linus/master v6.12-rc1 v6.11 v6.11-rc7]
[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/Thomas-Zimmermann/drm-i915-Select-DRM_CLIENT_SELECTION/20241002-211520
base: next-20241002
patch link:
https://lore.kernel.org/r/20241002131306.288618-4-tzimmermann%40suse.de
patch subject: [PATCH v2 03/11] drm/fbdev: Select fbdev I/O helpers from
modules that require them
config: arm-aspeed_g5_defconfig
(https://download.01.org/0day-ci/archive/20241005/202410050241.mox9qrjp-...@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.3.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241005/202410050241.mox9qrjp-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410050241.mox9qrjp-...@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/drm_fbdev_dma.c: In function
'drm_fbdev_dma_driver_fbdev_probe':
>> drivers/gpu/drm/drm_fbdev_dma.c:218:26: error: 'struct drm_fb_helper' has no
>> member named 'fbdefio'
218 | fb_helper->fbdefio.delay = HZ / 20;
| ^~
drivers/gpu/drm/drm_fbdev_dma.c:219:26: error: 'struct drm_fb_helper' has no
member named 'fbdefio'
219 | fb_helper->fbdefio.deferred_io =
drm_fb_helper_deferred_io;
| ^~
>> drivers/gpu/drm/drm_fbdev_dma.c:221:21: error: 'struct fb_info' has no
>> member named 'fbdefio'
221 | info->fbdefio = &fb_helper->fbdefio;
| ^~
drivers/gpu/drm/drm_fbdev_dma.c:221:43: error: 'struct drm_fb_helper' has no
member named 'fbdefio'
221 | info->fbdefio = &fb_helper->fbdefio;
| ^~
--
In file included from include/linux/bitfield.h:10,
from arch/arm/include/asm/ptrace.h:13,
from arch/arm/include/asm/processor.h:14,
from include/linux/prefetch.h:15,
from arch/arm/include/asm/atomic.h:12,
from include/linux/atomic.h:7,
from include/linux/console.h:17,
from drivers/gpu/drm/drm_fb_helper.c:32:
drivers/gpu/drm/drm_fb_helper.c: In function 'drm_fb_helper_deferred_io':
>> include/linux/container_of.h:20:54: error: invalid use of undefined type
>> 'struct fb_deferred_io_pageref'
20 | static_assert(__same_type(*(ptr), ((type *)0)->member) ||
\
| ^~
include/linux/build_bug.h:78:56: note: in definition of macro
'__static_assert'
78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
|^~~~
include/linux/container_of.h:20:9: note: in expansion of macro
'static_assert'
20 | static_assert(__same_type(*(ptr), ((type *)0)->member) ||
\
| ^
include/linux/container_of.h:20:23: note: in expansion of macro '__same_type'
20 | static_assert(__same_type(*(ptr), ((type *)0)->member) ||
\
| ^~~
include/linux/list.h:601:9: note: in expansion of macro 'container_of'
601 | container_of(ptr, type, member)
| ^~~~
include/linux/list.h:612:9: note: in expansion of macro 'list_entry'
612 | list_entry((ptr)->next, type, member)
| ^~
include/linux/list.h:778:20: note: in expansion of macro 'list_first_entry'
778 | for (pos = list_first_entry(head, typeof(*pos), member);
\
|^~~~
drivers/gpu/drm/drm_fb_helper.c:717:9: note: in expansion of macro
'list_for_each_entry'
717 | list_for_each_entry(pageref, pagereflist, list) {
| ^~~
include/linux/compiler_types.h:458:27: error: expression in static assertion
is not an integer
458
Re: [PATCH v2 02/10] drm/tilcdc: Allow build with COMPILE_TEST=y
Hi Ville,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20241003]
[cannot apply to shawnguo/for-next linus/master rmk-arm/drm-armada-devel
rmk-arm/drm-armada-fixes v6.12-rc1 v6.11 v6.11-rc7 v6.12-rc1]
[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/Ville-Syrjala/drm-tilcdc-Allow-build-without-__iowmb/20241003-192043
base: next-20241003
patch link:
https://lore.kernel.org/r/20241003111851.10453-3-ville.syrjala%40linux.intel.com
patch subject: [PATCH v2 02/10] drm/tilcdc: Allow build with COMPILE_TEST=y
config: alpha-allyesconfig
(https://download.01.org/0day-ci/archive/20241004/202410042345.cqdnf4wd-...@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/20241004/202410042345.cqdnf4wd-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410042345.cqdnf4wd-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/gpu/drm/tilcdc/tilcdc_crtc.c:24:
drivers/gpu/drm/tilcdc/tilcdc_regs.h: In function 'tilcdc_write64':
>> drivers/gpu/drm/tilcdc/tilcdc_regs.h:126:25: warning: passing argument 2 of
>> 'iowrite64' discards 'volatile' qualifier from pointer target type
>> [-Wdiscarded-qualifiers]
126 | iowrite64(data, addr);
| ^~~~
In file included from arch/alpha/include/asm/io.h:15,
from include/linux/scatterlist.h:9,
from include/linux/dma-mapping.h:11,
from drivers/gpu/drm/tilcdc/tilcdc_crtc.c:8:
include/asm-generic/iomap.h:56:28: note: expected 'void *' but argument is
of type 'volatile void *'
56 | extern void iowrite64(u64, void __iomem *);
|^~
vim +126 drivers/gpu/drm/tilcdc/tilcdc_regs.h
16ea975eac671f Rob Clark 2013-01-08 119
7eb9f069ff5dd3 Jyri Sarha 2016-08-26 120 static inline void
tilcdc_write64(struct drm_device *dev, u32 reg, u64 data)
7eb9f069ff5dd3 Jyri Sarha 2016-08-26 121 {
7eb9f069ff5dd3 Jyri Sarha 2016-08-26 122 struct
tilcdc_drm_private *priv = dev->dev_private;
7eb9f069ff5dd3 Jyri Sarha 2016-08-26 123 volatile void __iomem
*addr = priv->mmio + reg;
7eb9f069ff5dd3 Jyri Sarha 2016-08-26 124
4e5ca2d930aa87 Logan Gunthorpe 2017-12-05 125 #if defined(iowrite64) &&
!defined(iowrite64_is_nonatomic)
7eb9f069ff5dd3 Jyri Sarha 2016-08-26 @126 iowrite64(data, addr);
7eb9f069ff5dd3 Jyri Sarha 2016-08-26 127 #else
d5b0aa96231c76 Ville Syrjälä 2024-10-03 128 /* allow compilation
without __iowmb() for COMPILE_TEST */
d5b0aa96231c76 Ville Syrjälä 2024-10-03 129 #ifdef __iowmb
7eb9f069ff5dd3 Jyri Sarha 2016-08-26 130 __iowmb();
d5b0aa96231c76 Ville Syrjälä 2024-10-03 131 #endif
7eb9f069ff5dd3 Jyri Sarha 2016-08-26 132 /* This compiles to
strd (=64-bit write) on ARM7 */
7eb9f069ff5dd3 Jyri Sarha 2016-08-26 133 *(volatile u64 __force
*)addr = __cpu_to_le64(data);
7eb9f069ff5dd3 Jyri Sarha 2016-08-26 134 #endif
7eb9f069ff5dd3 Jyri Sarha 2016-08-26 135 }
7eb9f069ff5dd3 Jyri Sarha 2016-08-26 136
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH drm-dp 3/4] drm/hisilicon/hibmc: add dp kapi moduel in hibmc drivers
Hi shiyongbang, kernel test robot noticed the following build errors: [auto build test ERROR on drm-misc/drm-misc-next] [also build test ERROR on linus/master v6.12-rc1 next-20241003] [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/shiyongbang/drm-hisilicon-hibmc-add-dp-aux-in-hibmc-drivers/20240930-181437 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240930100610.782363-4-shiyongbang%40huawei.com patch subject: [PATCH drm-dp 3/4] drm/hisilicon/hibmc: add dp kapi moduel in hibmc drivers config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20241004/202410040328.vevxm9yb-...@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/20241004/202410040328.vevxm9yb-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410040328.vevxm9yb-...@intel.com/ All errors (new ones prefixed by >>): ld: drivers/gpu/drm/hisilicon/hibmc/dp/dp_kapi.o: in function `hibmc_dp_link_cfg': >> dp_kapi.c:(.text+0x233): undefined reference to `__udivdi3' >> ld: dp_kapi.c:(.text+0x35a): undefined reference to `__udivdi3' ld: dp_kapi.c:(.text+0x3cd): undefined reference to `__udivdi3' -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH drm-dp 2/4] drm/hisilicon/hibmc: add dp link moduel in hibmc drivers
Hi shiyongbang, kernel test robot noticed the following build errors: [auto build test ERROR on drm-misc/drm-misc-next] [also build test ERROR on linus/master v6.12-rc1 next-20241003] [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/shiyongbang/drm-hisilicon-hibmc-add-dp-aux-in-hibmc-drivers/20240930-181437 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240930100610.782363-3-shiyongbang%40huawei.com patch subject: [PATCH drm-dp 2/4] drm/hisilicon/hibmc: add dp link moduel in hibmc drivers config: i386-buildonly-randconfig-003-20241003 (https://download.01.org/0day-ci/archive/20241003/202410031735.8irzzr6t-...@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/20241003/202410031735.8irzzr6t-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410031735.8irzzr6t-...@intel.com/ All errors (new ones prefixed by >>): In file included from drivers/gpu/drm/hisilicon/hibmc/dp/dp_link.c:10: drivers/gpu/drm/hisilicon/hibmc/dp/dp_link.c: In function 'dp_link_training_cr_pre': >> drivers/gpu/drm/hisilicon/hibmc/dp/dp_aux.h:45:41: error: implicit >> declaration of function 'FIELD_PREP' [-Werror=implicit-function-declaration] 45 | #define DPCD_VOLTAGE_SWING_LEVEL_2 FIELD_PREP(GENMASK(1, 0), 2) | ^~ drivers/gpu/drm/hisilicon/hibmc/dp/dp_link.c:105:32: note: in expansion of macro 'DPCD_VOLTAGE_SWING_LEVEL_2' 105 | train_set[i] = DPCD_VOLTAGE_SWING_LEVEL_2 | DPCD_PRE_EMPHASIS_LEVEL_0; |^~ cc1: some warnings being treated as errors vim +/FIELD_PREP +45 drivers/gpu/drm/hisilicon/hibmc/dp/dp_aux.h ff6e8ef6021188 baihan li 2024-09-30 37 ff6e8ef6021188 baihan li 2024-09-30 38 #define DPCD_TRAINING_PATTERN_DISABLE 0x0 ff6e8ef6021188 baihan li 2024-09-30 39 #define DPCD_TRAINING_PATTERN_1 0x1 ff6e8ef6021188 baihan li 2024-09-30 40 #define DPCD_TRAINING_PATTERN_2 0x2 ff6e8ef6021188 baihan li 2024-09-30 41 #define DPCD_TRAINING_PATTERN_3 0x3 ff6e8ef6021188 baihan li 2024-09-30 42 #define DPCD_TRAINING_PATTERN_4 0x7 ff6e8ef6021188 baihan li 2024-09-30 43 #define DPCD_VOLTAGE_SWING_LEVEL_0 FIELD_PREP(GENMASK(1, 0), 0) ff6e8ef6021188 baihan li 2024-09-30 44 #define DPCD_VOLTAGE_SWING_LEVEL_1 FIELD_PREP(GENMASK(1, 0), 1) ff6e8ef6021188 baihan li 2024-09-30 @45 #define DPCD_VOLTAGE_SWING_LEVEL_2 FIELD_PREP(GENMASK(1, 0), 2) ff6e8ef6021188 baihan li 2024-09-30 46 #define DPCD_VOLTAGE_SWING_LEVEL_3 FIELD_PREP(GENMASK(1, 0), 3) ff6e8ef6021188 baihan li 2024-09-30 47 #define DPCD_PRE_EMPHASIS_LEVEL_0 FIELD_PREP(GENMASK(4, 3), 0) ff6e8ef6021188 baihan li 2024-09-30 48 #define DPCD_PRE_EMPHASIS_LEVEL_1 FIELD_PREP(GENMASK(4, 3), 1) ff6e8ef6021188 baihan li 2024-09-30 49 #define DPCD_PRE_EMPHASIS_LEVEL_2 FIELD_PREP(GENMASK(4, 3), 2) ff6e8ef6021188 baihan li 2024-09-30 50 #define DPCD_PRE_EMPHASIS_LEVEL_3 FIELD_PREP(GENMASK(4, 3), 3) ff6e8ef6021188 baihan li 2024-09-30 51 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v5 2/2] drm/mediatek: Add blend_modes to mtk_plane_init() for different SoCs
Hi Jason-JH.Lin,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm/drm-next]
[also build test ERROR on linus/master v6.12-rc1 next-20241001]
[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/Jason-JH-Lin/drm-mediatek-ovl-Add-fmt_convert-function-pointer-to-driver-data/20240925-182056
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20240925101927.17042-3-jason-jh.lin%40mediatek.com
patch subject: [PATCH v5 2/2] drm/mediatek: Add blend_modes to mtk_plane_init()
for different SoCs
config: arm64-randconfig-002-20241002
(https://download.01.org/0day-ci/archive/20241002/202410021332.viwq2mtz-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
fef3566a25ff0e34fb87339ba5e13eca17cec00f)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241002/202410021332.viwq2mtz-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410021332.viwq2mtz-...@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/mediatek/mtk_disp_gamma.c:14:
In file included from drivers/gpu/drm/mediatek/mtk_crtc.h:9:
In file included from include/drm/drm_crtc.h:32:
In file included from include/drm/drm_modes.h:33:
In file included from include/drm/drm_connector.h:32:
In file included from include/drm/drm_util.h:36:
In file included from include/linux/kgdb.h:19:
In file included from include/linux/kprobes.h:28:
In file included from include/linux/ftrace.h:13:
In file included from include/linux/kallsyms.h:13:
In file included from include/linux/mm.h:2232:
include/linux/vmstat.h:517:36: error: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Werror,-Wenum-enum-conversion]
517 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
In file included from drivers/gpu/drm/mediatek/mtk_disp_gamma.c:14:
In file included from drivers/gpu/drm/mediatek/mtk_crtc.h:10:
>> drivers/gpu/drm/mediatek/mtk_ddp_comp.h:83:2: error: 'const' type qualifier
>> on return type has no effect [-Werror,-Wignored-qualifiers]
83 | const u32 (*get_blend_modes)(struct device *dev);
| ^
drivers/gpu/drm/mediatek/mtk_ddp_comp.h:271:1: error: 'const' type qualifier
on return type has no effect [-Werror,-Wignored-qualifiers]
271 | const u32 mtk_ddp_comp_get_blend_modes(struct mtk_ddp_comp *comp)
| ^
In file included from drivers/gpu/drm/mediatek/mtk_disp_gamma.c:16:
>> drivers/gpu/drm/mediatek/mtk_disp_drv.h:106:1: error: 'const' type qualifier
>> on return type has no effect [-Werror,-Wignored-qualifiers]
106 | const u32 mtk_ovl_get_blend_modes(struct device *dev);
| ^
drivers/gpu/drm/mediatek/mtk_disp_drv.h:135:1: error: 'const' type qualifier
on return type has no effect [-Werror,-Wignored-qualifiers]
135 | const u32 mtk_ovl_adaptor_get_blend_modes(struct device *dev);
| ^
drivers/gpu/drm/mediatek/mtk_disp_drv.h:170:1: error: 'const' type qualifier
on return type has no effect [-Werror,-Wignored-qualifiers]
170 | const u32 mtk_mdp_rdma_get_blend_modes(struct device *dev);
| ^
6 errors generated.
--
In file included from drivers/gpu/drm/mediatek/mtk_ethdr.c:18:
In file included from drivers/gpu/drm/mediatek/mtk_crtc.h:9:
In file included from include/drm/drm_crtc.h:32:
In file included from include/drm/drm_modes.h:33:
In file included from include/drm/drm_connector.h:32:
In file included from include/drm/drm_util.h:36:
In file included from include/linux/kgdb.h:19:
In file included from include/linux/kprobes.h:28:
In file included from include/linux/ftrace.h:13:
In file included from include/linux/kallsyms.h:13:
In file included from include/linux/mm.h:2232:
include/linux/vmstat.h:517:36: error: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Werror,-Wenum-enum-conversion]
517 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
In file included from drivers/gpu/drm/mediatek/mtk_ethdr.c:18:
In file included from drivers/gpu/drm/mediatek/mtk_crtc.h:10:
>> drivers/gpu/drm/mediatek/mtk_ddp_comp.
Re: [PATCH v3] drm/meson: switch to a managed drm device
Hi Anastasia,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.12-rc1 next-20240930]
[cannot apply to drm-misc/drm-misc-next]
[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/Anastasia-Belova/drm-meson-switch-to-a-managed-drm-device/20240930-162755
base: linus/master
patch link:
https://lore.kernel.org/r/20240930082640.129543-1-abelova%40astralinux.ru
patch subject: [PATCH v3] drm/meson: switch to a managed drm device
config: arm64-defconfig
(https://download.01.org/0day-ci/archive/20241001/202410011034.ntokwoxq-...@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241001/202410011034.ntokwoxq-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202410011034.ntokwoxq-...@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/meson/meson_viu.c:14:
>> drivers/gpu/drm/meson/meson_drv.h:56:27: error: field 'drm' has incomplete
>> type
56 | struct drm_device drm;
| ^~~
--
drivers/gpu/drm/meson/meson_encoder_hdmi.c: In function
'meson_encoder_hdmi_probe':
>> drivers/gpu/drm/meson/meson_encoder_hdmi.c:405:43: error: incompatible type
>> for argument 1 of 'drm_simple_encoder_init'
405 | ret = drm_simple_encoder_init(priv->drm,
&meson_encoder_hdmi->encoder,
| ^
| |
| struct drm_device
In file included from drivers/gpu/drm/meson/meson_encoder_hdmi.c:27:
include/drm/drm_simple_kms_helper.h:261:48: note: expected 'struct
drm_device *' but argument is of type 'struct drm_device'
261 | int drm_simple_encoder_init(struct drm_device *dev,
| ~~~^~~
>> drivers/gpu/drm/meson/meson_encoder_hdmi.c:423:71: error: incompatible type
>> for argument 1 of 'drm_bridge_connector_init'
423 | meson_encoder_hdmi->connector =
drm_bridge_connector_init(priv->drm,
|
^
|
|
|
struct drm_device
In file included from drivers/gpu/drm/meson/meson_encoder_hdmi.c:23:
include/drm/drm_bridge_connector.h:13:68: note: expected 'struct drm_device
*' but argument is of type 'struct drm_device'
13 | struct drm_connector *drm_bridge_connector_init(struct drm_device
*drm,
|
~~~^~~
--
drivers/gpu/drm/meson/meson_encoder_dsi.c: In function
'meson_encoder_dsi_probe':
>> drivers/gpu/drm/meson/meson_encoder_dsi.c:135:43: error: incompatible type
>> for argument 1 of 'drm_simple_encoder_init'
135 | ret = drm_simple_encoder_init(priv->drm,
&meson_encoder_dsi->encoder,
| ^
| |
| struct drm_device
In file included from drivers/gpu/drm/meson/meson_encoder_dsi.c:13:
include/drm/drm_simple_kms_helper.h:261:48: note: expected 'struct
drm_device *' but argument is of type 'struct drm_device'
261 | int drm_simple_encoder_init(struct drm_device *dev,
| ~~~^~~
vim +/drm +56 drivers/gpu/drm/meson/meson_drv.h
42
43 struct meson_drm {
44 struct device *dev;
45 enum vpu_compatible compat;
46 void __iomem *io_base;
47 struct regmap *hhi;
48 int vsync_irq;
49
50 struct meson_canvas *canvas;
51 u8 canvas_id_osd1;
52 u8 canvas_id_vd1_0;
53 u8 canvas_id_vd1_1;
54 u8 canvas_id_vd1_2;
55
> 56 struct drm_device drm;
57 struct drm_crtc *crtc;
58 struct drm_plane *primary_plane;
59 struct drm_plane *overlay_plane;
60 void *encoders[MESON_ENC_LAST];
61
62 const struct meson_drm_soc_lim
Re: [PATCH v3] drm/meson: switch to a managed drm device
Hi Anastasia, kernel test robot noticed the following build errors: [auto build test ERROR on linus/master] [also build test ERROR on v6.12-rc1 next-20240930] [cannot apply to drm-misc/drm-misc-next] [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/Anastasia-Belova/drm-meson-switch-to-a-managed-drm-device/20240930-162755 base: linus/master patch link: https://lore.kernel.org/r/20240930082640.129543-1-abelova%40astralinux.ru patch subject: [PATCH v3] drm/meson: switch to a managed drm device config: arm-randconfig-001-20240930 (https://download.01.org/0day-ci/archive/20241001/202410010450.fokiu1ki-...@intel.com/config) compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241001/202410010450.fokiu1ki-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202410010450.fokiu1ki-...@intel.com/ All errors (new ones prefixed by >>): In file included from drivers/gpu/drm/meson/meson_osd_afbcd.c:12: >> drivers/gpu/drm/meson/meson_drv.h:56:20: error: field has incomplete type >> 'struct drm_device' struct drm_device drm; ^ include/drm/drm_print.h:37:8: note: forward declaration of 'struct drm_device' struct drm_device; ^ 1 error generated. -- In file included from drivers/gpu/drm/meson/meson_venc.c:14: >> drivers/gpu/drm/meson/meson_drv.h:56:20: error: field has incomplete type >> 'struct drm_device' struct drm_device drm; ^ include/drm/drm_lease.h:12:8: note: forward declaration of 'struct drm_device' struct drm_device; ^ 1 error generated. -- In file included from drivers/gpu/drm/meson/meson_vclk.c:12: >> drivers/gpu/drm/meson/meson_drv.h:56:20: error: field has incomplete type >> 'struct drm_device' struct drm_device drm; ^ include/drm/drm_print.h:37:8: note: forward declaration of 'struct drm_device' struct drm_device; ^ In file included from drivers/gpu/drm/meson/meson_vclk.c:13: In file included from drivers/gpu/drm/meson/meson_vclk.h:12: In file included from include/drm/drm_modes.h:33: In file included from include/drm/drm_connector.h:32: In file included from include/drm/drm_util.h:36: In file included from include/linux/kgdb.h:19: In file included from include/linux/kprobes.h:28: In file included from include/linux/ftrace.h:13: In file included from include/linux/kallsyms.h:13: In file included from include/linux/mm.h:1120: In file included from include/linux/huge_mm.h:8: In file included from include/linux/fs.h:33: In file included from include/linux/percpu-rwsem.h:7: In file included from include/linux/rcuwait.h:6: In file included from include/linux/sched/signal.h:6: include/linux/signal.h:98:11: warning: array index 3 is past the end of the array (which contains 2 elements) [-Warray-bounds] return (set->sig[3] | set->sig[2] | ^~ arch/arm/include/asm/signal.h:17:2: note: array 'sig' declared here unsigned long sig[_NSIG_WORDS]; ^ In file included from drivers/gpu/drm/meson/meson_vclk.c:13: In file included from drivers/gpu/drm/meson/meson_vclk.h:12: In file included from include/drm/drm_modes.h:33: In file included from include/drm/drm_connector.h:32: In file included from include/drm/drm_util.h:36: In file included from include/linux/kgdb.h:19: In file included from include/linux/kprobes.h:28: In file included from include/linux/ftrace.h:13: In file included from include/linux/kallsyms.h:13: In file included from include/linux/mm.h:1120: In file included from include/linux/huge_mm.h:8: In file included from include/linux/fs.h:33: In file included from include/linux/percpu-rwsem.h:7: In file included from include/linux/rcuwait.h:6: In file included from include/linux/sched/signal.h:6: include/linux/signal.h:98:25: warning: array index 2 is past the end of the array (which contains 2 elements) [-Warray-bounds] return (set->sig[3] | set->sig[2] | ^~ arch/arm/include/asm/signal.h:17:2: note: array 'sig' declared here unsigned long sig[_NSIG_WORDS]; ^ In file included
Re: [PATCH v2 1/1] platform/x86/tuxedo: Add virtual LampArray for TUXEDO
Hi Werner, kernel test robot noticed the following build errors: [auto build test ERROR on drm-misc/drm-misc-next] [also build test ERROR on drm-tip/drm-tip linus/master v6.11 next-20240927] [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/Werner-Sembach/platform-x86-tuxedo-Add-virtual-LampArray-for-TUXEDO/20240927-214157 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240927124152.139099-2-wse%40tuxedocomputers.com patch subject: [PATCH v2 1/1] platform/x86/tuxedo: Add virtual LampArray for TUXEDO config: x86_64-buildonly-randconfig-003-20240929 (https://download.01.org/0day-ci/archive/20240929/202409291428.gvfls4l1-...@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/20240929/202409291428.gvfls4l1-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202409291428.gvfls4l1-...@intel.com/ All errors (new ones prefixed by >>): ld: drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_init.o: in function `remove': >> tuxedo_nb04_wmi_ab_init.c:(.text+0x34): undefined reference to >> `hid_destroy_device' ld: drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_virtual_lamp_array.o: in function `ll_parse': >> tuxedo_nb04_wmi_ab_virtual_lamp_array.c:(.text+0xdbd): undefined reference >> to `hid_parse_report' ld: drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_virtual_lamp_array.o: in function `tuxedo_nb04_virtual_lamp_array_add_device': >> tuxedo_nb04_wmi_ab_virtual_lamp_array.c:(.text+0xeff): undefined reference >> to `hid_allocate_device' >> ld: tuxedo_nb04_wmi_ab_virtual_lamp_array.c:(.text+0xfbb): undefined >> reference to `hid_add_device' >> ld: tuxedo_nb04_wmi_ab_virtual_lamp_array.c:(.text+0x1004): undefined >> reference to `hid_destroy_device' -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 1/1] platform/x86/tuxedo: Add virtual LampArray for TUXEDO
Hi Werner, kernel test robot noticed the following build errors: [auto build test ERROR on drm-misc/drm-misc-next] [also build test ERROR on drm-tip/drm-tip linus/master v6.11 next-20240927] [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/Werner-Sembach/platform-x86-tuxedo-Add-virtual-LampArray-for-TUXEDO/20240927-214157 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240927124152.139099-2-wse%40tuxedocomputers.com patch subject: [PATCH v2 1/1] platform/x86/tuxedo: Add virtual LampArray for TUXEDO config: x86_64-randconfig-161-20240928 (https://download.01.org/0day-ci/archive/20240929/202409290814.ogfhxrw7-...@intel.com/config) compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240929/202409290814.ogfhxrw7-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202409290814.ogfhxrw7-...@intel.com/ All errors (new ones prefixed by >>): >> ld.lld: error: undefined symbol: wmidev_evaluate_method >>> referenced by tuxedo_nb04_wmi_util.c:26 (drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_util.c:26) >>> vmlinux.o:(__wmi_method_buffer_out) -- >> ld.lld: error: undefined symbol: __wmi_driver_register >>> referenced by tuxedo_nb04_wmi_ab_init.c:86 (drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_init.c:86) >>> vmlinux.o:(tuxedo_nb04_wmi_ab_driver_init) -- >> ld.lld: error: undefined symbol: wmi_driver_unregister >>> referenced by tuxedo_nb04_wmi_ab_init.c:86 (drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_init.c:86) >>> vmlinux.o:(tuxedo_nb04_wmi_ab_driver_exit) -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v8 3/5] drm/panthor: add DRM fdinfo support
Hi Adrián,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.11 next-20240927]
[cannot apply to drm-misc/drm-misc-next]
[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/Adri-n-Larumbe/drm-panthor-introduce-job-cycle-and-timestamp-accounting/20240924-071018
base: linus/master
patch link:
https://lore.kernel.org/r/20240923230912.2207320-4-adrian.larumbe%40collabora.com
patch subject: [PATCH v8 3/5] drm/panthor: add DRM fdinfo support
config: arm-randconfig-002-20240929
(https://download.01.org/0day-ci/archive/20240929/202409291048.zlqdeqpo-...@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240929/202409291048.zlqdeqpo-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202409291048.zlqdeqpo-...@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/math64.h:6,
from include/linux/time.h:6,
from include/linux/stat.h:19,
from include/linux/module.h:13,
from drivers/gpu/drm/panthor/panthor_drv.c:7:
drivers/gpu/drm/panthor/panthor_drv.c: In function 'panthor_gpu_show_fdinfo':
>> drivers/gpu/drm/panthor/panthor_drv.c:1389:45: error: implicit declaration
>> of function 'arch_timer_get_cntfrq' [-Wimplicit-function-declaration]
1389 |
arch_timer_get_cntfrq()));
| ^
include/linux/math.h:40:39: note: in definition of macro 'DIV_ROUND_DOWN_ULL'
40 | ({ unsigned long long _tmp = (ll); do_div(_tmp, d); _tmp; })
| ^~
drivers/gpu/drm/panthor/panthor_drv.c:1388:28: note: in expansion of macro
'DIV_ROUND_UP_ULL'
1388 |DIV_ROUND_UP_ULL((pfile->stats.time *
NSEC_PER_SEC),
|^~~~
vim +/arch_timer_get_cntfrq +1389 drivers/gpu/drm/panthor/panthor_drv.c
1377
1378 static void panthor_gpu_show_fdinfo(struct panthor_device *ptdev,
1379 struct panthor_file *pfile,
1380 struct drm_printer *p)
1381 {
1382 if (ptdev->profile_mask & PANTHOR_DEVICE_PROFILING_ALL)
1383 panthor_fdinfo_gather_group_samples(pfile);
1384
1385 if (ptdev->profile_mask & PANTHOR_DEVICE_PROFILING_TIMESTAMP) {
1386 #ifdef CONFIG_ARM_ARCH_TIMER
1387 drm_printf(p, "drm-engine-panthor:\t%llu ns\n",
1388 DIV_ROUND_UP_ULL((pfile->stats.time *
NSEC_PER_SEC),
> 1389 arch_timer_get_cntfrq()));
1390 #endif
1391 }
1392 if (ptdev->profile_mask & PANTHOR_DEVICE_PROFILING_CYCLES)
1393 drm_printf(p, "drm-cycles-panthor:\t%llu\n",
pfile->stats.cycles);
1394
1395 drm_printf(p, "drm-maxfreq-panthor:\t%lu Hz\n",
ptdev->fast_rate);
1396 drm_printf(p, "drm-curfreq-panthor:\t%lu Hz\n",
ptdev->current_frequency);
1397 }
1398
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 2/2] drm/mediatek: Add blend_modes to mtk_plane_init() for different SoCs
Hi Jason-JH.Lin,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on linus/master next-20240927]
[cannot apply to v6.11]
[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/Jason-JH-Lin/drm-mediatek-ovl-Add-blend_modes-to-driver-data/20240926-163734
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20240926083526.24629-3-jason-jh.lin%40mediatek.com
patch subject: [PATCH v6 2/2] drm/mediatek: Add blend_modes to mtk_plane_init()
for different SoCs
config: arm64-randconfig-001-20240929
(https://download.01.org/0day-ci/archive/20240929/202409290651.ylksl39c-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
7773243d9916f98ba0ffce0c3a960e4aa9f03e81)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240929/202409290651.ylksl39c-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202409290651.ylksl39c-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/gpu/drm/mediatek/mtk_ethdr.c:18:
In file included from drivers/gpu/drm/mediatek/mtk_crtc.h:9:
In file included from include/drm/drm_crtc.h:32:
In file included from include/drm/drm_modes.h:33:
In file included from include/drm/drm_connector.h:32:
In file included from include/drm/drm_util.h:36:
In file included from include/linux/kgdb.h:19:
In file included from include/linux/kprobes.h:28:
In file included from include/linux/ftrace.h:13:
In file included from include/linux/kallsyms.h:13:
In file included from include/linux/mm.h:2232:
include/linux/vmstat.h:517:36: warning: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Wenum-enum-conversion]
517 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
In file included from drivers/gpu/drm/mediatek/mtk_ethdr.c:18:
In file included from drivers/gpu/drm/mediatek/mtk_crtc.h:10:
drivers/gpu/drm/mediatek/mtk_ddp_comp.h:83:2: warning: 'const' type
qualifier on return type has no effect [-Wignored-qualifiers]
83 | const u32 (*get_blend_modes)(struct device *dev);
| ^
drivers/gpu/drm/mediatek/mtk_ddp_comp.h:271:1: warning: 'const' type
qualifier on return type has no effect [-Wignored-qualifiers]
271 | const u32 mtk_ddp_comp_get_blend_modes(struct mtk_ddp_comp *comp)
| ^
In file included from drivers/gpu/drm/mediatek/mtk_ethdr.c:21:
>> drivers/gpu/drm/mediatek/mtk_ethdr.h:16:1: warning: 'const' type qualifier
>> on return type has no effect [-Wignored-qualifiers]
16 | const u32 mtk_ethdr_get_blend_modes(struct device *dev);
| ^
>> drivers/gpu/drm/mediatek/mtk_ethdr.c:148:1: warning: 'const' type qualifier
>> on return type has no effect [-Wignored-qualifiers]
148 | const u32 mtk_ethdr_get_blend_modes(struct device *dev)
| ^
5 warnings generated.
--
In file included from drivers/gpu/drm/mediatek/mtk_disp_ovl_adaptor.c:7:
In file included from include/drm/drm_of.h:8:
In file included from include/drm/drm_bridge.h:30:
In file included from include/drm/drm_atomic.h:31:
In file included from include/drm/drm_crtc.h:32:
In file included from include/drm/drm_modes.h:33:
In file included from include/drm/drm_connector.h:32:
In file included from include/drm/drm_util.h:36:
In file included from include/linux/kgdb.h:19:
In file included from include/linux/kprobes.h:28:
In file included from include/linux/ftrace.h:13:
In file included from include/linux/kallsyms.h:13:
In file included from include/linux/mm.h:2232:
include/linux/vmstat.h:517:36: warning: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Wenum-enum-conversion]
517 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
In file included from drivers/gpu/drm/mediatek/mtk_disp_ovl_adaptor.c:20:
drivers/gpu/drm/mediatek/mtk_ddp_comp.h:83:2: warning: 'const' type
qualifier on return type has no effect [-Wignored-qualifiers]
83 | const u32 (*get_blend_modes)(struct device *dev);
| ^
drivers/gpu/drm/mediatek/mtk_ddp_comp.h:271:1: warn
Re: [PATCH v6 2/2] drm/mediatek: Add blend_modes to mtk_plane_init() for different SoCs
Hi Jason-JH.Lin, kernel test robot noticed the following build errors: [auto build test ERROR on drm/drm-next] [also build test ERROR on linus/master next-20240927] [cannot apply to v6.11] [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/Jason-JH-Lin/drm-mediatek-ovl-Add-blend_modes-to-driver-data/20240926-163734 base: git://anongit.freedesktop.org/drm/drm drm-next patch link: https://lore.kernel.org/r/20240926083526.24629-3-jason-jh.lin%40mediatek.com patch subject: [PATCH v6 2/2] drm/mediatek: Add blend_modes to mtk_plane_init() for different SoCs config: arm-randconfig-002-20240929 (https://download.01.org/0day-ci/archive/20240929/202409290616.inw9ugyc-...@intel.com/config) compiler: arm-linux-gnueabi-gcc (GCC) 14.1.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240929/202409290616.inw9ugyc-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202409290616.inw9ugyc-...@intel.com/ All errors (new ones prefixed by >>): In file included from drivers/gpu/drm/mediatek/mtk_crtc.h:10, from drivers/gpu/drm/mediatek/mtk_ethdr.c:18: drivers/gpu/drm/mediatek/mtk_ddp_comp.h:83:9: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] 83 | const u32 (*get_blend_modes)(struct device *dev); | ^ drivers/gpu/drm/mediatek/mtk_ddp_comp.h:271:1: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] 271 | const u32 mtk_ddp_comp_get_blend_modes(struct mtk_ddp_comp *comp) | ^ In file included from drivers/gpu/drm/mediatek/mtk_ethdr.c:21: >> drivers/gpu/drm/mediatek/mtk_ethdr.h:16:1: error: type qualifiers ignored on >> function return type [-Werror=ignored-qualifiers] 16 | const u32 mtk_ethdr_get_blend_modes(struct device *dev); | ^ >> drivers/gpu/drm/mediatek/mtk_ethdr.c:148:1: error: type qualifiers ignored >> on function return type [-Werror=ignored-qualifiers] 148 | const u32 mtk_ethdr_get_blend_modes(struct device *dev) | ^ cc1: all warnings being treated as errors -- In file included from drivers/gpu/drm/mediatek/mtk_disp_ovl_adaptor.c:20: drivers/gpu/drm/mediatek/mtk_ddp_comp.h:83:9: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] 83 | const u32 (*get_blend_modes)(struct device *dev); | ^ drivers/gpu/drm/mediatek/mtk_ddp_comp.h:271:1: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] 271 | const u32 mtk_ddp_comp_get_blend_modes(struct mtk_ddp_comp *comp) | ^ In file included from drivers/gpu/drm/mediatek/mtk_disp_ovl_adaptor.c:21: drivers/gpu/drm/mediatek/mtk_disp_drv.h:106:1: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] 106 | const u32 mtk_ovl_get_blend_modes(struct device *dev); | ^ drivers/gpu/drm/mediatek/mtk_disp_drv.h:135:1: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] 135 | const u32 mtk_ovl_adaptor_get_blend_modes(struct device *dev); | ^ In file included from drivers/gpu/drm/mediatek/mtk_disp_ovl_adaptor.c:23: >> drivers/gpu/drm/mediatek/mtk_ethdr.h:16:1: error: type qualifiers ignored on >> function return type [-Werror=ignored-qualifiers] 16 | const u32 mtk_ethdr_get_blend_modes(struct device *dev); | ^ drivers/gpu/drm/mediatek/mtk_disp_ovl_adaptor.c:403:1: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] 403 | const u32 mtk_ovl_adaptor_get_blend_modes(struct device *dev) | ^ cc1: all warnings being treated as errors vim +16 drivers/gpu/drm/mediatek/mtk_ethdr.h 8 9 void mtk_ethdr_start(struct device *dev); 10 void mtk_ethdr_stop(struct device *dev); 11 int mtk_ethdr_clk_enable(struct device *dev); 12 void mtk_ethdr_clk_disable(struct device *dev); 13 void mtk_ethdr_config(struct device *dev, unsigned int w, 14unsigned int h, unsigned int vrefresh, 15unsigned int bpc, struct cmdq_pkt *cmdq_pkt); > 16 const u32 mtk_ethdr_get_blend_modes(struct device *dev); -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v5 2/2] drm/mediatek: Add blend_modes to mtk_plane_init() for different SoCs
Hi Jason-JH.Lin, kernel test robot noticed the following build errors: [auto build test ERROR on drm/drm-next] [also build test ERROR on linus/master next-20240927] [cannot apply to v6.11] [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/Jason-JH-Lin/drm-mediatek-ovl-Add-fmt_convert-function-pointer-to-driver-data/20240925-182056 base: git://anongit.freedesktop.org/drm/drm drm-next patch link: https://lore.kernel.org/r/20240925101927.17042-3-jason-jh.lin%40mediatek.com patch subject: [PATCH v5 2/2] drm/mediatek: Add blend_modes to mtk_plane_init() for different SoCs config: arm-randconfig-002-20240929 (https://download.01.org/0day-ci/archive/20240929/202409290726.oaatx2or-...@intel.com/config) compiler: arm-linux-gnueabi-gcc (GCC) 14.1.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240929/202409290726.oaatx2or-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202409290726.oaatx2or-...@intel.com/ All errors (new ones prefixed by >>): In file included from drivers/gpu/drm/mediatek/mtk_crtc.h:10, from drivers/gpu/drm/mediatek/mtk_crtc.c:22: >> drivers/gpu/drm/mediatek/mtk_ddp_comp.h:83:9: error: type qualifiers ignored >> on function return type [-Werror=ignored-qualifiers] 83 | const u32 (*get_blend_modes)(struct device *dev); | ^ drivers/gpu/drm/mediatek/mtk_ddp_comp.h:271:1: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] 271 | const u32 mtk_ddp_comp_get_blend_modes(struct mtk_ddp_comp *comp) | ^ cc1: all warnings being treated as errors -- In file included from drivers/gpu/drm/mediatek/mtk_crtc.h:10, from drivers/gpu/drm/mediatek/mtk_disp_color.c:13: >> drivers/gpu/drm/mediatek/mtk_ddp_comp.h:83:9: error: type qualifiers ignored >> on function return type [-Werror=ignored-qualifiers] 83 | const u32 (*get_blend_modes)(struct device *dev); | ^ drivers/gpu/drm/mediatek/mtk_ddp_comp.h:271:1: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] 271 | const u32 mtk_ddp_comp_get_blend_modes(struct mtk_ddp_comp *comp) | ^ In file included from drivers/gpu/drm/mediatek/mtk_disp_color.c:15: >> drivers/gpu/drm/mediatek/mtk_disp_drv.h:106:1: error: type qualifiers >> ignored on function return type [-Werror=ignored-qualifiers] 106 | const u32 mtk_ovl_get_blend_modes(struct device *dev); | ^ drivers/gpu/drm/mediatek/mtk_disp_drv.h:135:1: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] 135 | const u32 mtk_ovl_adaptor_get_blend_modes(struct device *dev); | ^ drivers/gpu/drm/mediatek/mtk_disp_drv.h:170:1: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] 170 | const u32 mtk_mdp_rdma_get_blend_modes(struct device *dev); | ^ cc1: all warnings being treated as errors -- In file included from drivers/gpu/drm/mediatek/mtk_mdp_rdma.c:15: >> drivers/gpu/drm/mediatek/mtk_disp_drv.h:106:1: error: type qualifiers >> ignored on function return type [-Werror=ignored-qualifiers] 106 | const u32 mtk_ovl_get_blend_modes(struct device *dev); | ^ drivers/gpu/drm/mediatek/mtk_disp_drv.h:135:1: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] 135 | const u32 mtk_ovl_adaptor_get_blend_modes(struct device *dev); | ^ drivers/gpu/drm/mediatek/mtk_disp_drv.h:170:1: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] 170 | const u32 mtk_mdp_rdma_get_blend_modes(struct device *dev); | ^ In file included from drivers/gpu/drm/mediatek/mtk_drm_drv.h:10, from drivers/gpu/drm/mediatek/mtk_mdp_rdma.c:16: >> drivers/gpu/drm/mediatek/mtk_ddp_comp.h:83:9: error: type qualifiers ignored >> on function return type [-Werror=ignored-qualifiers] 83 | const u32 (*get_blend_modes)(struct device *dev); | ^ drivers/gpu/drm/mediatek/mtk_ddp_comp.h:271:1: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] 271 | const u32 mtk_ddp_comp_get_blend_modes(struct mtk_ddp_comp *comp) | ^ >> drivers/gpu/drm/mediatek/mtk_mdp_rdma.c:236:1: error: type qualifiers >> ignored on function return type [-Werror=ignored-qualifiers] 236 |
Re: [PATCH v3] platform/x86/tuxedo: Add virtual LampArray for TUXEDO NB04 devices
Hi Werner,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on drm-tip/drm-tip linus/master v6.11 next-20240927]
[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/Werner-Sembach/platform-x86-tuxedo-Add-virtual-LampArray-for-TUXEDO-NB04-devices/20240927-221932
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240927141745.145176-1-wse%40tuxedocomputers.com
patch subject: [PATCH v3] platform/x86/tuxedo: Add virtual LampArray for TUXEDO
NB04 devices
config: x86_64-buildonly-randconfig-002-20240928
(https://download.01.org/0day-ci/archive/20240928/202409281630.xjuvwu5v-...@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/20240928/202409281630.xjuvwu5v-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202409281630.xjuvwu5v-...@intel.com/
All errors (new ones prefixed by >>):
ld: vmlinux.o: in function `remove':
>> drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_init.c:67: undefined
>> reference to `hid_destroy_device'
ld: vmlinux.o: in function `__wmi_method_acpi_object_out':
>> drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_util.c:26: undefined reference
>> to `wmidev_evaluate_method'
ld: vmlinux.o: in function `ll_parse':
>> drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_virtual_lamp_array.c:355:
>> undefined reference to `hid_parse_report'
ld: vmlinux.o: in function `tuxedo_nb04_virtual_lamp_array_add_device':
>> drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_virtual_lamp_array.c:721:
>> undefined reference to `hid_allocate_device'
>> ld: drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_virtual_lamp_array.c:734:
>> undefined reference to `hid_add_device'
>> ld: drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_virtual_lamp_array.c:736:
>> undefined reference to `hid_destroy_device'
ld: vmlinux.o: in function `tuxedo_nb04_wmi_ab_driver_init':
>> drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_init.c:86: undefined
>> reference to `__wmi_driver_register'
ld: vmlinux.o: in function `tuxedo_nb04_wmi_ab_driver_exit':
>> drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_init.c:86: undefined
>> reference to `wmi_driver_unregister'
vim +67 drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_init.c
62
63 static void remove(struct wmi_device *wdev)
64 {
65 struct tuxedo_nb04_wmi_driver_data_t *driver_data =
dev_get_drvdata(&wdev->dev);
66
> 67 hid_destroy_device(driver_data->virtual_lamp_array_hdev);
68 }
69
70 static const struct wmi_device_id tuxedo_nb04_wmi_ab_device_ids[] = {
71 { .guid_string = "80C9BAA6-AC48-4538-9234-9F81A55E7C85" },
72 { }
73 };
74 MODULE_DEVICE_TABLE(wmi, tuxedo_nb04_wmi_ab_device_ids);
75
76 static struct wmi_driver tuxedo_nb04_wmi_ab_driver = {
77 .driver = {
78 .name = "tuxedo_nb04_wmi_ab",
79 .probe_type = PROBE_PREFER_ASYNCHRONOUS,
80 },
81 .id_table = tuxedo_nb04_wmi_ab_device_ids,
82 .probe = probe,
83 .remove = remove,
84 .no_singleton = true,
85 };
> 86 module_wmi_driver(tuxedo_nb04_wmi_ab_driver);
87
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3] platform/x86/tuxedo: Add virtual LampArray for TUXEDO NB04 devices
Hi Werner, kernel test robot noticed the following build errors: [auto build test ERROR on drm-misc/drm-misc-next] [also build test ERROR on drm-tip/drm-tip linus/master v6.11 next-20240927] [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/Werner-Sembach/platform-x86-tuxedo-Add-virtual-LampArray-for-TUXEDO-NB04-devices/20240927-221932 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240927141745.145176-1-wse%40tuxedocomputers.com patch subject: [PATCH v3] platform/x86/tuxedo: Add virtual LampArray for TUXEDO NB04 devices config: x86_64-buildonly-randconfig-004-20240928 (https://download.01.org/0day-ci/archive/20240928/202409281513.tyxqagoh-...@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/20240928/202409281513.tyxqagoh-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202409281513.tyxqagoh-...@intel.com/ All errors (new ones prefixed by >>, old ones prefixed by <<): WARNING: modpost: missing MODULE_DESCRIPTION() in arch/x86/mm/testmmiotrace.o WARNING: modpost: missing MODULE_DESCRIPTION() in kernel/locking/test-ww_mutex.o WARNING: modpost: missing MODULE_DESCRIPTION() in mm/kasan/kasan_test.o WARNING: modpost: missing MODULE_DESCRIPTION() in mm/kasan/kasan_test_module.o WARNING: modpost: missing MODULE_DESCRIPTION() in lib/slub_kunit.o ERROR: modpost: "hid_destroy_device" [drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab.ko] undefined! >> ERROR: modpost: "wmidev_evaluate_method" >> [drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab.ko] undefined! >> ERROR: modpost: "wmi_driver_unregister" >> [drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab.ko] undefined! >> ERROR: modpost: "__wmi_driver_register" >> [drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab.ko] undefined! ERROR: modpost: "hid_parse_report" [drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab.ko] undefined! ERROR: modpost: "hid_add_device" [drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab.ko] undefined! ERROR: modpost: "hid_allocate_device" [drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab.ko] undefined! -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/1] platform/x86/tuxedo: Add virtual LampArray for TUXEDO NB04 devices
Hi Werner, kernel test robot noticed the following build errors: [auto build test ERROR on drm-misc/drm-misc-next] [also build test ERROR on drm-tip/drm-tip linus/master v6.11 next-20240927] [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/Werner-Sembach/platform-x86-tuxedo-Add-virtual-LampArray-for-TUXEDO-NB04-devices/20240927-014628 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240926174405.110748-2-wse%40tuxedocomputers.com patch subject: [PATCH 1/1] platform/x86/tuxedo: Add virtual LampArray for TUXEDO NB04 devices config: i386-alldefconfig (https://download.01.org/0day-ci/archive/20240927/202409271950.jumzgcg8-...@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/20240927/202409271950.jumzgcg8-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202409271950.jumzgcg8-...@intel.com/ All errors (new ones prefixed by >>): ld: drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_init.o: in function `tuxedo_nb04_wmi_ab_driver_init': >> tuxedo_nb04_wmi_ab_init.c:(.init.text+0xb): undefined reference to >> `__wmi_driver_register' ld: drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_init.o: in function `tuxedo_nb04_wmi_ab_driver_exit': >> tuxedo_nb04_wmi_ab_init.c:(.exit.text+0x9): undefined reference to >> `wmi_driver_unregister' ld: drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_util.o: in function `__wmi_method_buffer_out.constprop.0': >> tuxedo_nb04_wmi_util.c:(.text+0x52): undefined reference to >> `wmidev_evaluate_method' -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/1] platform/x86/tuxedo: Add virtual LampArray for TUXEDO NB04 devices
Hi Werner,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-tip/drm-tip lee-leds/for-leds-next linus/master
v6.11 next-20240927]
[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/Werner-Sembach/platform-x86-tuxedo-Add-virtual-LampArray-for-TUXEDO-NB04-devices/20240927-014628
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240926174405.110748-2-wse%40tuxedocomputers.com
patch subject: [PATCH 1/1] platform/x86/tuxedo: Add virtual LampArray for
TUXEDO NB04 devices
config: i386-buildonly-randconfig-002-20240927
(https://download.01.org/0day-ci/archive/20240927/202409271653.raiw37rn-...@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/20240927/202409271653.raiw37rn-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202409271653.raiw37rn-...@intel.com/
All warnings (new ones prefixed by >>):
drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_virtual_lamp_array.c: In
function 'll_raw_request':
>> : warning: format '%lu' expects argument of type 'long
>> unsigned int', but argument 6 has type 'size_t' {aka 'unsigned int'}
>> [-Wformat=]
: note: in definition of macro 'KBUILD_MODNAME'
include/linux/dynamic_debug.h:224:29: note: in expansion of macro 'pr_fmt'
224 | func(&id, ##__VA_ARGS__); \
| ^~~
include/linux/dynamic_debug.h:248:9: note: in expansion of macro
'__dynamic_func_call_cls'
248 | __dynamic_func_call_cls(__UNIQUE_ID(ddebug), cls, fmt, func,
##__VA_ARGS__)
| ^~~
include/linux/dynamic_debug.h:250:9: note: in expansion of macro
'_dynamic_func_call_cls'
250 | _dynamic_func_call_cls(_DPRINTK_CLASS_DFLT, fmt, func,
##__VA_ARGS__)
| ^~
include/linux/dynamic_debug.h:269:9: note: in expansion of macro
'_dynamic_func_call'
269 | _dynamic_func_call(fmt, __dynamic_pr_debug, \
| ^~
include/linux/printk.h:589:9: note: in expansion of macro 'dynamic_pr_debug'
589 | dynamic_pr_debug(fmt, ##__VA_ARGS__)
| ^~~~
drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_virtual_lamp_array.c:669:9:
note: in expansion of macro 'pr_debug'
669 | pr_debug("Recived report: rtype: %u, reqtype: %u, reportnum:
%u, len: %lu buf:\n", rtype,
| ^~~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/1] platform/x86/tuxedo: Add virtual LampArray for TUXEDO NB04 devices
Hi Werner,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm-tip/drm-tip lee-leds/for-leds-next linus/master
v6.11 next-20240927]
[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/Werner-Sembach/platform-x86-tuxedo-Add-virtual-LampArray-for-TUXEDO-NB04-devices/20240927-014628
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240926174405.110748-2-wse%40tuxedocomputers.com
patch subject: [PATCH 1/1] platform/x86/tuxedo: Add virtual LampArray for
TUXEDO NB04 devices
config: i386-buildonly-randconfig-001-20240927
(https://download.01.org/0day-ci/archive/20240927/202409271601.cdupq1zd-...@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project
3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240927/202409271601.cdupq1zd-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202409271601.cdupq1zd-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_virtual_lamp_array.c:601:11:
>> warning: variable 'lamp_count' is used uninitialized whenever 'if' condition
>> is false [-Wsometimes-uninitialized]
601 | else if (driver_data->keyboard_type ==
WMI_AB_GET_DEVICE_STATUS_KEYBOARD_LAYOUT_ISO)
|
^~
drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_virtual_lamp_array.c:604:28:
note: uninitialized use occurs here
604 | if (report->lamp_id_end > lamp_count - 1) {
| ^~
drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_virtual_lamp_array.c:601:7:
note: remove the 'if' if its condition is always true
601 | else if (driver_data->keyboard_type ==
WMI_AB_GET_DEVICE_STATUS_KEYBOARD_LAYOUT_ISO)
|
^~~
602 | lamp_count = sizeof(sirius_16_ansii_kbl_mapping);
drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_virtual_lamp_array.c:587:20:
note: initialize the variable 'lamp_count' to silence this warning
587 | uint8_t lamp_count;
| ^
|= '\0'
>> drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_virtual_lamp_array.c:670:24:
>> warning: format specifies type 'unsigned long' but the argument has type
>> 'size_t' (aka 'unsigned int') [-Wformat]
669 | pr_debug("Recived report: rtype: %u, reqtype: %u, reportnum:
%u, len: %lu buf:\n", rtype,
|
~~~
|
%zu
670 | reqtype, reportnum, len);
| ^~~
include/linux/printk.h:595:38: note: expanded from macro 'pr_debug'
595 | no_printk(KERN_DEBUG pr_fmt(fmt), ##__VA_ARGS__)
| ~~~ ^~~
include/linux/printk.h:133:18: note: expanded from macro 'no_printk'
133 | _printk(fmt, ##__VA_ARGS__);\
| ~~~^~~
2 warnings generated.
vim +601 drivers/platform/x86/tuxedo/tuxedo_nb04_wmi_ab_virtual_lamp_array.c
581
582 static int handle_lamp_range_update_report(struct hid_device *hdev,
583 struct
lamp_range_update_report_t *report)
584 {
585 int ret;
586 struct driver_data_t *driver_data = hdev->driver_data;
587 uint8_t lamp_count;
588 struct lamp_multi_update_report_t lamp_multi_update_report = {
589 .report_id = LAMP_MULTI_UPDATE_REPORT_ID
590 };
591
592 // Catching missformated lamp_range_update_report and fail
silently according to
593 // "HID Usage Tables v1.5"
594 if (report->lamp_id_start > report->lamp_id_end) {
595 pr_debug("lamp_id_start > lamp_id_end in
lamp_range_update_report. Skippng whole report!\n"
Re: [PATCH v5 2/2] drm/mediatek: Add blend_modes to mtk_plane_init() for different SoCs
Hi Jason-JH.Lin,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on linus/master next-20240926]
[cannot apply to v6.11]
[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/Jason-JH-Lin/drm-mediatek-ovl-Add-fmt_convert-function-pointer-to-driver-data/20240925-182056
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20240925101927.17042-3-jason-jh.lin%40mediatek.com
patch subject: [PATCH v5 2/2] drm/mediatek: Add blend_modes to mtk_plane_init()
for different SoCs
config: arm64-allmodconfig
(https://download.01.org/0day-ci/archive/20240926/202409261653.fyqbl1w8-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
7773243d9916f98ba0ffce0c3a960e4aa9f03e81)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240926/202409261653.fyqbl1w8-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202409261653.fyqbl1w8-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/gpu/drm/mediatek/mtk_crtc.c:7:
In file included from include/linux/dma-mapping.h:11:
In file included from include/linux/scatterlist.h:8:
In file included from include/linux/mm.h:2232:
include/linux/vmstat.h:503:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
503 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
504 |item];
|
include/linux/vmstat.h:510:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
510 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
511 |NR_VM_NUMA_EVENT_ITEMS +
|~~
include/linux/vmstat.h:517:36: warning: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Wenum-enum-conversion]
517 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
include/linux/vmstat.h:523:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
523 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
524 |NR_VM_NUMA_EVENT_ITEMS +
|~~
In file included from drivers/gpu/drm/mediatek/mtk_crtc.c:22:
In file included from drivers/gpu/drm/mediatek/mtk_crtc.h:10:
>> drivers/gpu/drm/mediatek/mtk_ddp_comp.h:83:2: warning: 'const' type
>> qualifier on return type has no effect [-Wignored-qualifiers]
83 | const u32 (*get_blend_modes)(struct device *dev);
| ^
drivers/gpu/drm/mediatek/mtk_ddp_comp.h:271:1: warning: 'const' type
qualifier on return type has no effect [-Wignored-qualifiers]
271 | const u32 mtk_ddp_comp_get_blend_modes(struct mtk_ddp_comp *comp)
| ^
6 warnings generated.
--
In file included from drivers/gpu/drm/mediatek/mtk_ddp_comp.c:17:
In file included from drivers/gpu/drm/mediatek/mtk_crtc.h:9:
In file included from include/drm/drm_crtc.h:32:
In file included from include/drm/drm_modes.h:33:
In file included from include/drm/drm_connector.h:32:
In file included from include/drm/drm_util.h:36:
In file included from include/linux/kgdb.h:19:
In file included from include/linux/kprobes.h:28:
In file included from include/linux/ftrace.h:13:
In file included from include/linux/kallsyms.h:13:
In file included from include/linux/mm.h:2232:
include/linux/vmstat.h:503:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
503 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
504 |item];
|
include/linux/vmstat.h:510:43:
Re: [PATCH v3 2/3] drm/bridge: it6505: HDCP CTS fail on repeater items
Hi Hermes,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-exynos/exynos-drm-next drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip
linus/master v6.11 next-20240923]
[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/Hermes-Wu/drm-bridge-it6505-fix-AUX-read-use-aux-fifo/20240923-175041
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20240923094826.13471-3-Hermes.Wu%40ite.com.tw
patch subject: [PATCH v3 2/3] drm/bridge: it6505: HDCP CTS fail on repeater
items
config: nios2-randconfig-r073-20240924
(https://download.01.org/0day-ci/archive/20240924/202409241856.owgr1x3y-...@intel.com/config)
compiler: nios2-linux-gcc (GCC) 14.1.0
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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202409241856.owgr1x3y-...@intel.com/
smatch warnings:
drivers/gpu/drm/bridge/ite-it6505.c:2027 it6505_setup_sha1_input() warn:
inconsistent indenting
vim +2027 drivers/gpu/drm/bridge/ite-it6505.c
b5c84a9edcd418 Allen Chen 2022-01-14 1996
b5c84a9edcd418 Allen Chen 2022-01-14 1997 static int
it6505_setup_sha1_input(struct it6505 *it6505, u8 *sha1_input)
b5c84a9edcd418 Allen Chen 2022-01-14 1998 {
d65feac281ab47 Pin-yen Lin 2023-07-18 1999 struct device *dev =
it6505->dev;
b5c84a9edcd418 Allen Chen 2022-01-14 2000 u8 binfo[2];
9665163df60e16 Hermes Wu 2024-09-23 2001 int down_stream_count, err,
msg_count = 0;
b5c84a9edcd418 Allen Chen 2022-01-14 2002
b5c84a9edcd418 Allen Chen 2022-01-14 2003 err = it6505_get_dpcd(it6505,
DP_AUX_HDCP_BINFO, binfo,
b5c84a9edcd418 Allen Chen 2022-01-14 2004
ARRAY_SIZE(binfo));
b5c84a9edcd418 Allen Chen 2022-01-14 2005
b5c84a9edcd418 Allen Chen 2022-01-14 2006 if (err < 0) {
b5c84a9edcd418 Allen Chen 2022-01-14 2007 dev_err(dev, "Read
binfo value Fail");
b5c84a9edcd418 Allen Chen 2022-01-14 2008 return err;
b5c84a9edcd418 Allen Chen 2022-01-14 2009 }
b5c84a9edcd418 Allen Chen 2022-01-14 2010
b5c84a9edcd418 Allen Chen 2022-01-14 2011 down_stream_count = binfo[0] &
0x7F;
b5c84a9edcd418 Allen Chen 2022-01-14 2012 DRM_DEV_DEBUG_DRIVER(dev,
"binfo:0x%*ph", (int)ARRAY_SIZE(binfo),
b5c84a9edcd418 Allen Chen 2022-01-14 2013 binfo);
b5c84a9edcd418 Allen Chen 2022-01-14 2014
b5c84a9edcd418 Allen Chen 2022-01-14 2015 if ((binfo[0] & BIT(7)) ||
(binfo[1] & BIT(3))) {
b5c84a9edcd418 Allen Chen 2022-01-14 2016 dev_err(dev, "HDCP max
cascade device exceed");
b5c84a9edcd418 Allen Chen 2022-01-14 2017 return 0;
b5c84a9edcd418 Allen Chen 2022-01-14 2018 }
b5c84a9edcd418 Allen Chen 2022-01-14 2019
b5c84a9edcd418 Allen Chen 2022-01-14 2020 if (!down_stream_count ||
b5c84a9edcd418 Allen Chen 2022-01-14 2021 down_stream_count >
MAX_HDCP_DOWN_STREAM_COUNT) {
b5c84a9edcd418 Allen Chen 2022-01-14 2022 dev_err(dev, "HDCP down
stream count Error %d",
b5c84a9edcd418 Allen Chen 2022-01-14 2023
down_stream_count);
b5c84a9edcd418 Allen Chen 2022-01-14 2024 return 0;
b5c84a9edcd418 Allen Chen 2022-01-14 2025 }
9665163df60e16 Hermes Wu 2024-09-23 2026 err =
it6505_get_ksvlist(it6505, sha1_input, down_stream_count * 5);
b5c84a9edcd418 Allen Chen 2022-01-14 @2027 if (err < 0)
b5c84a9edcd418 Allen Chen 2022-01-14 2028 return err;
b5c84a9edcd418 Allen Chen 2022-01-14 2029
9665163df60e16 Hermes Wu 2024-09-23 2030 msg_count += down_stream_count
* 5;
b5c84a9edcd418 Allen Chen 2022-01-14 2031
b5c84a9edcd418 Allen Chen 2022-01-14 2032 it6505->hdcp_down_stream_count
= down_stream_count;
b5c84a9edcd418 Allen Chen 2022-01-14 2033 sha1_input[msg_count++] =
binfo[0];
b5c84a9edcd418 Allen Chen 2022-01-14 2034 sha1_input[msg_count++] =
binfo[1];
b5c84a9edcd418 Allen Chen 2022-01-14 2035
b5c84a9edcd418 Allen Chen 2022-01-14 2036 it6505_set_bits(it6505,
REG_HDCP_CTRL2, HDCP_EN_M0_READ,
b5c84a9edcd418 Allen Chen 2022-01-14 2037
HDCP_EN_M0_READ);
b5c84a9edcd418 Allen Chen 2022-01-14 2038
b5c84a9edcd418 Allen Chen 2022-01-14 2039 err =
regmap_bulk_read(it6505->regmap, REG_M0_0_7,
b5c84a9edcd418 Allen Chen 2022-01-14 2040
sha1_input + msg_count, 8);
b5c84a9edcd418 Allen Chen 2022-01-1
Re: [PATCH v1 1/1] drm/mediatek: dp: Add sdp path reset
Hi Liankun,
kernel test robot noticed the following build errors:
[auto build test ERROR on pza/reset/next]
[also build test ERROR on linus/master v6.11 next-20240923]
[cannot apply to pza/imx-drm/next]
[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/Liankun-Yang/drm-mediatek-dp-Add-sdp-path-reset/20240923-213747
base: https://git.pengutronix.de/git/pza/linux reset/next
patch link:
https://lore.kernel.org/r/20240923133610.23728-1-liankun.yang%40mediatek.com
patch subject: [PATCH v1 1/1] drm/mediatek: dp: Add sdp path reset
config: arm64-allmodconfig
(https://download.01.org/0day-ci/archive/20240924/202409240818.3cqdkw5o-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
8663a75fa2f31299ab8d1d90288d9df92aadee88)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240924/202409240818.3cqdkw5o-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202409240818.3cqdkw5o-...@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/mediatek/mtk_dp.c:9:
In file included from include/drm/display/drm_dp_helper.h:27:
In file included from include/linux/i2c.h:13:
In file included from include/linux/acpi.h:39:
In file included from include/acpi/acpi_io.h:7:
In file included from arch/arm64/include/asm/acpi.h:14:
In file included from include/linux/memblock.h:12:
In file included from include/linux/mm.h:2228:
include/linux/vmstat.h:503:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
503 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
504 |item];
|
include/linux/vmstat.h:510:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
510 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
511 |NR_VM_NUMA_EVENT_ITEMS +
|~~
include/linux/vmstat.h:517:36: warning: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Wenum-enum-conversion]
517 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
include/linux/vmstat.h:523:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
523 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
524 |NR_VM_NUMA_EVENT_ITEMS +
|~~
>> drivers/gpu/drm/mediatek/mtk_dp.c:1058:5: error: use of undeclared
>> identifier 'SDP_RESET_SW_DP_ENC0_P0'
1058 | SDP_RESET_SW_DP_ENC0_P0,
| ^
drivers/gpu/drm/mediatek/mtk_dp.c:1059:5: error: use of undeclared
identifier 'SDP_RESET_SW_DP_ENC0_P0'
1059 | SDP_RESET_SW_DP_ENC0_P0);
| ^
drivers/gpu/drm/mediatek/mtk_dp.c:1064:8: error: use of undeclared
identifier 'SDP_RESET_SW_DP_ENC0_P0'
1064 | 0, SDP_RESET_SW_DP_ENC0_P0);
|^
4 warnings and 3 errors generated.
vim +/SDP_RESET_SW_DP_ENC0_P0 +1058 drivers/gpu/drm/mediatek/mtk_dp.c
1054
1055 static void mtk_dp_sdp_path_reset(struct mtk_dp *mtk_dp)
1056 {
1057 mtk_dp_update_bits(mtk_dp, MTK_DP_ENC0_P0_3004,
> 1058 SDP_RESET_SW_DP_ENC0_P0,
1059 SDP_RESET_SW_DP_ENC0_P0);
1060
1061 /* Wait for sdp path reset to complete */
1062 usleep_range(1000, 5000);
1063 mtk_dp_update_bits(mtk_dp, MTK_DP_ENC0_P0_3004,
1064 0, SDP_RESET_SW_DP_ENC0_P0);
1065 }
1066
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v1 1/1] drm/mediatek: dp: Add sdp path reset
Hi Liankun,
kernel test robot noticed the following build errors:
[auto build test ERROR on pza/reset/next]
[also build test ERROR on linus/master v6.11 next-20240923]
[cannot apply to pza/imx-drm/next]
[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/Liankun-Yang/drm-mediatek-dp-Add-sdp-path-reset/20240923-213747
base: https://git.pengutronix.de/git/pza/linux reset/next
patch link:
https://lore.kernel.org/r/20240923133610.23728-1-liankun.yang%40mediatek.com
patch subject: [PATCH v1 1/1] drm/mediatek: dp: Add sdp path reset
config: arm-allmodconfig
(https://download.01.org/0day-ci/archive/20240924/202409240700.arp9pduk-...@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240924/202409240700.arp9pduk-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202409240700.arp9pduk-...@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/mediatek/mtk_dp.c: In function 'mtk_dp_sdp_path_reset':
>> drivers/gpu/drm/mediatek/mtk_dp.c:1058:33: error: 'SDP_RESET_SW_DP_ENC0_P0'
>> undeclared (first use in this function); did you mean
>> 'SDP_PACKET_W_DP_ENC1_P0'?
1058 | SDP_RESET_SW_DP_ENC0_P0,
| ^~~
| SDP_PACKET_W_DP_ENC1_P0
drivers/gpu/drm/mediatek/mtk_dp.c:1058:33: note: each undeclared identifier
is reported only once for each function it appears in
vim +1058 drivers/gpu/drm/mediatek/mtk_dp.c
1054
1055 static void mtk_dp_sdp_path_reset(struct mtk_dp *mtk_dp)
1056 {
1057 mtk_dp_update_bits(mtk_dp, MTK_DP_ENC0_P0_3004,
> 1058 SDP_RESET_SW_DP_ENC0_P0,
1059 SDP_RESET_SW_DP_ENC0_P0);
1060
1061 /* Wait for sdp path reset to complete */
1062 usleep_range(1000, 5000);
1063 mtk_dp_update_bits(mtk_dp, MTK_DP_ENC0_P0_3004,
1064 0, SDP_RESET_SW_DP_ENC0_P0);
1065 }
1066
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[linus:master] [drm/ast] 2a2391f857: WARNING:at_drivers/gpu/drm/ast/ast_mode.c:#ast_primary_plane_helper_atomic_check[ast]
Hello,
kernel test robot noticed
"WARNING:at_drivers/gpu/drm/ast/ast_mode.c:#ast_primary_plane_helper_atomic_check[ast]"
on:
commit: 2a2391f857cdc5cf16f8df030944cef8d3d2bc30 ("drm/ast: vga: Transparently
handle BMC support")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 88264981f2082248e892a706b2c5004650faac54]
[test failed on linux-next/master 62f92d634458a1e308bb699986b9147a6d670457]
in testcase: igt
version: igt-x86_64-73e21b2bb-1_20240623
with following parameters:
group: group-23
compiler: gcc-12
test machine: 128 threads 2 sockets Intel(R) Xeon(R) Platinum 8358 CPU @
2.60GHz (Ice Lake) with 128G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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
| Closes:
https://lore.kernel.org/oe-lkp/202409231329.c40e1dd8-oliver.s...@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240923/202409231329.c40e1dd8-oliver.s...@intel.com
[ 250.121296][ T3960] [ cut here ]
[ 250.121299][ T3960] ast :02:00.0: [drm]
drm_WARN_ON(new_plane_state->crtc)
[ 250.121343][ T3960] WARNING: CPU: 72 PID: 3960 at
drivers/gpu/drm/ast/ast_mode.c:618
ast_primary_plane_helper_atomic_check+0x2e0/0x410 [ast]
[ 250.121353][ T3960] Modules linked in: kmem device_dax nd_pmem dax_pmem
nd_btt i915 drm_buddy intel_gtt drm_display_helper ttm video intel_rapl_msr
intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common
x86_pkg_temp_thermal intel_powerclamp btrfs coretemp blake2b_generic xor
zstd_compress raid6_pq libcrc32c sd_mod kvm_intel sg kvm crct10dif_pclmul
crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 rapl ast ahci
ipmi_ssif drm_shmem_helper libahci mei_me acpi_power_meter intel_cstate
intel_th_gth i2c_i801 intel_th_pci ioatdma intel_uncore dax_hmem libata
drm_kms_helper mei intel_pch_thermal i2c_smbus intel_vsec intel_th dca wmi
ipmi_si acpi_ipmi nfit ipmi_devintf libnvdimm ipmi_msghandler acpi_pad joydev
binfmt_misc drm fuse loop dm_mod ip_tables
[ 250.121407][ T3960] CPU: 72 UID: 0 PID: 3960 Comm: kms_cursor_lega Not
tainted 6.11.0-rc2-00356-g2a2391f857cd #1
[ 250.121411][ T3960] RIP:
0010:ast_primary_plane_helper_atomic_check+0x2e0/0x410 [ast]
[ 250.121417][ T3960] Code: 48 8b 6b 50 48 85 ed 74 59 48 89 df e8 29 d9 8d c1
48 c7 c1 20 23 12 c1 48 89 ea 48 c7 c7 80 23 12 c1 48 89 c6 e8 a0 47 0d c0 <0f>
0b b8 ea ff ff ff e9 55 ff ff ff 48 89 34 24 e8 1b 39 98 c0 48
[ 250.121420][ T3960] RSP: 0018:ffa026b1f8f8 EFLAGS: 00010282
[ 250.121423][ T3960] RAX: RBX: ff1100017299a0c8 RCX:
0027
[ 250.121425][ T3960] RDX: 0027 RSI: 0004 RDI:
ff11000c3f430b08
[ 250.121427][ T3960] RBP: ff11000113c335a0 R08: 0001 R09:
ffe21c0187e86161
[ 250.121428][ T3960] R10: ff11000c3f430b0b R11: 0014 R12:
ff1100018f9db000
[ 250.121430][ T3960] R13: ff11000215a3 R14: ff1100018f9d8808 R15:
ff11000215a30688
[ 250.121432][ T3960] FS: 7f5cb09fe8c0() GS:ff11000c3f40()
knlGS:
[ 250.121434][ T3960] CS: 0010 DS: ES: CR0: 80050033
[ 250.121435][ T3960] CR2: 7f5cb0942000 CR3: 0001451d6004 CR4:
00771ef0
[ 250.121437][ T3960] DR0: DR1: DR2:
[ 250.121438][ T3960] DR3: DR6: fffe0ff0 DR7:
0400
[ 250.121439][ T3960] PKRU: 5554
[ 250.121441][ T3960] Call Trace:
[ 250.121442][ T3960]
[ 250.121444][ T3960] ? __warn+0xcc/0x260
[ 250.121450][ T3960] ? ast_primary_plane_helper_atomic_check+0x2e0/0x410
[ast]
[ 250.121455][ T3960] ? report_bug+0x261/0x2c0
[ 250.121461][ T3960] ? handle_bug+0x3c/0x70
[ 250.121465][ T3960] ? exc_invalid_op+0x17/0x40
[ 250.121468][ T3960] ? asm_exc_invalid_op+0x1a/0x20
[ 250.121473][ T3960] ? ast_primary_plane_helper_atomic_check+0x2e0/0x410
[ast]
[ 250.121478][ T3960] ? ast_primary_plane_helper_atomic_check+0x2e0/0x410
[ast]
[ 250.121483][ T3960] drm_atomic_helper_check_planes+0x30a/0x8f0
[drm_kms_helper]
[ 250.121503][ T3960] drm_atomic_helper_check+0x7a/0x120 [drm_kms_helper]
[ 250.121517][ T3960] ? __pfx_drm_atomic_helper_check+0x10/0x10
[drm_kms_helper]
[ 250.121530][ T3960] drm_atomic_check_only+0x5ac/0x11a0 [drm]
[ 250.121580][ T3960] ? __pfx___drm_dev_dbg+0x10/0x10 [drm]
[ 250.121621][ T3960] drm_atomic_commit+0x114/0x2b0 [drm]
[ 250.121654][ T3960] ? __pfx_drm_atomic_commit+0x10/0x10 [drm]
[ 250.121692][ T3960] ? __pfx___drm_printfn_info+0x10/0x10 [drm]
[ 250.121732][ T3960] drm_mode_atomic_ioctl+0x985/0xe80 [drm]
[ 250.121765][ T3960] ? __pfx_drm_mode_atomic_ioctl+0x10/0x10 [drm]
[ 250.121797][ T3960]
Re: [PATCH 1/2] drm/panthor: Add csg_priority to panthor_group
Hi Mary, kernel test robot noticed the following build warnings: [auto build test WARNING on drm/drm-next] [also build test WARNING on drm-exynos/exynos-drm-next drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip linus/master v6.11 next-20240920] [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/Mary-Guillemard/drm-panthor-Add-csg_priority-to-panthor_group/20240918-165602 base: git://anongit.freedesktop.org/drm/drm drm-next patch link: https://lore.kernel.org/r/20240918085056.24422-3-mary.guillemard%40collabora.com patch subject: [PATCH 1/2] drm/panthor: Add csg_priority to panthor_group config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20240922/202409220025.v4ccqjai-...@intel.com/config) compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240922/202409220025.v4ccqjai-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202409220025.v4ccqjai-...@intel.com/ All warnings (new ones prefixed by >>): drivers/gpu/drm/panthor/panthor_sched.c:319: warning: Excess struct member 'runnable' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:319: warning: Excess struct member 'idle' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:319: warning: Excess struct member 'waiting' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:319: warning: Excess struct member 'has_ref' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:319: warning: Excess struct member 'in_progress' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:319: warning: Excess struct member 'stopped_groups' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'mem' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'input' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'output' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'input_fw_va' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'output_fw_va' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'gpu_va' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'ref' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'gt' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'sync64' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'bo' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'offset' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'kmap' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'lock' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'id' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'seqno' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'last_fence' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:479: warning: Excess struct member 'in_flight_jobs' description in 'panthor_queue' >> drivers/gpu/drm/panthor/panthor_sched.c:669: warning: Function parameter or >> struct member 'csg_priority' not described in 'panthor_group' drivers/gpu/drm/panthor/panthor_sched.c:78
Re: [PATCH v2 2/3] PCI: Allow extending VF BAR within original resource boundary
Hi Michał,
kernel test robot noticed the following build warnings:
[auto build test WARNING on pci/for-linus]
[also build test WARNING on drm-xe/drm-xe-next drm/drm-next
drm-exynos/exynos-drm-next drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip
linus/master v6.11 next-20240920]
[cannot apply to pci/next]
[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/Micha-Winiarski/PCI-Add-support-for-VF-Resizable-Bar-extended-cap/20240920-064112
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git for-linus
patch link:
https://lore.kernel.org/r/20240919223557.1897608-3-michal.winiarski%40intel.com
patch subject: [PATCH v2 2/3] PCI: Allow extending VF BAR within original
resource boundary
config: arm-allnoconfig
(https://download.01.org/0day-ci/archive/20240920/202409201934.ym9hvuai-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
8663a75fa2f31299ab8d1d90288d9df92aadee88)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240920/202409201934.ym9hvuai-...@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
| Closes:
https://lore.kernel.org/oe-kbuild-all/202409201934.ym9hvuai-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from arch/arm/mm/iomap.c:9:
>> include/linux/pci.h:2421:3: warning: void function 'pci_iov_resource_extend'
>> should not return a value [-Wreturn-mismatch]
2421 | { return -ENODEV; }
| ^ ~~~
In file included from arch/arm/mm/iomap.c:9:
In file included from include/linux/pci.h:2672:
In file included from include/linux/dma-mapping.h:11:
In file included from include/linux/scatterlist.h:8:
In file included from include/linux/mm.h:2228:
include/linux/vmstat.h:514:36: warning: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Wenum-enum-conversion]
514 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
2 warnings generated.
vim +/pci_iov_resource_extend +2421 include/linux/pci.h
2397
2398 static inline int pci_iov_sysfs_link(struct pci_dev *dev,
2399 struct pci_dev *virtfn, int id)
2400 {
2401 return -ENODEV;
2402 }
2403 static inline int pci_iov_add_virtfn(struct pci_dev *dev, int id)
2404 {
2405 return -ENOSYS;
2406 }
2407 static inline void pci_iov_remove_virtfn(struct pci_dev *dev,
2408 int id) { }
2409 static inline void pci_disable_sriov(struct pci_dev *dev) { }
2410 static inline int pci_num_vf(struct pci_dev *dev) { return 0; }
2411 static inline int pci_vfs_assigned(struct pci_dev *dev)
2412 { return 0; }
2413 static inline int pci_sriov_set_totalvfs(struct pci_dev *dev, u16
numvfs)
2414 { return 0; }
2415 static inline int pci_sriov_get_totalvfs(struct pci_dev *dev)
2416 { return 0; }
2417 #define pci_sriov_configure_simple NULL
2418 static inline resource_size_t pci_iov_resource_size(struct pci_dev
*dev, int resno)
2419 { return 0; }
2420 static inline void pci_iov_resource_extend(struct pci_dev *dev, int
resno, bool enable)
> 2421 { return -ENODEV; }
2422 static inline void pci_vf_drivers_autoprobe(struct pci_dev *dev, bool
probe) { }
2423 #endif
2424
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
