Changes in Makefile

f875976e - staging: vc04_services: Drop vchiq_connected.[ch] files

Fri, 12 Apr 2024 07:57:37 +0000

staging: vc04_services: Drop vchiq_connected.[ch] filesThe vchiq_connected.[ch] just implements two function:- vchiq_add_connected_callback()- vchiq_call_connected_callbacks()for the deferred vchiq callbacks. Those can easily live invchiq_arm.[ch], hence move them. This allows making thevchiq_call_connected_callbacks() function static.The move doesn't copy over MAX_CALLBACKS because it is the same asVCHIQ_DRV_MAX_CALLBACKS. Hence, it now being used invchiq_add_connected_callback().No functional changes intended in this patch.Suggested-by: Laurent Pinchart Reviewed-by: Laurent Pinchart Signed-off-by: Umang Jain Link: https://lore.kernel.org/r/20240412075743.60712-6-umang.jain@ideasonboard.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

027e5703 - staging: vc04_services: vchiq_arm: Add new bus type and device type

Sat, 23 Sep 2023 14:31:57 +0000

staging: vc04_services: vchiq_arm: Add new bus type and device typeThe devices that the vchiq interface registers (bcm2835-audio,bcm2835-camera) are implemented and exposed by the VC04 firmware.The device tree describes the VC04 itself with the resources requiredto communicate with it through a mailbox interface. However, thevchiq interface registers these devices as platform devices. Thisalso means the specific drivers for these devices are gettingregistered as platform drivers. This is not correct and a blatantabuse of platform device/driver.Add a new bus type, vchiq_bus_type and device type (struct vchiq_device)which will be used to migrate child devices that the vchiq interfacescreates/registers from the platform device/driver.Signed-off-by: Umang Jain Link: https://lore.kernel.org/r/20230923143200.268063-4-umang.jain@ideasonboard.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

2529ca21 - staging: vc04_services: interface: Drop include Makefile directive

Fri, 20 Jan 2023 20:11:03 +0000

staging: vc04_services: interface: Drop include Makefile directiveDrop the include directive. They can break the build, when one onlywants to build a subdirectory. Replace with "../" for the includes,in the interface/ files instead.Suggested-by: Greg Kroah-Hartman Signed-off-by: Umang Jain Link: https://lore.kernel.org/r/20230120201104.606876-6-umang.jain@ideasonboard.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

7b9148dc - staging: vchiq: Combine vchiq platform code into single file

Wed, 21 Jul 2021 16:20:53 +0000

staging: vchiq: Combine vchiq platform code into single fileCombine the vchiq platform initialization code into a single file bymerging vchiq_2835_arm.c into vchiq_arm.cReviewed-by: Stefan Wahren Signed-off-by: Ojaswin Mujoo Link: https://lore.kernel.org/r/647cad50aa3306d1a49bacff76eaa3130fb363f4.1626882325.git.ojaswin98@gmail.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

2b5930fb - staging: vchiq: Make creation of vchiq cdev optional

Wed, 21 Jul 2021 16:20:52 +0000

staging: vchiq: Make creation of vchiq cdev optionalBefore this commit, vchiq cdev (/dev/vchiq) was always created duringplatform initialization. Introduce a new Kconfig optionCONFIG_VCHIQ_CDEV which determines if the cdev will be created or not.Reviewed-by: Stefan Wahren Signed-off-by: Ojaswin Mujoo Link: https://lore.kernel.org/r/846c424dd4aae14d1cc28c8f30877a06e2b7dd10.1626882325.git.ojaswin98@gmail.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

f0591628 - staging: vchiq: Move vchiq char driver to its own file

Wed, 21 Jul 2021 16:20:51 +0000

staging: vchiq: Move vchiq char driver to its own fileSplit the initialization code of vchiq char driver and device files fromthat of vchiq platform. The char driver code now resides in vchiq_dev.cand the platform code resides in the original vchiq_arm.c file.This commit focuses on separating the code into different files whilemaintaining the same functionality. It does not completely decouple themas the cdev init code is still called from the platform's vchiq_probe()function.Reviewed-by: Stefan Wahren Signed-off-by: Ojaswin Mujoo Link: https://lore.kernel.org/r/ed53690e217f631b746aad0585fccaa6fb1453c1.1626882325.git.ojaswin98@gmail.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

