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
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: arc-allnoconfig
(https://download.01.org/0day-ci/archive/20240920/202409201854.z0daqyye-...@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/20240920/202409201854.z0daqyye-...@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/202409201854.z0daqyye-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/pci/of.c:12:
include/linux/pci.h: In function 'pci_iov_resource_extend':
>> include/linux/pci.h:2421:10: warning: 'return' with a value, in function
>> returning void [-Wreturn-type]
2421 | { return -ENODEV; }
| ^
include/linux/pci.h:2420:20: note: declared here
2420 | static inline void pci_iov_resource_extend(struct pci_dev *dev, int
resno, bool enable)
|^~~
vim +/return +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
Re: [PATCH v2 1/3] PCI: Add support for VF Resizable Bar extended cap
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-20240919]
[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-2-michal.winiarski%40intel.com
patch subject: [PATCH v2 1/3] PCI: Add support for VF Resizable Bar extended cap
config: x86_64-kexec
(https://download.01.org/0day-ci/archive/20240920/202409201629.qlc0mrbn-...@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/20240920/202409201629.qlc0mrbn-...@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/202409201629.qlc0mrbn-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/pci/pci.c:1920:20: warning: variable 'res' set but not used
>> [-Wunused-but-set-variable]
1920 | struct resource *res;
| ^
1 warning generated.
vim +/res +1920 drivers/pci/pci.c
1903
1904 static void pci_restore_vf_rebar_state(struct pci_dev *pdev)
1905 {
1906 unsigned int pos, nbars, i;
1907 u32 ctrl;
1908
1909 if (!pdev->is_physfn)
1910 return;
1911
1912 pos = pci_find_ext_capability(pdev, PCI_EXT_CAP_ID_VF_REBAR);
1913 if (!pos)
1914 return;
1915
1916 pci_read_config_dword(pdev, pos + PCI_REBAR_CTRL, &ctrl);
1917 nbars = FIELD_GET(PCI_REBAR_CTRL_NBAR_MASK, ctrl);
1918
1919 for (i = 0; i < nbars; i++, pos += 8) {
> 1920 struct resource *res;
1921 int bar_idx, size;
1922
1923 pci_read_config_dword(pdev, pos + PCI_REBAR_CTRL,
&ctrl);
1924 bar_idx = ctrl & PCI_REBAR_CTRL_BAR_IDX;
1925 res = pdev->resource + bar_idx;
1926 size =
pci_rebar_bytes_to_size(pdev->sriov->barsz[bar_idx]);
1927 ctrl &= ~PCI_REBAR_CTRL_BAR_SIZE;
1928 ctrl |= FIELD_PREP(PCI_REBAR_CTRL_BAR_SIZE, size);
1929 pci_write_config_dword(pdev, pos + PCI_REBAR_CTRL,
ctrl);
1930 }
1931 }
1932
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 3/3] drm/amdgpu: use drm_file name
Hi Pierre-Eric,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-exynos/exynos-drm-next]
[also build test WARNING on 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-20240919]
[cannot apply to drm/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/Pierre-Eric-Pelloux-Prayer/drm-use-drm_file-name-in-fdinfo/20240916-213521
base: https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git
exynos-drm-next
patch link:
https://lore.kernel.org/r/20240916133223.1023773-3-pierre-eric.pelloux-prayer%40amd.com
patch subject: [PATCH v2 3/3] drm/amdgpu: use drm_file name
config: x86_64-allyesconfig
(https://download.01.org/0day-ci/archive/20240920/202409200113.0aee5yg9-...@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/20240920/202409200113.0aee5yg9-...@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/202409200113.0aee5yg9-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c:997:32: warning: variable 'file' is
>> uninitialized when used here [-Wuninitialized]
997 | r = mutex_lock_interruptible(&file->name_lock);
| ^~~~
include/linux/mutex.h:162:72: note: expanded from macro
'mutex_lock_interruptible'
162 | #define mutex_lock_interruptible(lock)
mutex_lock_interruptible_nested(lock, 0)
|
^~~~
drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c:990:23: note: initialize the
variable 'file' to silence this warning
990 | struct drm_file *file;
| ^
| = NULL
1 warning generated.
vim +/file +997 drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
984
985 #if defined(CONFIG_DEBUG_FS)
986 static int amdgpu_debugfs_gem_info_show(struct seq_file *m, void
*unused)
987 {
988 struct amdgpu_device *adev = m->private;
989 struct drm_device *dev = adev_to_drm(adev);
990 struct drm_file *file;
991 int r;
992
993 r = mutex_lock_interruptible(&dev->filelist_mutex);
994 if (r)
995 return r;
996
> 997 r = mutex_lock_interruptible(&file->name_lock);
998 if (r)
999 goto out;
1000
1001 list_for_each_entry(file, &dev->filelist, lhead) {
1002 struct task_struct *task;
1003 struct drm_gem_object *gobj;
1004 struct pid *pid;
1005 int id;
1006
1007 /*
1008 * Although we have a valid reference on file->pid,
that does
1009 * not guarantee that the task_struct who called
get_pid() is
1010 * still alive (e.g. get_pid(current) => fork() =>
exit()).
1011 * Therefore, we need to protect this ->comm access
using RCU.
1012 */
1013 rcu_read_lock();
1014 pid = rcu_dereference(file->pid);
1015 task = pid_task(pid, PIDTYPE_TGID);
1016 seq_printf(m, "pid %8d command %s", pid_nr(pid),
1017 task ? task->comm : "");
1018 if (file->name) {
1019 seq_putc(m, '/');
1020 seq_puts(m, file->name);
1021 }
1022 seq_puts(m, ":\n");
1023 rcu_read_unlock();
1024
1025 spin_lock(&file->table_lock);
1026 idr_for_each_entry(&file->object_idr, gobj, id) {
1027 struct amdgpu_bo *bo = gem_to_amdgpu_bo(gobj);
1028
1029 amdgpu_bo_print_info(id, bo, m);
1030 }
1031 spin_unlock(&file->table_lock);
1032 }
1033 mutex_unlock(&file->name_lock);
1034 out:
1035 mutex_unlock(&dev->filelist_mutex);
1036 return 0;
1037 }
1038
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 10/10] drm/amd/display: Fetch the EDID from _DDC if available for eDP
Hi Mario,
kernel test robot noticed the following build errors:
[auto build test ERROR on amd-pstate/linux-next]
[also build test ERROR on amd-pstate/bleeding-edge linus/master v6.11]
[cannot apply to next-20240918]
[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/Mario-Limonciello/drm-amd-display-switch-amdgpu_dm_connector-to-use-struct-drm_edid/20240912-093827
base: https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git
linux-next
patch link:
https://lore.kernel.org/r/20240911213537.2338164-11-superm1%40kernel.org
patch subject: [PATCH v6 10/10] drm/amd/display: Fetch the EDID from _DDC if
available for eDP
config: arm64-randconfig-003-20240918
(https://download.01.org/0day-ci/archive/20240919/202409191128.4bvjysve-...@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/20240919/202409191128.4bvjysve-...@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/202409191128.4bvjysve-...@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.c: In
function 'dm_helpers_probe_acpi_edid':
>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.c:883:28:
>> error: unused variable 'ddev' [-Werror=unused-variable]
883 | struct drm_device *ddev = connector->dev;
|^~~~
cc1: all warnings being treated as errors
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for FB_IOMEM_HELPERS
Depends on [n]: HAS_IOMEM [=y] && FB_CORE [=n]
Selected by [m]:
- DRM_XE_DISPLAY [=y] && HAS_IOMEM [=y] && DRM [=y] && DRM_XE [=m] && DRM_XE
[=m]=m [=m]
vim +/ddev +883
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.c
878
879 static int
880 dm_helpers_probe_acpi_edid(void *data, u8 *buf, unsigned int block,
size_t len)
881 {
882 struct drm_connector *connector = data;
> 883 struct drm_device *ddev = connector->dev;
884 struct acpi_device *acpidev = ACPI_COMPANION(ddev->dev);
885 unsigned char start = block * EDID_LENGTH;
886 void *edid;
887 int r;
888
889 if (!acpidev)
890 return -ENODEV;
891
892 /* fetch the entire edid from BIOS */
893 r = acpi_video_get_edid(acpidev, ACPI_VIDEO_DISPLAY_LCD, -1,
&edid);
894 if (r < 0) {
895 DRM_DEBUG_KMS("Failed to get EDID from ACPI: %d\n", r);
896 return r;
897 }
898 if (len > r || start > r || start + len > r) {
899 r = -EINVAL;
900 goto cleanup;
901 }
902
903 memcpy(buf, edid + start, len);
904 r = 0;
905
906 cleanup:
907 kfree(edid);
908
909 return r;
910 }
911
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 10/10] drm/amd/display: Fetch the EDID from _DDC if available for eDP
Hi Mario,
kernel test robot noticed the following build warnings:
[auto build test WARNING on amd-pstate/linux-next]
[also build test WARNING on amd-pstate/bleeding-edge linus/master v6.11]
[cannot apply to next-20240913]
[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/Mario-Limonciello/drm-amd-display-switch-amdgpu_dm_connector-to-use-struct-drm_edid/20240912-093827
base: https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git
linux-next
patch link:
https://lore.kernel.org/r/20240911213537.2338164-11-superm1%40kernel.org
patch subject: [PATCH v6 10/10] drm/amd/display: Fetch the EDID from _DDC if
available for eDP
config: alpha-allyesconfig
(https://download.01.org/0day-ci/archive/20240916/202409161225.xuqvkkor-...@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/20240916/202409161225.xuqvkkor-...@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/202409161225.xuqvkkor-...@intel.com/
All warnings (new ones prefixed by >>):
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.c: In
function 'dm_helpers_probe_acpi_edid':
>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.c:883:28:
>> warning: unused variable 'ddev' [-Wunused-variable]
883 | struct drm_device *ddev = connector->dev;
|^~~~
vim +/ddev +883
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_helpers.c
878
879 static int
880 dm_helpers_probe_acpi_edid(void *data, u8 *buf, unsigned int block,
size_t len)
881 {
882 struct drm_connector *connector = data;
> 883 struct drm_device *ddev = connector->dev;
884 struct acpi_device *acpidev = ACPI_COMPANION(ddev->dev);
885 unsigned char start = block * EDID_LENGTH;
886 void *edid;
887 int r;
888
889 if (!acpidev)
890 return -ENODEV;
891
892 /* fetch the entire edid from BIOS */
893 r = acpi_video_get_edid(acpidev, ACPI_VIDEO_DISPLAY_LCD, -1,
&edid);
894 if (r < 0) {
895 DRM_DEBUG_KMS("Failed to get EDID from ACPI: %d\n", r);
896 return r;
897 }
898 if (len > r || start > r || start + len > r) {
899 r = -EINVAL;
900 goto cleanup;
901 }
902
903 memcpy(buf, edid + start, len);
904 r = 0;
905
906 cleanup:
907 kfree(edid);
908
909 return r;
910 }
911
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 1/5] drm/panthor: introduce job cycle and timestamp accounting
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-20240913] [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/20240913-205038 base: linus/master patch link: https://lore.kernel.org/r/20240913124857.389630-2-adrian.larumbe%40collabora.com patch subject: [PATCH v6 1/5] drm/panthor: introduce job cycle and timestamp accounting config: i386-buildonly-randconfig-002-20240915 (https://download.01.org/0day-ci/archive/20240916/202409160050.m7ved3py-...@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/20240916/202409160050.m7ved3py-...@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/202409160050.m7ved3py-...@intel.com/ All errors (new ones prefixed by >>): >> ld.lld: error: call to __compiletime_assert_341 marked "dontcall-error": >> min(ringbuf_size - start, size) signedness error -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 1/5] drm/panthor: introduce job cycle and timestamp accounting
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-rc7 next-20240913]
[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/20240913-205038
base: linus/master
patch link:
https://lore.kernel.org/r/20240913124857.389630-2-adrian.larumbe%40collabora.com
patch subject: [PATCH v6 1/5] drm/panthor: introduce job cycle and timestamp
accounting
config: i386-buildonly-randconfig-003-20240915
(https://download.01.org/0day-ci/archive/20240915/202409152243.r3t2jdoj-...@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/20240915/202409152243.r3t2jdoj-...@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/202409152243.r3t2jdoj-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/panthor/panthor_sched.c:2885:12: error: call to
>> '__compiletime_assert_371' declared with 'error' attribute: min(ringbuf_size
>> - start, size) signedness error
2885 | written = min(ringbuf_size - start, size);
| ^
include/linux/minmax.h:129:19: note: expanded from macro 'min'
129 | #define min(x, y) __careful_cmp(min, x, y)
| ^
include/linux/minmax.h:105:2: note: expanded from macro '__careful_cmp'
105 | __careful_cmp_once(op, x, y, __UNIQUE_ID(x_),
__UNIQUE_ID(y_))
| ^
include/linux/minmax.h:100:2: note: expanded from macro '__careful_cmp_once'
100 | BUILD_BUG_ON_MSG(!__types_ok(x,y,ux,uy),\
| ^
note: (skipping 2 expansions in backtrace; use -fmacro-backtrace-limit=0 to
see all)
include/linux/compiler_types.h:498:2: note: expanded from macro
'_compiletime_assert'
498 | __compiletime_assert(condition, msg, prefix, suffix)
| ^
include/linux/compiler_types.h:491:4: note: expanded from macro
'__compiletime_assert'
491 | prefix ## suffix();
\
| ^
:68:1: note: expanded from here
68 | __compiletime_assert_371
| ^
1 error generated.
vim +2885 drivers/gpu/drm/panthor/panthor_sched.c
2862
2863 #define JOB_INSTR(__prof, __instr) \
2864 { \
2865 .profile_mask = __prof, \
2866 .instr = __instr, \
2867 }
2868
2869 static void
2870 copy_instrs_to_ringbuf(struct panthor_queue *queue,
2871 struct panthor_job *job,
2872 struct panthor_job_ringbuf_instrs *instrs)
2873 {
2874 ssize_t ringbuf_size = panthor_kernel_bo_size(queue->ringbuf);
2875 u32 start = job->ringbuf.start & (ringbuf_size - 1);
2876 ssize_t size, written;
2877
2878 /*
2879 * We need to write a whole slot, including any trailing zeroes
2880 * that may come at the end of it. Also, because instrs.buffer
has
2881 * been zero-initialised, there's no need to pad it with 0's
2882 */
2883 instrs->count = ALIGN(instrs->count, NUM_INSTRS_PER_CACHE_LINE);
2884 size = instrs->count * sizeof(u64);
> 2885 written = min(ringbuf_size - start, size);
2886
2887 memcpy(queue->ringbuf->kmap + start, instrs->buffer, written);
2888
2889 if (written < size)
2890 memcpy(queue->ringbuf->kmap,
2891 &instrs->buffer[(ringbuf_size -
start)/sizeof(u64)],
2892 size - written);
2893 }
2894
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 01/10] drm/amd/display: switch amdgpu_dm_connector to use struct drm_edid
Hi Mario,
kernel test robot noticed the following build warnings:
[auto build test WARNING on amd-pstate/linux-next]
[also build test WARNING on amd-pstate/bleeding-edge linus/master v6.11-rc7
next-20240913]
[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/Mario-Limonciello/drm-amd-display-switch-amdgpu_dm_connector-to-use-struct-drm_edid/20240912-093827
base: https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git
linux-next
patch link:
https://lore.kernel.org/r/20240911213537.2338164-2-superm1%40kernel.org
patch subject: [PATCH v6 01/10] drm/amd/display: switch amdgpu_dm_connector to
use struct drm_edid
config: alpha-allyesconfig
(https://download.01.org/0day-ci/archive/20240915/202409151547.hcdvok5l-...@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/20240915/202409151547.hcdvok5l-...@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/202409151547.hcdvok5l-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:11976: warning:
>> Function parameter or struct member 'drm_edid' not described in
>> 'amdgpu_dm_update_freesync_caps'
>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:11976: warning:
>> Excess function parameter 'edid' description in
>> 'amdgpu_dm_update_freesync_caps'
vim +11976 drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c
f9b4f20c4777bd Stylon Wang 2020-12-04 11962
c620e79bb695b8 Rodrigo Siqueira 2022-02-21 11963 /**
c620e79bb695b8 Rodrigo Siqueira 2022-02-21 11964 *
amdgpu_dm_update_freesync_caps - Update Freesync capabilities
c620e79bb695b8 Rodrigo Siqueira 2022-02-21 11965 *
41ee1f18ef5239 Alex Deucher 2022-08-30 11966 * @connector: Connector
to query.
41ee1f18ef5239 Alex Deucher 2022-08-30 11967 * @edid: EDID from
monitor
c620e79bb695b8 Rodrigo Siqueira 2022-02-21 11968 *
c620e79bb695b8 Rodrigo Siqueira 2022-02-21 11969 * Amdgpu supports
Freesync in DP and HDMI displays, and it is required to keep
c620e79bb695b8 Rodrigo Siqueira 2022-02-21 11970 * track of some of the
display information in the internal data struct used by
c620e79bb695b8 Rodrigo Siqueira 2022-02-21 11971 * amdgpu_dm. This
function checks which type of connector we need to set the
c620e79bb695b8 Rodrigo Siqueira 2022-02-21 11972 * FreeSync parameters.
c620e79bb695b8 Rodrigo Siqueira 2022-02-21 11973 */
98e6436d3af5fe Anthony Koo 2018-08-21 11974 void
amdgpu_dm_update_freesync_caps(struct drm_connector *connector,
c8133532d2e08c Melissa Wen 2024-09-11 11975
const struct drm_edid *drm_edid)
e7b07ceef2a650 Harry Wentland 2017-08-10 @11976 {
eb0709ba077a21 Souptick Joarder 2021-02-23 11977 int i = 0;
c8133532d2e08c Melissa Wen 2024-09-11 11978 const struct
detailed_timing *timing;
c8133532d2e08c Melissa Wen 2024-09-11 11979 const struct
detailed_non_pixel *data;
c8133532d2e08c Melissa Wen 2024-09-11 11980 const struct
detailed_data_monitor_range *range;
c84dec2fe8837f Harry Wentland 2017-09-05 11981 struct
amdgpu_dm_connector *amdgpu_dm_connector =
c84dec2fe8837f Harry Wentland 2017-09-05 11982
to_amdgpu_dm_connector(connector);
bb47de73666188 Nicholas Kazlauskas 2018-10-04 11983 struct
dm_connector_state *dm_con_state = NULL;
9ad544670514e2 Colin Ian King 2021-08-29 11984 struct dc_sink *sink;
534eee82356c22 Srinivasan Shanmugam 2023-11-12 11985 struct amdgpu_device
*adev = drm_to_adev(connector->dev);
f9b4f20c4777bd Stylon Wang 2020-12-04 11986 struct
amdgpu_hdmi_vsdb_info vsdb_info = {0};
c8133532d2e08c Melissa Wen 2024-09-11 11987 const struct edid *edid;
c620e79bb695b8 Rodrigo Siqueira 2022-02-21 11988 bool freesync_capable =
false;
5b49da02ddbe1b Sung Joon Kim2023-01-12 11989 enum adaptive_sync_type
as_type = ADAPTIVE_SYNC_TYPE_NONE;
b830ebc910f641 Harry Wentland 2017-07-26 11990
8218d7f1f70179 Harry Wentland 2017-10-17 11991 if (!connector->state) {
8218d7f1f70179 Harry Wentland 2017-10-17 11992 DRM_ERROR("%s -
Connector has no state", __func__);
bb47de73666188 Nicholas Kazlauskas 2018-10-04 11993 goto update;
8218d7f1f70179 Harry Wentland 2017-10-17 11994 }
8
Re: [PATCH v3] firmware: coreboot: Don't register a pdev if screen_info data is present
Hi Javier, kernel test robot noticed the following build errors: [auto build test ERROR on chrome-platform/for-next] [also build test ERROR on chrome-platform/for-firmware-next linus/master v6.11-rc7 next-20240913] [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/Javier-Martinez-Canillas/firmware-coreboot-Don-t-register-a-pdev-if-screen_info-data-is-present/20240914-053323 base: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next patch link: https://lore.kernel.org/r/20240913213246.1549213-1-javierm%40redhat.com patch subject: [PATCH v3] firmware: coreboot: Don't register a pdev if screen_info data is present config: riscv-randconfig-001-20240915 (https://download.01.org/0day-ci/archive/20240915/202409151528.ciwzrpbq-...@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/20240915/202409151528.ciwzrpbq-...@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/202409151528.ciwzrpbq-...@intel.com/ All errors (new ones prefixed by >>): >> ld.lld: error: undefined symbol: screen_info >>> referenced by framebuffer-coreboot.c:27 (drivers/firmware/google/framebuffer-coreboot.c:27) >>> drivers/firmware/google/framebuffer-coreboot.o:(framebuffer_probe) in archive vmlinux.a >>> referenced by framebuffer-coreboot.c:27 (drivers/firmware/google/framebuffer-coreboot.c:27) >>> drivers/firmware/google/framebuffer-coreboot.o:(framebuffer_probe) in archive vmlinux.a -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3] firmware: coreboot: Don't register a pdev if screen_info data is present
Hi Javier, kernel test robot noticed the following build errors: [auto build test ERROR on chrome-platform/for-next] [also build test ERROR on chrome-platform/for-firmware-next linus/master v6.11-rc7 next-20240913] [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/Javier-Martinez-Canillas/firmware-coreboot-Don-t-register-a-pdev-if-screen_info-data-is-present/20240914-053323 base: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next patch link: https://lore.kernel.org/r/20240913213246.1549213-1-javierm%40redhat.com patch subject: [PATCH v3] firmware: coreboot: Don't register a pdev if screen_info data is present config: csky-randconfig-002-20240915 (https://download.01.org/0day-ci/archive/20240915/202409150915.n7egvnya-...@intel.com/config) compiler: csky-linux-gcc (GCC) 14.1.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240915/202409150915.n7egvnya-...@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/202409150915.n7egvnya-...@intel.com/ All errors (new ones prefixed by >>, old ones prefixed by <<): WARNING: modpost: missing MODULE_DESCRIPTION() in kernel/locking/test-ww_mutex.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/usb/serial/usb_debug.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/usb/serial/mxuport.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/usb/serial/symbolserial.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/devfreq/governor_simpleondemand.o >> ERROR: modpost: "screen_info" >> [drivers/firmware/google/framebuffer-coreboot.ko] undefined! -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH V3 06/11] accel/amdxdna: Add GEM buffer object management
Hi Lizhi,
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-rc7 next-20240913]
[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/Lizhi-Hou/accel-amdxdna-Add-documentation-for-AMD-NPU-accelerator-driver/20240912-020807
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240911180604.1834434-7-lizhi.hou%40amd.com
patch subject: [PATCH V3 06/11] accel/amdxdna: Add GEM buffer object management
config: x86_64-allyesconfig
(https://download.01.org/0day-ci/archive/20240914/202409142134.bxn16uqn-...@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/20240914/202409142134.bxn16uqn-...@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/202409142134.bxn16uqn-...@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/accel/amdxdna/aie2_ctx.c:13:
>> drivers/accel/amdxdna/amdxdna_ctx.h:16:26: error: use of undeclared
>> identifier 'count'
16 | u32 data[] __counted_by(count);
| ^
1 error generated.
--
In file included from drivers/accel/amdxdna/aie2_pci.c:16:
>> drivers/accel/amdxdna/amdxdna_ctx.h:16:26: error: use of undeclared
>> identifier 'count'
16 | u32 data[] __counted_by(count);
| ^
drivers/accel/amdxdna/aie2_pci.c:406:46: warning: shift count >= width of
type [-Wshift-count-overflow]
406 | ret = dma_set_mask_and_coherent(&pdev->dev,
DMA_BIT_MASK(64));
| ^~~~
include/linux/dma-mapping.h:77:54: note: expanded from macro 'DMA_BIT_MASK'
77 | #define DMA_BIT_MASK(n) (((n) == 64) ? ~0ULL : ((1ULL<<(n))-1))
| ^ ~~~
1 warning and 1 error generated.
vim +/count +16 drivers/accel/amdxdna/amdxdna_ctx.h
8
9 /* Exec buffer command header format */
10 #define AMDXDNA_CMD_STATE GENMASK(3, 0)
11 #define AMDXDNA_CMD_EXTRA_CU_MASK GENMASK(11, 10)
12 #define AMDXDNA_CMD_COUNT GENMASK(22, 12)
13 #define AMDXDNA_CMD_OPCODE GENMASK(27, 23)
14 struct amdxdna_cmd {
15 u32 header;
> 16 u32 data[] __counted_by(count);
17 };
18
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v4 03/27] gcc-sdm845: Add general purpose clock ops
Hi Dzmitry,
kernel test robot noticed the following build errors:
[auto build test ERROR on 5acd9952f95fb4b7da6d09a3be39195a80845eb6]
url:
https://github.com/intel-lab-lkp/linux/commits/Dzmitry-Sankouski/power-supply-add-undervoltage-health-status-property/20240913-231027
base: 5acd9952f95fb4b7da6d09a3be39195a80845eb6
patch link:
https://lore.kernel.org/r/20240913-starqltechn_integration_upstream-v4-3-2d2efd5c5877%40gmail.com
patch subject: [PATCH v4 03/27] gcc-sdm845: Add general purpose clock ops
config: arm-randconfig-001-20240914
(https://download.01.org/0day-ci/archive/20240914/202409141429.wv6wjpeq-...@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/20240914/202409141429.wv6wjpeq-...@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/202409141429.wv6wjpeq-...@intel.com/
All errors (new ones prefixed by >>):
arm-linux-gnueabi-ld: drivers/clk/qcom/clk-rcg2.o: in function
`clk_rcg2_calc_mnd':
>> drivers/clk/qcom/clk-rcg2.c:437:(.text.clk_rcg2_calc_mnd+0x26): undefined
>> reference to `__aeabi_uldivmod'
>> arm-linux-gnueabi-ld:
>> drivers/clk/qcom/clk-rcg2.c:438:(.text.clk_rcg2_calc_mnd+0x38): undefined
>> reference to `__aeabi_uldivmod'
vim +437 drivers/clk/qcom/clk-rcg2.c
427
428 static void clk_rcg2_calc_mnd(u64 parent_rate, u64 rate, struct
freq_tbl *f,
429 unsigned int mnd_max, unsigned int hid_max)
430 {
431 int i = 2, count = 0;
432 unsigned int pre_div_pure = 1;
433 unsigned long rates_gcd, scaled_parent_rate;
434 u16 m, n = 1, n_candidate = 1, n_max;
435
436 rates_gcd = gcd(parent_rate, rate);
> 437 m = rate / rates_gcd;
> 438 scaled_parent_rate = parent_rate / rates_gcd;
439 while (scaled_parent_rate > (mnd_max + m) * hid_max) {
440 // we're exceeding divisor's range, trying lower scale.
441 if (m > 1) {
442 m--;
443 scaled_parent_rate =
mult_frac(scaled_parent_rate, m, (m + 1));
444 } else {
445 f->n = mnd_max + m;
446 f->pre_div = hid_max;
447 f->m = m;
448 }
449 }
450
451 n_max = m + mnd_max;
452
453 while (scaled_parent_rate > 1) {
454 while (scaled_parent_rate % i == 0) {
455 n_candidate *= i;
456 if (n_candidate < n_max)
457 n = n_candidate;
458 else if (pre_div_pure * i < hid_max)
459 pre_div_pure *= i;
460 else
461 clk_rcg2_split_div(i, &pre_div_pure,
&n, hid_max);
462
463 scaled_parent_rate /= i;
464 }
465 i++;
466 count++;
467 }
468
469 f->m = m;
470 f->n = n;
471 f->pre_div = pre_div_pure > 1 ? pre_div_pure : 0;
472 }
473
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v4 11/27] power: supply: max77705: Add charger driver for Maxim 77705
Hi Dzmitry,
kernel test robot noticed the following build errors:
[auto build test ERROR on 5acd9952f95fb4b7da6d09a3be39195a80845eb6]
url:
https://github.com/intel-lab-lkp/linux/commits/Dzmitry-Sankouski/power-supply-add-undervoltage-health-status-property/20240913-231027
base: 5acd9952f95fb4b7da6d09a3be39195a80845eb6
patch link:
https://lore.kernel.org/r/20240913-starqltechn_integration_upstream-v4-11-2d2efd5c5877%40gmail.com
patch subject: [PATCH v4 11/27] power: supply: max77705: Add charger driver for
Maxim 77705
config: sh-allmodconfig
(https://download.01.org/0day-ci/archive/20240914/202409141322.ptabmnj9-...@intel.com/config)
compiler: sh4-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240914/202409141322.ptabmnj9-...@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/202409141322.ptabmnj9-...@intel.com/
All errors (new ones prefixed by >>):
drivers/power/supply/max77705_charger.c: In function
'max77705_charger_probe':
>> drivers/power/supply/max77705_charger.c:523:48: error: assignment of member
>> 'irq_drv_data' in read-only object
523 | max77705_charger_irq_chip.irq_drv_data = chg;
|^
vim +/irq_drv_data +523 drivers/power/supply/max77705_charger.c
497
498 static int max77705_charger_probe(struct platform_device *pdev)
499 {
500 struct power_supply_config pscfg = {};
501 struct max77693_dev *max77705;
502 struct max77705_charger_data *chg;
503 struct device *dev, *parent;
504 struct regmap_irq_chip_data *irq_data;
505 int ret;
506
507 dev = &pdev->dev;
508 parent = dev->parent;
509 max77705 = dev_get_drvdata(parent);
510
511 chg = devm_kzalloc(dev, sizeof(*chg), GFP_KERNEL);
512 if (!chg)
513 return -ENOMEM;
514
515 platform_set_drvdata(pdev, chg);
516
517 chg->regmap = max77705->regmap_chg;
518 if (!chg->regmap)
519 return -ENODEV;
520
521 chg->dev = dev;
522
> 523 max77705_charger_irq_chip.irq_drv_data = chg;
524 ret = devm_regmap_add_irq_chip(chg->dev, chg->regmap,
max77705->irq,
525 IRQF_ONESHOT | IRQF_SHARED, 0,
526 &max77705_charger_irq_chip,
527 &irq_data);
528 if (ret) {
529 dev_err(dev, "failed to add irq chip: %d\n", ret);
530 return ret;
531 }
532
533 ret = regmap_update_bits(chg->regmap,
534 MAX77705_CHG_REG_INT_MASK,
535 MAX77705_CHGIN_IM, 0);
536
537 if (ret)
538 return ret;
539
540 chg->wqueue = create_singlethread_workqueue(dev_name(dev));
541 if (IS_ERR(chg->wqueue)) {
542 dev_err(dev, "failed to create workqueue\n");
543 return PTR_ERR(chg->wqueue);
544 }
545 INIT_WORK(&chg->chgin_work, max77705_chgin_isr_work);
546
547 pscfg.of_node = dev->of_node;
548 pscfg.drv_data = chg;
549
550 chg->psy_chg = devm_power_supply_register(dev,
&max77705_charger_psy_desc,
551&pscfg);
552 if (IS_ERR(chg->psy_chg))
553 return PTR_ERR(chg->psy_chg);
554
555 max77705_charger_initialize(chg);
556
557 return max77705_charger_enable(chg);
558 }
559
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v4 03/27] gcc-sdm845: Add general purpose clock ops
Hi Dzmitry,
kernel test robot noticed the following build errors:
[auto build test ERROR on 5acd9952f95fb4b7da6d09a3be39195a80845eb6]
url:
https://github.com/intel-lab-lkp/linux/commits/Dzmitry-Sankouski/power-supply-add-undervoltage-health-status-property/20240913-231027
base: 5acd9952f95fb4b7da6d09a3be39195a80845eb6
patch link:
https://lore.kernel.org/r/20240913-starqltechn_integration_upstream-v4-3-2d2efd5c5877%40gmail.com
patch subject: [PATCH v4 03/27] gcc-sdm845: Add general purpose clock ops
config: i386-buildonly-randconfig-004-20240914
(https://download.01.org/0day-ci/archive/20240914/202409141246.h3882zgf-...@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/20240914/202409141246.h3882zgf-...@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/202409141246.h3882zgf-...@intel.com/
All error/warnings (new ones prefixed by >>):
>> drivers/clk/qcom/gcc-sdm845.c:291:9: warning: braces around scalar
>> initializer
291 | .freq_tbl = {},
| ^
drivers/clk/qcom/gcc-sdm845.c:291:9: note: (near initialization for
'gcc_gp1_clk_src..freq_tbl')
>> drivers/clk/qcom/gcc-sdm845.c:291:21: error: empty scalar initializer
291 | .freq_tbl = {},
| ^
drivers/clk/qcom/gcc-sdm845.c:291:21: note: (near initialization for
'gcc_gp1_clk_src..freq_tbl')
drivers/clk/qcom/gcc-sdm845.c:305:9: warning: braces around scalar
initializer
305 | .freq_tbl = {},
| ^
drivers/clk/qcom/gcc-sdm845.c:305:9: note: (near initialization for
'gcc_gp2_clk_src..freq_tbl')
drivers/clk/qcom/gcc-sdm845.c:305:21: error: empty scalar initializer
305 | .freq_tbl = {},
| ^
drivers/clk/qcom/gcc-sdm845.c:305:21: note: (near initialization for
'gcc_gp2_clk_src..freq_tbl')
drivers/clk/qcom/gcc-sdm845.c:319:9: warning: braces around scalar
initializer
319 | .freq_tbl = {},
| ^
drivers/clk/qcom/gcc-sdm845.c:319:9: note: (near initialization for
'gcc_gp3_clk_src..freq_tbl')
drivers/clk/qcom/gcc-sdm845.c:319:21: error: empty scalar initializer
319 | .freq_tbl = {},
| ^
drivers/clk/qcom/gcc-sdm845.c:319:21: note: (near initialization for
'gcc_gp3_clk_src..freq_tbl')
vim +291 drivers/clk/qcom/gcc-sdm845.c
285
286 static struct clk_rcg2 gcc_gp1_clk_src = {
287 .cmd_rcgr = 0x64004,
288 .mnd_width = 8,
289 .hid_width = 5,
290 .parent_map = gcc_parent_map_1,
> 291 .freq_tbl = {},
292 .clkr.hw.init = &(struct clk_init_data){
293 .name = "gcc_gp1_clk_src",
294 .parent_data = gcc_parent_data_1,
295 .num_parents = ARRAY_SIZE(gcc_parent_data_1),
296 .ops = &clk_rcg2_gp_ops,
297 },
298 };
299
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/3] drm: add DRM_SET_NAME ioctl
Hi Pierre-Eric,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-exynos/exynos-drm-next]
[also build test WARNING on drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip
linus/master v6.11-rc7 next-20240913]
[cannot apply to drm/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/Pierre-Eric-Pelloux-Prayer/drm-use-drm_file-name-in-fdinfo/20240911-230058
base: https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git
exynos-drm-next
patch link:
https://lore.kernel.org/r/20240911145836.734080-1-pierre-eric.pelloux-prayer%40amd.com
patch subject: [PATCH 1/3] drm: add DRM_SET_NAME ioctl
config: x86_64-randconfig-121-20240913
(https://download.01.org/0day-ci/archive/20240914/202409140642.zdkf0cja-...@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/20240914/202409140642.zdkf0cja-...@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/202409140642.zdkf0cja-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/drm_ioctl.c:553:18: sparse: sparse: incorrect type in
>> assignment (different address spaces) @@ expected void *user_ptr @@
>> got void [noderef] __user * @@
drivers/gpu/drm/drm_ioctl.c:553:18: sparse: expected void *user_ptr
drivers/gpu/drm/drm_ioctl.c:553:18: sparse: got void [noderef] __user *
>> drivers/gpu/drm/drm_ioctl.c:555:36: sparse: sparse: incorrect type in
>> argument 1 (different address spaces) @@ expected void const [noderef]
>> __user * @@ got void *user_ptr @@
drivers/gpu/drm/drm_ioctl.c:555:36: sparse: expected void const
[noderef] __user *
drivers/gpu/drm/drm_ioctl.c:555:36: sparse: got void *user_ptr
vim +553 drivers/gpu/drm/drm_ioctl.c
542
543 static int drm_set_name(struct drm_device *dev, void *data,
544 struct drm_file *file_priv)
545 {
546 struct drm_set_name *name = data;
547 void *user_ptr;
548 char *new_name;
549
550 if (name->name_len >= NAME_MAX)
551 return -EINVAL;
552
> 553 user_ptr = u64_to_user_ptr(name->name);
554
> 555 new_name = memdup_user_nul(user_ptr, name->name_len);
556
557 if (IS_ERR(new_name))
558 return PTR_ERR(new_name);
559
560 mutex_lock(&file_priv->name_lock);
561 if (file_priv->name)
562 kvfree(file_priv->name);
563 file_priv->name = new_name;
564 mutex_unlock(&file_priv->name_lock);
565
566 return 0;
567 }
568
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 1/5] drm/panthor: introduce job cycle and timestamp accounting
Hi Adrián, kernel test robot noticed the following build warnings: [auto build test WARNING on linus/master] [also build test WARNING on v6.11-rc7 next-20240913] [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/20240913-205038 base: linus/master patch link: https://lore.kernel.org/r/20240913124857.389630-2-adrian.larumbe%40collabora.com patch subject: [PATCH v6 1/5] drm/panthor: introduce job cycle and timestamp accounting config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20240914/202409140506.oboqsivk-...@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/20240914/202409140506.oboqsivk-...@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/202409140506.oboqsivk-...@intel.com/ All warnings (new ones prefixed by >>): drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'runnable' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'idle' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'waiting' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'has_ref' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'in_progress' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'stopped_groups' description in 'panthor_scheduler' >> drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Function parameter or >> struct member 'profiling' not described in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'mem' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'input' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'output' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'input_fw_va' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'output_fw_va' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'gpu_va' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'ref' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'gt' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'sync64' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'bo' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'offset' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'kmap' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'lock' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'id' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'seqno' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'last_fence' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'in_flight_jobs' description in 'panthor_queue' >> drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member >> 'profiling_info' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: E
Re: [PATCH 3/3] drm/amdgpu: use drm_file name
Hi Pierre-Eric,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-exynos/exynos-drm-next]
[also build test WARNING on drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip
linus/master v6.11-rc7 next-20240912]
[cannot apply to drm/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/Pierre-Eric-Pelloux-Prayer/drm-use-drm_file-name-in-fdinfo/20240911-230058
base: https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git
exynos-drm-next
patch link:
https://lore.kernel.org/r/20240911145836.734080-3-pierre-eric.pelloux-prayer%40amd.com
patch subject: [PATCH 3/3] drm/amdgpu: use drm_file name
config: x86_64-allyesconfig
(https://download.01.org/0day-ci/archive/20240913/202409130526.fve4aems-...@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/20240913/202409130526.fve4aems-...@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/202409130526.fve4aems-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c:2374: warning: Function parameter or
>> struct member 'file' not described in 'amdgpu_vm_set_task_info'
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c:2801: warning: Function parameter or
struct member 'ts' not described in 'amdgpu_vm_handle_fault'
vim +2374 drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2367
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2368 /**
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2369 *
amdgpu_vm_set_task_info - Sets VMs task info.
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2370 *
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2371 * @vm: vm for
which to set the info
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2372 */
cd1125e8edc565 Pierre-Eric Pelloux-Prayer 2024-09-11 2373 void
amdgpu_vm_set_task_info(struct amdgpu_vm *vm, struct drm_file *file)
b8f67b9ddf4f8f Shashank Sharma2024-01-18 @2374 {
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2375 if
(!vm->task_info)
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2376 return;
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2377
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2378 if
(vm->task_info->pid == current->pid)
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2379 return;
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2380
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2381
vm->task_info->pid = current->pid;
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2382
get_task_comm(vm->task_info->task_name, current);
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2383
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2384 if
(current->group_leader->mm != current->mm)
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2385 return;
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2386
b8f67b9ddf4f8f Shashank Sharma2024-01-18 2387
vm->task_info->tgid = current->group_leader->pid;
cd1125e8edc565 Pierre-Eric Pelloux-Prayer 2024-09-11 2388
__get_task_comm(vm->task_info->process_name, TASK_COMM_LEN,
cd1125e8edc565 Pierre-Eric Pelloux-Prayer 2024-09-11 2389
current->group_leader);
cd1125e8edc565 Pierre-Eric Pelloux-Prayer 2024-09-11 2390 /* Append
drm_client_name if set. */
cd1125e8edc565 Pierre-Eric Pelloux-Prayer 2024-09-11 2391 if (file &&
file->name) {
cd1125e8edc565 Pierre-Eric Pelloux-Prayer 2024-09-11 2392 int n;
cd1125e8edc565 Pierre-Eric Pelloux-Prayer 2024-09-11 2393
cd1125e8edc565 Pierre-Eric Pelloux-Prayer 2024-09-11 2394
mutex_lock(&file->name_lock);
cd1125e8edc565 Pierre-Eric Pelloux-Prayer 2024-09-11 2395 n =
strlen(vm->task_info->process_name);
cd1125e8edc565 Pierre-Eric Pelloux-Prayer 2024-09-11 2396 if (n <
NAME_MAX) {
cd1125e8edc565 Pierre-Eric Pelloux-Prayer 2024-09-11 2397
if (file->name) {
cd1125e8edc565 Pierre-Eric Pelloux-Prayer 2024-09-11 2398
vm->task_info->process_name[n] = '/';
cd1125e8edc565 Pierre-Eri
Re: [PATCH 7/7] dma-buf: rework the enable_signaling handling
Hi Christian,
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-misc/drm-misc-next drm-tip/drm-tip next-20240912]
[cannot apply to drm-intel/for-linux-next drm-intel/for-linux-next-fixes
linus/master 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/Christian-K-nig/dma-buf-sw_sync-remove-pointless-enable_signaling-implementation/20240911-175943
base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link:
https://lore.kernel.org/r/20240911085903.1496-8-christian.koenig%40amd.com
patch subject: [PATCH 7/7] dma-buf: rework the enable_signaling handling
config: loongarch-allmodconfig
(https://download.01.org/0day-ci/archive/20240913/202409130132.scyyyhqm-...@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/20240913/202409130132.scyyyhqm-...@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/202409130132.scyyyhqm-...@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/ttm/tests/ttm_bo_validate_test.c: In function
'dma_resv_kunit_active_fence_init':
>> drivers/gpu/drm/ttm/tests/ttm_bo_validate_test.c:72:9: error: implicit
>> declaration of function 'dma_fence_enable_sw_signaling'; did you mean
>> 'dma_fence_enable_signaling'? [-Wimplicit-function-declaration]
72 | dma_fence_enable_sw_signaling(fence);
| ^
| dma_fence_enable_signaling
vim +72 drivers/gpu/drm/ttm/tests/ttm_bo_validate_test.c
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 64
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 65 static void
dma_resv_kunit_active_fence_init(struct kunit *test,
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 66
struct dma_resv *resv,
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 67
enum dma_resv_usage usage)
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 68 {
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 69 struct dma_fence *fence;
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 70
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 71 fence =
alloc_mock_fence(test);
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 @72
dma_fence_enable_sw_signaling(fence);
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 73
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 74 dma_resv_lock(resv,
NULL);
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 75
dma_resv_reserve_fences(resv, 1);
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 76
dma_resv_add_fence(resv, fence, usage);
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 77 dma_resv_unlock(resv);
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 78 }
8eda41dfc9b2f0 Karolina Stolarek 2024-06-12 79
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 3/3] drm/nouveau: Add drm_panic support for nv50+
Hi Jocelyn,
kernel test robot noticed the following build warnings:
[auto build test WARNING on e8653e63e834e4c7de60b81b8b24deb7bdd3bf56]
url:
https://github.com/intel-lab-lkp/linux/commits/Jocelyn-Falempe/drm-panic-Add-ABGR2101010-support/20240906-180717
base: e8653e63e834e4c7de60b81b8b24deb7bdd3bf56
patch link:
https://lore.kernel.org/r/20240906100434.1171093-4-jfalempe%40redhat.com
patch subject: [PATCH v2 3/3] drm/nouveau: Add drm_panic support for nv50+
config: x86_64-randconfig-121-20240909
(https://download.01.org/0day-ci/archive/20240909/202409091805.3pzxoay6-...@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/20240909/202409091805.3pzxoay6-...@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/202409091805.3pzxoay6-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/nouveau/dispnv50/wndw.c:651:66: sparse: sparse: incorrect
>> type in argument 2 (different address spaces) @@ expected void [noderef]
>> __iomem *vaddr_iomem @@ got void *virtual @@
drivers/gpu/drm/nouveau/dispnv50/wndw.c:651:66: sparse: expected void
[noderef] __iomem *vaddr_iomem
drivers/gpu/drm/nouveau/dispnv50/wndw.c:651:66: sparse: got void *virtual
vim +651 drivers/gpu/drm/nouveau/dispnv50/wndw.c
628
629 static int
630 nv50_wndw_get_scanout_buffer(struct drm_plane *plane, struct
drm_scanout_buffer *sb)
631 {
632 struct drm_framebuffer *fb;
633 struct nouveau_bo *nvbo;
634
635 if (!plane->state || !plane->state->fb)
636 return -EINVAL;
637
638 fb = plane->state->fb;
639 nvbo = nouveau_gem_object(fb->obj[0]);
640
641 /* Don't support compressed format, or multiplane yet. */
642 if (nvbo->comp || fb->format->num_planes != 1)
643 return -EOPNOTSUPP;
644
645 if (nouveau_bo_map(nvbo)) {
646 pr_warn("nouveau bo map failed, panic won't be
displayed\n");
647 return -ENOMEM;
648 }
649
650 if (nvbo->kmap.bo_kmap_type & TTM_BO_MAP_IOMEM_MASK)
> 651 iosys_map_set_vaddr_iomem(&sb->map[0],
> nvbo->kmap.virtual);
652 else
653 iosys_map_set_vaddr(&sb->map[0], nvbo->kmap.virtual);
654
655 sb->height = fb->height;
656 sb->width = fb->width;
657 sb->pitch[0] = fb->pitches[0];
658 sb->format = fb->format;
659
660 /* If tiling is enabled, use the set_pixel() to display
correctly.
661 * Only handle 32bits format for now.
662 */
663 if (fb->modifier & 0xf) {
664 if (fb->format->cpp[0] != 4)
665 return -EOPNOTSUPP;
666 sb->private = (void *) fb;
667 sb->set_pixel = nv50_set_pixel;
668 }
669 return 0;
670 }
671
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3] drm/edid: add CTA Video Format Data Block support
Hi Hamza, kernel test robot noticed the following build errors: [auto build test ERROR on drm-misc/drm-misc-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-tip/drm-tip linus/master v6.11-rc7 next-20240906] [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/Hamza-Mahfooz/drm-edid-add-CTA-Video-Format-Data-Block-support/20240907-064359 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240906224307.423250-1-hamza.mahfooz%40amd.com patch subject: [PATCH v3] drm/edid: add CTA Video Format Data Block support config: arm-nhk8815_defconfig (https://download.01.org/0day-ci/archive/20240909/202409091450.s7bzv2ho-...@intel.com/config) compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 05f5a91d00b02f4369f46d076411c700755ae041) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240909/202409091450.s7bzv2ho-...@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/202409091450.s7bzv2ho-...@intel.com/ All errors (new ones prefixed by >>): >> ld.lld: error: undefined symbol: __aeabi_uldivmod >>> referenced by drm_edid.c:5470 (drivers/gpu/drm/drm_edid.c:5470) >>> drivers/gpu/drm/drm_edid.o:(_drm_edid_connector_add_modes) in archive vmlinux.a >>> referenced by drm_edid.c:5508 (drivers/gpu/drm/drm_edid.c:5508) >>> drivers/gpu/drm/drm_edid.o:(_drm_edid_connector_add_modes) in archive vmlinux.a >>> referenced by drm_edid.c:5509 (drivers/gpu/drm/drm_edid.c:5509) >>> drivers/gpu/drm/drm_edid.o:(_drm_edid_connector_add_modes) in archive vmlinux.a >>> referenced 1 more times >>> did you mean: __aeabi_uidivmod >>> defined in: vmlinux.a(arch/arm/lib/lib1funcs.o) -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3] drm/edid: add CTA Video Format Data Block support
Hi Hamza, kernel test robot noticed the following build errors: [auto build test ERROR on drm-misc/drm-misc-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-tip/drm-tip linus/master v6.11-rc7 next-20240906] [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/Hamza-Mahfooz/drm-edid-add-CTA-Video-Format-Data-Block-support/20240907-064359 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240906224307.423250-1-hamza.mahfooz%40amd.com patch subject: [PATCH v3] drm/edid: add CTA Video Format Data Block support config: parisc-defconfig (https://download.01.org/0day-ci/archive/20240909/202409091135.vfcwivxn-...@intel.com/config) compiler: hppa-linux-gcc (GCC) 14.1.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240909/202409091135.vfcwivxn-...@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/202409091135.vfcwivxn-...@intel.com/ All errors (new ones prefixed by >>, old ones prefixed by <<): WARNING: modpost: missing MODULE_DESCRIPTION() in lib/asn1_decoder.o >> ERROR: modpost: "__umoddi3" [drivers/gpu/drm/drm.ko] undefined! >> ERROR: modpost: "__udivdi3" [drivers/gpu/drm/drm.ko] undefined! -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 3/3] drm/rockchip: Add basic RK3588 HDMI output support
Hi Cristian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 8400291e289ee6b2bf9779ff1c83a291501f017b]
url:
https://github.com/intel-lab-lkp/linux/commits/Cristian-Ciocaltea/drm-bridge-synopsys-Add-DW-HDMI-QP-TX-Controller-support-library/20240906-092027
base: 8400291e289ee6b2bf9779ff1c83a291501f017b
patch link:
https://lore.kernel.org/r/20240906-b4-rk3588-bridge-upstream-v6-3-a3128fb103eb%40collabora.com
patch subject: [PATCH v6 3/3] drm/rockchip: Add basic RK3588 HDMI output support
config: powerpc64-randconfig-r122-20240908
(https://download.01.org/0day-ci/archive/20240909/202409090615.l6bkur5k-...@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project
6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce:
(https://download.01.org/0day-ci/archive/20240909/202409090615.l6bkur5k-...@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/202409090615.l6bkur5k-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/bridge/synopsys/dw-hdmi-qp.c:679:24: sparse: sparse:
>> incorrect type in return expression (different address spaces) @@
>> expected struct dw_hdmi_qp * @@ got void [noderef] __iomem *[assigned]
>> regs @@
drivers/gpu/drm/bridge/synopsys/dw-hdmi-qp.c:679:24: sparse: expected
struct dw_hdmi_qp *
drivers/gpu/drm/bridge/synopsys/dw-hdmi-qp.c:679:24: sparse: got void
[noderef] __iomem *[assigned] regs
vim +679 drivers/gpu/drm/bridge/synopsys/dw-hdmi-qp.c
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 653
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 654 struct dw_hdmi_qp
*dw_hdmi_qp_bind(struct platform_device *pdev,
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 655
struct drm_encoder *encoder,
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 656
const struct dw_hdmi_qp_plat_data *plat_data)
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 657 {
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 658 struct device *dev =
&pdev->dev;
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 659 struct dw_hdmi_qp *hdmi;
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 660 void __iomem *regs;
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 661 int ret;
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 662
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 663 if (!plat_data->phy_ops
|| !plat_data->phy_ops->init ||
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 664
!plat_data->phy_ops->disable || !plat_data->phy_ops->read_hpd) {
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 665 dev_err(dev,
"Missing platform PHY ops\n");
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 666 return
ERR_PTR(-ENODEV);
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 667 }
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 668
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 669 hdmi =
devm_kzalloc(dev, sizeof(*hdmi), GFP_KERNEL);
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 670 if (!hdmi)
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 671 return
ERR_PTR(-ENOMEM);
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 672
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 673
INIT_DELAYED_WORK(&hdmi->scramb_work, dw_hdmi_qp_scramb_work);
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 674
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 675 hdmi->dev = dev;
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 676
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 677 regs =
devm_platform_ioremap_resource(pdev, 0);
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 678 if (IS_ERR(regs))
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 @679 return regs;
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 680
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 681 hdmi->regm =
devm_regmap_init_mmio(dev, regs, &dw_hdmi_qp_regmap_config);
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 682 if (IS_ERR(hdmi->regm))
{
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 683 dev_err(dev,
"Failed to configure regmap\n");
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 684 return
ERR_CAST(hdmi->regm);
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 685 }
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 686
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 687 hdmi->phy.ops =
plat_data->phy_ops;
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 688 hdmi->phy.data =
plat_data->phy_data;
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 689
4ae2f13b217e6c Cristian Ciocaltea 2024-09-06 690
dw_hdmi_qp_init_hw(hdmi);
4ae2f13b217e6c Cristian Ciocalt
Re: [PATCH 1/1] drm/imx: Add missing DRM_BRIDGE_CONNECTOR dependency
Hi Alexander, kernel test robot noticed the following build warnings: [auto build test WARNING on next-20240905] [cannot apply to v6.11-rc6 v6.11-rc5 v6.11-rc4 linus/master v6.11-rc6] [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/Alexander-Stein/drm-imx-Add-missing-DRM_BRIDGE_CONNECTOR-dependency/20240906-144116 base: next-20240905 patch link: https://lore.kernel.org/r/20240906063857.2223442-1-alexander.stein%40ew.tq-group.com patch subject: [PATCH 1/1] drm/imx: Add missing DRM_BRIDGE_CONNECTOR dependency config: alpha-kismet-CONFIG_DRM_BRIDGE_CONNECTOR-CONFIG_DRM_IMX_PARALLEL_DISPLAY-0-0 (https://download.01.org/0day-ci/archive/20240907/202409072155.3p25zqju-...@intel.com/config) reproduce: (https://download.01.org/0day-ci/archive/20240907/202409072155.3p25zqju-...@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/202409072155.3p25zqju-...@intel.com/ kismet warnings: (new ones prefixed by >>) >> kismet: WARNING: unmet direct dependencies detected for DRM_BRIDGE_CONNECTOR >> when selected by DRM_IMX_PARALLEL_DISPLAY WARNING: unmet direct dependencies detected for DRM_BRIDGE_CONNECTOR Depends on [n]: HAS_IOMEM [=y] && DRM [=y] && DRM_DISPLAY_HELPER [=n] Selected by [y]: - DRM_IMX_PARALLEL_DISPLAY [=y] && HAS_IOMEM [=y] && DRM [=y] && DRM_IMX [=y] -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/1] drm/imx: Add missing DRM_BRIDGE_CONNECTOR dependency
Hi Alexander, kernel test robot noticed the following build warnings: [auto build test WARNING on next-20240905] [cannot apply to v6.11-rc6 v6.11-rc5 v6.11-rc4 linus/master v6.11-rc6] [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/Alexander-Stein/drm-imx-Add-missing-DRM_BRIDGE_CONNECTOR-dependency/20240906-144116 base: next-20240905 patch link: https://lore.kernel.org/r/20240906063857.2223442-1-alexander.stein%40ew.tq-group.com patch subject: [PATCH 1/1] drm/imx: Add missing DRM_BRIDGE_CONNECTOR dependency config: alpha-kismet-CONFIG_DRM_BRIDGE_CONNECTOR-CONFIG_DRM_IMX_LDB-0-0 (https://download.01.org/0day-ci/archive/20240907/202409071746.fbgs0kyw-...@intel.com/config) reproduce: (https://download.01.org/0day-ci/archive/20240907/202409071746.fbgs0kyw-...@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/202409071746.fbgs0kyw-...@intel.com/ kismet warnings: (new ones prefixed by >>) >> kismet: WARNING: unmet direct dependencies detected for DRM_BRIDGE_CONNECTOR >> when selected by DRM_IMX_LDB WARNING: unmet direct dependencies detected for DRM_BRIDGE_CONNECTOR Depends on [n]: HAS_IOMEM [=y] && DRM [=y] && DRM_DISPLAY_HELPER [=n] Selected by [y]: - DRM_IMX_LDB [=y] && HAS_IOMEM [=y] && DRM [=y] && DRM_IMX [=y] && COMMON_CLK [=y] -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/2] drm/ttm: Change ttm_device_init to use a struct instead of multiple bools
Hi Thomas,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on next-20240905]
[cannot apply to drm-xe/drm-xe-next linus/master v6.11-rc6]
[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-Hellstr-m/drm-ttm-Change-ttm_device_init-to-use-a-struct-instead-of-multiple-bools/20240905-173606
base: git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240905093322.29786-2-thomas.hellstrom%40linux.intel.com
patch subject: [PATCH 1/2] drm/ttm: Change ttm_device_init to use a struct
instead of multiple bools
config: i386-randconfig-006-20240906
(https://download.01.org/0day-ci/archive/20240906/202409061330.a2rryeml-...@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/20240906/202409061330.a2rryeml-...@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/202409061330.a2rryeml-...@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/drm_gem_vram_helper.c: In function 'drm_vram_mm_init':
>> drivers/gpu/drm/drm_gem_vram_helper.c:981:34: error: incompatible type for
>> argument 6 of 'ttm_device_init'
981 | false, true);
| ^
| |
| int
In file included from include/drm/ttm/ttm_bo.h:39,
from include/drm/drm_gem_ttm_helper.h:10,
from drivers/gpu/drm/drm_gem_vram_helper.c:13:
include/drm/ttm/ttm_device.h:303:56: note: expected 'const struct
ttm_device_init_flags' but argument is of type 'int'
303 | const struct ttm_device_init_flags flags);
| ~~~^
>> drivers/gpu/drm/drm_gem_vram_helper.c:978:15: error: too many arguments to
>> function 'ttm_device_init'
978 | ret = ttm_device_init(&vmm->bdev, &bo_driver, dev->dev,
| ^~~
include/drm/ttm/ttm_device.h:300:5: note: declared here
300 | int ttm_device_init(struct ttm_device *bdev, const struct
ttm_device_funcs *funcs,
| ^~~
vim +/ttm_device_init +981 drivers/gpu/drm/drm_gem_vram_helper.c
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 969
c30b225dba01b4 Thomas Zimmermann 2019-09-11 970 static int
drm_vram_mm_init(struct drm_vram_mm *vmm, struct drm_device *dev,
b0e40e0805221d Thomas Zimmermann 2019-09-11 971
uint64_t vram_base, size_t vram_size)
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 972 {
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 973int ret;
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 974
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 975vmm->vram_base =
vram_base;
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 976vmm->vram_size =
vram_size;
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 977
8af8a109b34fa8 Christian König 2020-10-01 @978ret =
ttm_device_init(&vmm->bdev, &bo_driver, dev->dev,
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 979
dev->anon_inode->i_mapping,
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 980
dev->vma_offset_manager,
ee5d2a8e549e90 Christian König 2020-10-24 @981
false, true);
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 982if (ret)
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 983return ret;
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 984
37205891d84f92 Dave Airlie 2020-08-04 985ret =
ttm_range_man_init(&vmm->bdev, TTM_PL_VRAM,
0fe438cec9e1d2 Christian König 2020-09-11 986
false, vram_size >> PAGE_SHIFT);
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 987if (ret)
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 988return ret;
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 989
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 990return 0;
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 991 }
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 992
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/2] drm/ttm: Change ttm_device_init to use a struct instead of multiple bools
Hi Thomas,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on next-20240905]
[cannot apply to drm-xe/drm-xe-next drm-intel/for-linux-next-fixes
drm-tip/drm-tip linus/master v6.11-rc6]
[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-Hellstr-m/drm-ttm-Change-ttm_device_init-to-use-a-struct-instead-of-multiple-bools/20240905-173606
base: git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240905093322.29786-2-thomas.hellstrom%40linux.intel.com
patch subject: [PATCH 1/2] drm/ttm: Change ttm_device_init to use a struct
instead of multiple bools
config: i386-randconfig-002-20240906
(https://download.01.org/0day-ci/archive/20240906/202409061145.atkjpwfj-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240906/202409061145.atkjpwfj-...@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/202409061145.atkjpwfj-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/drm_gem_vram_helper.c:981:13: error: too many arguments to
>> function call, expected 6, have 7
978 | ret = ttm_device_init(&vmm->bdev, &bo_driver, dev->dev,
| ~~~
979 | dev->anon_inode->i_mapping,
980 | dev->vma_offset_manager,
981 | false, true);
| ^~~~
include/drm/ttm/ttm_device.h:300:5: note: 'ttm_device_init' declared here
300 | int ttm_device_init(struct ttm_device *bdev, const struct
ttm_device_funcs *funcs,
| ^
~~
301 | struct device *dev, struct address_space
*mapping,
|
~~
302 | struct drm_vma_offset_manager *vma_manager,
| ~~~
303 | const struct ttm_device_init_flags flags);
|
1 error generated.
vim +981 drivers/gpu/drm/drm_gem_vram_helper.c
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 969
c30b225dba01b4 Thomas Zimmermann 2019-09-11 970 static int
drm_vram_mm_init(struct drm_vram_mm *vmm, struct drm_device *dev,
b0e40e0805221d Thomas Zimmermann 2019-09-11 971
uint64_t vram_base, size_t vram_size)
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 972 {
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 973int ret;
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 974
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 975vmm->vram_base =
vram_base;
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 976vmm->vram_size =
vram_size;
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 977
8af8a109b34fa8 Christian König 2020-10-01 978ret =
ttm_device_init(&vmm->bdev, &bo_driver, dev->dev,
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 979
dev->anon_inode->i_mapping,
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 980
dev->vma_offset_manager,
ee5d2a8e549e90 Christian König 2020-10-24 @981
false, true);
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 982if (ret)
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 983return ret;
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 984
37205891d84f92 Dave Airlie 2020-08-04 985ret =
ttm_range_man_init(&vmm->bdev, TTM_PL_VRAM,
0fe438cec9e1d2 Christian König 2020-09-11 986
false, vram_size >> PAGE_SHIFT);
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 987if (ret)
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 988return ret;
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 989
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 990return 0;
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 991 }
6b5ce4a1fb8489 Thomas Zimmermann 2019-09-11 992
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v5 2/4] drm/panthor: add DRM fdinfo support
Hi Adrián, 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.11-rc6 next-20240904] [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/20240904-042645 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240903202541.430225-3-adrian.larumbe%40collabora.com patch subject: [PATCH v5 2/4] drm/panthor: add DRM fdinfo support config: x86_64-buildonly-randconfig-002-20240904 (https://download.01.org/0day-ci/archive/20240905/202409050134.uxrikhqc-...@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/20240905/202409050134.uxrikhqc-...@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/202409050134.uxrikhqc-...@intel.com/ All warnings (new ones prefixed by >>): drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'runnable' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'idle' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'waiting' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'has_ref' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'in_progress' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'stopped_groups' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'mem' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'input' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'output' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'input_fw_va' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'output_fw_va' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'gpu_va' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'ref' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'gt' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'sync64' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'bo' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'offset' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'kmap' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'lock' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'id' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'seqno' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'last_fence' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'in_flight_jobs' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'slots' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'slot_count' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member
Re: [PATCH v5 1/4] drm/panthor: introduce job cycle and timestamp accounting
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.11-rc6 next-20240904] [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/20240904-042645 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240903202541.430225-2-adrian.larumbe%40collabora.com patch subject: [PATCH v5 1/4] drm/panthor: introduce job cycle and timestamp accounting config: arc-allmodconfig (https://download.01.org/0day-ci/archive/20240905/202409050054.orwtzlq4-...@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/20240905/202409050054.orwtzlq4-...@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/202409050054.orwtzlq4-...@intel.com/ All errors (new ones prefixed by >>): In file included from : In function 'copy_instrs_to_ringbuf', inlined from 'queue_run_job' at drivers/gpu/drm/panthor/panthor_sched.c:3089:2: >> include/linux/compiler_types.h:510:45: error: call to >> '__compiletime_assert_435' declared with attribute error: min(ringbuf_size - >> start, size) signedness error 510 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) | ^ include/linux/compiler_types.h:491:25: note: in definition of macro '__compiletime_assert' 491 | prefix ## suffix(); \ | ^~ include/linux/compiler_types.h:510:9: note: in expansion of macro '_compiletime_assert' 510 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) | ^~~ include/linux/build_bug.h:39:37: note: in expansion of macro 'compiletime_assert' 39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg) | ^~ include/linux/minmax.h:100:9: note: in expansion of macro 'BUILD_BUG_ON_MSG' 100 | BUILD_BUG_ON_MSG(!__types_ok(x,y,ux,uy),\ | ^~~~ include/linux/minmax.h:105:9: note: in expansion of macro '__careful_cmp_once' 105 | __careful_cmp_once(op, x, y, __UNIQUE_ID(x_), __UNIQUE_ID(y_)) | ^~ include/linux/minmax.h:129:25: note: in expansion of macro '__careful_cmp' 129 | #define min(x, y) __careful_cmp(min, x, y) | ^ drivers/gpu/drm/panthor/panthor_sched.c:2882:19: note: in expansion of macro 'min' 2882 | written = min(ringbuf_size - start, size); | ^~~ vim +/__compiletime_assert_435 +510 include/linux/compiler_types.h eb5c2d4b45e3d2 Will Deacon 2020-07-21 496 eb5c2d4b45e3d2 Will Deacon 2020-07-21 497 #define _compiletime_assert(condition, msg, prefix, suffix) \ eb5c2d4b45e3d2 Will Deacon 2020-07-21 498 __compiletime_assert(condition, msg, prefix, suffix) eb5c2d4b45e3d2 Will Deacon 2020-07-21 499 eb5c2d4b45e3d2 Will Deacon 2020-07-21 500 /** eb5c2d4b45e3d2 Will Deacon 2020-07-21 501 * compiletime_assert - break build and emit msg if condition is false eb5c2d4b45e3d2 Will Deacon 2020-07-21 502 * @condition: a compile-time constant condition to check eb5c2d4b45e3d2 Will Deacon 2020-07-21 503 * @msg: a message to emit if condition is false eb5c2d4b45e3d2 Will Deacon 2020-07-21 504 * eb5c2d4b45e3d2 Will Deacon 2020-07-21 505 * In tradition of POSIX assert, this macro will break the build if the eb5c2d4b45e3d2 Will Deacon 2020-07-21 506 * supplied condition is *false*, emitting the supplied error message if the eb5c2d4b45e3d2 Will Deacon 2020-07-21 507 * compiler has support to do so. eb5c2d4b45e3d2 Will Deacon 2020-07-21 508 */ eb5c2d4b45e3d2 Will Deacon 2020-07-21 509 #define compiletime_assert(condition, msg) \ eb5c2d4b45e3d2 Will Deacon 2020-07-21 @510 _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) eb5c2d4b45e3d2 Will Deacon 2020-07-21 511 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v5 1/4] drm/panthor: introduce job cycle and timestamp accounting
Hi Adrián, 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.11-rc6 next-20240904] [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/20240904-042645 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240903202541.430225-2-adrian.larumbe%40collabora.com patch subject: [PATCH v5 1/4] drm/panthor: introduce job cycle and timestamp accounting config: x86_64-buildonly-randconfig-002-20240904 (https://download.01.org/0day-ci/archive/20240904/202409042317.crcmb6bs-...@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/20240904/202409042317.crcmb6bs-...@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/202409042317.crcmb6bs-...@intel.com/ All warnings (new ones prefixed by >>): drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'runnable' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'idle' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'waiting' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'has_ref' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'in_progress' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:322: warning: Excess struct member 'stopped_groups' description in 'panthor_scheduler' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'mem' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'input' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'output' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'input_fw_va' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'output_fw_va' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'gpu_va' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'ref' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'gt' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'sync64' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'bo' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'offset' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'kmap' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'lock' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'id' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'seqno' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'last_fence' description in 'panthor_queue' drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member 'in_flight_jobs' description in 'panthor_queue' >> drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member >> 'slots' description in 'panthor_queue' >> drivers/gpu/drm/panthor/panthor_sched.c:494: warning: Excess struct member >> 'slot_count' description in 'panthor_queue' >> drivers/gpu/drm/panth
Re: [PATCH] drm/panel: hx83112a: Switch to wrapped mipi_dsi functions
Hi Abhishek,
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.11-rc6 next-20240903]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Abhishek-Tamboli/drm-panel-hx83112a-Switch-to-wrapped-mipi_dsi-functions/20240903-010317
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240902170153.34512-1-abhishektamboli9%40gmail.com
patch subject: [PATCH] drm/panel: hx83112a: Switch to wrapped mipi_dsi functions
config: x86_64-randconfig-005-20240903
(https://download.01.org/0day-ci/archive/20240904/202409040049.2hf8jrzg-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240904/202409040049.2hf8jrzg-...@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/202409040049.2hf8jrzg-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/panel/panel-himax-hx83112a.c:63:2: error: use of undeclared
>> identifier 'dsi'
63 | dsi->mode_flags |= MIPI_DSI_MODE_LPM;
| ^
drivers/gpu/drm/panel/panel-himax-hx83112a.c:197:2: error: use of undeclared
identifier 'dsi'
197 | dsi->mode_flags &= ~MIPI_DSI_MODE_LPM;
| ^
2 errors generated.
vim +/dsi +63 drivers/gpu/drm/panel/panel-himax-hx83112a.c
654f26a0f43cfd3 Luca Weiss 2024-02-16 58
654f26a0f43cfd3 Luca Weiss 2024-02-16 59 static int hx83112a_on(struct
hx83112a_panel *ctx)
654f26a0f43cfd3 Luca Weiss 2024-02-16 60 {
a76c4f29a2e42d1 Abhishek Tamboli 2024-09-02 61struct
mipi_dsi_multi_context dsi_ctx = {.dsi = ctx->dsi};
654f26a0f43cfd3 Luca Weiss 2024-02-16 62
654f26a0f43cfd3 Luca Weiss 2024-02-16 @63dsi->mode_flags |=
MIPI_DSI_MODE_LPM;
654f26a0f43cfd3 Luca Weiss 2024-02-16 64
a76c4f29a2e42d1 Abhishek Tamboli 2024-09-02 65
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETEXTC, 0x83, 0x11, 0x2a);
a76c4f29a2e42d1 Abhishek Tamboli 2024-09-02 66
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETPOWER1,
654f26a0f43cfd3 Luca Weiss 2024-02-16 67
0x08, 0x28, 0x28, 0x83, 0x83, 0x4c, 0x4f, 0x33);
a76c4f29a2e42d1 Abhishek Tamboli 2024-09-02 68
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETDISP,
654f26a0f43cfd3 Luca Weiss 2024-02-16 69
0x00, 0x02, 0x00, 0x90, 0x24, 0x00, 0x08, 0x19,
654f26a0f43cfd3 Luca Weiss 2024-02-16 70
0xea, 0x11, 0x11, 0x00, 0x11, 0xa3);
a76c4f29a2e42d1 Abhishek Tamboli 2024-09-02 71
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETDRV,
654f26a0f43cfd3 Luca Weiss 2024-02-16 72
0x58, 0x68, 0x58, 0x68, 0x0f, 0xef, 0x0b, 0xc0,
654f26a0f43cfd3 Luca Weiss 2024-02-16 73
0x0b, 0xc0, 0x0b, 0xc0, 0x00, 0xff, 0x00, 0xff,
654f26a0f43cfd3 Luca Weiss 2024-02-16 74
0x00, 0x00, 0x14, 0x15, 0x00, 0x29, 0x11, 0x07,
654f26a0f43cfd3 Luca Weiss 2024-02-16 75
0x12, 0x00, 0x29);
a76c4f29a2e42d1 Abhishek Tamboli 2024-09-02 76
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETBANK, 0x02);
a76c4f29a2e42d1 Abhishek Tamboli 2024-09-02 77
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETDRV,
654f26a0f43cfd3 Luca Weiss 2024-02-16 78
0x00, 0x12, 0x12, 0x11, 0x88, 0x12, 0x12, 0x00,
654f26a0f43cfd3 Luca Weiss 2024-02-16 79
0x53);
a76c4f29a2e42d1 Abhishek Tamboli 2024-09-02 80
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETBANK, 0x00);
a76c4f29a2e42d1 Abhishek Tamboli 2024-09-02 81
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETBANK, 0x03);
a76c4f29a2e42d1 Abhishek Tamboli 2024-09-02 82
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETDGCLUT,
654f26a0f43cfd3 Luca Weiss 2024-02-16 83
0xff, 0xfe, 0xfb, 0xf8, 0xf4, 0xf1, 0xed, 0xe6,
654f26a0f43cfd3 Luca Weiss 2024-02-16 84
0xe2, 0xde, 0xdb, 0xd6, 0xd3, 0xcf, 0xca, 0xc6,
654f26a0f43cfd3 Luca Weiss 2024-02-16 85
Re: [PATCH v5 2/2] drm/tiny: Add driver for Sharp Memory LCD
Hi Alex,
kernel test robot noticed the following build errors:
[auto build test ERROR on robh/for-next]
[also build test ERROR on drm-misc/drm-misc-next linus/master v6.11-rc6
next-20240903]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Alex-Lanzano/dt-bindings-display-Add-Sharp-Memory-LCD-bindings/20240902-041405
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link:
https://lore.kernel.org/r/20240901201118.3179206-3-lanzano.alex%40gmail.com
patch subject: [PATCH v5 2/2] drm/tiny: Add driver for Sharp Memory LCD
config: x86_64-randconfig-102-20240903
(https://download.01.org/0day-ci/archive/20240903/202409032359.jhpoadbf-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240903/202409032359.jhpoadbf-...@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/202409032359.jhpoadbf-...@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/tiny/sharp-memory.c: In function 'sharp_memory_crtc_enable':
>> drivers/gpu/drm/tiny/sharp-memory.c:344:17: error: implicit declaration of
>> function 'pwm_apply_state'; did you mean 'pwm_apply_args'?
>> [-Werror=implicit-function-declaration]
344 | pwm_apply_state(smd->pwm_vcom_signal, &pwm_state);
| ^~~
| pwm_apply_args
cc1: some warnings being treated as errors
vim +344 drivers/gpu/drm/tiny/sharp-memory.c
318
319 static void sharp_memory_crtc_enable(struct drm_crtc *crtc,
320 struct drm_atomic_state *state)
321 {
322 struct pwm_state pwm_state;
323 struct sharp_memory_device *smd =
drm_to_sharp_memory_device(crtc->dev);
324
325 sharp_memory_clear_display(smd);
326
327 if (smd->enable_gpio)
328 gpiod_set_value(smd->enable_gpio, 1);
329
330 switch (smd->vcom_mode) {
331 case SHARP_MEMORY_SOFTWARE_VCOM:
332 smd->sw_vcom_signal =
kthread_run(sharp_memory_sw_vcom_signal_thread,
333smd,
"sw_vcom_signal");
334 break;
335
336 case SHARP_MEMORY_EXTERNAL_VCOM:
337 break;
338
339 case SHARP_MEMORY_PWM_VCOM:
340 pwm_get_state(smd->pwm_vcom_signal, &pwm_state);
341 pwm_state.period =10;
342 pwm_state.duty_cycle = 1;
343 pwm_state.enabled = true;
> 344 pwm_apply_state(smd->pwm_vcom_signal, &pwm_state);
345 break;
346 }
347 }
348
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH] drm/panel: hx83112a: Switch to wrapped mipi_dsi functions
Hi Abhishek,
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.11-rc6 next-20240903]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Abhishek-Tamboli/drm-panel-hx83112a-Switch-to-wrapped-mipi_dsi-functions/20240903-010317
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240902170153.34512-1-abhishektamboli9%40gmail.com
patch subject: [PATCH] drm/panel: hx83112a: Switch to wrapped mipi_dsi functions
config: x86_64-buildonly-randconfig-003-20240903
(https://download.01.org/0day-ci/archive/20240903/202409032131.ea1cqdff-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240903/202409032131.ea1cqdff-...@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/202409032131.ea1cqdff-...@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/panel/panel-himax-hx83112a.c: In function 'hx83112a_on':
>> drivers/gpu/drm/panel/panel-himax-hx83112a.c:63:9: error: 'dsi' undeclared
>> (first use in this function)
63 | dsi->mode_flags |= MIPI_DSI_MODE_LPM;
| ^~~
drivers/gpu/drm/panel/panel-himax-hx83112a.c:63:9: note: each undeclared
identifier is reported only once for each function it appears in
drivers/gpu/drm/panel/panel-himax-hx83112a.c: In function 'hx83112a_disable':
drivers/gpu/drm/panel/panel-himax-hx83112a.c:197:9: error: 'dsi' undeclared
(first use in this function)
197 | dsi->mode_flags &= ~MIPI_DSI_MODE_LPM;
| ^~~
vim +/dsi +63 drivers/gpu/drm/panel/panel-himax-hx83112a.c
654f26a0f43cfd Luca Weiss 2024-02-16 58
654f26a0f43cfd Luca Weiss 2024-02-16 59 static int hx83112a_on(struct
hx83112a_panel *ctx)
654f26a0f43cfd Luca Weiss 2024-02-16 60 {
a76c4f29a2e42d Abhishek Tamboli 2024-09-02 61 struct
mipi_dsi_multi_context dsi_ctx = {.dsi = ctx->dsi};
654f26a0f43cfd Luca Weiss 2024-02-16 62
654f26a0f43cfd Luca Weiss 2024-02-16 @63 dsi->mode_flags |=
MIPI_DSI_MODE_LPM;
654f26a0f43cfd Luca Weiss 2024-02-16 64
a76c4f29a2e42d Abhishek Tamboli 2024-09-02 65
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETEXTC, 0x83, 0x11, 0x2a);
a76c4f29a2e42d Abhishek Tamboli 2024-09-02 66
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETPOWER1,
654f26a0f43cfd Luca Weiss 2024-02-16 67
0x08, 0x28, 0x28, 0x83, 0x83, 0x4c, 0x4f, 0x33);
a76c4f29a2e42d Abhishek Tamboli 2024-09-02 68
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETDISP,
654f26a0f43cfd Luca Weiss 2024-02-16 69
0x00, 0x02, 0x00, 0x90, 0x24, 0x00, 0x08, 0x19,
654f26a0f43cfd Luca Weiss 2024-02-16 70
0xea, 0x11, 0x11, 0x00, 0x11, 0xa3);
a76c4f29a2e42d Abhishek Tamboli 2024-09-02 71
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETDRV,
654f26a0f43cfd Luca Weiss 2024-02-16 72
0x58, 0x68, 0x58, 0x68, 0x0f, 0xef, 0x0b, 0xc0,
654f26a0f43cfd Luca Weiss 2024-02-16 73
0x0b, 0xc0, 0x0b, 0xc0, 0x00, 0xff, 0x00, 0xff,
654f26a0f43cfd Luca Weiss 2024-02-16 74
0x00, 0x00, 0x14, 0x15, 0x00, 0x29, 0x11, 0x07,
654f26a0f43cfd Luca Weiss 2024-02-16 75
0x12, 0x00, 0x29);
a76c4f29a2e42d Abhishek Tamboli 2024-09-02 76
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETBANK, 0x02);
a76c4f29a2e42d Abhishek Tamboli 2024-09-02 77
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETDRV,
654f26a0f43cfd Luca Weiss 2024-02-16 78
0x00, 0x12, 0x12, 0x11, 0x88, 0x12, 0x12, 0x00,
654f26a0f43cfd Luca Weiss 2024-02-16 79
0x53);
a76c4f29a2e42d Abhishek Tamboli 2024-09-02 80
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETBANK, 0x00);
a76c4f29a2e42d Abhishek Tamboli 2024-09-02 81
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETBANK, 0x03);
a76c4f29a2e42d Abhishek Tamboli 2024-09-02 82
mipi_dsi_dcs_write_seq_multi(&dsi_ctx, HX83112A_SETDGCLUT,
654f26a0f43cfd Luca Weiss 2024-02-16 83
0xff, 0xfe,
Re: [PATCH v1 2/2] arm64: dts: mediatek: Add MT8186 Ponyta Chromebooks
Hi Jianeng, kernel test robot noticed the following build errors: [auto build test ERROR on robh/for-next] [also build test ERROR on linus/master v6.11-rc6 next-20240902] [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/Jianeng-Ceng/dt-bindings-arm-mediatek-Add-MT8186-Ponyta-Chromebook/20240902-210651 base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next patch link: https://lore.kernel.org/r/20240902125502.1844374-3-cengjianeng%40huaqin.corp-partner.google.com patch subject: [PATCH v1 2/2] arm64: dts: mediatek: Add MT8186 Ponyta Chromebooks config: arm64-randconfig-002-20240903 (https://download.01.org/0day-ci/archive/20240903/202409031258.s4i2qvfw-...@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/20240903/202409031258.s4i2qvfw-...@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/202409031258.s4i2qvfw-...@intel.com/ All errors (new ones prefixed by >>): make[4]: *** No rule to make target 'arch/arm64/boot/dts/mediatek/mt8186-corsola-ponyta-rev2-sku1.dtb', needed by 'arch/arm64/boot/dts/mediatek/'. >> make[4]: *** No rule to make target >> 'arch/arm64/boot/dts/mediatek/mt8186-corsola-ponyta-rev2-sku0.dtb', needed >> by 'arch/arm64/boot/dts/mediatek/dtbs-list'. make[4]: Target 'arch/arm64/boot/dts/mediatek/' not remade because of errors. -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v1 2/2] arm64: dts: mediatek: Add MT8186 Ponyta Chromebooks
Hi Jianeng, kernel test robot noticed the following build errors: [auto build test ERROR on robh/for-next] [also build test ERROR on linus/master v6.11-rc6 next-20240902] [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/Jianeng-Ceng/dt-bindings-arm-mediatek-Add-MT8186-Ponyta-Chromebook/20240902-210651 base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next patch link: https://lore.kernel.org/r/20240902125502.1844374-3-cengjianeng%40huaqin.corp-partner.google.com patch subject: [PATCH v1 2/2] arm64: dts: mediatek: Add MT8186 Ponyta Chromebooks config: arm64-randconfig-001-20240903 (https://download.01.org/0day-ci/archive/20240903/202409031236.7k1thbdg-...@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/20240903/202409031236.7k1thbdg-...@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/202409031236.7k1thbdg-...@intel.com/ All errors (new ones prefixed by >>): >> make[4]: *** No rule to make target >> 'arch/arm64/boot/dts/mediatek/mt8186-corsola-ponyta-rev2-sku0.dtb', needed >> by 'arch/arm64/boot/dts/mediatek/'. >> make[4]: *** No rule to make target >> 'arch/arm64/boot/dts/mediatek/mt8186-corsola-ponyta-rev2-sku1.dtb', needed >> by 'arch/arm64/boot/dts/mediatek/'. make[4]: Target 'arch/arm64/boot/dts/mediatek/' not remade because of errors. -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH 2/3] drm/bridge: microchip-lvds: Drop unused headers
Hi Claudiu,
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.11-rc5 next-20240830]
[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/Claudiu-Beznea/drm-bridge-microchip-lvds-Revert-clk_prepare_enable-in-case-of-failure/20240828-001456
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240827161223.4152195-3-claudiu.beznea%40tuxon.dev
patch subject: [PATCH 2/3] drm/bridge: microchip-lvds: Drop unused headers
config: x86_64-allyesconfig
(https://download.01.org/0day-ci/archive/20240901/202409011412.dqvmnhiw-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240901/202409011412.dqvmnhiw-...@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/202409011412.dqvmnhiw-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/bridge/microchip-lvds.c:62:9: error: call to undeclared
>> function 'readl_relaxed'; ISO C99 and later do not support implicit function
>> declarations [-Wimplicit-function-declaration]
62 | return readl_relaxed(lvds->regs + offset);
|^
>> drivers/gpu/drm/bridge/microchip-lvds.c:67:2: error: call to undeclared
>> function 'writel_relaxed'; ISO C99 and later do not support implicit
>> function declarations [-Wimplicit-function-declaration]
67 | writel_relaxed(val, lvds->regs + offset);
| ^
2 errors generated.
vim +/readl_relaxed +62 drivers/gpu/drm/bridge/microchip-lvds.c
179b0769fc5fc19 Dharma Balasubiramani 2024-04-21 59
179b0769fc5fc19 Dharma Balasubiramani 2024-04-21 60 static inline u32
lvds_readl(struct mchp_lvds *lvds, u32 offset)
179b0769fc5fc19 Dharma Balasubiramani 2024-04-21 61 {
179b0769fc5fc19 Dharma Balasubiramani 2024-04-21 @62return
readl_relaxed(lvds->regs + offset);
179b0769fc5fc19 Dharma Balasubiramani 2024-04-21 63 }
179b0769fc5fc19 Dharma Balasubiramani 2024-04-21 64
179b0769fc5fc19 Dharma Balasubiramani 2024-04-21 65 static inline void
lvds_writel(struct mchp_lvds *lvds, u32 offset, u32 val)
179b0769fc5fc19 Dharma Balasubiramani 2024-04-21 66 {
179b0769fc5fc19 Dharma Balasubiramani 2024-04-21 @67writel_relaxed(val,
lvds->regs + offset);
179b0769fc5fc19 Dharma Balasubiramani 2024-04-21 68 }
179b0769fc5fc19 Dharma Balasubiramani 2024-04-21 69
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 2/3] drm/bridge: microchip-lvds: Drop unused headers
Hi Claudiu,
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.11-rc5 next-20240830]
[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/Claudiu-Beznea/drm-bridge-microchip-lvds-Revert-clk_prepare_enable-in-case-of-failure/20240828-001456
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240827161223.4152195-3-claudiu.beznea%40tuxon.dev
patch subject: [PATCH 2/3] drm/bridge: microchip-lvds: Drop unused headers
config: i386-allmodconfig
(https://download.01.org/0day-ci/archive/20240831/202408311600.hvive8ju-...@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/20240831/202408311600.hvive8ju-...@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/202408311600.hvive8ju-...@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/bridge/microchip-lvds.c: In function 'lvds_readl':
>> drivers/gpu/drm/bridge/microchip-lvds.c:62:16: error: implicit declaration
>> of function 'readl_relaxed' [-Werror=implicit-function-declaration]
62 | return readl_relaxed(lvds->regs + offset);
|^
drivers/gpu/drm/bridge/microchip-lvds.c: In function 'lvds_writel':
>> drivers/gpu/drm/bridge/microchip-lvds.c:67:9: error: implicit declaration of
>> function 'writel_relaxed' [-Werror=implicit-function-declaration]
67 | writel_relaxed(val, lvds->regs + offset);
| ^~
cc1: some warnings being treated as errors
vim +/readl_relaxed +62 drivers/gpu/drm/bridge/microchip-lvds.c
179b0769fc5fc1 Dharma Balasubiramani 2024-04-21 59
179b0769fc5fc1 Dharma Balasubiramani 2024-04-21 60 static inline u32
lvds_readl(struct mchp_lvds *lvds, u32 offset)
179b0769fc5fc1 Dharma Balasubiramani 2024-04-21 61 {
179b0769fc5fc1 Dharma Balasubiramani 2024-04-21 @62 return
readl_relaxed(lvds->regs + offset);
179b0769fc5fc1 Dharma Balasubiramani 2024-04-21 63 }
179b0769fc5fc1 Dharma Balasubiramani 2024-04-21 64
179b0769fc5fc1 Dharma Balasubiramani 2024-04-21 65 static inline void
lvds_writel(struct mchp_lvds *lvds, u32 offset, u32 val)
179b0769fc5fc1 Dharma Balasubiramani 2024-04-21 66 {
179b0769fc5fc1 Dharma Balasubiramani 2024-04-21 @67 writel_relaxed(val,
lvds->regs + offset);
179b0769fc5fc1 Dharma Balasubiramani 2024-04-21 68 }
179b0769fc5fc1 Dharma Balasubiramani 2024-04-21 69
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 5/6] drm/vkms: Switch to managed for CRTC
Hi Louis,
kernel test robot noticed the following build errors:
[auto build test ERROR on 071d583e01c88272f6ff216d4f867f8f35e94d7d]
url:
https://github.com/intel-lab-lkp/linux/commits/Louis-Chauvet/drm-vkms-Switch-to-managed-for-connector/20240827-180427
base: 071d583e01c88272f6ff216d4f867f8f35e94d7d
patch link:
https://lore.kernel.org/r/20240827-google-vkms-managed-v2-5-f41104553aeb%40bootlin.com
patch subject: [PATCH v2 5/6] drm/vkms: Switch to managed for CRTC
config: i386-randconfig-141-20240831
(https://download.01.org/0day-ci/archive/20240831/202408310628.jjbxamor-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240831/202408310628.jjbxamor-...@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/202408310628.jjbxamor-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/vkms/vkms_output.c:58:6: error: variable 'cursor' is used
>> uninitialized whenever 'if' condition is false
>> [-Werror,-Wsometimes-uninitialized]
58 | if (vkmsdev->config->cursor) {
| ^~~
drivers/gpu/drm/vkms/vkms_output.c:65:10: note: uninitialized use occurs here
65 | cursor ? &cursor->base : NULL);
| ^~
drivers/gpu/drm/vkms/vkms_output.c:58:2: note: remove the 'if' if its
condition is always true
58 | if (vkmsdev->config->cursor) {
| ^~~~
drivers/gpu/drm/vkms/vkms_output.c:32:37: note: initialize the variable
'cursor' to silence this warning
32 | struct vkms_plane *primary, *cursor, *overlay = NULL;
|^
| = NULL
1 error generated.
vim +58 drivers/gpu/drm/vkms/vkms_output.c
d16489307a52f0 Rodrigo Siqueira2018-07-11 29
e9d85f731de06a Rodrigo Siqueira2019-06-25 30 int vkms_output_init(struct
vkms_device *vkmsdev, int index)
854502fa0a38dc Rodrigo Siqueira2018-05-16 31 {
2abd7e59001123 Louis Chauvet 2024-08-27 32 struct vkms_plane
*primary, *cursor, *overlay = NULL;
854502fa0a38dc Rodrigo Siqueira2018-05-16 33 struct drm_device *dev
= &vkmsdev->drm;
a12934d3402c04 Louis Chauvet 2024-08-27 34 struct drm_connector
*connector;
e3b4c152118a04 Louis Chauvet 2024-08-27 35 struct drm_encoder
*encoder;
2abd7e59001123 Louis Chauvet 2024-08-27 36 struct vkms_crtc *crtc;
df2d385cb4132e José Expósito 2022-01-07 37 unsigned int n;
2abd7e59001123 Louis Chauvet 2024-08-27 38 int ret;
854502fa0a38dc Rodrigo Siqueira2018-05-16 39
2abd7e59001123 Louis Chauvet 2024-08-27 40 /*
2abd7e59001123 Louis Chauvet 2024-08-27 41* Initialize used
plane. One primary plane is required to perform the composition.
2abd7e59001123 Louis Chauvet 2024-08-27 42*
2abd7e59001123 Louis Chauvet 2024-08-27 43* The overlay and
cursor planes are not mandatory, but can be used to perform complex
2abd7e59001123 Louis Chauvet 2024-08-27 44* composition.
2abd7e59001123 Louis Chauvet 2024-08-27 45*/
e9d85f731de06a Rodrigo Siqueira2019-06-25 46 primary =
vkms_plane_init(vkmsdev, DRM_PLANE_TYPE_PRIMARY, index);
854502fa0a38dc Rodrigo Siqueira2018-05-16 47 if (IS_ERR(primary))
854502fa0a38dc Rodrigo Siqueira2018-05-16 48 return
PTR_ERR(primary);
854502fa0a38dc Rodrigo Siqueira2018-05-16 49
310e506c06e495 Melissa Wen 2021-04-24 50 if
(vkmsdev->config->overlay) {
df2d385cb4132e José Expósito 2022-01-07 51 for (n = 0; n <
NUM_OVERLAY_PLANES; n++) {
2abd7e59001123 Louis Chauvet 2024-08-27 52 overlay
= vkms_plane_init(vkmsdev, DRM_PLANE_TYPE_OVERLAY, index);
2abd7e59001123 Louis Chauvet 2024-08-27 53 if
(IS_ERR(overlay))
2abd7e59001123 Louis Chauvet 2024-08-27 54
return PTR_ERR(overlay);
310e506c06e495 Melissa Wen 2021-04-24 55 }
df2d385cb4132e José Expósito 2022-01-07 56 }
310e506c06e495 Melissa Wen 2021-04-24 57
2df7af93fdadb9 Sumera Priyadarsini 2021-01-12 @58 if
(vkmsdev->config->cursor) {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 5/6] drm/vkms: Switch to managed for CRTC
Hi Louis,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 071d583e01c88272f6ff216d4f867f8f35e94d7d]
url:
https://github.com/intel-lab-lkp/linux/commits/Louis-Chauvet/drm-vkms-Switch-to-managed-for-connector/20240827-180427
base: 071d583e01c88272f6ff216d4f867f8f35e94d7d
patch link:
https://lore.kernel.org/r/20240827-google-vkms-managed-v2-5-f41104553aeb%40bootlin.com
patch subject: [PATCH v2 5/6] drm/vkms: Switch to managed for CRTC
config: i386-buildonly-randconfig-004-20240831
(https://download.01.org/0day-ci/archive/20240831/202408310524.jpbkb81e-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240831/202408310524.jpbkb81e-...@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/202408310524.jpbkb81e-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/vkms/vkms_output.c:58:6: warning: variable 'cursor' is used
>> uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
58 | if (vkmsdev->config->cursor) {
| ^~~
drivers/gpu/drm/vkms/vkms_output.c:65:10: note: uninitialized use occurs here
65 | cursor ? &cursor->base : NULL);
| ^~
drivers/gpu/drm/vkms/vkms_output.c:58:2: note: remove the 'if' if its
condition is always true
58 | if (vkmsdev->config->cursor) {
| ^~~~
drivers/gpu/drm/vkms/vkms_output.c:32:37: note: initialize the variable
'cursor' to silence this warning
32 | struct vkms_plane *primary, *cursor, *overlay = NULL;
|^
| = NULL
1 warning generated.
vim +58 drivers/gpu/drm/vkms/vkms_output.c
d16489307a52f0 Rodrigo Siqueira2018-07-11 29
e9d85f731de06a Rodrigo Siqueira2019-06-25 30 int vkms_output_init(struct
vkms_device *vkmsdev, int index)
854502fa0a38dc Rodrigo Siqueira2018-05-16 31 {
2abd7e59001123 Louis Chauvet 2024-08-27 32 struct vkms_plane
*primary, *cursor, *overlay = NULL;
854502fa0a38dc Rodrigo Siqueira2018-05-16 33 struct drm_device *dev
= &vkmsdev->drm;
a12934d3402c04 Louis Chauvet 2024-08-27 34 struct drm_connector
*connector;
e3b4c152118a04 Louis Chauvet 2024-08-27 35 struct drm_encoder
*encoder;
2abd7e59001123 Louis Chauvet 2024-08-27 36 struct vkms_crtc *crtc;
df2d385cb4132e José Expósito 2022-01-07 37 unsigned int n;
2abd7e59001123 Louis Chauvet 2024-08-27 38 int ret;
854502fa0a38dc Rodrigo Siqueira2018-05-16 39
2abd7e59001123 Louis Chauvet 2024-08-27 40 /*
2abd7e59001123 Louis Chauvet 2024-08-27 41* Initialize used
plane. One primary plane is required to perform the composition.
2abd7e59001123 Louis Chauvet 2024-08-27 42*
2abd7e59001123 Louis Chauvet 2024-08-27 43* The overlay and
cursor planes are not mandatory, but can be used to perform complex
2abd7e59001123 Louis Chauvet 2024-08-27 44* composition.
2abd7e59001123 Louis Chauvet 2024-08-27 45*/
e9d85f731de06a Rodrigo Siqueira2019-06-25 46 primary =
vkms_plane_init(vkmsdev, DRM_PLANE_TYPE_PRIMARY, index);
854502fa0a38dc Rodrigo Siqueira2018-05-16 47 if (IS_ERR(primary))
854502fa0a38dc Rodrigo Siqueira2018-05-16 48 return
PTR_ERR(primary);
854502fa0a38dc Rodrigo Siqueira2018-05-16 49
310e506c06e495 Melissa Wen 2021-04-24 50 if
(vkmsdev->config->overlay) {
df2d385cb4132e José Expósito 2022-01-07 51 for (n = 0; n <
NUM_OVERLAY_PLANES; n++) {
2abd7e59001123 Louis Chauvet 2024-08-27 52 overlay
= vkms_plane_init(vkmsdev, DRM_PLANE_TYPE_OVERLAY, index);
2abd7e59001123 Louis Chauvet 2024-08-27 53 if
(IS_ERR(overlay))
2abd7e59001123 Louis Chauvet 2024-08-27 54
return PTR_ERR(overlay);
310e506c06e495 Melissa Wen 2021-04-24 55 }
df2d385cb4132e José Expósito 2022-01-07 56 }
310e506c06e495 Melissa Wen 2021-04-24 57
2df7af93fdadb9 Sumera Priyadarsini 2021-01-12 @58 if
(vkmsdev->config->cursor) {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/4] drm/sched: add optional errno to drm_sched_start()
Hi Christian,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20240826]
[cannot apply to drm-intel/for-linux-next drm-intel/for-linux-next-fixes
linus/master v6.11-rc5 v6.11-rc4 v6.11-rc3 v6.11-rc5]
[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/Christian-K-nig/dma-buf-give-examples-of-error-codes-to-use/20240826-202848
base: next-20240826
patch link:
https://lore.kernel.org/r/20240826122541.85663-1-christian.koenig%40amd.com
patch subject: [PATCH 1/4] drm/sched: add optional errno to drm_sched_start()
config: x86_64-allyesconfig
(https://download.01.org/0day-ci/archive/20240830/202408301653.9umdd9cc-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240830/202408301653.9umdd9cc-...@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/202408301653.9umdd9cc-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/panthor/panthor_sched.c:2541:35: error: too few arguments to
>> function call, expected 2, have 1
2541 | drm_sched_start(&queue->scheduler);
| ~~~ ^
include/drm/gpu_scheduler.h:582:6: note: 'drm_sched_start' declared here
582 | void drm_sched_start(struct drm_gpu_scheduler *sched, int errno);
| ^ ~~
1 error 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 +2541 drivers/gpu/drm/panthor/panthor_sched.c
de85488138247d0 Boris Brezillon 2024-02-29 2532
de85488138247d0 Boris Brezillon 2024-02-29 2533 static void
queue_start(struct panthor_queue *queue)
de85488138247d0 Boris Brezillon 2024-02-29 2534 {
de85488138247d0 Boris Brezillon 2024-02-29 2535struct panthor_job *job;
de85488138247d0 Boris Brezillon 2024-02-29 2536
de85488138247d0 Boris Brezillon 2024-02-29 2537/* Re-assign the parent
fences. */
de85488138247d0 Boris Brezillon 2024-02-29 2538
list_for_each_entry(job, &queue->scheduler.pending_list, base.list)
de85488138247d0 Boris Brezillon 2024-02-29 2539
job->base.s_fence->parent = dma_fence_get(job->done_fence);
de85488138247d0 Boris Brezillon 2024-02-29 2540
83b501c1799a96a Christian König 2024-07-19 @2541
drm_sched_start(&queue->scheduler);
de85488138247d0 Boris Brezillon 2024-02-29 2542 }
de85488138247d0 Boris Brezillon 2024-02-29 2543
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/4] drm/sched: add optional errno to drm_sched_start()
Hi Christian,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20240826]
[cannot apply to drm-intel/for-linux-next drm-intel/for-linux-next-fixes
linus/master v6.11-rc5 v6.11-rc4 v6.11-rc3 v6.11-rc5]
[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/Christian-K-nig/dma-buf-give-examples-of-error-codes-to-use/20240826-202848
base: next-20240826
patch link:
https://lore.kernel.org/r/20240826122541.85663-1-christian.koenig%40amd.com
patch subject: [PATCH 1/4] drm/sched: add optional errno to drm_sched_start()
config: i386-allmodconfig
(https://download.01.org/0day-ci/archive/20240830/202408301500.gd1se900-...@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/20240830/202408301500.gd1se900-...@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/202408301500.gd1se900-...@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/amd/amdgpu/amdgpu_job.c: In function 'amdgpu_job_timedout':
>> drivers/gpu/drm/amd/amdgpu/amdgpu_job.c:90:33: error: too few arguments to
>> function 'drm_sched_start'
90 | drm_sched_start(&ring->sched);
| ^~~
In file included from drivers/gpu/drm/amd/amdgpu/amdgpu_ring.h:28,
from drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.h:29,
from drivers/gpu/drm/amd/amdgpu/amdgpu.h:43,
from drivers/gpu/drm/amd/amdgpu/amdgpu_job.c:30:
include/drm/gpu_scheduler.h:582:6: note: declared here
582 | void drm_sched_start(struct drm_gpu_scheduler *sched, int errno);
| ^~~
--
drivers/gpu/drm/panthor/panthor_sched.c: In function 'queue_start':
>> drivers/gpu/drm/panthor/panthor_sched.c:2541:9: error: too few arguments to
>> function 'drm_sched_start'
2541 | drm_sched_start(&queue->scheduler);
| ^~~
In file included from drivers/gpu/drm/panthor/panthor_sched.c:8:
include/drm/gpu_scheduler.h:582:6: note: declared here
582 | void drm_sched_start(struct drm_gpu_scheduler *sched, int errno);
| ^~~
Kconfig warnings: (for reference only)
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])
vim +/drm_sched_start +90 drivers/gpu/drm/amd/amdgpu/amdgpu_job.c
c1b69ed0c62f9d8 drivers/gpu/drm/amd/amdgpu/amdgpu_sched.c Chunming Zhou
2015-07-21 33
a6a1f036c74e3d2 drivers/gpu/drm/amd/amdgpu/amdgpu_job.c Luben Tuikov
2021-01-20 34 static enum drm_gpu_sched_stat amdgpu_job_timedout(struct
drm_sched_job *s_job)
0de2479c953ae07 drivers/gpu/drm/amd/amdgpu/amdgpu_job.c Monk Liu
2016-03-04 35 {
3320b8d2acd3d48 drivers/gpu/drm/amd/amdgpu/amdgpu_job.c Christian König
2018-07-13 36 struct amdgpu_ring *ring = to_amdgpu_ring(s_job->sched);
3320b8d2acd3d48 drivers/gpu/drm/amd/amdgpu/amdgpu_job.c Christian König
2018-07-13 37 struct amdgpu_job *job = to_amdgpu_job(s_job);
b8f67b9ddf4f8fe drivers/gpu/drm/amd/amdgpu/amdgpu_job.c Shashank Sharma
2024-01-18 38 struct amdgpu_task_info *ti;
95a2f917387a23c drivers/gpu/drm/amd/amdgpu/amdgpu_job.c Yintian Tao
2020-04-07 39 struct amdgpu_device *adev = ring->adev;
ca4e17244bd213e drivers/gpu/drm/amd/amdgpu/amdgpu_job.c Andrey Grodzovsky
2021-05-12 40 int idx;
7258fa31eabd882 drivers/gpu/drm/amd/amdgpu/amdgpu_job.c Surbhi Kakarya
2022-01-26 41 int r;
ca4e17244bd213e drivers/gpu/drm/amd/amdgpu/amdgpu_job.c Andrey Grodzovsky
2021-05-12 42
c58a863b1ccf638 drivers/gpu/drm/amd/amdgpu/amdgpu_job.c Guchun Chen
2021-10-08 43 if (!drm_dev_enter(adev_to_drm(adev), &idx)) {
7d570f56f1e1005 drivers/gpu/drm/amd/amdgpu/amdgpu_job.c Alex Deucher
2024-07-08 44 dev_info(adev->dev, "%s - device unplugged skipping
recovery on scheduler:%s",
ca4e17244bd213e drivers/gpu/drm/amd/amdgpu/amdgpu_job.c Andrey Grodzovsky
2021-05-12 45 __func__, s_job->sched->name);
ca4e17244bd213e drivers/gpu/drm/amd/amdgpu/amdgpu_job.c Andrey Grodzovsky
2021-05-12 46
ca4e17244bd213e drivers/gpu/drm/amd/amdgpu/amdgpu_job.c Andrey Grodzovs
Re: [PATCH 09/10] drm/bochs: Validate display modes against available video memory
Hi Thomas,
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.11-rc5 next-20240829]
[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-bochs-Remove-manual-format-test-from-fb_create/20240826-131701
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20240823124422.286989-10-tzimmermann%40suse.de
patch subject: [PATCH 09/10] drm/bochs: Validate display modes against
available video memory
config: i386-randconfig-006-20240829
(https://download.01.org/0day-ci/archive/20240830/202408300420.qcgoiim6-...@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/20240830/202408300420.qcgoiim6-...@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/202408300420.qcgoiim6-...@intel.com/
All errors (new ones prefixed by >>):
ld: drivers/gpu/drm/tiny/bochs.o: in function `bochs_mode_config_mode_valid':
>> drivers/gpu/drm/tiny/bochs.c:574: undefined reference to `__udivdi3'
vim +574 drivers/gpu/drm/tiny/bochs.c
560
561 static enum drm_mode_status bochs_mode_config_mode_valid(struct
drm_device *dev,
562 const struct
drm_display_mode *mode)
563 {
564 struct bochs_device *bochs = to_bochs_device(dev);
565 const struct drm_format_info *format =
drm_format_info(DRM_FORMAT_XRGB);
566 uint64_t pitch;
567
568 if (drm_WARN_ON(dev, !format))
569 return MODE_ERROR;
570
571 pitch = drm_format_info_min_pitch(format, 0, mode->vdisplay);
572 if (!pitch)
573 return MODE_BAD_WIDTH;
> 574 if (bochs->fb_size / pitch < mode->hdisplay)
575 return MODE_MEM;
576
577 return MODE_OK;
578 }
579
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 2/2] drm: ensure drm headers are self-contained and pass kernel-doc
Hi Jani, kernel test robot noticed the following build errors: [auto build test ERROR on drm/drm-next] [also build test ERROR on next-20240826] [cannot apply to drm-misc/drm-misc-next linus/master v6.11-rc5] [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-ensure-drm-headers-are-self-contained-and-pass-kernel-doc/20240826-134953 base: git://anongit.freedesktop.org/drm/drm drm-next patch link: https://lore.kernel.org/r/20240823141110.3431423-2-jani.nikula%40intel.com patch subject: [PATCH 2/2] drm: ensure drm headers are self-contained and pass kernel-doc config: arc-allmodconfig (https://download.01.org/0day-ci/archive/20240827/202408270538.dev4dxpq-...@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/20240827/202408270538.dev4dxpq-...@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/202408270538.dev4dxpq-...@intel.com/ All errors (new ones prefixed by >>): | ^~~ arch/arc/include/asm/pgtable-levels.h:160:34: note: in expansion of macro 'pmd_val' 160 | #define pmd_page_vaddr(pmd) (pmd_val(pmd) & PAGE_MASK) | ^~~ include/linux/pgtable.h:96:25: note: in expansion of macro 'pmd_page_vaddr' 96 | return (pte_t *)pmd_page_vaddr(*pmd) + pte_index(address); | ^~ include/linux/pgtable.h: In function 'pmd_off': include/linux/pgtable.h:165:38: error: implicit declaration of function 'p4d_offset'; did you mean 'pmd_offset'? [-Werror=implicit-function-declaration] 165 | return pmd_offset(pud_offset(p4d_offset(pgd_offset(mm, va), va), va), va); | ^~ | pmd_offset include/linux/pgtable.h:165:38: warning: passing argument 1 of 'pud_offset' makes pointer from integer without a cast [-Wint-conversion] 165 | return pmd_offset(pud_offset(p4d_offset(pgd_offset(mm, va), va), va), va); | ^~ | | | int include/asm-generic/pgtable-nopud.h:42:40: note: expected 'p4d_t *' but argument is of type 'int' 42 | static inline pud_t *pud_offset(p4d_t *p4d, unsigned long address) | ~~~^~~ include/linux/pgtable.h: In function 'pmd_off_k': include/linux/pgtable.h:170:38: warning: passing argument 1 of 'pud_offset' makes pointer from integer without a cast [-Wint-conversion] 170 | return pmd_offset(pud_offset(p4d_offset(pgd_offset_k(va), va), va), va); | ^~~~ | | | int include/asm-generic/pgtable-nopud.h:42:40: note: expected 'p4d_t *' but argument is of type 'int' 42 | static inline pud_t *pud_offset(p4d_t *p4d, unsigned long address) | ~~~^~~ include/linux/pgtable.h: In function 'virt_to_kpte': arch/arc/include/asm/page.h:41:29: error: request for member 'pgd' in something not a structure or union 41 | #define pgd_val(x) ((x).pgd) | ^ include/asm-generic/pgtable-nop4d.h:40:50: note: in expansion of macro 'pgd_val' 40 | #define p4d_val(x) (pgd_val((x).pgd)) | ^~~ include/asm-generic/pgtable-nopud.h:48:50: note: in expansion of macro 'p4d_val' 48 | #define pud_val(x) (p4d_val((x).p4d)) | ^~~ include/asm-generic/pgtable-nopmd.h:52:50: note: in expansion of macro 'pud_val' 52 | #define pmd_val(x) (pud_val((x).pud)) | ^~~ arch/arc/include/asm/pgtable-levels.h:156:35: note: in expansion of macro 'pmd_val' 156 | #define pmd_none(x) (!pmd_val(x)) | ^~~ inc
Re: [PATCH v3 14/15] drm/i915/gt: Implement creation and removal routines for CCS engines
Hi Andi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-intel/for-linux-next-fixes drm-tip/drm-tip
drm/drm-next drm-exynos/exynos-drm-next drm-misc/drm-misc-next linus/master
v6.11-rc5 next-20240826]
[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/Andi-Shyti/drm-i915-gt-Avoid-using-masked-workaround-for-CCS_MODE-setting/20240826-165045
base: git://anongit.freedesktop.org/drm-intel for-linux-next
patch link:
https://lore.kernel.org/r/20240823130855.72436-15-andi.shyti%40linux.intel.com
patch subject: [PATCH v3 14/15] drm/i915/gt: Implement creation and removal
routines for CCS engines
config: i386-buildonly-randconfig-002-20240827
(https://download.01.org/0day-ci/archive/20240827/202408270545.o4dlo6la-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240827/202408270545.o4dlo6la-...@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/202408270545.o4dlo6la-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/i915/gt/intel_gt_ccs_mode.c:164:12: warning: function
>> 'rb_engine_cmp' is not needed and will not be emitted
>> [-Wunneeded-internal-declaration]
164 | static int rb_engine_cmp(struct rb_node *rb_new, const struct
rb_node *rb_old)
|^
1 warning generated.
vim +/rb_engine_cmp +164 drivers/gpu/drm/i915/gt/intel_gt_ccs_mode.c
163
> 164 static int rb_engine_cmp(struct rb_node *rb_new, const struct rb_node
> *rb_old)
165 {
166 struct intel_engine_cs *new = rb_to_uabi_engine(rb_new);
167 struct intel_engine_cs *old = rb_to_uabi_engine(rb_old);
168
169 if (new->uabi_class - old->uabi_class == 0)
170 return new->uabi_instance - old->uabi_instance;
171
172 return new->uabi_class - old->uabi_class;
173 }
174
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 2/2] drm: ensure drm headers are self-contained and pass kernel-doc
Hi Jani,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm/drm-next]
[also build test ERROR on drm-misc/drm-misc-next next-20240826]
[cannot apply to linus/master v6.11-rc5]
[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-ensure-drm-headers-are-self-contained-and-pass-kernel-doc/20240826-134953
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20240823141110.3431423-2-jani.nikula%40intel.com
patch subject: [PATCH 2/2] drm: ensure drm headers are self-contained and pass
kernel-doc
config: sparc-allmodconfig
(https://download.01.org/0day-ci/archive/20240826/202408262328.mknfi1mv-...@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/20240826/202408262328.mknfi1mv-...@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/202408262328.mknfi1mv-...@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/sparc/include/asm/pgtable_64.h:16,
from arch/sparc/include/asm/pgtable.h:5,
from include/linux/pgtable.h:6,
from include/drm/ttm/ttm_caching.h:28,
from :
include/asm-generic/pgtable-nop4d.h:9:18: error: unknown type name 'pgd_t';
did you mean 'pid_t'?
9 | typedef struct { pgd_t pgd; } p4d_t;
| ^
| pid_t
include/asm-generic/pgtable-nop4d.h:21:28: error: unknown type name 'pgd_t';
did you mean 'p4d_t'?
21 | static inline int pgd_none(pgd_t pgd) { return 0; }
|^
|p4d_t
include/asm-generic/pgtable-nop4d.h:22:27: error: unknown type name 'pgd_t';
did you mean 'p4d_t'?
22 | static inline int pgd_bad(pgd_t pgd){ return 0; }
| ^
| p4d_t
include/asm-generic/pgtable-nop4d.h:23:31: error: unknown type name 'pgd_t';
did you mean 'p4d_t'?
23 | static inline int pgd_present(pgd_t pgd){ return 1; }
| ^
| p4d_t
include/asm-generic/pgtable-nop4d.h:24:30: error: unknown type name 'pgd_t';
did you mean 'p4d_t'?
24 | static inline void pgd_clear(pgd_t *pgd){ }
| ^
| p4d_t
include/asm-generic/pgtable-nop4d.h:35:33: error: unknown type name 'pgd_t';
did you mean 'p4d_t'?
35 | static inline p4d_t *p4d_offset(pgd_t *pgd, unsigned long address)
| ^
| p4d_t
In file included from arch/sparc/include/asm/page.h:8,
from arch/sparc/include/asm/pgtable_64.h:23:
include/linux/pgtable.h: In function 'pud_offset':
arch/sparc/include/asm/page_64.h:79:29: error: request for member 'pgd' in
something not a structure or union
79 | #define pgd_val(x) ((x).pgd)
| ^
arch/sparc/include/asm/page_64.h:147:60: note: in definition of macro '__va'
147 | #define __va(x) ((void *)((unsigned long) (x) +
PAGE_OFFSET))
|^
include/asm-generic/pgtable-nop4d.h:40:50: note: in expansion of macro
'pgd_val'
40 | #define p4d_val(x) (pgd_val((x).pgd))
| ^~~
arch/sparc/include/asm/pgtable_64.h:863:25: note: in expansion of macro
'p4d_val'
863 | ((pud_t *) __va(p4d_val(p4d)))
| ^~~
include/linux/pgtable.h:133:16: note: in expansion of macro 'p4d_pgtable'
133 | return p4d_pgtable(*p4d) + pud_index(address);
|^~~
include/linux/pgtable.h: In function 'pmd_off':
include/linux/pgtable.h:165:38: error: implicit declaration of function
'p4d_offset'; did you mean 'pud_offset'? [-Wimplicit-function-declaration]
165 | return pmd_offset(pud_offset(p4d_offset(pgd_offset(mm, va),
va), va), va);
| ^~
Re: [PATCH v6] drm/i915/hwmon: expose fan speed
Hi Raag, kernel test robot noticed the following build errors: [auto build test ERROR on groeck-staging/hwmon-next] [also build test ERROR on linus/master v6.11-rc5 next-20240823] [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-i915-hwmon-expose-fan-speed/20240820-135849 base: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next patch link: https://lore.kernel.org/r/20240820062010.2000873-1-raag.jadav%40intel.com patch subject: [PATCH v6] drm/i915/hwmon: expose fan speed config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20240826/202408260446.0eeopmo6-...@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/20240826/202408260446.0eeopmo6-...@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/202408260446.0eeopmo6-...@intel.com/ All errors (new ones prefixed by >>): ld: drivers/gpu/drm/i915/i915_hwmon.o: in function `hwm_read': >> i915_hwmon.c:(.text+0xe36): undefined reference to `__udivdi3' -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH -next 5/5] drm/amd/display: Make dcn35_fpga_funcs static
Hi Jinjie,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20240821]
url:
https://github.com/intel-lab-lkp/linux/commits/Jinjie-Ruan/drm-amd-display-Make-core_dcn4_g6_temp_read_blackout_table-static/20240821-143421
base: next-20240821
patch link:
https://lore.kernel.org/r/20240821064040.2292969-6-ruanjinjie%40huawei.com
patch subject: [PATCH -next 5/5] drm/amd/display: Make dcn35_fpga_funcs static
config: i386-randconfig-003-20240824
(https://download.01.org/0day-ci/archive/20240825/202408250235.xz6ztozy-...@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/20240825/202408250235.xz6ztozy-...@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/202408250235.xz6ztozy-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn35/dcn35_clk_mgr.c:1071:29:
>> warning: 'dcn35_fpga_funcs' defined but not used [-Wunused-variable]
1071 | static struct clk_mgr_funcs dcn35_fpga_funcs = {
| ^~~~
vim +/dcn35_fpga_funcs +1071
drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn35/dcn35_clk_mgr.c
1070
> 1071 static struct clk_mgr_funcs dcn35_fpga_funcs = {
1072 .get_dp_ref_clk_frequency = dce12_get_dp_ref_freq_khz,
1073 .update_clocks = dcn35_update_clocks_fpga,
1074 .init_clocks = dcn35_init_clocks_fpga,
1075 .get_dtb_ref_clk_frequency = dcn31_get_dtb_ref_freq_khz,
1076 };
1077
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH -next 5/5] drm/amd/display: Make dcn35_fpga_funcs static
Hi Jinjie,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20240821]
url:
https://github.com/intel-lab-lkp/linux/commits/Jinjie-Ruan/drm-amd-display-Make-core_dcn4_g6_temp_read_blackout_table-static/20240821-143421
base: next-20240821
patch link:
https://lore.kernel.org/r/20240821064040.2292969-6-ruanjinjie%40huawei.com
patch subject: [PATCH -next 5/5] drm/amd/display: Make dcn35_fpga_funcs static
config: x86_64-allyesconfig
(https://download.01.org/0day-ci/archive/20240824/202408241600.uhrtix7j-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240824/202408241600.uhrtix7j-...@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/202408241600.uhrtix7j-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn35/dcn35_clk_mgr.c:1071:29:
>> warning: unused variable 'dcn35_fpga_funcs' [-Wunused-variable]
1071 | static struct clk_mgr_funcs dcn35_fpga_funcs = {
| ^~~~
1 warning generated.
vim +/dcn35_fpga_funcs +1071
drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn35/dcn35_clk_mgr.c
1070
> 1071 static struct clk_mgr_funcs dcn35_fpga_funcs = {
1072 .get_dp_ref_clk_frequency = dce12_get_dp_ref_freq_khz,
1073 .update_clocks = dcn35_update_clocks_fpga,
1074 .init_clocks = dcn35_init_clocks_fpga,
1075 .get_dtb_ref_clk_frequency = dcn31_get_dtb_ref_freq_khz,
1076 };
1077
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH -next v2 RESEND] drm/amd/display: Remove unused dcn35_fpga_funcs
Hi Jinjie,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20240821]
url:
https://github.com/intel-lab-lkp/linux/commits/Jinjie-Ruan/drm-amd-display-Remove-unused-dcn35_fpga_funcs/20240822-095139
base: next-20240821
patch link:
https://lore.kernel.org/r/20240822015819.3356282-1-ruanjinjie%40huawei.com
patch subject: [PATCH -next v2 RESEND] drm/amd/display: Remove unused
dcn35_fpga_funcs
config: i386-randconfig-006-20240823
(https://download.01.org/0day-ci/archive/20240823/202408231338.egp42fkn-...@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/20240823/202408231338.egp42fkn-...@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/202408231338.egp42fkn-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn35/dcn35_clk_mgr.c:989:13:
>> error: 'dcn35_update_clocks_fpga' defined but not used
>> [-Werror=unused-function]
989 | static void dcn35_update_clocks_fpga(struct clk_mgr *clk_mgr,
| ^~~~
>> drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn35/dcn35_clk_mgr.c:982:13:
>> error: 'dcn35_init_clocks_fpga' defined but not used
>> [-Werror=unused-function]
982 | static void dcn35_init_clocks_fpga(struct clk_mgr *clk_mgr)
| ^~
cc1: all warnings being treated as errors
vim +/dcn35_update_clocks_fpga +989
drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn35/dcn35_clk_mgr.c
93a66cef607cfe Sung Joon Kim 2023-08-18 981
8774029f76b980 Qingqing Zhuo 2023-08-02 @982 static void
dcn35_init_clocks_fpga(struct clk_mgr *clk_mgr)
8774029f76b980 Qingqing Zhuo 2023-08-02 983 {
f2a905b01c6dcc Eric Yang 2024-01-16 984 init_clk_states(clk_mgr);
8774029f76b980 Qingqing Zhuo 2023-08-02 985
8774029f76b980 Qingqing Zhuo 2023-08-02 986 /* TODO: Implement the functions
and remove the ifndef guard */
8774029f76b980 Qingqing Zhuo 2023-08-02 987 }
8774029f76b980 Qingqing Zhuo 2023-08-02 988
8774029f76b980 Qingqing Zhuo 2023-08-02 @989 static void
dcn35_update_clocks_fpga(struct clk_mgr *clk_mgr,
8774029f76b980 Qingqing Zhuo 2023-08-02 990 struct dc_state
*context,
8774029f76b980 Qingqing Zhuo 2023-08-02 991 bool safe_to_lower)
8774029f76b980 Qingqing Zhuo 2023-08-02 992 {
8774029f76b980 Qingqing Zhuo 2023-08-02 993 struct clk_mgr_internal
*clk_mgr_int = TO_CLK_MGR_INTERNAL(clk_mgr);
8774029f76b980 Qingqing Zhuo 2023-08-02 994 struct dc_clocks *new_clocks =
&context->bw_ctx.bw.dcn.clk;
8774029f76b980 Qingqing Zhuo 2023-08-02 995 int fclk_adj =
new_clocks->fclk_khz;
8774029f76b980 Qingqing Zhuo 2023-08-02 996
8774029f76b980 Qingqing Zhuo 2023-08-02 997 /* TODO: remove this after
correctly set by DML */
8774029f76b980 Qingqing Zhuo 2023-08-02 998 new_clocks->dcfclk_khz = 40;
8774029f76b980 Qingqing Zhuo 2023-08-02 999 new_clocks->socclk_khz = 40;
8774029f76b980 Qingqing Zhuo 2023-08-02 1000
8774029f76b980 Qingqing Zhuo 2023-08-02 1001 /* Min fclk = 1.2GHz since all
the extra scemi logic seems to run off of it */
8774029f76b980 Qingqing Zhuo 2023-08-02 1002 //int fclk_adj =
new_clocks->fclk_khz > 120 ? new_clocks->fclk_khz : 120;
8774029f76b980 Qingqing Zhuo 2023-08-02 1003 new_clocks->fclk_khz = 432;
8774029f76b980 Qingqing Zhuo 2023-08-02 1004
8774029f76b980 Qingqing Zhuo 2023-08-02 1005 if
(should_set_clock(safe_to_lower, new_clocks->phyclk_khz,
clk_mgr->clks.phyclk_khz)) {
8774029f76b980 Qingqing Zhuo 2023-08-02 1006
clk_mgr->clks.phyclk_khz = new_clocks->phyclk_khz;
8774029f76b980 Qingqing Zhuo 2023-08-02 1007 }
8774029f76b980 Qingqing Zhuo 2023-08-02 1008
8774029f76b980 Qingqing Zhuo 2023-08-02 1009 if
(should_set_clock(safe_to_lower, new_clocks->dcfclk_khz,
clk_mgr->clks.dcfclk_khz)) {
8774029f76b980 Qingqing Zhuo 2023-08-02 1010
clk_mgr->clks.dcfclk_khz = new_clocks->dcfclk_khz;
8774029f76b980 Qingqing Zhuo 2023-08-02 1011 }
8774029f76b980 Qingqing Zhuo 2023-08-02 1012
8774029f76b980 Qingqing Zhuo 2023-08-02 1013 if
(should_set_clock(safe_to_lower,
8774029f76b980 Qingqing Zhuo 2023-08-02 1014
new_clocks->dcfclk_deep_sleep_khz, clk_mgr->clks.dcfclk_deep_sleep_khz)) {
8774029f76b980 Qingqing Zhuo 2023-08-02 1015
clk_mgr->clks.dcfclk_deep_sleep_khz = new_clocks->dcfclk_deep_sleep_khz;
8774029f76b980 Qingqing Zhuo 2023-08-02 1016 }
8774029f76b980 Qingqing Zhuo 2023-08-02 1017
8774029f76b980 Qingqing Zhuo 2023-08-02
Re: [PATCH -next v2 RESEND] drm/amd/display: Remove unused dcn35_fpga_funcs
Hi Jinjie,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20240821]
url:
https://github.com/intel-lab-lkp/linux/commits/Jinjie-Ruan/drm-amd-display-Remove-unused-dcn35_fpga_funcs/20240822-095139
base: next-20240821
patch link:
https://lore.kernel.org/r/20240822015819.3356282-1-ruanjinjie%40huawei.com
patch subject: [PATCH -next v2 RESEND] drm/amd/display: Remove unused
dcn35_fpga_funcs
config: x86_64-buildonly-randconfig-005-20240823
(https://download.01.org/0day-ci/archive/20240823/202408231105.bpoypnk6-...@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/20240823/202408231105.bpoypnk6-...@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/202408231105.bpoypnk6-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn35/dcn35_clk_mgr.c:989:13:
>> warning: 'dcn35_update_clocks_fpga' defined but not used [-Wunused-function]
989 | static void dcn35_update_clocks_fpga(struct clk_mgr *clk_mgr,
| ^~~~
>> drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn35/dcn35_clk_mgr.c:982:13:
>> warning: 'dcn35_init_clocks_fpga' defined but not used [-Wunused-function]
982 | static void dcn35_init_clocks_fpga(struct clk_mgr *clk_mgr)
| ^~
vim +/dcn35_update_clocks_fpga +989
drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn35/dcn35_clk_mgr.c
93a66cef607cfe Sung Joon Kim 2023-08-18 981
8774029f76b980 Qingqing Zhuo 2023-08-02 @982 static void
dcn35_init_clocks_fpga(struct clk_mgr *clk_mgr)
8774029f76b980 Qingqing Zhuo 2023-08-02 983 {
f2a905b01c6dcc Eric Yang 2024-01-16 984 init_clk_states(clk_mgr);
8774029f76b980 Qingqing Zhuo 2023-08-02 985
8774029f76b980 Qingqing Zhuo 2023-08-02 986 /* TODO: Implement the functions
and remove the ifndef guard */
8774029f76b980 Qingqing Zhuo 2023-08-02 987 }
8774029f76b980 Qingqing Zhuo 2023-08-02 988
8774029f76b980 Qingqing Zhuo 2023-08-02 @989 static void
dcn35_update_clocks_fpga(struct clk_mgr *clk_mgr,
8774029f76b980 Qingqing Zhuo 2023-08-02 990 struct dc_state
*context,
8774029f76b980 Qingqing Zhuo 2023-08-02 991 bool safe_to_lower)
8774029f76b980 Qingqing Zhuo 2023-08-02 992 {
8774029f76b980 Qingqing Zhuo 2023-08-02 993 struct clk_mgr_internal
*clk_mgr_int = TO_CLK_MGR_INTERNAL(clk_mgr);
8774029f76b980 Qingqing Zhuo 2023-08-02 994 struct dc_clocks *new_clocks =
&context->bw_ctx.bw.dcn.clk;
8774029f76b980 Qingqing Zhuo 2023-08-02 995 int fclk_adj =
new_clocks->fclk_khz;
8774029f76b980 Qingqing Zhuo 2023-08-02 996
8774029f76b980 Qingqing Zhuo 2023-08-02 997 /* TODO: remove this after
correctly set by DML */
8774029f76b980 Qingqing Zhuo 2023-08-02 998 new_clocks->dcfclk_khz = 40;
8774029f76b980 Qingqing Zhuo 2023-08-02 999 new_clocks->socclk_khz = 40;
8774029f76b980 Qingqing Zhuo 2023-08-02 1000
8774029f76b980 Qingqing Zhuo 2023-08-02 1001 /* Min fclk = 1.2GHz since all
the extra scemi logic seems to run off of it */
8774029f76b980 Qingqing Zhuo 2023-08-02 1002 //int fclk_adj =
new_clocks->fclk_khz > 120 ? new_clocks->fclk_khz : 120;
8774029f76b980 Qingqing Zhuo 2023-08-02 1003 new_clocks->fclk_khz = 432;
8774029f76b980 Qingqing Zhuo 2023-08-02 1004
8774029f76b980 Qingqing Zhuo 2023-08-02 1005 if
(should_set_clock(safe_to_lower, new_clocks->phyclk_khz,
clk_mgr->clks.phyclk_khz)) {
8774029f76b980 Qingqing Zhuo 2023-08-02 1006
clk_mgr->clks.phyclk_khz = new_clocks->phyclk_khz;
8774029f76b980 Qingqing Zhuo 2023-08-02 1007 }
8774029f76b980 Qingqing Zhuo 2023-08-02 1008
8774029f76b980 Qingqing Zhuo 2023-08-02 1009 if
(should_set_clock(safe_to_lower, new_clocks->dcfclk_khz,
clk_mgr->clks.dcfclk_khz)) {
8774029f76b980 Qingqing Zhuo 2023-08-02 1010
clk_mgr->clks.dcfclk_khz = new_clocks->dcfclk_khz;
8774029f76b980 Qingqing Zhuo 2023-08-02 1011 }
8774029f76b980 Qingqing Zhuo 2023-08-02 1012
8774029f76b980 Qingqing Zhuo 2023-08-02 1013 if
(should_set_clock(safe_to_lower,
8774029f76b980 Qingqing Zhuo 2023-08-02 1014
new_clocks->dcfclk_deep_sleep_khz, clk_mgr->clks.dcfclk_deep_sleep_khz)) {
8774029f76b980 Qingqing Zhuo 2023-08-02 1015
clk_mgr->clks.dcfclk_deep_sleep_khz = new_clocks->dcfclk_deep_sleep_khz;
8774029f76b980 Qingqing Zhuo 2023-08-02 1016 }
8774029f76b980 Qingqing Zhuo 2023-08-02 1017
8774029f76b980 Qingqing Zhuo 2023-08-02 1018 if
(should_set_clock(safe_to_lower, new_
Re: [PATCH v5 20/44] drm/tests: Add a few tests around drm_fixed.h
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.11-rc4 next-20240822]
[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/20240820-050138
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20240819205714.316380-21-harry.wentland%40amd.com
patch subject: [PATCH v5 20/44] drm/tests: Add a few tests around drm_fixed.h
config: um-randconfig-r123-20240821
(https://download.01.org/0day-ci/archive/20240822/20240809.vpdzqng3-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
26670e7fa4f032a019d23d56c6a02926e854e8af)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240822/20240809.vpdzqng3-...@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/20240809.vpdzqng3-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/tests/drm_fixp_test.c:11:59: error: overflow in expression;
>> result is 9'223'372'036'854'775'807 with type 'long long'
>> [-Werror,-Winteger-overflow]
11 | KUNIT_EXPECT_EQ(test, 0x7fffll, ((1LL << 63) -
1));
| ^~~
include/kunit/test.h:917:34: note: expanded from macro 'KUNIT_EXPECT_EQ'
917 | KUNIT_EXPECT_EQ_MSG(test, left, right, NULL)
| ^
include/kunit/test.h:922:18: note: expanded from macro 'KUNIT_EXPECT_EQ_MSG'
922 |left, ==, right,
\
| ^
include/kunit/test.h:758:19: note: expanded from macro
'KUNIT_BINARY_INT_ASSERTION'
758 | left, op, right,
\
| ^
include/kunit/test.h:725:33: note: expanded from macro
'KUNIT_BASE_BINARY_ASSERTION'
725 | const typeof(right) __right = (right);
\
|^
1 error generated.
vim +11 drivers/gpu/drm/tests/drm_fixp_test.c
8
9 static void drm_test_sm2fixp(struct kunit *test)
10 {
> 11 KUNIT_EXPECT_EQ(test, 0x7fffll, ((1LL << 63) - 1));
12
13 /* 1 */
14 KUNIT_EXPECT_EQ(test, drm_int2fixp(1), drm_sm2fixp(1ull <<
DRM_FIXED_POINT));
15
16 /* -1 */
17 KUNIT_EXPECT_EQ(test, drm_int2fixp(-1), drm_sm2fixp((1ull <<
63) | (1ull << DRM_FIXED_POINT)));
18
19 /* 0.5 */
20 KUNIT_EXPECT_EQ(test, drm_fixp_from_fraction(1, 2),
drm_sm2fixp(1ull << (DRM_FIXED_POINT - 1)));
21
22 /* -0.5 */
23 KUNIT_EXPECT_EQ(test, drm_fixp_from_fraction(-1, 2),
drm_sm2fixp((1ull << 63) | (1ull << (DRM_FIXED_POINT - 1;
24
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH] drm: komeda: Fix an issue related to normalized zpos
Hi hongchi.peng, 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.11-rc4 next-20240822] [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/hongchi-peng/drm-komeda-Fix-an-issue-related-to-normalized-zpos/20240822-045334 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240821085613.5408-1-hongchi.peng%40siengine.com patch subject: [PATCH] drm: komeda: Fix an issue related to normalized zpos config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20240822/202408222146.r7e6lcgh-...@intel.com/config) compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 26670e7fa4f032a019d23d56c6a02926e854e8af) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240822/202408222146.r7e6lcgh-...@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/202408222146.r7e6lcgh-...@intel.com/ All errors (new ones prefixed by >>): In file included from drivers/gpu/drm/arm/display/komeda/komeda_kms.c:7: 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/arm/display/komeda/komeda_kms.c:7: 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/arm/display/komeda/komeda_kms.c:7: 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: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)cp
Re: [PATCH V3 4/9] drm/vc4: hdmi: add PM suspend/resume support
Hi Stefan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on arm/for-next arm/fixes v6.11-rc4 next-20240822]
[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/Stefan-Wahren/mailbox-bcm2835-Fix-timeout-during-suspend-mode/20240822-063725
base: linus/master
patch link:
https://lore.kernel.org/r/20240821214052.6800-5-wahrenst%40gmx.net
patch subject: [PATCH V3 4/9] drm/vc4: hdmi: add PM suspend/resume support
config: arc-allmodconfig
(https://download.01.org/0day-ci/archive/20240822/202408221940.t4pwjzvz-...@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/20240822/202408221940.t4pwjzvz-...@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/202408221940.t4pwjzvz-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/vc4/vc4_hdmi.c:3118:12: warning: 'vc4_hdmi_resume' defined
>> but not used [-Wunused-function]
3118 | static int vc4_hdmi_resume(struct device *dev)
|^~~
>> drivers/gpu/drm/vc4/vc4_hdmi.c:3107:12: warning: 'vc4_hdmi_suspend' defined
>> but not used [-Wunused-function]
3107 | static int vc4_hdmi_suspend(struct device *dev)
|^~~~
vim +/vc4_hdmi_resume +3118 drivers/gpu/drm/vc4/vc4_hdmi.c
3106
> 3107 static int vc4_hdmi_suspend(struct device *dev)
3108 {
3109 struct vc4_hdmi *vc4_hdmi = dev_get_drvdata(dev);
3110 struct drm_device *drm = vc4_hdmi->connector.dev;
3111
3112 if (drm && drm->mode_config.poll_enabled)
3113 drm_kms_helper_poll_disable(drm);
3114
3115 return pm_runtime_force_suspend(dev);
3116 }
3117
> 3118 static int vc4_hdmi_resume(struct device *dev)
3119 {
3120 struct vc4_hdmi *vc4_hdmi = dev_get_drvdata(dev);
3121 struct drm_device *drm = vc4_hdmi->connector.dev;
3122 int ret;
3123
3124 ret = pm_runtime_force_resume(dev);
3125
3126 if (drm && drm->mode_config.poll_enabled)
3127 drm_kms_helper_poll_enable(drm);
3128
3129 return ret;
3130 }
3131
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH] drm: komeda: Fix an issue related to normalized zpos
Hi hongchi.peng, 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.11-rc4 next-20240822] [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/hongchi-peng/drm-komeda-Fix-an-issue-related-to-normalized-zpos/20240822-045334 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240821085613.5408-1-hongchi.peng%40siengine.com patch subject: [PATCH] drm: komeda: Fix an issue related to normalized zpos config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20240822/202408222005.pr9vj8sj-...@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/20240822/202408222005.pr9vj8sj-...@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/202408222005.pr9vj8sj-...@intel.com/ All errors (new ones prefixed by >>): In file included from : drivers/gpu/drm/arm/display/komeda/komeda_kms.c: In function 'komeda_crtc_normalize_zpos': >> include/linux/compiler_types.h:510:45: error: call to >> '__compiletime_assert_301' declared with attribute error: max(slave_zpos, >> kcrtc_st->max_slave_zorder) signedness error 510 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) | ^ include/linux/compiler_types.h:491:25: note: in definition of macro '__compiletime_assert' 491 | prefix ## suffix(); \ | ^~ include/linux/compiler_types.h:510:9: note: in expansion of macro '_compiletime_assert' 510 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) | ^~~ include/linux/build_bug.h:39:37: note: in expansion of macro 'compiletime_assert' 39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg) | ^~ include/linux/minmax.h:100:9: note: in expansion of macro 'BUILD_BUG_ON_MSG' 100 | BUILD_BUG_ON_MSG(!__types_ok(x,y,ux,uy),\ | ^~~~ include/linux/minmax.h:105:9: note: in expansion of macro '__careful_cmp_once' 105 | __careful_cmp_once(op, x, y, __UNIQUE_ID(x_), __UNIQUE_ID(y_)) | ^~ include/linux/minmax.h:136:25: note: in expansion of macro '__careful_cmp' 136 | #define max(x, y) __careful_cmp(max, x, y) | ^ drivers/gpu/drm/arm/display/komeda/komeda_kms.c:207:33: note: in expansion of macro 'max' 207 | max(slave_zpos, kcrtc_st->max_slave_zorder); | ^~~ vim +/__compiletime_assert_301 +510 include/linux/compiler_types.h eb5c2d4b45e3d2 Will Deacon 2020-07-21 496 eb5c2d4b45e3d2 Will Deacon 2020-07-21 497 #define _compiletime_assert(condition, msg, prefix, suffix) \ eb5c2d4b45e3d2 Will Deacon 2020-07-21 498 __compiletime_assert(condition, msg, prefix, suffix) eb5c2d4b45e3d2 Will Deacon 2020-07-21 499 eb5c2d4b45e3d2 Will Deacon 2020-07-21 500 /** eb5c2d4b45e3d2 Will Deacon 2020-07-21 501 * compiletime_assert - break build and emit msg if condition is false eb5c2d4b45e3d2 Will Deacon 2020-07-21 502 * @condition: a compile-time constant condition to check eb5c2d4b45e3d2 Will Deacon 2020-07-21 503 * @msg: a message to emit if condition is false eb5c2d4b45e3d2 Will Deacon 2020-07-21 504 * eb5c2d4b45e3d2 Will Deacon 2020-07-21 505 * In tradition of POSIX assert, this macro will break the build if the eb5c2d4b45e3d2 Will Deacon 2020-07-21 506 * supplied condition is *false*, emitting the supplied error message if the eb5c2d4b45e3d2 Will Deacon 2020-07-21 507 * compiler has support to do so. eb5c2d4b45e3d2 Will Deacon 2020-07-21 508 */ eb5c2d4b45e3d2 Will Deacon 2020-07-21 509 #define compiletime_assert(condition, msg) \ eb5c2d4b45e3d2 Will Deacon 2020-07-21 @510 _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) eb5c2d4b45e3d2 Will Deacon 2020-07-21 511 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH V3 7/9] usb: dwc2: Refactor backup/restore of registers
Hi Stefan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on arm/for-next arm/fixes v6.11-rc4 next-20240822]
[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/Stefan-Wahren/mailbox-bcm2835-Fix-timeout-during-suspend-mode/20240822-063725
base: linus/master
patch link:
https://lore.kernel.org/r/20240821214052.6800-8-wahrenst%40gmx.net
patch subject: [PATCH V3 7/9] usb: dwc2: Refactor backup/restore of registers
config: x86_64-randconfig-161-20240822
(https://download.01.org/0day-ci/archive/20240822/202408221629.jv9agcrf-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240822/202408221629.jv9agcrf-...@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/202408221629.jv9agcrf-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/usb/dwc2/gadget.c:5605:28: warning: variable 'dr' set but not used
>> [-Wunused-but-set-variable]
5605 | struct dwc2_dregs_backup *dr;
| ^
1 warning generated.
vim +/dr +5605 drivers/usb/dwc2/gadget.c
be2b960e57154a Artur Petrosyan 2021-04-08 5588
be2b960e57154a Artur Petrosyan 2021-04-08 5589 /*
be2b960e57154a Artur Petrosyan 2021-04-08 5590 *
dwc2_gadget_exit_partial_power_down() - Exit controller from device partial
be2b960e57154a Artur Petrosyan 2021-04-08 5591 * power down.
be2b960e57154a Artur Petrosyan 2021-04-08 5592 *
be2b960e57154a Artur Petrosyan 2021-04-08 5593 * @hsotg: Programming view of
the DWC_otg controller
be2b960e57154a Artur Petrosyan 2021-04-08 5594 * @restore: indicates whether
need to restore the registers or not.
be2b960e57154a Artur Petrosyan 2021-04-08 5595 *
be2b960e57154a Artur Petrosyan 2021-04-08 5596 * Return: non-zero if failed
to exit device partial power down.
be2b960e57154a Artur Petrosyan 2021-04-08 5597 *
be2b960e57154a Artur Petrosyan 2021-04-08 5598 * This function is for
exiting from device mode partial power down.
be2b960e57154a Artur Petrosyan 2021-04-08 5599 */
be2b960e57154a Artur Petrosyan 2021-04-08 5600 int
dwc2_gadget_exit_partial_power_down(struct dwc2_hsotg *hsotg,
be2b960e57154a Artur Petrosyan 2021-04-08 5601
bool restore)
be2b960e57154a Artur Petrosyan 2021-04-08 5602 {
be2b960e57154a Artur Petrosyan 2021-04-08 5603 u32 pcgcctl;
be2b960e57154a Artur Petrosyan 2021-04-08 5604 u32 dctl;
be2b960e57154a Artur Petrosyan 2021-04-08 @5605 struct
dwc2_dregs_backup *dr;
be2b960e57154a Artur Petrosyan 2021-04-08 5606 int ret = 0;
be2b960e57154a Artur Petrosyan 2021-04-08 5607
be2b960e57154a Artur Petrosyan 2021-04-08 5608 dr = &hsotg->dr_backup;
be2b960e57154a Artur Petrosyan 2021-04-08 5609
be2b960e57154a Artur Petrosyan 2021-04-08 5610 dev_dbg(hsotg->dev,
"Exiting device partial Power Down started.\n");
be2b960e57154a Artur Petrosyan 2021-04-08 5611
be2b960e57154a Artur Petrosyan 2021-04-08 5612 pcgcctl =
dwc2_readl(hsotg, PCGCTL);
be2b960e57154a Artur Petrosyan 2021-04-08 5613 pcgcctl &=
~PCGCTL_STOPPCLK;
be2b960e57154a Artur Petrosyan 2021-04-08 5614 dwc2_writel(hsotg,
pcgcctl, PCGCTL);
be2b960e57154a Artur Petrosyan 2021-04-08 5615
be2b960e57154a Artur Petrosyan 2021-04-08 5616 pcgcctl =
dwc2_readl(hsotg, PCGCTL);
be2b960e57154a Artur Petrosyan 2021-04-08 5617 pcgcctl &=
~PCGCTL_PWRCLMP;
be2b960e57154a Artur Petrosyan 2021-04-08 5618 dwc2_writel(hsotg,
pcgcctl, PCGCTL);
be2b960e57154a Artur Petrosyan 2021-04-08 5619
be2b960e57154a Artur Petrosyan 2021-04-08 5620 pcgcctl =
dwc2_readl(hsotg, PCGCTL);
be2b960e57154a Artur Petrosyan 2021-04-08 5621 pcgcctl &=
~PCGCTL_RSTPDWNMODULE;
be2b960e57154a Artur Petrosyan 2021-04-08 5622 dwc2_writel(hsotg,
pcgcctl, PCGCTL);
be2b960e57154a Artur Petrosyan 2021-04-08 5623
be2b960e57154a Artur Petrosyan 2021-04-08 5624 udelay(100);
be2b960e57154a Artur Petrosyan 2021-04-08 5625 if (restore) {
78c09c66698a77 Stefan Wahren 2024-08-21 5626 ret =
dwc2_gadget_restore_critical_registers(hsotg);
78c09c66698a77 Stefan Wahren 2024-08-21 5627 if (ret)
be2b960e57154a Artur Petrosyan 2021-04-08 5628
Re: [PATCH v5 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.11-rc4 next-20240821]
[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/20240820-050138
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20240819205714.316380-37-harry.wentland%40amd.com
patch subject: [PATCH v5 36/44] drm/amd/display: add 3x4 matrix colorop
config: parisc-randconfig-001-20240821
(https://download.01.org/0day-ci/archive/20240821/202408211502.ev7fxurd-...@intel.com/config)
compiler: hppa-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240821/202408211502.ev7fxurd-...@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/202408211502.ev7fxurd-...@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 '%ld'
>> expects argument of type 'long 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:470:9: note: in expansion of macro 'dev_warn'
470 | dev_##level##type((drm) ? (drm)->dev : NULL, "[drm] " fmt,
##__VA_ARGS__)
| ^~~~
include/drm/drm_print.h:480:9: note: in expansion of macro '__drm_printk'
480 | __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 (%ld) isn't
equal to drm_color_ctm_3x4 (%ld)\n",
| ^~~~
>> drivers/gpu/drm/amd/amdgpu/../amdgpu/amdgpu.h:41:22: error: format '%ld'
>> expects argument of type 'long 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:470:9: note: in expansion of macro 'dev_warn'
470 | dev_##level##type((drm) ? (drm)->dev : NULL, "[drm] " fmt,
##__VA_ARGS__)
| ^~~~
include/drm/drm_print.h:480:9: note: in expansion of macro '__drm_printk'
480 | __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, "b
Re: [PATCH v5 28/44] drm/amd/display: Add support for sRGB Inverse EOTF in SHAPER 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-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip
linus/master v6.11-rc4 next-20240820]
[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/20240820-050138
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20240819205714.316380-29-harry.wentland%40amd.com
patch subject: [PATCH v5 28/44] drm/amd/display: Add support for sRGB Inverse
EOTF in SHAPER block
config: x86_64-randconfig-003-20240821
(https://download.01.org/0day-ci/archive/20240821/202408211241.xavubshv-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240821/202408211241.xavubshv-...@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/202408211241.xavubshv-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_color.c:1232:42:
>> warning: variable 'shaper_size' is uninitialized when used here
>> [-Wuninitialized]
1232 | return __set_output_tf(tf, shaper_lut, shaper_size,
false);
|^~~
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_color.c:1214:22:
note: initialize the variable 'shaper_size' to silence this warning
1214 | uint32_t shaper_size;
| ^
| = 0
1 warning generated.
vim +/shaper_size +1232
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_color.c
1205
1206 static int
1207 __set_colorop_in_shaper_1d_curve(struct dc_plane_state *dc_plane_state,
1208 struct drm_colorop_state *colorop_state)
1209 {
1210 struct dc_transfer_func *tf = &dc_plane_state->in_shaper_func;
1211 struct drm_colorop *colorop = colorop_state->colorop;
1212 struct drm_device *drm = colorop->dev;
1213 const struct drm_color_lut *shaper_lut;
1214 uint32_t shaper_size;
1215
1216 if (colorop->type != DRM_COLOROP_1D_CURVE &&
1217 colorop_state->curve_1d_type !=
DRM_COLOROP_1D_CURVE_SRGB_INV_EOTF)
1218 return -EINVAL;
1219
1220 if (colorop_state->bypass) {
1221 tf->type = TF_TYPE_BYPASS;
1222 tf->tf = TRANSFER_FUNCTION_LINEAR;
1223 return 0;
1224 }
1225
1226 drm_dbg(drm, "Shaper colorop with ID: %d\n", colorop->base.id);
1227
1228 if (colorop->type == DRM_COLOROP_1D_CURVE) {
1229 tf->type = TF_TYPE_DISTRIBUTED_POINTS;
1230 tf->tf =
amdgpu_colorop_tf_to_dc_tf(colorop_state->curve_1d_type);
1231 tf->sdr_ref_white_level = SDR_WHITE_LEVEL_INIT_VALUE;
> 1232 return __set_output_tf(tf, shaper_lut, shaper_size,
> false);
1233 }
1234
1235 return -EINVAL;
1236 }
1237
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v5 20/44] drm/tests: Add a few tests around drm_fixed.h
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.11-rc4 next-20240820]
[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/20240820-050138
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20240819205714.316380-21-harry.wentland%40amd.com
patch subject: [PATCH v5 20/44] drm/tests: Add a few tests around drm_fixed.h
config: parisc-randconfig-001-20240821
(https://download.01.org/0day-ci/archive/20240821/202408211157.n8ubzpfl-...@intel.com/config)
compiler: hppa-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240821/202408211157.n8ubzpfl-...@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/202408211157.n8ubzpfl-...@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/tests/drm_fixp_test.c:6:
drivers/gpu/drm/tests/drm_fixp_test.c: In function 'drm_test_sm2fixp':
>> drivers/gpu/drm/tests/drm_fixp_test.c:11:66: error: integer overflow in
>> expression of type 'long long int' results in '9223372036854775807'
>> [-Werror=overflow]
11 | KUNIT_EXPECT_EQ(test, 0x7fffll, ((1LL << 63) -
1));
| ^
include/kunit/test.h:725:40: note: in definition of macro
'KUNIT_BASE_BINARY_ASSERTION'
725 | const typeof(right) __right = (right);
\
|^
include/kunit/test.h:920:9: note: in expansion of macro
'KUNIT_BINARY_INT_ASSERTION'
920 | KUNIT_BINARY_INT_ASSERTION(test,
\
| ^~
include/kunit/test.h:917:9: note: in expansion of macro 'KUNIT_EXPECT_EQ_MSG'
917 | KUNIT_EXPECT_EQ_MSG(test, left, right, NULL)
| ^~~
drivers/gpu/drm/tests/drm_fixp_test.c:11:9: note: in expansion of macro
'KUNIT_EXPECT_EQ'
11 | KUNIT_EXPECT_EQ(test, 0x7fffll, ((1LL << 63) -
1));
| ^~~
cc1: all warnings being treated as errors
vim +11 drivers/gpu/drm/tests/drm_fixp_test.c
8
9 static void drm_test_sm2fixp(struct kunit *test)
10 {
> 11 KUNIT_EXPECT_EQ(test, 0x7fffll, ((1LL << 63) - 1));
12
13 /* 1 */
14 KUNIT_EXPECT_EQ(test, drm_int2fixp(1), drm_sm2fixp(1ull <<
DRM_FIXED_POINT));
15
16 /* -1 */
17 KUNIT_EXPECT_EQ(test, drm_int2fixp(-1), drm_sm2fixp((1ull <<
63) | (1ull << DRM_FIXED_POINT)));
18
19 /* 0.5 */
20 KUNIT_EXPECT_EQ(test, drm_fixp_from_fraction(1, 2),
drm_sm2fixp(1ull << (DRM_FIXED_POINT - 1)));
21
22 /* -0.5 */
23 KUNIT_EXPECT_EQ(test, drm_fixp_from_fraction(-1, 2),
drm_sm2fixp((1ull << 63) | (1ull << (DRM_FIXED_POINT - 1;
24
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v5 36/44] drm/amd/display: add 3x4 matrix colorop
Hi Harry,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-intel/for-linux-next
drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip
linus/master v6.11-rc4 next-20240820]
[cannot apply to drm-exynos/exynos-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/Harry-Wentland/drm-Add-helper-for-conversion-from-signed-magnitude/20240820-050138
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20240819205714.316380-37-harry.wentland%40amd.com
patch subject: [PATCH v5 36/44] drm/amd/display: add 3x4 matrix colorop
config: arm-randconfig-002-20240821
(https://download.01.org/0day-ci/archive/20240821/202408211016.tkund7h3-...@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/20240821/202408211016.tkund7h3-...@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/202408211016.tkund7h3-...@intel.com/
All warnings (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: warning: format '%ld'
>> expects argument of type 'long int', but argument 3 has type 'size_t' {aka
>> 'unsigned int'} [-Wformat=]
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:470:9: note: in expansion of macro 'dev_warn'
470 | dev_##level##type((drm) ? (drm)->dev : NULL, "[drm] " fmt,
##__VA_ARGS__)
| ^~~~
include/drm/drm_print.h:480:9: note: in expansion of macro '__drm_printk'
480 | __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 (%ld) isn't
equal to drm_color_ctm_3x4 (%ld)\n",
| ^~~~
>> drivers/gpu/drm/amd/amdgpu/../amdgpu/amdgpu.h:41:22: warning: format '%ld'
>> expects argument of type 'long int', but argument 4 has type 'unsigned int'
>> [-Wformat=]
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:470:9: note: in expansion of macro 'dev_warn'
470 | dev_##level##type((drm) ? (drm)->dev : NULL, "[drm] " fmt,
##__VA_ARGS__)
| ^~~~
include/drm/drm_print.h:480:9: note: in expansion of macro '__drm_printk'
480 | __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 |
Re: [PATCH V2] video/aperture: match the pci device when calling sysfb_disable()
Hi Alex, kernel test robot noticed the following build warnings: [auto build test WARNING on drm-tip/drm-tip] [also build test WARNING on robh/for-next drm-misc/drm-misc-next linus/master v6.11-rc4 next-20240820] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Alex-Deucher/video-aperture-match-the-pci-device-when-calling-sysfb_disable/20240820-005528 base: git://anongit.freedesktop.org/drm/drm-tip drm-tip patch link: https://lore.kernel.org/r/20240819165341.799848-1-alexander.deucher%40amd.com patch subject: [PATCH V2] video/aperture: match the pci device when calling sysfb_disable() config: i386-randconfig-054-20240820 (https://download.01.org/0day-ci/archive/20240821/202408210620.ntcwlpco-...@intel.com/config) compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240821/202408210620.ntcwlpco-...@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/202408210620.ntcwlpco-...@intel.com/ All warnings (new ones prefixed by >>, old ones prefixed by <<): >> WARNING: modpost: vmlinux: section mismatch in reference: sysfb_disable+0x7a >> (section: .text) -> sysfb_pci_dev_is_enabled (section: .init.text) WARNING: modpost: missing MODULE_DESCRIPTION() in lib/test_objpool.o WARNING: modpost: missing MODULE_DESCRIPTION() in lib/asn1_decoder.o -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3 09/17] drm/bridge: dp_typec: Allow users to hook hpd notify path
Hi Stephen,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 8400291e289ee6b2bf9779ff1c83a291501f017b]
url:
https://github.com/intel-lab-lkp/linux/commits/Stephen-Boyd/drm-atomic-helper-Introduce-lane-remapping-support-to-bridges/20240820-064107
base: 8400291e289ee6b2bf9779ff1c83a291501f017b
patch link:
https://lore.kernel.org/r/20240819223834.2049862-10-swboyd%40chromium.org
patch subject: [PATCH v3 09/17] drm/bridge: dp_typec: Allow users to hook hpd
notify path
config: arc-allyesconfig
(https://download.01.org/0day-ci/archive/20240820/202408201747.nmpzutog-...@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/20240820/202408201747.nmpzutog-...@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/202408201747.nmpzutog-...@intel.com/
All warnings (new ones prefixed by >>):
drivers/gpu/drm/bridge/aux-hpd-bridge.c:61: warning: Function parameter or
struct member 'orientation_switch' not described in
'drm_dp_typec_bridge_typec_port'
>> drivers/gpu/drm/bridge/aux-hpd-bridge.c:336: warning: Function parameter or
>> struct member 'typec_bridge_dev' not described in
>> 'drm_dp_typec_bridge_add_hpd_notify'
vim +336 drivers/gpu/drm/bridge/aux-hpd-bridge.c
327
328 /**
329 * drm_dp_typec_bridge_add_hpd_notify: Register a callback called when
the
330 * bridge chain hpd state changes
331 * @hpd_notify: callback for bridge hot plug detect events
332 * @hpd_data: data passed to @hpd_notify callback
333 */
334 void drm_dp_typec_bridge_add_hpd_notify(struct drm_dp_typec_bridge_dev
*typec_bridge_dev,
335 hpd_notify_fn_t hpd_notify,
void *hpd_data)
> 336 {
337 typec_bridge_dev->hpd_notify = hpd_notify;
338 typec_bridge_dev->hpd_data = hpd_data;
339 }
340 EXPORT_SYMBOL_GPL(drm_dp_typec_bridge_add_hpd_notify);
341
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3 07/17] drm/bridge: dp_typec: Support USB Type-C orientation
Hi Stephen,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 8400291e289ee6b2bf9779ff1c83a291501f017b]
url:
https://github.com/intel-lab-lkp/linux/commits/Stephen-Boyd/drm-atomic-helper-Introduce-lane-remapping-support-to-bridges/20240820-064107
base: 8400291e289ee6b2bf9779ff1c83a291501f017b
patch link:
https://lore.kernel.org/r/20240819223834.2049862-8-swboyd%40chromium.org
patch subject: [PATCH v3 07/17] drm/bridge: dp_typec: Support USB Type-C
orientation
config: arc-allyesconfig
(https://download.01.org/0day-ci/archive/20240820/202408201530.jpgxbsck-...@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/20240820/202408201530.jpgxbsck-...@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/202408201530.jpgxbsck-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/bridge/aux-hpd-bridge.c:60: warning: Function parameter or
>> struct member 'orientation_switch' not described in
>> 'drm_dp_typec_bridge_typec_port'
vim +60 drivers/gpu/drm/bridge/aux-hpd-bridge.c
c77d47cea15ad1 Stephen Boyd 2024-08-19 46
c77d47cea15ad1 Stephen Boyd 2024-08-19 47 /**
c77d47cea15ad1 Stephen Boyd 2024-08-19 48 * struct
drm_dp_typec_bridge_typec_port - USB type-c port associated with DP bridge
c77d47cea15ad1 Stephen Boyd 2024-08-19 49 * @lane_mapping: Physical (array
index) to logical (array value) USB type-C lane mapping
9edcc62024ff61 Stephen Boyd 2024-08-19 50 * @orientation: Orientation of USB
type-c port
c77d47cea15ad1 Stephen Boyd 2024-08-19 51 * @mode_switch: DP altmode switch
c77d47cea15ad1 Stephen Boyd 2024-08-19 52 * @typec_data: Back pointer to
type-c bridge data
c77d47cea15ad1 Stephen Boyd 2024-08-19 53 */
c77d47cea15ad1 Stephen Boyd 2024-08-19 54 struct
drm_dp_typec_bridge_typec_port {
c77d47cea15ad1 Stephen Boyd 2024-08-19 55 u32 lane_mapping[NUM_USB_SS];
9edcc62024ff61 Stephen Boyd 2024-08-19 56 enum typec_orientation
orientation;
c77d47cea15ad1 Stephen Boyd 2024-08-19 57 struct typec_mux_dev
*mode_switch;
9edcc62024ff61 Stephen Boyd 2024-08-19 58 struct typec_switch_dev
*orientation_switch;
c77d47cea15ad1 Stephen Boyd 2024-08-19 59 struct drm_dp_typec_bridge_data
*typec_data;
c77d47cea15ad1 Stephen Boyd 2024-08-19 @60 };
c77d47cea15ad1 Stephen Boyd 2024-08-19 61
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 2/2] mtd: rawnand: nuvoton: add new driver for the Nuvoton MA35 SoC
Hi Hui-Ping,
kernel test robot noticed the following build warnings:
[auto build test WARNING on mtd/nand/next]
[also build test WARNING on linus/master v6.11-rc4 next-20240820]
[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/Hui-Ping-Chen/dt-bindings-mtd-nuvoton-ma35d1-nand-add-new-bindings/20240819-172155
base: https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git nand/next
patch link:
https://lore.kernel.org/r/20240819092037.110260-3-hpchen0nvt%40gmail.com
patch subject: [PATCH v2 2/2] mtd: rawnand: nuvoton: add new driver for the
Nuvoton MA35 SoC
config: parisc-randconfig-r123-20240820
(https://download.01.org/0day-ci/archive/20240820/202408201329.v0sof3es-...@intel.com/config)
compiler: hppa-linux-gcc (GCC) 14.1.0
reproduce:
(https://download.01.org/0day-ci/archive/20240820/202408201329.v0sof3es-...@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/202408201329.v0sof3es-...@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:231:20: sparse: sparse: cast
removes address space '__iomem' of expression
>> drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:736:20: sparse: sparse: incorrect
>> type in initializer (different address spaces) @@ expected unsigned char
>> [usertype] *ptr @@ got unsigned char [noderef] [usertype] __iomem * @@
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:736:20: sparse: expected
unsigned char [usertype] *ptr
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:736:20: sparse: got unsigned
char [noderef] [usertype] __iomem *
>> drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:764:22: sparse: sparse: incorrect
>> type in initializer (different address spaces) @@ expected char *ptr @@
>>got char [noderef] __iomem * @@
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:764:22: sparse: expected char
*ptr
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:764:22: sparse: got char
[noderef] __iomem *
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:803:22: sparse: sparse: incorrect
type in initializer (different address spaces) @@ expected char *ptr @@
got char [noderef] __iomem * @@
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:803:22: sparse: expected char
*ptr
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:803:22: sparse: got char
[noderef] __iomem *
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:506:28: sparse: sparse: incorrect
type in initializer (different address spaces) @@ expected unsigned char
[usertype] *ptr @@ got unsigned char [noderef] [usertype] __iomem * @@
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:506:28: sparse: expected
unsigned char [usertype] *ptr
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:506:28: sparse: got unsigned
char [noderef] [usertype] __iomem *
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:506:28: sparse: sparse: incorrect
type in initializer (different address spaces) @@ expected unsigned char
[usertype] *ptr @@ got unsigned char [noderef] [usertype] __iomem * @@
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:506:28: sparse: expected
unsigned char [usertype] *ptr
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:506:28: sparse: got unsigned
char [noderef] [usertype] __iomem *
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:506:28: sparse: sparse: incorrect
type in initializer (different address spaces) @@ expected unsigned char
[usertype] *ptr @@ got unsigned char [noderef] [usertype] __iomem * @@
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:506:28: sparse: expected
unsigned char [usertype] *ptr
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:506:28: sparse: got unsigned
char [noderef] [usertype] __iomem *
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:506:28: sparse: sparse: incorrect
type in initializer (different address spaces) @@ expected unsigned char
[usertype] *ptr @@ got unsigned char [noderef] [usertype] __iomem * @@
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:506:28: sparse: expected
unsigned char [usertype] *ptr
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:506:28: sparse: got unsigned
char [noderef] [usertype] __iomem *
vim +736 drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c
731
732 static int ma35_nand_write_page_hwecc(struct nand_chip *chip, const u8
*buf,
733int oob_required, int page)
734 {
735 struct ma35_nand_info *nand = nand_get_controller_data(chip);
> 736 u8 *ptr = (u8 __iomem *)(nand->regs + MA35_NFI_REG_NANDRA
Re: [PATCH v2 3/5] drm/log: Introduce a new boot logger to draw the kmsg on the screen
Hi Jocelyn, kernel test robot noticed the following build warnings: [auto build test WARNING on 8befe8fa5a4e4b30787b17e078d9d7b5cb92ea19] url: https://github.com/intel-lab-lkp/linux/commits/Jocelyn-Falempe/drm-panic-Squash-of-pending-series/20240816-205859 base: 8befe8fa5a4e4b30787b17e078d9d7b5cb92ea19 patch link: https://lore.kernel.org/r/20240816125612.1003295-4-jfalempe%40redhat.com patch subject: [PATCH v2 3/5] drm/log: Introduce a new boot logger to draw the kmsg on the screen config: arm-randconfig-r121-20240818 (https://download.01.org/0day-ci/archive/20240818/202408181614.aar0qm24-...@intel.com/config) compiler: arm-linux-gnueabi-gcc (GCC) 14.1.0 reproduce: (https://download.01.org/0day-ci/archive/20240818/202408181614.aar0qm24-...@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/202408181614.aar0qm24-...@intel.com/ sparse warnings: (new ones prefixed by >>) >> drivers/gpu/drm/drm_log.c:66:17: sparse: sparse: symbol 'drm_log_buf' was >> not declared. Should it be static? >> drivers/gpu/drm/drm_log.c:384:1: sparse: sparse: symbol 'drm_log_work' was >> not declared. Should it be static? drivers/gpu/drm/drm_log.c: note: in included file (through include/linux/rculist.h, include/linux/console.h): include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true vim +/drm_log_buf +66 drivers/gpu/drm/drm_log.c 59 60 /* 61 * A circular buffer, with the last kmsg logs to print. 62 * 8K is more than what can be drawn on most monitors. 63 */ 64 #define CIRC_BUF_SIZE (1 << 13) 65 #define CIRC_BUF_MASK (CIRC_BUF_SIZE - 1) > 66 struct circ_buf drm_log_buf; 67 static DEFINE_SPINLOCK(drm_log_writer_lock); 68 static DEFINE_SPINLOCK(drm_log_reader_lock); 69 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH 4/7] drm/msm/A6xx: Implement preemption for A7XX targets
Hi Antonino,
kernel test robot noticed the following build errors:
[auto build test ERROR on 7c626ce4bae1ac14f60076d00eafe71af30450ba]
url:
https://github.com/intel-lab-lkp/linux/commits/Antonino-Maniscalco/drm-msm-Fix-bv_fence-being-used-as-bv_rptr/20240816-023442
base: 7c626ce4bae1ac14f60076d00eafe71af30450ba
patch link:
https://lore.kernel.org/r/20240815-preemption-a750-t-v1-4-7bda26c34037%40gmail.com
patch subject: [PATCH 4/7] drm/msm/A6xx: Implement preemption for A7XX targets
config: x86_64-buildonly-randconfig-001-20240818
(https://download.01.org/0day-ci/archive/20240818/202408180848.cwzpm85g-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240818/202408180848.cwzpm85g-...@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/202408180848.cwzpm85g-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/msm/adreno/a6xx_preempt.c:49:17: error: unused variable
>> 'cur_wptr' [-Werror,-Wunused-variable]
49 | uint32_t wptr, cur_wptr;
|^~~~
1 error generated.
vim +/cur_wptr +49 drivers/gpu/drm/msm/adreno/a6xx_preempt.c
44
45 /* Write the most recent wptr for the given ring into the hardware */
46 static inline void update_wptr(struct msm_gpu *gpu, struct
msm_ringbuffer *ring)
47 {
48 unsigned long flags;
> 49 uint32_t wptr, cur_wptr;
50
51 if (!ring)
52 return;
53
54 spin_lock_irqsave(&ring->preempt_lock, flags);
55
56 if (ring->skip_inline_wptr) {
57 wptr = get_wptr(ring);
58
59 gpu_write(gpu, REG_A6XX_CP_RB_WPTR, wptr);
60
61 ring->skip_inline_wptr = false;
62 }
63
64 spin_unlock_irqrestore(&ring->preempt_lock, flags);
65 }
66
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH] Fix warning: symbol 'dcn3_14_ip' was not declared. Should it be static? in dcn314_fpu.c
Hi Dipendra, 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-rc3 next-20240816] [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/Dipendra-Khadka/Fix-warning-symbol-dcn3_14_ip-was-not-declared-Should-it-be-static-in-dcn314_fpu-c/20240816-025925 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240815185629.65725-1-kdipendra88%40gmail.com patch subject: [PATCH] Fix warning: symbol 'dcn3_14_ip' was not declared. Should it be static? in dcn314_fpu.c config: x86_64-randconfig-121-20240816 (https://download.01.org/0day-ci/archive/20240818/202408180054.z1y6mfuo-...@intel.com/config) compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240818/202408180054.z1y6mfuo-...@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/202408180054.z1y6mfuo-...@intel.com/ All errors (new ones prefixed by >>, old ones prefixed by <<): WARNING: modpost: missing MODULE_DESCRIPTION() in kernel/locking/test-ww_mutex.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/usb/serial/usb_debug.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/usb/serial/mxuport.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/usb/serial/navman.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/usb/serial/qcaux.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/usb/serial/symbolserial.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/devfreq/governor_userspace.o >> ERROR: modpost: "dcn3_14_ip" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] >> undefined! -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH 83/86] drm/{i915,xe}: Run DRM default client setup
Hi Thomas,
kernel test robot noticed the following build errors:
[auto build test ERROR on 70d6d55dea574b7b78ccf714699cc5d8d62fcc2c]
url:
https://github.com/intel-lab-lkp/linux/commits/Thomas-Zimmermann/drm-fbdev-helper-Move-color-mode-lookup-into-4CC-format-helper/20240816-210651
base: 70d6d55dea574b7b78ccf714699cc5d8d62fcc2c
patch link:
https://lore.kernel.org/r/20240816125408.310253-84-tzimmermann%40suse.de
patch subject: [PATCH 83/86] drm/{i915,xe}: Run DRM default client setup
config: riscv-allyesconfig
(https://download.01.org/0day-ci/archive/20240817/202408171913.l3jtjyjx-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
26670e7fa4f032a019d23d56c6a02926e854e8af)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240817/202408171913.l3jtjyjx-...@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/202408171913.l3jtjyjx-...@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/xe/xe_device.c:6:
In file included from drivers/gpu/drm/xe/xe_device.h:9:
In file included from include/drm/drm_util.h:35:
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:2228:
include/linux/vmstat.h:500:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
500 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
501 |item];
|
include/linux/vmstat.h:507:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
507 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
508 |NR_VM_NUMA_EVENT_ITEMS +
|~~
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_"
| ~~~ ^ ~~~
include/linux/vmstat.h:519:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
519 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
520 |NR_VM_NUMA_EVENT_ITEMS +
|~~
include/linux/vmstat.h:528:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
528 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
529 |NR_VM_NUMA_EVENT_ITEMS +
|~~
>> drivers/gpu/drm/xe/xe_device.c:20:10: fatal error: 'intel_fbdev.h' file not
>> found
20 | #include "intel_fbdev.h"
| ^~~~~~~
5 warnings and 1 error generated.
vim +20 drivers/gpu/drm/xe/xe_device.c
19
> 20 #include "intel_fbdev.h"
21
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 83/86] drm/{i915,xe}: Run DRM default client setup
Hi Thomas,
kernel test robot noticed the following build errors:
[auto build test ERROR on 70d6d55dea574b7b78ccf714699cc5d8d62fcc2c]
url:
https://github.com/intel-lab-lkp/linux/commits/Thomas-Zimmermann/drm-fbdev-helper-Move-color-mode-lookup-into-4CC-format-helper/20240816-210651
base: 70d6d55dea574b7b78ccf714699cc5d8d62fcc2c
patch link:
https://lore.kernel.org/r/20240816125408.310253-84-tzimmermann%40suse.de
patch subject: [PATCH 83/86] drm/{i915,xe}: Run DRM default client setup
config: openrisc-allyesconfig
(https://download.01.org/0day-ci/archive/20240817/202408171746.ju5kg2d3-...@intel.com/config)
compiler: or1k-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240817/202408171746.ju5kg2d3-...@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/202408171746.ju5kg2d3-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/xe/xe_device.c:20:10: fatal error: intel_fbdev.h: No such
>> file or directory
20 | #include "intel_fbdev.h"
| ^~~
compilation terminated.
vim +20 drivers/gpu/drm/xe/xe_device.c
19
> 20 #include "intel_fbdev.h"
21
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH] Fix warning: symbol 'dcn3_14_ip' was not declared. Should it be static? in dcn314_fpu.c
Hi Dipendra, 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-rc3 next-20240816] [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/Dipendra-Khadka/Fix-warning-symbol-dcn3_14_ip-was-not-declared-Should-it-be-static-in-dcn314_fpu-c/20240816-025925 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240815185629.65725-1-kdipendra88%40gmail.com patch subject: [PATCH] Fix warning: symbol 'dcn3_14_ip' was not declared. Should it be static? in dcn314_fpu.c config: x86_64-randconfig-002-20240816 (https://download.01.org/0day-ci/archive/20240817/202408170525.giopwt8a-...@intel.com/config) compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240817/202408170525.giopwt8a-...@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/202408170525.giopwt8a-...@intel.com/ All errors (new ones prefixed by >>): >> ld.lld: error: undefined symbol: dcn3_14_ip >>> referenced by dcn314_resource.c:0 (drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn314/dcn314_resource.c:0) >>> drivers/gpu/drm/amd/display/dc/resource/dcn314/dcn314_resource.o:(dcn314_create_resource_pool) in archive vmlinux.a >>> referenced by dcn314_resource.c:1093 (drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn314/dcn314_resource.c:1093) >>> drivers/gpu/drm/amd/display/dc/resource/dcn314/dcn314_resource.o:(dcn314_create_resource_pool) in archive vmlinux.a >>> referenced by dcn314_resource.c:1093 (drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn314/dcn314_resource.c:1093) >>> drivers/gpu/drm/amd/display/dc/resource/dcn314/dcn314_resource.o:(dcn314_create_resource_pool) in archive vmlinux.a >>> referenced 13 more times >>> did you mean: dcn3_15_ip >>> defined in: vmlinux.a(drivers/gpu/drm/amd/display/dc/dml/dcn31/dcn31_fpu.o) -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v8 5/6] drm/xe: Add a shrinker for xe bos
Hi Thomas,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20240816]
[cannot apply to drm-xe/drm-xe-next linus/master v6.11-rc3 v6.11-rc2 v6.11-rc1
v6.11-rc3]
[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-Hellstr-m/drm-ttm-Add-a-virtual-base-class-for-graphics-memory-backup/20240816-213947
base: next-20240816
patch link:
https://lore.kernel.org/r/20240816133717.3102-6-thomas.hellstrom%40linux.intel.com
patch subject: [PATCH v8 5/6] drm/xe: Add a shrinker for xe bos
config: s390-allmodconfig
(https://download.01.org/0day-ci/archive/20240817/202408170320.ssodtn1a-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
26670e7fa4f032a019d23d56c6a02926e854e8af)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240817/202408170320.ssodtn1a-...@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/202408170320.ssodtn1a-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/gpu/drm/xe/xe_bo.c:6:
In file included from drivers/gpu/drm/xe/xe_bo.h:9:
In file included from include/drm/ttm/ttm_tt.h:30:
In file included from include/linux/pagemap.h:8:
In file included from include/linux/mm.h:2199:
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/gpu/drm/xe/xe_bo.c:6:
In file included from drivers/gpu/drm/xe/xe_bo.h:11:
In file included from drivers/gpu/drm/xe/xe_bo_types.h:9:
In file included from include/linux/iosys-map.h:10:
In file included from include/linux/io.h:14:
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/gpu/drm/xe/xe_bo.c:6:
In file included from drivers/gpu/drm/xe/xe_bo.h:11:
In file included from drivers/gpu/drm/xe/xe_bo_types.h:9:
In file included from include/linux/iosys-map.h:10:
In file included from include/linux/io.h:14:
In file included from arch/s390/include/asm/io.h:93:
inc
Re: [PATCH v8 3/6] drm/ttm: Use fault-injection to test error paths
Hi Thomas,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20240816]
[also build test ERROR on v6.11-rc3]
[cannot apply to drm-xe/drm-xe-next linus/master v6.11-rc3 v6.11-rc2 v6.11-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-Hellstr-m/drm-ttm-Add-a-virtual-base-class-for-graphics-memory-backup/20240816-213947
base: next-20240816
patch link:
https://lore.kernel.org/r/20240816133717.3102-4-thomas.hellstrom%40linux.intel.com
patch subject: [PATCH v8 3/6] drm/ttm: Use fault-injection to test error paths
config: x86_64-rhel-8.3-rust
(https://download.01.org/0day-ci/archive/20240817/202408170144.n7yowtcx-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240817/202408170144.n7yowtcx-...@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/202408170144.n7yowtcx-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/ttm/ttm_pool.c:456:8: error: call to undeclared function
>> 'should_fail'; ISO C99 and later do not support implicit function
>> declarations [-Wimplicit-function-declaration]
456 | should_fail(&backup_fault_inject, 1)) {
| ^
>> drivers/gpu/drm/ttm/ttm_pool.c:456:21: error: use of undeclared identifier
>> 'backup_fault_inject'
456 | should_fail(&backup_fault_inject, 1)) {
| ^
drivers/gpu/drm/ttm/ttm_pool.c:908:44: error: call to undeclared function
'should_fail'; ISO C99 and later do not support implicit function declarations
[-Wimplicit-function-declaration]
908 | if (IS_ENABLED(CONFIG_FAULT_INJECTION) &&
should_fail(&backup_fault_inject, 1))
| ^
drivers/gpu/drm/ttm/ttm_pool.c:908:57: error: use of undeclared identifier
'backup_fault_inject'
908 | if (IS_ENABLED(CONFIG_FAULT_INJECTION) &&
should_fail(&backup_fault_inject, 1))
|^
4 errors generated.
vim +/should_fail +456 drivers/gpu/drm/ttm/ttm_pool.c
434
435 static int ttm_pool_restore_tt(struct ttm_pool_tt_restore *restore,
436 struct ttm_backup *backup,
437 struct ttm_operation_ctx *ctx)
438 {
439 static unsigned long __maybe_unused swappedin;
440 unsigned int i, nr = 1 << restore->order;
441 int ret = 0;
442
443 if (!ttm_pool_restore_valid(restore))
444 return 0;
445
446 for (i = restore->restored_pages; i < nr; ++i) {
447 struct page *p = restore->old_pages[i];
448
449 if (ttm_backup_page_ptr_is_handle(p)) {
450 unsigned long handle =
ttm_backup_page_ptr_to_handle(p);
451
452 if (handle == 0)
453 continue;
454
455 if (IS_ENABLED(CONFIG_FAULT_INJECTION) &&
ctx->interruptible &&
> 456 should_fail(&backup_fault_inject, 1)) {
457 ret = -EINTR;
458 break;
459 }
460
461 ret = backup->ops->copy_backed_up_page
462 (backup, restore->first_page[i],
463 handle, ctx->interruptible);
464 if (ret)
465 break;
466
467 backup->ops->drop(backup, handle);
468 } else if (p) {
469 /*
470 * We could probably avoid splitting the old
page
471 * using clever logic, but ATM we don't care.
472 */
473 ttm_pool_split_for_swap(restore->pool, p);
474 copy_highpage(restore->first_page[i], p);
475 __free_pages(p, 0);
476
[drm-misc:topic/rust-drm 9/19] error[E0425]: cannot find function `iounmap` in crate `bindings`
tree: git://anongit.freedesktop.org/drm/drm-misc topic/rust-drm
head: ac3b90930f007514defbf06ec63a07122b02ba8a
commit: 41bf8ed78cc51e13c60dbc7ff755a74ca968b91f [9/19] rust: add `io::Io` base
type
config: um-randconfig-001-20240816
(https://download.01.org/0day-ci/archive/20240817/202408170035.k8vpd6fk-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
26670e7fa4f032a019d23d56c6a02926e854e8af)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240817/202408170035.k8vpd6fk-...@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/202408170035.k8vpd6fk-...@intel.com/
All errors (new ones prefixed by >>):
>> error[E0425]: cannot find function `iounmap` in crate `bindings`
--> rust/doctests_kernel_generated.rs:2439:28
|
2439 | unsafe { bindings::iounmap(self.0.base_addr() as _); };
|^^^ not found in `bindings`
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v8 3/6] drm/ttm: Use fault-injection to test error paths
Hi Thomas,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20240816]
[also build test ERROR on v6.11-rc3]
[cannot apply to drm-xe/drm-xe-next linus/master v6.11-rc3 v6.11-rc2 v6.11-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-Hellstr-m/drm-ttm-Add-a-virtual-base-class-for-graphics-memory-backup/20240816-213947
base: next-20240816
patch link:
https://lore.kernel.org/r/20240816133717.3102-4-thomas.hellstrom%40linux.intel.com
patch subject: [PATCH v8 3/6] drm/ttm: Use fault-injection to test error paths
config: x86_64-defconfig
(https://download.01.org/0day-ci/archive/20240817/202408170041.l5so7ipq-...@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/20240817/202408170041.l5so7ipq-...@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/202408170041.l5so7ipq-...@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/ttm/ttm_pool.c: In function 'ttm_pool_restore_tt':
>> drivers/gpu/drm/ttm/ttm_pool.c:456:29: error: implicit declaration of
>> function 'should_fail'; did you mean 'schedule_tail'?
>> [-Werror=implicit-function-declaration]
456 | should_fail(&backup_fault_inject, 1)) {
| ^~~
| schedule_tail
>> drivers/gpu/drm/ttm/ttm_pool.c:456:42: error: 'backup_fault_inject'
>> undeclared (first use in this function)
456 | should_fail(&backup_fault_inject, 1)) {
| ^~~
drivers/gpu/drm/ttm/ttm_pool.c:456:42: note: each undeclared identifier is
reported only once for each function it appears in
drivers/gpu/drm/ttm/ttm_pool.c: In function 'ttm_pool_backup_tt':
drivers/gpu/drm/ttm/ttm_pool.c:908:64: error: 'backup_fault_inject'
undeclared (first use in this function)
908 | if (IS_ENABLED(CONFIG_FAULT_INJECTION) &&
should_fail(&backup_fault_inject, 1))
|
^~~
cc1: some warnings being treated as errors
vim +456 drivers/gpu/drm/ttm/ttm_pool.c
434
435 static int ttm_pool_restore_tt(struct ttm_pool_tt_restore *restore,
436 struct ttm_backup *backup,
437 struct ttm_operation_ctx *ctx)
438 {
439 static unsigned long __maybe_unused swappedin;
440 unsigned int i, nr = 1 << restore->order;
441 int ret = 0;
442
443 if (!ttm_pool_restore_valid(restore))
444 return 0;
445
446 for (i = restore->restored_pages; i < nr; ++i) {
447 struct page *p = restore->old_pages[i];
448
449 if (ttm_backup_page_ptr_is_handle(p)) {
450 unsigned long handle =
ttm_backup_page_ptr_to_handle(p);
451
452 if (handle == 0)
453 continue;
454
455 if (IS_ENABLED(CONFIG_FAULT_INJECTION) &&
ctx->interruptible &&
> 456 should_fail(&backup_fault_inject, 1)) {
457 ret = -EINTR;
458 break;
459 }
460
461 ret = backup->ops->copy_backed_up_page
462 (backup, restore->first_page[i],
463 handle, ctx->interruptible);
464 if (ret)
465 break;
466
467 backup->ops->drop(backup, handle);
468 } else if (p) {
469 /*
470 * We could probably avoid splitting the old
page
471 * using clever logic, but ATM we don't care.
472 */
473 ttm_pool_split_for_swap(restore->pool, p);
474 copy_highpage(restore->first_page[i], p);
475 __free_pages(p, 0);
476 }
477
478 restore->rest
Re: [PATCH v3 2/2] drm/vmwgfx: Fix prime with external buffers
Hi Zack,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm/drm-next]
[also build test ERROR on drm-intel/for-linux-next-fixes drm-misc/drm-misc-next
drm-tip/drm-tip linus/master v6.11-rc3 next-20240816]
[cannot apply to drm-exynos/exynos-drm-next drm-intel/for-linux-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/Zack-Rusin/drm-vmwgfx-Fix-prime-with-external-buffers/20240815-234842
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20240815153404.630214-2-zack.rusin%40broadcom.com
patch subject: [PATCH v3 2/2] drm/vmwgfx: Fix prime with external buffers
config: i386-randconfig-013-20240816
(https://download.01.org/0day-ci/archive/20240817/202408170033.rkcwgtsp-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240817/202408170033.rkcwgtsp-...@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/202408170033.rkcwgtsp-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/vmwgfx/vmwgfx_blit.c:503:18: error: call to undeclared
>> function 'floor'; ISO C99 and later do not support implicit function
>> declarations [-Wimplicit-function-declaration]
503 | diff->rect.y1 = floor(dst_offset / dst_stride);
| ^
1 error generated.
vim +/floor +503 drivers/gpu/drm/vmwgfx/vmwgfx_blit.c
455
456 static int vmw_external_bo_copy(struct vmw_bo *dst, u32 dst_offset,
457 u32 dst_stride, struct vmw_bo *src,
458 u32 src_offset, u32 src_stride,
459 u32 width_in_bytes, u32 height,
460 struct vmw_diff_cpy *diff)
461 {
462 struct vmw_private *vmw =
463 container_of(dst->tbo.bdev, struct vmw_private, bdev);
464 size_t dst_size = dst->tbo.resource->size;
465 size_t src_size = src->tbo.resource->size;
466 struct iosys_map dst_map = {0};
467 struct iosys_map src_map = {0};
468 int ret, i;
469 u8 *vsrc;
470 u8 *vdst;
471
472 vsrc = map_external(src, &src_map);
473 if (!vsrc) {
474 drm_dbg_driver(&vmw->drm, "Wasn't able to map src\n");
475 ret = -ENOMEM;
476 goto out;
477 }
478
479 vdst = map_external(dst, &dst_map);
480 if (!vdst) {
481 drm_dbg_driver(&vmw->drm, "Wasn't able to map dst\n");
482 ret = -ENOMEM;
483 goto out;
484 }
485
486 vsrc += src_offset;
487 vdst += dst_offset;
488 if (src_stride == dst_stride) {
489 dst_size -= dst_offset;
490 src_size -= src_offset;
491 memcpy(vdst, vsrc,
492 min(dst_stride * height, min(dst_size,
src_size)));
493 } else {
494 WARN_ON(dst_stride < width_in_bytes);
495 for (i = 0; i < height; ++i) {
496 memcpy(vdst, vsrc, width_in_bytes);
497 vsrc += src_stride;
498 vdst += dst_stride;
499 }
500 }
501
502 diff->rect.x1 = (dst_offset % dst_stride) / diff->cpp;
> 503 diff->rect.y1 = floor(dst_offset / dst_stride);
504 diff->rect.x2 = diff->rect.x1 + width_in_bytes / diff->cpp;
505 diff->rect.y2 = diff->rect.y1 + height;
506
507 ret = 0;
508 out:
509 unmap_external(src, &src_map);
510 unmap_external(dst, &dst_map);
511
512 return ret;
513 }
514
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3 2/2] drm/vmwgfx: Fix prime with external buffers
Hi Zack,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm/drm-next]
[also build test ERROR on drm-intel/for-linux-next-fixes drm-misc/drm-misc-next
drm-tip/drm-tip linus/master v6.11-rc3 next-20240816]
[cannot apply to drm-exynos/exynos-drm-next drm-intel/for-linux-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/Zack-Rusin/drm-vmwgfx-Fix-prime-with-external-buffers/20240815-234842
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link:
https://lore.kernel.org/r/20240815153404.630214-2-zack.rusin%40broadcom.com
patch subject: [PATCH v3 2/2] drm/vmwgfx: Fix prime with external buffers
config: i386-allmodconfig
(https://download.01.org/0day-ci/archive/20240816/202408162343.umopamf9-...@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/20240816/202408162343.umopamf9-...@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/202408162343.umopamf9-...@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/vmwgfx/vmwgfx_blit.c: In function 'vmw_external_bo_copy':
>> drivers/gpu/drm/vmwgfx/vmwgfx_blit.c:503:25: error: implicit declaration of
>> function 'floor' [-Werror=implicit-function-declaration]
503 | diff->rect.y1 = floor(dst_offset / dst_stride);
| ^
cc1: some warnings being treated as errors
vim +/floor +503 drivers/gpu/drm/vmwgfx/vmwgfx_blit.c
455
456 static int vmw_external_bo_copy(struct vmw_bo *dst, u32 dst_offset,
457 u32 dst_stride, struct vmw_bo *src,
458 u32 src_offset, u32 src_stride,
459 u32 width_in_bytes, u32 height,
460 struct vmw_diff_cpy *diff)
461 {
462 struct vmw_private *vmw =
463 container_of(dst->tbo.bdev, struct vmw_private, bdev);
464 size_t dst_size = dst->tbo.resource->size;
465 size_t src_size = src->tbo.resource->size;
466 struct iosys_map dst_map = {0};
467 struct iosys_map src_map = {0};
468 int ret, i;
469 u8 *vsrc;
470 u8 *vdst;
471
472 vsrc = map_external(src, &src_map);
473 if (!vsrc) {
474 drm_dbg_driver(&vmw->drm, "Wasn't able to map src\n");
475 ret = -ENOMEM;
476 goto out;
477 }
478
479 vdst = map_external(dst, &dst_map);
480 if (!vdst) {
481 drm_dbg_driver(&vmw->drm, "Wasn't able to map dst\n");
482 ret = -ENOMEM;
483 goto out;
484 }
485
486 vsrc += src_offset;
487 vdst += dst_offset;
488 if (src_stride == dst_stride) {
489 dst_size -= dst_offset;
490 src_size -= src_offset;
491 memcpy(vdst, vsrc,
492 min(dst_stride * height, min(dst_size,
src_size)));
493 } else {
494 WARN_ON(dst_stride < width_in_bytes);
495 for (i = 0; i < height; ++i) {
496 memcpy(vdst, vsrc, width_in_bytes);
497 vsrc += src_stride;
498 vdst += dst_stride;
499 }
500 }
501
502 diff->rect.x1 = (dst_offset % dst_stride) / diff->cpp;
> 503 diff->rect.y1 = floor(dst_offset / dst_stride);
504 diff->rect.x2 = diff->rect.x1 + width_in_bytes / diff->cpp;
505 diff->rect.y2 = diff->rect.y1 + height;
506
507 ret = 0;
508 out:
509 unmap_external(src, &src_map);
510 unmap_external(dst, &dst_map);
511
512 return ret;
513 }
514
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3 2/4] drm/bridge: add Microchip DSI controller support for sam9x7 SoC series
Hi Manikandan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on drm-misc/drm-misc-next linus/master v6.11-rc3
next-20240816]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Manikandan-Muralidharan/dt-bindings-display-bridge-add-sam9x75-mipi-dsi-binding/20240814-234923
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link:
https://lore.kernel.org/r/20240814105256.177319-3-manikandan.m%40microchip.com
patch subject: [PATCH v3 2/4] drm/bridge: add Microchip DSI controller support
for sam9x7 SoC series
config: arm-randconfig-r071-20240816
(https://download.01.org/0day-ci/archive/20240816/202408162158.tloqyoua-...@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project
8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
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/202408162158.tloqyoua-...@intel.com/
smatch warnings:
drivers/gpu/drm/bridge/dw-mipi-dsi-mchp.c:293 dw_mipi_dsi_mchp_get_lane_mbps()
warn: unsigned 'bpp' is never less than zero.
drivers/gpu/drm/bridge/dw-mipi-dsi-mchp.c:293 dw_mipi_dsi_mchp_get_lane_mbps()
warn: error code type promoted to positive: 'bpp'
drivers/gpu/drm/bridge/dw-mipi-dsi-mchp.c:314 dw_mipi_dsi_mchp_get_lane_mbps()
error: uninitialized symbol 'target_mbps'.
vim +/bpp +293 drivers/gpu/drm/bridge/dw-mipi-dsi-mchp.c
276
277 static int dw_mipi_dsi_mchp_get_lane_mbps(void *priv_data,
278const struct drm_display_mode
*mode,
279unsigned long mode_flags, u32
lanes,
280u32 format, unsigned int
*lane_mbps)
281 {
282 struct dw_mipi_dsi_mchp *dsi = priv_data;
283 unsigned long best_freq, fvco_min, fvco_max, fin, fout;
284 unsigned long min_delta = ULONG_MAX, delta;
285 unsigned int mpclk, target_mbps, desired_mbps;
286 unsigned int max_mbps = dppa_map[ARRAY_SIZE(dppa_map) -
1].max_mbps;
287 unsigned int bpp, min_prediv, max_prediv;
288 unsigned int _fbdiv, best_fbdiv, _prediv, best_prediv;
289 u64 freq_factor;
290
291 dsi->format = format;
292 bpp = mipi_dsi_pixel_format_to_bpp(dsi->format);
> 293 if (bpp < 0) {
294 dev_err(dsi->dev,
295 "failed to get bpp for pixel format %d\n",
296 dsi->format);
297 return bpp;
298 }
299
300 mpclk = DIV_ROUND_UP(mode->clock, MSEC_PER_SEC);
301 if (mpclk) {
302 /* take 1/0.8, since mbps must be bigger than bandwidth
of RGB */
303 desired_mbps = mpclk * (bpp / lanes) * 10 / 8;
304 if (desired_mbps < max_mbps) {
305 target_mbps = desired_mbps;
306 } else {
307 dev_err(dsi->dev,
308 "DPHY clock frequency is out of
range\n");
309 return -ERANGE;
310 }
311 }
312
313 fin = clk_get_rate(dsi->pllref_clk);
> 314 fout = target_mbps * USEC_PER_SEC;
315
316 /* constraint: 5Mhz <= Fref / N <= 40MHz */
317 min_prediv = DIV_ROUND_UP(fin, 40 * USEC_PER_SEC);
318 max_prediv = fin / (5 * USEC_PER_SEC);
319
320 /* constraint: 80MHz <= Fvco <= 1000Mhz */
321 fvco_min = 80 * USEC_PER_SEC;
322 fvco_max = 1000 * USEC_PER_SEC;
323
324 for (best_freq = 0, _prediv = min_prediv; _prediv <=
max_prediv; _prediv++) {
325 /* Fvco = Fref * M / N */
326 freq_factor = fout * _prediv;
327 do_div(freq_factor, fin);
328 _fbdiv = freq_factor;
329 /*
330 * Due to the use of a "by 2 pre-scaler," the range of
the
331 * feedback multiplication value M is limited to even
division
332 * numbers, and m must be greater than 6, not bigger
than 512.
333 */
334 if (_fbdiv < 6 || _fbdiv > 512)
335 continue;
336
337 _fbdiv +=
Re: [PATCH v3 5/5] udmabuf: remove udmabuf_folio
Hi Huan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 033a4691702cdca3a613256b0623b8eeacb4985e]
url:
https://github.com/intel-lab-lkp/linux/commits/Huan-Yang/udmabuf-cancel-mmap-page-fault-direct-map-it/20240814-231504
base: 033a4691702cdca3a613256b0623b8eeacb4985e
patch link:
https://lore.kernel.org/r/20240813090518.3252469-6-link%40vivo.com
patch subject: [PATCH v3 5/5] udmabuf: remove udmabuf_folio
config: s390-allyesconfig
(https://download.01.org/0day-ci/archive/20240816/202408162012.cl9pnfsm-...@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/20240816/202408162012.cl9pnfsm-...@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/202408162012.cl9pnfsm-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/dma-buf/udmabuf.c:175: warning: Function parameter or struct member
>> 'ubuf' not described in 'unpin_all_folios'
vim +175 drivers/dma-buf/udmabuf.c
17a7ce20349045 Gurchetan Singh 2019-12-02 165
d934739404652b Huan Yang 2024-08-13 166 /**
d934739404652b Huan Yang 2024-08-13 167 * unpin_all_folios:
unpin each folio we pinned in create
d934739404652b Huan Yang 2024-08-13 168 * The udmabuf set all folio in
folios and pinned it, but for large folio,
d934739404652b Huan Yang 2024-08-13 169 * We may have only used a
small portion of the physical in the folio.
d934739404652b Huan Yang 2024-08-13 170 * we will repeatedly,
sequentially set the folio into the array to ensure
d934739404652b Huan Yang 2024-08-13 171 * that the offset can index
the correct folio at the corresponding index.
d934739404652b Huan Yang 2024-08-13 172 * Hence, we only need to unpin
the first iterred folio.
d934739404652b Huan Yang 2024-08-13 173 */
d934739404652b Huan Yang 2024-08-13 174 static void
unpin_all_folios(struct udmabuf *ubuf)
c6a3194c05e7e6 Vivek Kasireddy 2024-06-23 @175 {
d934739404652b Huan Yang 2024-08-13 176 pgoff_t pg;
d934739404652b Huan Yang 2024-08-13 177 struct folio *last =
NULL;
c6a3194c05e7e6 Vivek Kasireddy 2024-06-23 178
d934739404652b Huan Yang 2024-08-13 179 for (pg = 0; pg <
ubuf->pagecount; pg++) {
d934739404652b Huan Yang 2024-08-13 180 struct folio
*tmp = ubuf->folios[pg];
c6a3194c05e7e6 Vivek Kasireddy 2024-06-23 181
d934739404652b Huan Yang 2024-08-13 182 if (tmp == last)
d934739404652b Huan Yang 2024-08-13 183
continue;
c6a3194c05e7e6 Vivek Kasireddy 2024-06-23 184
d934739404652b Huan Yang 2024-08-13 185 last = tmp;
d934739404652b Huan Yang 2024-08-13 186
unpin_folio(tmp);
d934739404652b Huan Yang 2024-08-13 187 }
c6a3194c05e7e6 Vivek Kasireddy 2024-06-23 188 }
c6a3194c05e7e6 Vivek Kasireddy 2024-06-23 189
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 4/7] drm/msm/A6xx: Implement preemption for A7XX targets
Hi Antonino,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 7c626ce4bae1ac14f60076d00eafe71af30450ba]
url:
https://github.com/intel-lab-lkp/linux/commits/Antonino-Maniscalco/drm-msm-Fix-bv_fence-being-used-as-bv_rptr/20240816-023442
base: 7c626ce4bae1ac14f60076d00eafe71af30450ba
patch link:
https://lore.kernel.org/r/20240815-preemption-a750-t-v1-4-7bda26c34037%40gmail.com
patch subject: [PATCH 4/7] drm/msm/A6xx: Implement preemption for A7XX targets
config: i386-buildonly-randconfig-001-20240816
(https://download.01.org/0day-ci/archive/20240816/202408161951.81zgvcj5-...@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/20240816/202408161951.81zgvcj5-...@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/202408161951.81zgvcj5-...@intel.com/
All warnings (new ones prefixed by >>):
drivers/gpu/drm/msm/adreno/a6xx_preempt.c: In function 'update_wptr':
>> drivers/gpu/drm/msm/adreno/a6xx_preempt.c:49:24: warning: unused variable
>> 'cur_wptr' [-Wunused-variable]
49 | uint32_t wptr, cur_wptr;
|^~~~
vim +/cur_wptr +49 drivers/gpu/drm/msm/adreno/a6xx_preempt.c
44
45 /* Write the most recent wptr for the given ring into the hardware */
46 static inline void update_wptr(struct msm_gpu *gpu, struct
msm_ringbuffer *ring)
47 {
48 unsigned long flags;
> 49 uint32_t wptr, cur_wptr;
50
51 if (!ring)
52 return;
53
54 spin_lock_irqsave(&ring->preempt_lock, flags);
55
56 if (ring->skip_inline_wptr) {
57 wptr = get_wptr(ring);
58
59 gpu_write(gpu, REG_A6XX_CP_RB_WPTR, wptr);
60
61 ring->skip_inline_wptr = false;
62 }
63
64 spin_unlock_irqrestore(&ring->preempt_lock, flags);
65 }
66
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 2/2] mtd: rawnand: nuvoton: add new driver for the Nuvoton MA35 SoC
Hi Hui-Ping,
kernel test robot noticed the following build warnings:
[auto build test WARNING on mtd/nand/next]
[also build test WARNING on linus/master v6.11-rc3 next-20240813]
[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/Hui-Ping-Chen/dt-bindings-mtd-nuvoton-ma35d1-nand-add-new-bindings/20240812-110259
base: https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git nand/next
patch link:
https://lore.kernel.org/r/20240812030045.20831-3-hpchen0nvt%40gmail.com
patch subject: [PATCH 2/2] mtd: rawnand: nuvoton: add new driver for the
Nuvoton MA35 SoC
config: arc-randconfig-r133-20240813
(https://download.01.org/0day-ci/archive/20240814/202408140515.pbhkvxzd-...@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce:
(https://download.01.org/0day-ci/archive/20240814/202408140515.pbhkvxzd-...@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/202408140515.pbhkvxzd-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:119:3: sparse: sparse: symbol
>> 'E_BCHALGORITHM' was not declared. Should it be static?
>> drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:333:28: sparse: sparse: cast
>> removes address space '__iomem' of expression
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:348:39: sparse: sparse: cast
removes address space '__iomem' of expression
>> drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:746:41: sparse: sparse: incorrect
>> type in initializer (different address spaces) @@ expected char
>> *register ptr @@ got void [noderef] __iomem * @@
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:746:41: sparse: expected char
*register ptr
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:746:41: sparse: got void
[noderef] __iomem *
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:760:18: sparse: sparse: cast
removes address space '__iomem' of expression
>> drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:774:32: sparse: sparse: incorrect
>> type in initializer (different address spaces) @@ expected char *ptr @@
>>got void [noderef] __iomem * @@
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:774:32: sparse: expected char
*ptr
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:774:32: sparse: got void
[noderef] __iomem *
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:813:32: sparse: sparse: incorrect
type in initializer (different address spaces) @@ expected char *ptr @@
got void [noderef] __iomem * @@
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:813:32: sparse: expected char
*ptr
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:813:32: sparse: got void
[noderef] __iomem *
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:516:49: sparse: sparse: incorrect
type in initializer (different address spaces) @@ expected char *register
ptr @@ got void [noderef] __iomem * @@
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:516:49: sparse: expected char
*register ptr
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:516:49: sparse: got void
[noderef] __iomem *
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:516:49: sparse: sparse: incorrect
type in initializer (different address spaces) @@ expected char *register
ptr @@ got void [noderef] __iomem * @@
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:516:49: sparse: expected char
*register ptr
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:516:49: sparse: got void
[noderef] __iomem *
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:516:49: sparse: sparse: incorrect
type in initializer (different address spaces) @@ expected char *register
ptr @@ got void [noderef] __iomem * @@
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:516:49: sparse: expected char
*register ptr
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:516:49: sparse: got void
[noderef] __iomem *
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:516:49: sparse: sparse: incorrect
type in initializer (different address spaces) @@ expected char *register
ptr @@ got void [noderef] __iomem * @@
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:516:49: sparse: expected char
*register ptr
drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:516:49: sparse: got void
[noderef] __iomem *
vim +/E_BCHALGORITHM +119 drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c
111
112 /* BCH algorithm related constants and variables */
113 enum {
114 eBCH_NONE = 0,
115 eBCH_T8,
116 eBCH_T12,
117 eBCH_T24,
118 eBCH_CNT
> 119 } E_BCHALGORITHM;
120
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3 1/5] workqueue: Split alloc_workqueue into internal function and lockdep init
Hello,
kernel test robot noticed "sysfs:cannot_create_duplicate_filename" on:
commit: 589686d5b8d589e30478cfb8db2e8e2cd54c20e9 ("[PATCH v3 1/5] workqueue:
Split alloc_workqueue into internal function and lockdep init")
url:
https://github.com/intel-lab-lkp/linux/commits/Matthew-Brost/workqueue-Split-alloc_workqueue-into-internal-function-and-lockdep-init/20240810-122131
base: https://git.kernel.org/cgit/linux/kernel/git/tj/wq.git for-next
patch link:
https://lore.kernel.org/all/20240809222827.3211998-2-matthew.br...@intel.com/
patch subject: [PATCH v3 1/5] workqueue: Split alloc_workqueue into internal
function and lockdep init
in testcase: boot
compiler: clang-18
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
++++
|| 3b47e19ebc | 589686d5b8 |
++++
| sysfs:cannot_create_duplicate_filename | 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/202408121610.d1cdf757-oliver.s...@intel.com
[ OK ] Started User Login Management.
Starting LSB: Load kernel image with kexec...
[ 11.888312][ T131] ata_piix :00:01.1: version 2.13
[ OK ] Started OpenBSD Secure Shell server.
[ 11.890919][ T131] scsi host0: ata_piix
[ 11.893885][ T131] sysfs: cannot create duplicate filename
'/devices/virtual/workqueue/scsi_tmf_4945632'
[ 11.895088][ T131] CPU: 0 UID: 0 PID: 131 Comm: systemd-udevd Not tainted
6.11.0-rc1-00010-g589686d5b8d5 #1
[ 11.896222][ T131] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 11.897360][ T131] Call Trace:
[ 11.897806][ T131]
[ 11.898206][ T131] dump_stack_lvl (kbuild/src/consumer/lib/dump_stack.c:121)
[ 11.898801][ T131] sysfs_create_dir_ns (kbuild/src/consumer/fs/sysfs/dir.c:32
kbuild/src/consumer/fs/sysfs/dir.c:63)
[ 11.899453][ T131] kobject_add_internal (kbuild/src/consumer/lib/kobject.c:74
kbuild/src/consumer/lib/kobject.c:240)
[ 11.900074][ T131] kobject_add (kbuild/src/consumer/lib/kobject.c:430)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240812/202408121610.d1cdf757-oliver.s...@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v5] drm/i915/hwmon: expose fan speed
Hi Raag, kernel test robot noticed the following build errors: [auto build test ERROR on groeck-staging/hwmon-next] [also build test ERROR on linus/master v6.11-rc3 next-20240812] [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-i915-hwmon-expose-fan-speed/20240812-161645 base: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next patch link: https://lore.kernel.org/r/20240812081538.1457396-1-raag.jadav%40intel.com patch subject: [PATCH v5] drm/i915/hwmon: expose fan speed config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20240813/202408130800.xty6xxq5-...@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/20240813/202408130800.xty6xxq5-...@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/202408130800.xty6xxq5-...@intel.com/ All errors (new ones prefixed by >>): ld: drivers/gpu/drm/i915/i915_hwmon.o: in function `hwm_read': >> i915_hwmon.c:(.text+0xe60): undefined reference to `__udivdi3' -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v5] drm/i915/hwmon: expose fan speed
Hi Raag,
kernel test robot noticed the following build errors:
[auto build test ERROR on groeck-staging/hwmon-next]
[also build test ERROR on linus/master v6.11-rc3 next-20240812]
[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-i915-hwmon-expose-fan-speed/20240812-161645
base:
https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
hwmon-next
patch link:
https://lore.kernel.org/r/20240812081538.1457396-1-raag.jadav%40intel.com
patch subject: [PATCH v5] drm/i915/hwmon: expose fan speed
config: i386-randconfig-012-20240813
(https://download.01.org/0day-ci/archive/20240813/202408130500.sgcvor2d-...@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/20240813/202408130500.sgcvor2d-...@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/202408130500.sgcvor2d-...@intel.com/
All errors (new ones prefixed by >>):
ld: drivers/gpu/drm/i915/i915_hwmon.o: in function `hwm_fan_read':
>> drivers/gpu/drm/i915/i915_hwmon.c:675: undefined reference to `__udivdi3'
vim +675 drivers/gpu/drm/i915/i915_hwmon.c
633
634 static int
635 hwm_fan_read(struct hwm_drvdata *ddat, u32 attr, long *val)
636 {
637 struct i915_hwmon *hwmon = ddat->hwmon;
638 struct hwm_fan_info *fi = &ddat->fi;
639 u64 rotations, time_now, time;
640 intel_wakeref_t wakeref;
641 u32 reg_val, pulses;
642 int ret = 0;
643
644 if (attr != hwmon_fan_input)
645 return -EOPNOTSUPP;
646
647 wakeref = intel_runtime_pm_get(ddat->uncore->rpm);
648 mutex_lock(&hwmon->hwmon_lock);
649
650 reg_val = intel_uncore_read(ddat->uncore, hwmon->rg.fan_speed);
651 time_now = get_jiffies_64();
652
653 /* Handle HW register overflow */
654 if (reg_val >= fi->reg_val_prev)
655 pulses = reg_val - fi->reg_val_prev;
656 else
657 pulses = UINT_MAX - fi->reg_val_prev + reg_val;
658
659 /*
660 * HW register value is accumulated count of pulses from
661 * PWM fan with the scale of 2 pulses per rotation.
662 */
663 rotations = pulses / 2;
664
665 time = jiffies_delta_to_msecs(time_now - fi->time_prev);
666 if (unlikely(!time)) {
667 ret = -EAGAIN;
668 goto exit;
669 }
670
671 /*
672 * Convert to minutes for calculating RPM.
673 * RPM = number of rotations * msecs per minute / time in msecs
674 */
> 675 *val = DIV_ROUND_UP(rotations * (MSEC_PER_SEC * 60), time);
676
677 fi->reg_val_prev = reg_val;
678 fi->time_prev = time_now;
679 exit:
680 mutex_unlock(&hwmon->hwmon_lock);
681 intel_runtime_pm_put(ddat->uncore->rpm, wakeref);
682 return ret;
683 }
684
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 2/2] mtd: rawnand: nuvoton: add new driver for the Nuvoton MA35 SoC
Hi Hui-Ping,
kernel test robot noticed the following build warnings:
[auto build test WARNING on mtd/nand/next]
[also build test WARNING on linus/master v6.11-rc3 next-20240812]
[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/Hui-Ping-Chen/dt-bindings-mtd-nuvoton-ma35d1-nand-add-new-bindings/20240812-110259
base: https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git nand/next
patch link:
https://lore.kernel.org/r/20240812030045.20831-3-hpchen0nvt%40gmail.com
patch subject: [PATCH 2/2] mtd: rawnand: nuvoton: add new driver for the
Nuvoton MA35 SoC
config: x86_64-allyesconfig
(https://download.01.org/0day-ci/archive/20240812/202408122007.qutidxpr-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240812/202408122007.qutidxpr-...@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/202408122007.qutidxpr-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c:991:29: warning: cast from
>> 'irqreturn_t (*)(int, struct ma35_nand_info *)' (aka 'enum irqreturn
>> (*)(int, struct ma35_nand_info *)') to 'irq_handler_t' (aka 'enum irqreturn
>> (*)(int, void *)') converts to incompatible function type
>> [-Wcast-function-type-strict]
991 | if (request_irq(nand->irq, (irq_handler_t)&ma35_nand_irq,
|^
1 warning generated.
vim +991 drivers/mtd/nand/raw/nuvoton_ma35d1_nand.c
921
922 static int ma35_nand_probe(struct platform_device *pdev)
923 {
924 struct ma35_nand_info *nand;
925 struct nand_chip *chip;
926 struct mtd_info *mtd;
927 int retval = 0;
928
929 nand = devm_kzalloc(&pdev->dev, sizeof(struct ma35_nand_info),
GFP_KERNEL);
930 if (!nand)
931 return -ENOMEM;
932
933 nand_controller_init(&nand->controller);
934
935 nand->regs = devm_platform_ioremap_resource(pdev, 0);
936 if (IS_ERR(nand->regs))
937 return PTR_ERR(nand->regs);
938
939 nand->dev = &pdev->dev;
940 chip = &nand->chip;
941 mtd = nand_to_mtd(chip);
942 nand_set_controller_data(chip, nand);
943 nand_set_flash_node(chip, pdev->dev.of_node);
944
945 mtd->priv = chip;
946 mtd->owner = THIS_MODULE;
947 mtd->dev.parent = &pdev->dev;
948
949 nand->clk = of_clk_get(pdev->dev.of_node, 0);
950 if (IS_ERR(nand->clk))
951 return dev_err_probe(&pdev->dev, PTR_ERR(nand->clk),
952 "failed to find nand clock\n");
953
954 retval = clk_prepare_enable(nand->clk);
955 if (retval < 0) {
956 dev_err(&pdev->dev, "Failed to enable clock\n");
957 return -ENXIO;
958 }
959
960 nand->chip.controller= &nand->controller;
961
962 chip->legacy.cmdfunc = ma35_nand_command;
963 chip->legacy.waitfunc= ma35_waitfunc;
964 chip->legacy.read_byte = ma35_nand_read_byte;
965 chip->legacy.select_chip = ma35_nand_select_chip;
966 chip->legacy.read_buf= ma35_read_buf_dma;
967 chip->legacy.write_buf = ma35_write_buf_dma;
968 chip->legacy.dev_ready = ma35_nand_devready;
969 chip->legacy.chip_delay = 25; /* us */
970
971 /* Read OOB data first, then HW read page */
972 chip->ecc.hwctl = ma35_nand_enable_hwecc;
973 chip->ecc.calculate = ma35_nand_calculate_ecc;
974 chip->ecc.correct= ma35_nand_correct_data;
975 chip->ecc.write_page = ma35_nand_write_page_hwecc;
976 chip->ecc.read_page = ma35_nand_read_page_hwecc_oob_first;
977 chip->ecc.read_oob = ma35_nand_read_oob_hwecc;
978 chip->options |= (NAND_NO_SUBPAGE_WRITE | NAND_USES_DMA);
979
980 ma35_nand_initialize(nand);
981 platform_set_drvdata(pdev, nand);
Re: [PATCH] video/aperture: match the pci device when calling sysfb_disable()
Hi Alex, 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.11-rc2 next-20240809] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Alex-Deucher/video-aperture-match-the-pci-device-when-calling-sysfb_disable/20240810-021357 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240809150327.2485848-1-alexander.deucher%40amd.com patch subject: [PATCH] video/aperture: match the pci device when calling sysfb_disable() config: i386-randconfig-001-20240810 (https://download.01.org/0day-ci/archive/20240810/202408102027.iwri1vxt-...@intel.com/config) compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240810/202408102027.iwri1vxt-...@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/202408102027.iwri1vxt-...@intel.com/ All errors (new ones prefixed by >>): >> ld.lld: error: undefined symbol: screen_info_pci_dev >>> referenced by aperture.c:358 (drivers/video/aperture.c:358) >>> drivers/video/aperture.o:(aperture_remove_conflicting_pci_devices) in archive vmlinux.a -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH] video/aperture: match the pci device when calling sysfb_disable()
Hi Alex, 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.11-rc2 next-20240809] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Alex-Deucher/video-aperture-match-the-pci-device-when-calling-sysfb_disable/20240810-021357 base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next patch link: https://lore.kernel.org/r/20240809150327.2485848-1-alexander.deucher%40amd.com patch subject: [PATCH] video/aperture: match the pci device when calling sysfb_disable() config: csky-randconfig-001-20240810 (https://download.01.org/0day-ci/archive/20240810/202408101951.txyqyozv-...@intel.com/config) compiler: csky-linux-gcc (GCC) 14.1.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240810/202408101951.txyqyozv-...@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/202408101951.txyqyozv-...@intel.com/ All errors (new ones prefixed by >>): csky-linux-ld: drivers/video/aperture.o: in function `aperture_remove_conflicting_pci_devices': >> aperture.c:(.text+0x222): undefined reference to `screen_info_pci_dev' csky-linux-ld: drivers/video/aperture.o: in function `devm_aperture_acquire_release': >> aperture.c:(.text+0x2c0): undefined reference to `screen_info' >> csky-linux-ld: aperture.c:(.text+0x2c4): undefined reference to >> `screen_info_pci_dev' -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 3/3] drm/rockchip: Add basic RK3588 HDMI output support
Hi Cristian, kernel test robot noticed the following build errors: [auto build test ERROR on 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0] url: https://github.com/intel-lab-lkp/linux/commits/Cristian-Ciocaltea/dt-bindings-display-rockchip-Add-schema-for-RK3588-HDMI-TX-Controller/20240802-173018 base: 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0 patch link: https://lore.kernel.org/r/20240801-b4-rk3588-bridge-upstream-v2-3-9fa657a4e15b%40collabora.com patch subject: [PATCH v2 3/3] drm/rockchip: Add basic RK3588 HDMI output support config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20240810/202408100431.ujb0m1q7-...@intel.com/config) compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project f86594788ce93b696675c94f54016d27a6c21d18) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240810/202408100431.ujb0m1q7-...@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/202408100431.ujb0m1q7-...@intel.com/ All errors (new ones prefixed by >>): In file included from drivers/gpu/drm/rockchip/dw_hdmi_qp-rockchip.c:15: In file included from include/linux/phy/phy.h:17: 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:9: 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/rockchip/dw_hdmi_qp-rockchip.c:15: In file included from include/linux/phy/phy.h:17: 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:9: 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/rockchip/dw_hdmi_qp-rockchip.c:15: In file included from include/linux/phy/phy.h:17: 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:9: 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 f
Re: [PATCH v2 3/3] drm/rockchip: Add basic RK3588 HDMI output support
Hi Cristian,
kernel test robot noticed the following build errors:
[auto build test ERROR on 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0]
url:
https://github.com/intel-lab-lkp/linux/commits/Cristian-Ciocaltea/dt-bindings-display-rockchip-Add-schema-for-RK3588-HDMI-TX-Controller/20240802-173018
base: 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0
patch link:
https://lore.kernel.org/r/20240801-b4-rk3588-bridge-upstream-v2-3-9fa657a4e15b%40collabora.com
patch subject: [PATCH v2 3/3] drm/rockchip: Add basic RK3588 HDMI output support
config: alpha-allyesconfig
(https://download.01.org/0day-ci/archive/20240810/202408100456.yy6k40pk-...@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/20240810/202408100456.yy6k40pk-...@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/202408100456.yy6k40pk-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/rockchip/dw_hdmi_qp-rockchip.c:18:10: fatal error:
>> drm/bridge/dw_hdmi_qp.h: No such file or directory
18 | #include
| ^
compilation terminated.
vim +18 drivers/gpu/drm/rockchip/dw_hdmi_qp-rockchip.c
17
> 18 #include
19 #include
20 #include
21 #include
22 #include
23
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/3] drm/panfrost: Add SYSTEM_TIMESTAMP and SYSTEM_TIMESTAMP_FREQUENCY parameters
Hi Mary,
kernel test robot noticed the following build errors:
[auto build test ERROR on f7f3ddb6e5c8dc7b621fd8c0903ea42190d67452]
url:
https://github.com/intel-lab-lkp/linux/commits/Mary-Guillemard/drm-panfrost-Add-SYSTEM_TIMESTAMP-and-SYSTEM_TIMESTAMP_FREQUENCY-parameters/20240808-032938
base: f7f3ddb6e5c8dc7b621fd8c0903ea42190d67452
patch link:
https://lore.kernel.org/r/20240807160900.149154-2-mary.guillemard%40collabora.com
patch subject: [PATCH 1/3] drm/panfrost: Add SYSTEM_TIMESTAMP and
SYSTEM_TIMESTAMP_FREQUENCY parameters
config: arm-defconfig
(https://download.01.org/0day-ci/archive/20240808/202408082014.xkxle32n-...@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/20240808/202408082014.xkxle32n-...@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/202408082014.xkxle32n-...@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/panfrost/panfrost_drv.c:75:18: error: implicit declaration
>> of function '__arch_counter_get_cntvct' is invalid in C99
>> [-Werror,-Wimplicit-function-declaration]
param->value = __arch_counter_get_cntvct();
^
>> drivers/gpu/drm/panfrost/panfrost_drv.c:83:18: error: implicit declaration
>> of function 'arch_timer_get_cntfrq' is invalid in C99
>> [-Werror,-Wimplicit-function-declaration]
param->value = arch_timer_get_cntfrq();
^
2 errors generated.
vim +/__arch_counter_get_cntvct +75 drivers/gpu/drm/panfrost/panfrost_drv.c
26
27 static int panfrost_ioctl_get_param(struct drm_device *ddev, void
*data, struct drm_file *file)
28 {
29 struct drm_panfrost_get_param *param = data;
30 struct panfrost_device *pfdev = ddev->dev_private;
31
32 if (param->pad != 0)
33 return -EINVAL;
34
35 #define PANFROST_FEATURE(name, member) \
36 case DRM_PANFROST_PARAM_ ## name: \
37 param->value = pfdev->features.member; \
38 break
39 #define PANFROST_FEATURE_ARRAY(name, member, max)
\
40 case DRM_PANFROST_PARAM_ ## name ## 0 ...
\
41 DRM_PANFROST_PARAM_ ## name ## max:
\
42 param->value = pfdev->features.member[param->param -
\
43 DRM_PANFROST_PARAM_ ## name ## 0];
\
44 break
45
46 switch (param->param) {
47 PANFROST_FEATURE(GPU_PROD_ID, id);
48 PANFROST_FEATURE(GPU_REVISION, revision);
49 PANFROST_FEATURE(SHADER_PRESENT, shader_present);
50 PANFROST_FEATURE(TILER_PRESENT, tiler_present);
51 PANFROST_FEATURE(L2_PRESENT, l2_present);
52 PANFROST_FEATURE(STACK_PRESENT, stack_present);
53 PANFROST_FEATURE(AS_PRESENT, as_present);
54 PANFROST_FEATURE(JS_PRESENT, js_present);
55 PANFROST_FEATURE(L2_FEATURES, l2_features);
56 PANFROST_FEATURE(CORE_FEATURES, core_features);
57 PANFROST_FEATURE(TILER_FEATURES, tiler_features);
58 PANFROST_FEATURE(MEM_FEATURES, mem_features);
59 PANFROST_FEATURE(MMU_FEATURES, mmu_features);
60 PANFROST_FEATURE(THREAD_FEATURES, thread_features);
61 PANFROST_FEATURE(MAX_THREADS, max_threads);
62 PANFROST_FEATURE(THREAD_MAX_WORKGROUP_SZ,
63 thread_max_workgroup_sz);
64 PANFROST_FEATURE(THREAD_MAX_BARRIER_SZ,
65 thread_max_barrier_sz);
66 PANFROST_FEATURE(COHERENCY_FEATURES,
coherency_features);
67 PANFROST_FEATURE(AFBC_FEATURES, afbc_features);
68 PANFROST_FEATURE_ARRAY(TEXTURE_FEATURES,
texture_features, 3);
69 PANFROST_FEATURE_ARRAY(JS_FEATURES, js_features, 15);
70 PANFROST_FEATURE(NR_CORE_GROUPS, nr_core_groups);
71 PANFROST_FEATURE(THREAD_TLS_ALLOC, thread_tls_alloc);
72
73 case DRM_PANFROST_PARAM_SYSTEM_TIMESTAMP:
74 #ifdef CONFIG_ARM_ARCH_TIMER
> 75 param->value = __arch_counter_get_cntvct();
76 #else
7
Re: [PATCH 7/7] drm/i915/pmu: Do not set event_init to NULL
Hello,
kernel test robot noticed "INFO:trying_to_register_non-static_key" on:
commit: a236f4d92e214998f7606430282249580f709423 ("[PATCH 7/7] drm/i915/pmu: Do
not set event_init to NULL")
url:
https://github.com/intel-lab-lkp/linux/commits/Lucas-De-Marchi/perf-core-Add-pmu-get-put/20240723-051755
base: https://git.kernel.org/cgit/linux/kernel/git/perf/perf-tools-next.git
perf-tools-next
patch link:
https://lore.kernel.org/all/20240722210648.80892-8-lucas.demar...@intel.com/
patch subject: [PATCH 7/7] drm/i915/pmu: Do not set event_init to NULL
in testcase: kernel-selftests
version: kernel-selftests-x86_64-977d51cf-1_20240508
with following parameters:
group: locking
compiler: gcc-13
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/202408051423.839b16eb-oliver.s...@intel.com
[ 45.439542][ T194] INFO: trying to register non-static key.
[ 45.445246][ T194] The code is fine but needs lockdep annotation, or maybe
[ 45.452244][ T194] you didn't initialize this object before use?
[ 45.458370][ T194] turning off the locking correctness validator.
[ 45.464586][ T194] CPU: 3 PID: 194 Comm: (udev-worker) Tainted: G S
6.10.0-rc3-00133-ga236f4d92e21 #1
[ 45.475322][ T194] Hardware name: HP HP Z238 Microtower Workstation/8183,
BIOS N51 Ver. 01.63 10/05/2017
[ 45.484923][ T194] Call Trace:
[ 45.488094][ T194]
[ 45.490908][ T194] dump_stack_lvl (lib/dump_stack.c:118)
[ 45.495297][ T194] register_lock_class (kernel/locking/lockdep.c:1290)
[ 45.500377][ T194] ? lock_acquire (kernel/locking/lockdep.c:467 (discriminator
4) kernel/locking/lockdep.c:5756 (discriminator 4)
kernel/locking/lockdep.c:5719 (discriminator 4))
[ 45.504938][ T194] ? intel_display_power_get
(drivers/gpu/drm/i915/display/intel_display_power.c:504
drivers/gpu/drm/i915/display/intel_display_power.c:532) i915
[ 45.511333][ T194] ? __pfx_register_lock_class (kernel/locking/lockdep.c:1276)
[ 45.516848][ T194] ? __pfx_lock_acquire (kernel/locking/lockdep.c:5722)
[ 45.521748][ T194] ? lock_is_held_type (kernel/locking/lockdep.c:5495
(discriminator 1) kernel/locking/lockdep.c:5825 (discriminator 1))
[ 45.526654][ T194] ? find_held_lock (kernel/locking/lockdep.c:5244
(discriminator 1))
[ 45.531306][ T194] __lock_acquire (kernel/locking/lockdep.c:5015)
[ 45.535870][ T194] ? trace_contention_end (include/trace/events/lock.h:122
(discriminator 2))
[ 45.541042][ T194] ? __mutex_lock (arch/x86/include/asm/preempt.h:94
(discriminator 1) kernel/locking/mutex.c:618 (discriminator 1)
kernel/locking/mutex.c:752 (discriminator 1))
[ 45.545688][ T194] lock_acquire (kernel/locking/lockdep.c:467 (discriminator
4) kernel/locking/lockdep.c:5756 (discriminator 4)
kernel/locking/lockdep.c:5719 (discriminator 4))
[ 45.550069][ T194] ? i915_pmu_gt_unparked
(drivers/gpu/drm/i915/i915_pmu.c:336) i915
[ 45.556233][ T194] ? __pfx_lock_acquire (kernel/locking/lockdep.c:5722)
[ 45.561162][ T194] ? __pfx___mutex_unlock_slowpath
(kernel/locking/mutex.c:907)
[ 45.567023][ T194] ? __pfx_intel_display_power_grab_async_put_ref
(drivers/gpu/drm/i915/display/intel_display_power.c:471) i915
[ 45.575181][ T194] _raw_spin_lock_irq (include/linux/spinlock_api_smp.h:120
kernel/locking/spinlock.c:170)
[ 45.579937][ T194] ? i915_pmu_gt_unparked
(drivers/gpu/drm/i915/i915_pmu.c:336) i915
[ 45.586041][ T194] i915_pmu_gt_unparked (drivers/gpu/drm/i915/i915_pmu.c:336)
i915
[ 45.591960][ T194] __gt_unpark (drivers/gpu/drm/i915/gt/intel_gt_pm.c:93) i915
[ 45.597075][ T194] __intel_wakeref_get_first
(drivers/gpu/drm/i915/intel_wakeref.c:32) i915
[ 45.603498][ T194] intel_gt_resume (drivers/gpu/drm/i915/gt/intel_gt_pm.c:259)
i915
[ 45.609021][ T194] ? __pfx_intel_execlists_submission_setup
(drivers/gpu/drm/i915/gt/intel_execlists_submission.c:3541) i915
[ 45.616560][ T194] intel_gt_init (drivers/gpu/drm/i915/gt/intel_gt.c:740) i915
[ 45.621888][ T194] i915_gem_init (drivers/gpu/drm/i915/i915_gem.c:1193) i915
[ 45.627261][ T194] i915_driver_probe (drivers/gpu/drm/i915/i915_driver.c:798)
i915
[ 45.632922][ T194] ? __pfx_i915_driver_probe
(drivers/gpu/drm/i915/i915_driver.c:750) i915
[ 45.639091][ T194] ? drm_privacy_screen_get
(drivers/gpu/drm/drm_privacy_screen.c:168) drm
[ 45.645110][ T194] ? intel_display_driver_probe_defer
(drivers/gpu/drm/i915/display/intel_display_driver.c:81) i915
[ 45.652258][ T194] ? i915_pci_probe (drivers/gpu/drm/i915/i915_pci.c:998
(discriminator 1)) i915
[ 45.657875][ T194] ? __pfx_i915_pci_probe
(drivers/gpu/drm/i915/i915_pci.c:959) i915
[ 45.663785][ T194] local_pci_probe (drivers/pci/pci-driver.c:324)
[ 45.668340][ T194] pci_call_probe
Re: [PATCH 07/11] dt-bindings: interconnect: qcom,sm8450: drop DISP nodes
Hi Dmitry, kernel test robot noticed the following build errors: [auto build test ERROR on 668d33c9ff922c4590c58754ab064aaf53c387dd] url: https://github.com/intel-lab-lkp/linux/commits/Dmitry-Baryshkov/clk-qcom-dispcc-sm8250-use-CLK_SET_RATE_PARENT-for-branch-clocks/20240804-134328 base: 668d33c9ff922c4590c58754ab064aaf53c387dd patch link: https://lore.kernel.org/r/20240804-sm8350-fixes-v1-7-1149dd8399fe%40linaro.org patch subject: [PATCH 07/11] dt-bindings: interconnect: qcom,sm8450: drop DISP nodes config: arm64-randconfig-051-20240804 (https://download.01.org/0day-ci/archive/20240804/202408041643.qhy043eg-...@intel.com/config) compiler: aarch64-linux-gcc (GCC) 14.1.0 dtschema version: 2024.6.dev8+gf13c181 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240804/202408041643.qhy043eg-...@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/202408041643.qhy043eg-...@intel.com/ All errors (new ones prefixed by >>): >> Error: arch/arm64/boot/dts/qcom/sm8450.dtsi:3055.31-32 syntax error FATAL ERROR: Unable to parse input tree -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v5 1/2] drm/loongson: Introduce component framework support
Hi Sui,
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.11-rc1 next-20240802]
[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/Sui-Jingfeng/drm-loongson-Introduce-component-framework-support/20240728-233029
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:
https://lore.kernel.org/r/20240728152858.346211-2-sui.jingfeng%40linux.dev
patch subject: [PATCH v5 1/2] drm/loongson: Introduce component framework
support
config: mips-randconfig-r111-20240802
(https://download.01.org/0day-ci/archive/20240803/202408031152.pavm0tor-...@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project
430b90f04533b099d788db2668176038be38c53b)
reproduce:
(https://download.01.org/0day-ci/archive/20240803/202408031152.pavm0tor-...@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/202408031152.pavm0tor-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/loongson/lsdc_drv.c:154:28: sparse: sparse: symbol
>> 'lsdc_pci_component_ops' was not declared. Should it be static?
vim +/lsdc_pci_component_ops +154 drivers/gpu/drm/loongson/lsdc_drv.c
153
> 154 const struct component_ops lsdc_pci_component_ops = {
155 .bind = lsdc_pci_component_bind,
156 .unbind = lsdc_pci_component_unbind,
157 };
158
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 3/5] dma-buf: heaps: support alloc async read file
Hi Huan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 931a3b3bccc96e7708c82b30b2b5fa82dfd04890]
url:
https://github.com/intel-lab-lkp/linux/commits/Huan-Yang/dma-buf-heaps-Introduce-DMA_HEAP_ALLOC_AND_READ_FILE-heap-flag/20240730-170340
base: 931a3b3bccc96e7708c82b30b2b5fa82dfd04890
patch link:https://lore.kernel.org/r/20240730075755.10941-4-link%40vivo.com
patch subject: [PATCH v2 3/5] dma-buf: heaps: support alloc async read file
config: xtensa-allyesconfig
(https://download.01.org/0day-ci/archive/20240731/202407312202.lhltlehx-...@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240731/202407312202.lhltlehx-...@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/202407312202.lhltlehx-...@intel.com/
All warnings (new ones prefixed by >>):
drivers/dma-buf/dma-heap.c:45: warning: Function parameter or struct member
'priv' not described in 'dma_heap'
drivers/dma-buf/dma-heap.c:45: warning: Function parameter or struct member
'heap_devt' not described in 'dma_heap'
drivers/dma-buf/dma-heap.c:45: warning: Function parameter or struct member
'list' not described in 'dma_heap'
drivers/dma-buf/dma-heap.c:45: warning: Function parameter or struct member
'heap_cdev' not described in 'dma_heap'
>> drivers/dma-buf/dma-heap.c:158: warning: Function parameter or struct member
>> 'lock' not described in 'dma_heap_file_control'
drivers/dma-buf/dma-heap.c:482: warning: expecting prototype for Trigger
sync file read, read into dma(). Prototype was for dma_heap_read_file_sync()
instead
vim +158 drivers/dma-buf/dma-heap.c
133
134 /**
135 * struct dma_heap_file_control - global control of dma_heap file read.
136 * @works: @dma_heap_file_work's list head.
137 *
138 * @threadwq: wait queue for @work_thread, if commit work,
@work_thread
139 * wakeup and read this work's file contains.
140 *
141 * @workwq: used for main thread wait for file read end, if
allocation
142 * end before file read. @dma_heap_file_task ref
effect this.
143 *
144 * @work_thread:file read kthread. the dma_heap_file_task
work's consumer.
145 *
146 * @heap_fwork_cachep: @dma_heap_file_work's cachep, it's alloc/free
frequently.
147 *
148 * @nr_work:global number of how many work committed.
149 */
150 struct dma_heap_file_control {
151 struct list_head works;
152 spinlock_t lock; // only lock for @works.
153 wait_queue_head_t threadwq;
154 wait_queue_head_t workwq;
155 struct task_struct *work_thread;
156 struct kmem_cache *heap_fwork_cachep;
157 atomic_t nr_work;
> 158 };
159
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 1/5] dma-buf: heaps: Introduce DMA_HEAP_ALLOC_AND_READ_FILE heap flag
Hi Huan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 931a3b3bccc96e7708c82b30b2b5fa82dfd04890]
url:
https://github.com/intel-lab-lkp/linux/commits/Huan-Yang/dma-buf-heaps-Introduce-DMA_HEAP_ALLOC_AND_READ_FILE-heap-flag/20240730-170340
base: 931a3b3bccc96e7708c82b30b2b5fa82dfd04890
patch link:https://lore.kernel.org/r/20240730075755.10941-2-link%40vivo.com
patch subject: [PATCH v2 1/5] dma-buf: heaps: Introduce
DMA_HEAP_ALLOC_AND_READ_FILE heap flag
config: xtensa-allyesconfig
(https://download.01.org/0day-ci/archive/20240731/202407311822.znenmq5i-...@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240731/202407311822.znenmq5i-...@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/202407311822.znenmq5i-...@intel.com/
All warnings (new ones prefixed by >>):
drivers/dma-buf/dma-heap.c:44: warning: Function parameter or struct member
'priv' not described in 'dma_heap'
drivers/dma-buf/dma-heap.c:44: warning: Function parameter or struct member
'heap_devt' not described in 'dma_heap'
drivers/dma-buf/dma-heap.c:44: warning: Function parameter or struct member
'list' not described in 'dma_heap'
drivers/dma-buf/dma-heap.c:44: warning: Function parameter or struct member
'heap_cdev' not described in 'dma_heap'
>> drivers/dma-buf/dma-heap.c:104: warning: expecting prototype for Trigger
>> sync file read, read into dma(). Prototype was for dma_heap_read_file_sync()
>> instead
vim +104 drivers/dma-buf/dma-heap.c
86
87 /**
88 * Trigger sync file read, read into dma-buf.
89 *
90 * @dmabuf: which we done alloced and export.
91 * @heap_file: file info wrapper to read from.
92 *
93 * Whether to use buffer I/O or direct I/O depends on the mode when the
94 * file is opened.
95 * Remember, if use direct I/O, file must be page aligned.
96 * Since the buffer used for file reading is provided by dma-buf, when
97 * using direct I/O, the file content will be directly filled into
98 * dma-buf without the need for additional CPU copying.
99 *
100 * 0 on success, negative if anything wrong.
101 */
102 static int dma_heap_read_file_sync(struct dma_buf *dmabuf,
103 struct dma_heap_file *heap_file)
> 104 {
105 struct iosys_map map;
106 ssize_t bytes;
107 int ret;
108
109 ret = dma_buf_vmap(dmabuf, &map);
110 if (ret)
111 return ret;
112
113 /**
114 * The kernel_read_file function can handle file reading
effectively,
115 * and if the return value does not match the file size,
116 * then it indicates an error.
117 */
118 bytes = kernel_read_file(heap_file->file, 0, &map.vaddr,
dmabuf->size,
119 &heap_file->fsize, READING_POLICY);
120 if (bytes != heap_file->fsize)
121 ret = -EIO;
122
123 dma_buf_vunmap(dmabuf, &map);
124
125 return ret;
126 }
127
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[drm-misc:drm-misc-next 2/37] drivers/gpu/drm/nouveau/nouveau_platform.c:29:13: warning: unused variable 'ret'
tree: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
head: 61671d85def2960bbf52db22e9e45b3bf8a5ceb5
commit: 961ae5f9807bb15af0065485785725768a7269b9 [2/37] drm/nouveau: handle
pci/tegra drm_dev_{alloc, register} from common code
config: arm-randconfig-004-20240728
(https://download.01.org/0day-ci/archive/20240729/202407290133.ijzaiy24-...@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/20240729/202407290133.ijzaiy24-...@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/202407290133.ijzaiy24-...@intel.com/
All warnings (new ones prefixed by >>):
drivers/gpu/drm/nouveau/nouveau_platform.c: In function
'nouveau_platform_probe':
>> drivers/gpu/drm/nouveau/nouveau_platform.c:29:13: warning: unused variable
>> 'ret' [-Wunused-variable]
29 | int ret;
| ^~~
vim +/ret +29 drivers/gpu/drm/nouveau/nouveau_platform.c
8ba9ff11632cb0 Alexandre Courbot 2014-06-26 23
8ba9ff11632cb0 Alexandre Courbot 2014-06-26 24 static int
nouveau_platform_probe(struct platform_device *pdev)
8ba9ff11632cb0 Alexandre Courbot 2014-06-26 25 {
e396ecd178c6c8 Alexandre Courbot 2015-09-04 26 const struct
nvkm_device_tegra_func *func;
870571a5698b2e Thierry Reding2016-02-24 27 struct nvkm_device
*device = NULL;
8ba9ff11632cb0 Alexandre Courbot 2014-06-26 28 struct drm_device *drm;
43a70661eaa64a Ben Skeggs2015-08-20 @29 int ret;
8ba9ff11632cb0 Alexandre Courbot 2014-06-26 30
e396ecd178c6c8 Alexandre Courbot 2015-09-04 31 func =
of_device_get_match_data(&pdev->dev);
e396ecd178c6c8 Alexandre Courbot 2015-09-04 32
e396ecd178c6c8 Alexandre Courbot 2015-09-04 33 drm =
nouveau_platform_device_create(func, pdev, &device);
43a70661eaa64a Ben Skeggs2015-08-20 34 if (IS_ERR(drm))
43a70661eaa64a Ben Skeggs2015-08-20 35 return
PTR_ERR(drm);
8ba9ff11632cb0 Alexandre Courbot 2014-06-26 36
43a70661eaa64a Ben Skeggs2015-08-20 37 return 0;
8ba9ff11632cb0 Alexandre Courbot 2014-06-26 38 }
8ba9ff11632cb0 Alexandre Courbot 2014-06-26 39
:: The code at line 29 was first introduced by commit
:: 43a70661eaa64aa4e36e421eee3b9ded3190837b drm/nouveau/tegra: merge
platform setup from nouveau drm
:: TO: Ben Skeggs
:: CC: Ben Skeggs
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 2/2] drm/tiny: Add driver for Sharp Memory LCD
Hi Alex, kernel test robot noticed the following build warnings: [auto build test WARNING on robh/for-next] [also build test WARNING on drm-misc/drm-misc-next linus/master v6.10 next-20240726] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Alex-Lanzano/dt-bindings-display-Add-Sharp-Memory-LCD-bindings/20240727-035313 base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next patch link: https://lore.kernel.org/r/20240726194456.1336484-3-lanzano.alex%40gmail.com patch subject: [PATCH v2 2/2] drm/tiny: Add driver for Sharp Memory LCD reproduce: (https://download.01.org/0day-ci/archive/20240727/202407270505.adlarsms-...@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/202407270505.adlarsms-...@intel.com/ All warnings (new ones prefixed by >>): Warning: Documentation/devicetree/bindings/power/wakeup-source.txt references a file that doesn't exist: Documentation/devicetree/bindings/input/qcom,pm8xxx-keypad.txt Warning: Documentation/devicetree/bindings/regulator/siliconmitus,sm5703-regulator.yaml references a file that doesn't exist: Documentation/devicetree/bindings/mfd/siliconmitus,sm5703.yaml Warning: Documentation/userspace-api/netlink/index.rst references a file that doesn't exist: Documentation/networking/netlink_spec/index.rst Warning: Documentation/userspace-api/netlink/specs.rst references a file that doesn't exist: Documentation/networking/netlink_spec/index.rst Warning: MAINTAINERS references a file that doesn't exist: Documentation/devicetree/bindings/reserved-memory/qcom >> Warning: MAINTAINERS references a file that doesn't exist: >> Documentation/devicetree/bindings/display/sharp,sharp-memory.yaml Warning: MAINTAINERS references a file that doesn't exist: Documentation/devicetree/bindings/display/exynos/ Warning: MAINTAINERS references a file that doesn't exist: Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt Using alabaster theme -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
[drm-misc:drm-misc-next 3/4] drivers/gpu/drm/drm_crtc_internal.h:324: multiple definition of `drm_panic_is_enabled'; drivers/gpu/drm/drm_atomic_helper.o:drivers/gpu/drm/drm_crtc_internal.h:324: first
tree: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
head: 7e33fc2ff6754b5ff39b11297f713cd0841d9962
commit: c2c2a91f3868515969a758042887fdc722216525 [3/4] drm/fb-helper: Set
skip_panic if the drm driver supports drm panic
config: i386-randconfig-011-20240720
(https://download.01.org/0day-ci/archive/20240721/202407210342.prqxrmzf-...@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240721/202407210342.prqxrmzf-...@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/202407210342.prqxrmzf-...@intel.com/
Note: the drm-misc/drm-misc-next HEAD 7e33fc2ff6754b5ff39b11297f713cd0841d9962
builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
ld: drivers/gpu/drm/drm_fb_helper.o: in function `drm_panic_is_enabled':
>> drivers/gpu/drm/drm_crtc_internal.h:324: multiple definition of
>> `drm_panic_is_enabled';
>> drivers/gpu/drm/drm_atomic_helper.o:drivers/gpu/drm/drm_crtc_internal.h:324:
>> first defined here
vim +324 drivers/gpu/drm/drm_crtc_internal.h
d70ca9069042c3 Jani Nikula 2024-03-08 319
9f774c42a908af Jocelyn Falempe 2024-07-17 320 /* drm_panic.c */
9f774c42a908af Jocelyn Falempe 2024-07-17 321 #ifdef CONFIG_DRM_PANIC
9f774c42a908af Jocelyn Falempe 2024-07-17 322 bool
drm_panic_is_enabled(struct drm_device *dev);
9f774c42a908af Jocelyn Falempe 2024-07-17 323 #else
9f774c42a908af Jocelyn Falempe 2024-07-17 @324 bool
drm_panic_is_enabled(struct drm_device *dev) {return false; }
9f774c42a908af Jocelyn Falempe 2024-07-17 325 #endif
9f774c42a908af Jocelyn Falempe 2024-07-17 326
:: The code at line 324 was first introduced by commit
:: 9f774c42a908affba615bbed7463dd4f904dd5f1 drm/panic: Add
drm_panic_is_enabled()
:: TO: Jocelyn Falempe
:: CC: Jocelyn Falempe
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[drm-misc:drm-misc-next 4/4] drivers/gpu/drm/drm_panic.c:712:6: error: no previous prototype for function 'drm_panic_is_enabled'
Hi Jocelyn,
First bad commit (maybe != root cause):
tree: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
head: 7e33fc2ff6754b5ff39b11297f713cd0841d9962
commit: 3a9b77cee7502f7450c725d4ead2c4a44924d158 [4/4] drm/panic: Remove build
time dependency with FRAMEBUFFER_CONSOLE
config: x86_64-allyesconfig
(https://download.01.org/0day-ci/archive/20240721/202407210209.qmitlgt0-...@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project
617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240721/202407210209.qmitlgt0-...@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/202407210209.qmitlgt0-...@intel.com/
Note: the drm-misc/drm-misc-next HEAD 7e33fc2ff6754b5ff39b11297f713cd0841d9962
builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/drm_panic.c:712:6: error: no previous prototype for function
>> 'drm_panic_is_enabled' [-Werror,-Wmissing-prototypes]
712 | bool drm_panic_is_enabled(struct drm_device *dev)
| ^
drivers/gpu/drm/drm_panic.c:712:1: note: declare 'static' if the function is
not intended to be used outside of this translation unit
712 | bool drm_panic_is_enabled(struct drm_device *dev)
| ^
| static
1 error generated.
vim +/drm_panic_is_enabled +712 drivers/gpu/drm/drm_panic.c
813ca3aa8fecac Jocelyn Falempe 2024-04-09 705
9f774c42a908af Jocelyn Falempe 2024-07-17 706 /**
9f774c42a908af Jocelyn Falempe 2024-07-17 707 * drm_panic_is_enabled
9f774c42a908af Jocelyn Falempe 2024-07-17 708 * @dev: the drm device that
may supports drm_panic
9f774c42a908af Jocelyn Falempe 2024-07-17 709 *
9f774c42a908af Jocelyn Falempe 2024-07-17 710 * returns true if the drm
device supports drm_panic
9f774c42a908af Jocelyn Falempe 2024-07-17 711 */
9f774c42a908af Jocelyn Falempe 2024-07-17 @712 bool
drm_panic_is_enabled(struct drm_device *dev)
9f774c42a908af Jocelyn Falempe 2024-07-17 713 {
9f774c42a908af Jocelyn Falempe 2024-07-17 714 struct drm_plane *plane;
9f774c42a908af Jocelyn Falempe 2024-07-17 715
9f774c42a908af Jocelyn Falempe 2024-07-17 716 if
(!dev->mode_config.num_total_plane)
9f774c42a908af Jocelyn Falempe 2024-07-17 717 return false;
9f774c42a908af Jocelyn Falempe 2024-07-17 718
9f774c42a908af Jocelyn Falempe 2024-07-17 719
drm_for_each_plane(plane, dev)
9f774c42a908af Jocelyn Falempe 2024-07-17 720 if
(plane->helper_private && plane->helper_private->get_scanout_buffer)
9f774c42a908af Jocelyn Falempe 2024-07-17 721 return
true;
9f774c42a908af Jocelyn Falempe 2024-07-17 722 return false;
9f774c42a908af Jocelyn Falempe 2024-07-17 723 }
9f774c42a908af Jocelyn Falempe 2024-07-17 724
EXPORT_SYMBOL(drm_panic_is_enabled);
9f774c42a908af Jocelyn Falempe 2024-07-17 725
:: The code at line 712 was first introduced by commit
:: 9f774c42a908affba615bbed7463dd4f904dd5f1 drm/panic: Add
drm_panic_is_enabled()
:: TO: Jocelyn Falempe
:: CC: Jocelyn Falempe
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[drm-misc:drm-misc-next 2/4] ERROR: modpost: "panic_cpu" [drivers/video/fbdev/core/fb.ko] undefined!
tree: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next head: 7e33fc2ff6754b5ff39b11297f713cd0841d9962 commit: d20a9f568f99591886ec73b80ff7283486710643 [2/4] fbcon: Add an option to disable fbcon in panic config: i386-randconfig-005-20240720 (https://download.01.org/0day-ci/archive/20240721/202407210203.2isiic9m-...@intel.com/config) compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240721/202407210203.2isiic9m-...@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/202407210203.2isiic9m-...@intel.com/ All errors (new ones prefixed by >>, old ones prefixed by <<): WARNING: modpost: missing MODULE_DESCRIPTION() in security/keys/trusted-keys/trusted.o WARNING: modpost: missing MODULE_DESCRIPTION() in crypto/curve25519-generic.o WARNING: modpost: missing MODULE_DESCRIPTION() in lib/kunit/kunit-test.o WARNING: modpost: missing MODULE_DESCRIPTION() in lib/kunit/kunit-example-test.o WARNING: modpost: missing MODULE_DESCRIPTION() in lib/math/prime_numbers.o WARNING: modpost: missing MODULE_DESCRIPTION() in lib/crypto/libarc4.o WARNING: modpost: missing MODULE_DESCRIPTION() in lib/crypto/libdes.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/pinctrl/pinctrl-mcp23s08_i2c.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/pinctrl/pinctrl-mcp23s08.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/gpio/gpio-gw-pld.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/gpio/gpio-pcf857x.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/pci/controller/pci-host-common.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/pci/controller/pci-host-generic.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/video/fbdev/matrox/matroxfb_accel.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/video/fbdev/matrox/matroxfb_DAC1064.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/video/fbdev/matrox/matroxfb_Ti3026.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/video/fbdev/kyro/kyrofb.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/video/fbdev/goldfishfb.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/video/fbdev/vfb.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/clk/clk_test.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/clk/clk-gate_test.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/clk/clk-fractional-divider_test.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/regulator/rt4831-regulator.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/tty/serial/8250/serial_cs.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/tty/goldfish.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/char/agp/ati-agp.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/char/agp/amd-k7-agp.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/char/agp/amd64-agp.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/char/lp.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/char/tlclk.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/base/regmap/regmap-kunit.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/base/regmap/regmap-ram.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/base/regmap/regmap-raw-ram.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/base/regmap/regmap-spmi.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/dax/dax.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/dax/device_dax.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/firewire/uapi-test.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/auxdisplay/hd44780_common.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/auxdisplay/line-display.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/pcmcia/i82092.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/input/touchscreen/cyttsp_i2c_common.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/input/matrix-keymap.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/rtc/rtc-tps65910.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/i2c/busses/i2c-pxa.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/media/radio/si470x/radio-si470x-common.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/hwmon/corsair-cpro.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/cpufreq/cpufreq-dt-platdev.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/leds/simple/simatic-ipc-leds.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/leds/simple/simatic-ipc-leds-gpio-core.o WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/leds/simple/simatic-i
[drm-misc:drm-misc-next 4/4] drivers/gpu/drm/drm_panic.c:712:6: error: no previous prototype for 'drm_panic_is_enabled'
Hi Jocelyn,
First bad commit (maybe != root cause):
tree: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
head: 7e33fc2ff6754b5ff39b11297f713cd0841d9962
commit: 3a9b77cee7502f7450c725d4ead2c4a44924d158 [4/4] drm/panic: Remove build
time dependency with FRAMEBUFFER_CONSOLE
config: i386-allmodconfig
(https://download.01.org/0day-ci/archive/20240721/202407210102.cvf3sr4i-...@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240721/202407210102.cvf3sr4i-...@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/202407210102.cvf3sr4i-...@intel.com/
Note: the drm-misc/drm-misc-next HEAD 7e33fc2ff6754b5ff39b11297f713cd0841d9962
builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/drm_panic.c:712:6: error: no previous prototype for
>> 'drm_panic_is_enabled' [-Werror=missing-prototypes]
712 | bool drm_panic_is_enabled(struct drm_device *dev)
| ^~~~
cc1: all warnings being treated as errors
vim +/drm_panic_is_enabled +712 drivers/gpu/drm/drm_panic.c
813ca3aa8fecac Jocelyn Falempe 2024-04-09 705
9f774c42a908af Jocelyn Falempe 2024-07-17 706 /**
9f774c42a908af Jocelyn Falempe 2024-07-17 707 * drm_panic_is_enabled
9f774c42a908af Jocelyn Falempe 2024-07-17 708 * @dev: the drm device that
may supports drm_panic
9f774c42a908af Jocelyn Falempe 2024-07-17 709 *
9f774c42a908af Jocelyn Falempe 2024-07-17 710 * returns true if the drm
device supports drm_panic
9f774c42a908af Jocelyn Falempe 2024-07-17 711 */
9f774c42a908af Jocelyn Falempe 2024-07-17 @712 bool
drm_panic_is_enabled(struct drm_device *dev)
9f774c42a908af Jocelyn Falempe 2024-07-17 713 {
9f774c42a908af Jocelyn Falempe 2024-07-17 714 struct drm_plane *plane;
9f774c42a908af Jocelyn Falempe 2024-07-17 715
9f774c42a908af Jocelyn Falempe 2024-07-17 716 if
(!dev->mode_config.num_total_plane)
9f774c42a908af Jocelyn Falempe 2024-07-17 717 return false;
9f774c42a908af Jocelyn Falempe 2024-07-17 718
9f774c42a908af Jocelyn Falempe 2024-07-17 719
drm_for_each_plane(plane, dev)
9f774c42a908af Jocelyn Falempe 2024-07-17 720 if
(plane->helper_private && plane->helper_private->get_scanout_buffer)
9f774c42a908af Jocelyn Falempe 2024-07-17 721 return
true;
9f774c42a908af Jocelyn Falempe 2024-07-17 722 return false;
9f774c42a908af Jocelyn Falempe 2024-07-17 723 }
9f774c42a908af Jocelyn Falempe 2024-07-17 724
EXPORT_SYMBOL(drm_panic_is_enabled);
9f774c42a908af Jocelyn Falempe 2024-07-17 725
:: The code at line 712 was first introduced by commit
:: 9f774c42a908affba615bbed7463dd4f904dd5f1 drm/panic: Add
drm_panic_is_enabled()
:: TO: Jocelyn Falempe
:: CC: Jocelyn Falempe
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