8ba5f91b - staging: vc04_services: remove VCCOREVER

Sat, 15 May 2021 19:10:43 +0000

staging: vc04_services: remove __VCCOREVER__This define isn't used anymore. Let's remove it.Signed-off-by: Stefan Wahren Link: https://lore.kernel.org/r/1621105859-30215-5-git-send-email-stefan.wahren@i2se.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

2ad4ba07 - staging: vchiq: Move vchiq.h into include directory

Mon, 29 Jun 2020 15:09:45 +0000

staging: vchiq: Move vchiq.h into include directoryTo make the separation clear between vchiq's header files and vchiq.h,which is to be used by services and is the 'public' API, move it into adedicated includes directory.Signed-off-by: Nicolas Saenz Julienne Link: https://lore.kernel.org/r/20200629150945.10720-48-nsaenzjulienne@suse.deSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

9d523111 - staging: vchiq: Get rid of vchi

Mon, 29 Jun 2020 15:09:41 +0000

staging: vchiq: Get rid of vchiAll the functions that vchi currently provides are a 1:1 mapping to itsvchiq counterparts. Get rid of vchi altogether and use vchiq's on allservices.In the process also get rid of the vchi directory, as the only remainingfile was a TODO file, which now lives in the parent directory.Signed-off-by: Nicolas Saenz Julienne Link: https://lore.kernel.org/r/20200629150945.10720-44-nsaenzjulienne@suse.deSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

77b3f6c4 - staging: vchiq: Move message queue into struct vchiq_service

Mon, 29 Jun 2020 15:09:21 +0000

staging: vchiq: Move message queue into struct vchiq_serviceThis has historically been handled by vchi, but there is no reason whythis couldn't be handled directly in vchiq.The patch tries to avoid altering any behavior, with the exception ofthe msg_queue size, which is now fixed to VCHIQ_MAX_SLOTS (it was set toVCHIQ_MAX_SLOTS / 2). This is done to match vchiq's user_service messagequeue, which could be merged with this one in the future.Signed-off-by: Nicolas Saenz Julienne Link: https://lore.kernel.org/r/20200629150945.10720-24-nsaenzjulienne@suse.deSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

b18ee53a - staging: bcm2835: Break MMAL support out from camera

Tue, 23 Jun 2020 16:41:47 +0000

staging: bcm2835: Break MMAL support out from cameraThe BCM2835 camera host is currently the only component that uses theVCHIQ MMAL interface. This will soon change with the upporting ofBCM2835 ISP, which make use of the same interface.Break VCHIQ MMAL interface support out from camera host directory tomake it possible for the ISP driver to use it as well.The only modification to the existing mmal code is the introduction ofEXPORT_SYMBOL() for symbols required by bcm2835-camera and the additionof the module author and licenses.Signed-off-by: Jacopo Mondi Signed-off-by: Nicolas Saenz Julienne Link: https://lore.kernel.org/r/20200623164235.29566-2-nsaenzjulienne@suse.deSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

e895bc1e - staging: vc04_services: remove header include path to vc04_services

Fri, 10 Jan 2020 13:56:15 +0000

staging: vc04_services: remove header include path to vc04_servicesFix up some relative paths in #include "..." directives, and removethe include path to drivers/staging/vc04_services.Signed-off-by: Masahiro Yamada Link: https://lore.kernel.org/r/20200110135615.11617-1-masahiroy@kernel.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

0b55753f - staging: vc04_services: Remove defines from Makefile

Sat, 28 Apr 2018 15:47:45 +0000

staging: vc04_services: Remove defines from MakefileThe definition of USE_VCHIQ_ARM and VCOS_VERIFY_BKPTS isn't really necessaryso remove them.Signed-off-by: Stefan Wahren Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

5c5e6ef6 - staging: vc04_services: merge vchiq_kern_lib.c into vchiq_arm.c

Fri, 02 Feb 2018 15:01:46 +0000

staging: vc04_services: merge vchiq_kern_lib.c into vchiq_arm.cThere are two incompatible definitions of 'vchiq_instance_struct', sopassing them through vchiq_initialise(), vchiq_connect() or anothersuch interface is broken, as shown by building the driver with link-timeoptimizations:drivers/staging/vc04_services/interface/vchiq_arm/vchiq_if.h:129:0: error: type of 'vchiq_initialise' does not match original declaration [-Werror=lto-type-mismatch] extern VCHIQ_STATUS_T vchiq_initialise(VCHIQ_INSTANCE_T *pinstance);drivers/staging/vc04_services/interface/vchiq_arm/vchiq_kern_lib.c:68:0: note: 'vchiq_initialise' was previously declared here VCHIQ_STATUS_T vchiq_initialise(VCHIQ_INSTANCE_T *instance_out)drivers/staging/vc04_services/interface/vchiq_arm/vchiq_kern_lib.c:68:0: note: code may be misoptimized unless -fno-strict-aliasing is useddrivers/staging/vc04_services/interface/vchiq_arm/vchiq_if.h:131:0: error: type of 'vchiq_connect' does not match original declaration [-Werror=lto-type-mismatch] extern VCHIQ_STATUS_T vchiq_connect(VCHIQ_INSTANCE_T instance);drivers/staging/vc04_services/interface/vchiq_arm/vchiq_kern_lib.c:168:0: note: 'vchiq_connect' was previously declared here VCHIQ_STATUS_T vchiq_connect(VCHIQ_INSTANCE_T instance)It's possible that only one of the two sides actually access the members,but it's clear that they need to agree on the layout. The easiest wayto achieve this appears to be to merge the two files into one. I triedmoving the structure definition into a shared header first, but endedup running into too many interdependencies that way.Signed-off-by: Arnd Bergmann Acked-by: Stefan Wahren Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

212afb97 - staging: bcm2835-camera: Move driver under vc04_services

Mon, 27 Feb 2017 23:35:13 +0000

staging: bcm2835-camera: Move driver under vc04_servicesThe bcm2835-camera driver is part of v04_services, so it makessense for it to be located under vc04_services to makeconfiguration clearer.Signed-off-by: Michael Zoran Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

051420a9 - staging: bcm2835-audio: Move driver under vc04_services

Mon, 27 Feb 2017 23:35:12 +0000

staging: bcm2835-audio: Move driver under vc04_servicesThe bcm2835-audio driver is part of v04_services, so it makessense for it to be located under vc04_services to makeconfiguration clearer.Signed-off-by: Michael Zoran Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

32774ef3 - staging: vc04_services: use bcm2835 consequently

Wed, 26 Oct 2016 18:34:21 +0000

staging: vc04_services: use bcm2835 consequentlyThe naming bcm2708 is used only in the vendor kernel, so betterreplace it with bcm2835 which is used in mainline in orderto avoid any confusion.Signed-off-by: Stefan Wahren Reviewed-by: Eric Anholt Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile

71bad7f0 - staging: add bcm2708 vchiq driver

Tue, 02 Jul 2013 22:42:01 +0000

staging: add bcm2708 vchiq driverSigned-off-by: popcornmix vchiq: create_pagelist copes with vmalloc memorySigned-off-by: Daniel Stone vchiq: fix the shim message releaseSigned-off-by: Daniel Stone vchiq: export additional symbolsSigned-off-by: Daniel Stone VCHIQ: Make service closure fully synchronous (drv)This is one half of a two-part patch, the other half of which is tothe vchiq_lib user library. With these patches, calls tovchiq_close_service and vchiq_remove_service won't return until anyassociated callbacks have been delivered to the callback thread.VCHIQ: Add per-service tracingThe new service option VCHIQ_SERVICE_OPTION_TRACE is a boolean thattoggles tracing for the specified service.This commit also introduces vchi_service_set_option and the associatedoption VCHI_SERVICE_OPTION_TRACE.vchiq: Make the synchronous-CLOSE logic more tolerantvchiq: Move logging control into debugfsvchiq: Take care of a corner case tickled by VCSMClosing a connection that isn't fully open requires care, since oneside does not know the other side's port number. Code was present tohandle the case where a CLOSE is sent immediately after an OPEN, i.e.before the OPENACK has been received, but this was incorrectly beingused when an OPEN from a client using port 0 was rejected.(In the observed failure, the host was attempting to use the VCSMservice, which isn't present in the 'cutdown' firmware. The failurewas intermittent because sometimes the keepalive service wouldgrab port 0.)This case can be distinguished because the client's remoteport willstill be VCHIQ_PORT_FREE, and the srvstate will be OPENING. Eithercondition is sufficient to differentiate it from the special casedescribed above.vchiq: Avoid high load when blocked and unkillablevchiq: Include SIGSTOP and SIGCONT in list of signals not-masked by vchiq to allow gdb to workvchiq_arm: Complete support for SYNCHRONOUS modevchiq: Remove inline from suspend/resumevchiq: Allocation does not need to be atomicvchiq: Fix wrong condition checkThe log level is checked from within the log call. Remove the check in the call.Signed-off-by: Pranith Kumar BCM270x: Add vchiq device to platform file and Device TreePrepare to turn the vchiq module into a driver.Signed-off-by: Noralf Trønnes bcm2708: vchiq: Add Device Tree supportTurn vchiq into a driver and stop hardcoding resources.Use devm_* functions in probe path to simplify cleanup.A global variable is used to hold the register address. This is doneto keep this patch as small as possible.Also make available on ARCH_BCM2835.Based on work by Lubomir Rintel.Signed-off-by: Noralf Trønnes vchiq: Change logging level for inbound datavchiq_arm: Two cacheing fixes1) Make fragment size vary with cache line sizeWithout this patch, non-cache-line-aligned transfers may corrupt(or be corrupted by) adjacent data structures.Both ARM and VC need to be updated to enable this feature. This isensured by having the loader apply a new DT parameter -cache-line-size. The existence of this parameter guarantees that thekernel is capable, and the parameter will only be modified from thesafe default if the loader is capable.2) Flush/invalidate vmalloc'd memory, and invalidate after readsvchiq: fix NULL pointer dereference when closing driverThe following code run as root will cause a null pointer dereference oops: int fd = open("/dev/vc-cma", O_RDONLY); if (fd < 0) err(1, "open failed"); (void)close(fd);[ 1704.877721] Unable to handle kernel NULL pointer dereference at virtual address 00000000[ 1704.877725] pgd = b899c000[ 1704.877736] [00000000] *pgd=37fab831, *pte=00000000, *ppte=00000000[ 1704.877748] Internal error: Oops: 817 [#1] PREEMPT SMP ARM[ 1704.877765] Modules linked in: evdev i2c_bcm2708 uio_pdrv_genirq uio[ 1704.877774] CPU: 2 PID: 3656 Comm: stress-ng-fstat Not tainted 3.19.1-12-generic-bcm2709 #12-Ubuntu[ 1704.877777] Hardware name: BCM2709[ 1704.877783] task: b8ab9b00 ti: b7e68000 task.ti: b7e68000[ 1704.877798] PC is at __down_interruptible+0x50/0xec[ 1704.877806] LR is at down_interruptible+0x5c/0x68[ 1704.877813] pc : [<80630ee8>] lr : [<800704b0>] psr: 60080093sp : b7e69e50 ip : b7e69e88 fp : b7e69e84[ 1704.877817] r10: b88123c8 r9 : 00000010 r8 : 00000001[ 1704.877822] r7 : b8ab9b00 r6 : 7fffffff r5 : 80a1cc34 r4 : 80a1cc34[ 1704.877826] r3 : b7e69e50 r2 : 00000000 r1 : 00000000 r0 : 80a1cc34[ 1704.877833] Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user[ 1704.877838] Control: 10c5387d Table: 3899c06a DAC: 00000015[ 1704.877843] Process do-oops (pid: 3656, stack limit = 0xb7e68238)[ 1704.877848] Stack: (0xb7e69e50 to 0xb7e6a000)[ 1704.877856] 9e40: 80a1cc3c 00000000 00000010 b88123c8[ 1704.877865] 9e60: b7e69e84 80a1cc34 fff9fee9 ffffffff b7e68000 00000009 b7e69ea4 b7e69e88[ 1704.877874] 9e80: 800704b0 80630ea4 fff9fee9 60080013 80a1cc28 fff9fee9 b7e69edc b7e69ea8[ 1704.877884] 9ea0: 8040f558 80070460 fff9fee9 ffffffff 00000000 00000000 00000009 80a1cb7c[ 1704.877893] 9ec0: 00000000 80a1cb7c 00000000 00000010 b7e69ef4 b7e69ee0 803e1ba4 8040f514[ 1704.877902] 9ee0: 00000e48 80a1cb7c b7e69f14 b7e69ef8 803e1c9c 803e1b74 b88123c0 b92acb18[ 1704.877911] 9f00: b8812790 b8d815d8 b7e69f24 b7e69f18 803e2250 803e1bc8 b7e69f5c b7e69f28[ 1704.877921] 9f20: 80167bac 803e222c 00000000 00000000 b7e69f54 b8ab9ffc 00000000 8098c794[ 1704.877930] 9f40: b8ab9b00 8000efc4 b7e68000 00000000 b7e69f6c b7e69f60 80167d6c 80167b28[ 1704.877939] 9f60: b7e69f8c b7e69f70 80047d38 80167d60 b7e68000 b7e68010 8000efc4 b7e69fb0[ 1704.877949] 9f80: b7e69fac b7e69f90 80012820 80047c84 01155490 011549a8 00000001 00000006[ 1704.877957] 9fa0: 00000000 b7e69fb0 8000ee5c 80012790 00000000 353d8c0f 7efc4308 00000000[ 1704.877966] 9fc0: 01155490 011549a8 00000001 00000006 00000000 00000000 76cf3ba0 00000003[ 1704.877975] 9fe0: 00000000 7efc42e4 0002272f 76e2ed66 60080030 00000003 00000000 00000000[ 1704.877998] [<80630ee8>] (__down_interruptible) from [<800704b0>] (down_interruptible+0x5c/0x68)[ 1704.878015] [<800704b0>] (down_interruptible) from [<8040f558>] (vchiu_queue_push+0x50/0xd8)[ 1704.878032] [<8040f558>] (vchiu_queue_push) from [<803e1ba4>] (send_worker_msg+0x3c/0x54)[ 1704.878045] [<803e1ba4>] (send_worker_msg) from [<803e1c9c>] (vc_cma_set_reserve+0xe0/0x1c4)[ 1704.878057] [<803e1c9c>] (vc_cma_set_reserve) from [<803e2250>] (vc_cma_release+0x30/0x38)[ 1704.878069] [<803e2250>] (vc_cma_release) from [<80167bac>] (__fput+0x90/0x1e0)[ 1704.878082] [<80167bac>] (__fput) from [<80167d6c>] (____fput+0x18/0x1c)[ 1704.878094] [<80167d6c>] (____fput) from [<80047d38>] (task_work_run+0xc0/0xf8)[ 1704.878109] [<80047d38>] (task_work_run) from [<80012820>] (do_work_pending+0x9c/0xc4)[ 1704.878123] [<80012820>] (do_work_pending) from [<8000ee5c>] (work_pending+0xc/0x20)[ 1704.878133] Code: e50b1034 e3a01000 e50b2030 e580300c (e5823000)..the fix is to ensure that we have actually initialized the queue before we attemptto push any items onto it. This occurs if we do an open() followed by a close() withoutany activity in between.Signed-off-by: Colin Ian King vchiq_arm: Sort out the vmalloc caseSee: https://github.com/raspberrypi/linux/issues/1055vchiq: hack: Add include depecated dma include file[gregkh] added dependancy on CONFIG_BROKEN to make things sane for now.Cc: Eric Anholt Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/staging/vc04_services/Makefile