Changes in Makefile

34f79c11 - rpmsg: glink: Introduce packet tracepoints

Tue, 06 Aug 2024 03:56:27 +0000

rpmsg: glink: Introduce packet tracepointsIntroduce tracepoints to allow tracing the GLINK packets being exchangedwith other subsystems. This is useful for debugging both interactionwith remote processors and client driver issues, as well as trackinglatency through the communication stack.Channel events are traced with both local and remote channel ids, aswell as the textual representation when possible. The channel ids areuseful when matching traces with traces from the firmware side logs,while the textual representation is necessary to identify channels whenwe're starting to trace an already running system.Signed-off-by: Bjorn Andersson Reviewed-by: Chris Lew Link: https://lore.kernel.org/r/20240805-glink-tracepoints-v1-3-a5f3293fb09e@quicinc.comSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/rpmsg/Makefile

617d3293 - rpmsg: Move the rpmsg control device from rpmsg_char to rpmsg_ctrl

Mon, 24 Jan 2022 10:25:16 +0000

rpmsg: Move the rpmsg control device from rpmsg_char to rpmsg_ctrlCreate the rpmsg_ctrl.c module and move the code related to therpmsg_ctrldev device in this new module.Add the dependency between rpmsg_char and rpmsg_ctrl in thekconfig file:1) RPMSG_CTRL can set as module or built-in if RPMSG=y || RPMSG_CHAR=y || RPMSG_CHAR=n2) RPMSG_CTRL can not be set as built-in if RPMSG=m || RPMSG_CHAR=mNote that RPMGH_CHAR and RPMSG_CTRL can be activated separately.Therefore, the RPMSG_CTRL configuration must be set for backwards compatibility.Signed-off-by: Arnaud Pouliquen Signed-off-by: Bjorn Andersson Link: https://lore.kernel.org/r/20220124102524.295783-4-arnaud.pouliquen@foss.st.com List of files: /linux-6.15/drivers/rpmsg/Makefile

950a7388 - rpmsg: Turn name service into a stand alone driver

Fri, 20 Nov 2020 21:42:45 +0000

rpmsg: Turn name service into a stand alone driverMake the RPMSG name service announcement a stand alone driver so that itcan be reused by other subsystems. It is also the first step in making thefunctionatlity transport independent, i.e that is not tied to virtIO.Reviewed-by: Guennadi Liakhovetski Tested-by: Guennadi Liakhovetski Co-developed-by: Mathieu Poirier Signed-off-by: Mathieu Poirier Co-developed-by: Guennadi Liakhovetski Signed-off-by: Guennadi Liakhovetski Signed-off-by: Arnaud Pouliquen Link: https://lore.kernel.org/r/20201120214245.172963-9-mathieu.poirier@linaro.orgSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/rpmsg/Makefile

93bc3fee - rpmsg: glink: Integrate glink_ssr in qcom_glink

Thu, 23 Apr 2020 00:37:35 +0000

rpmsg: glink: Integrate glink_ssr in qcom_glinkIn all but the very special case of a system with _only_ glink_rpm,GLINK is dependent on glink_ssr, so move it to rpmsg and combine it withqcom_glink_native in the new qcom_glink kernel module.Acked-by: Chris Lew Acked-by: Rishabh Bhatnagar Link: https://lore.kernel.org/r/20200423003736.2027371-4-bjorn.andersson@linaro.orgSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/rpmsg/Makefile

70179969 - rpmsg: add rpmsg support for mt8183 SCP.

Tue, 12 Nov 2019 11:03:26 +0000

rpmsg: add rpmsg support for mt8183 SCP.Add a simple rpmsg support for mt8183 SCP, that use IPI / IPC directly.Signed-off-by: Pi-Hsun Shih Link: https://lore.kernel.org/r/20191112110330.179649-4-pihsun@chromium.orgSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/rpmsg/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/rpmsg/Makefile

caf989c3 - rpmsg: glink: Introduce glink smem based transport

Thu, 24 Aug 2017 07:21:30 +0000

rpmsg: glink: Introduce glink smem based transportThe glink protocol supports different types of transports (sharedmemory). With the core protocol remaining the same, the way thetransport's memory is probed and accessed is different. So add supportfor glink's smem based transports.Adding a new smem transport register function and the fifo accessors forthe same.Acked-by: Arun Kumar Neelakantam Signed-off-by: Sricharan R Signed-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/rpmsg/Makefile

835764dd - rpmsg: glink: Move the common glink protocol implementation to glink_native.c

Thu, 24 Aug 2017 07:21:26 +0000

rpmsg: glink: Move the common glink protocol implementation to glink_native.cMove the common part of glink core protocol implementation toglink_native.c that can be shared with the smem based glinktransport in the later patches.Acked-by: Arun Kumar Neelakantam Signed-off-by: Sricharan R Signed-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/rpmsg/Makefile

b4f8e52b - rpmsg: Introduce Qualcomm RPM glink driver

Sat, 27 May 2017 23:23:35 +0000

rpmsg: Introduce Qualcomm RPM glink driverThis introduces a basic driver for communicating over "native glink"with the RPM found in Qualcomm platforms.Signed-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/rpmsg/Makefile

c0cdc19f - rpmsg: Driver for user space endpoint interface

Wed, 11 Jan 2017 14:35:12 +0000

rpmsg: Driver for user space endpoint interfaceThis driver allows rpmsg instances to expose access to rpmsg endpointsto user space processes. It provides a control interface, allowinguserspace to export endpoints and an endpoint interface for each exposedendpoint.The implementation is based on prior art by Texas Instrument, Google,PetaLogix and was derived from a FreeRTOS performance statistics driverwritten by Michal Simek.The control interface provides a "create endpoint" ioctl, which is fed aname, source and destination address. The three values are used tocreate the endpoint, in a backend-specific way, and a rpmsg endpointdevice is created - with the three parameters are available in sysfs forudev usage.E.g. to create an endpoint device for one of the Qualcomm SMD channelrelated to DIAG one would issue: struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 }; int fd = open("/dev/rpmsg_ctrl0", O_RDWR); ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);Each created endpoint device shows up as an individual character devicein /dev, allowing permission to be controlled on a per-endpoint basis.The rpmsg endpoint will be created and destroyed following the openingand closing of the endpoint device, allowing rpmsg backends to open andclose the physical channel, if supported by the wire protocol.Cc: Marek Novak Cc: Matteo Sartori Cc: Michal Simek Signed-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/rpmsg/Makefile

53e2822e - rpmsg: Introduce Qualcomm SMD backend

Thu, 01 Sep 2016 22:28:09 +0000

rpmsg: Introduce Qualcomm SMD backendThis introduces a new rpmsg backend for the Qualcomm SMD system,allowing communication with various remote processors found in Qualcommplatforms. The implementation is based on, and intends to replace,drivers/soc/qcom/smd.c with the necessary adaptions for fitting with therpmsg core.Based on original work by Sricharan R Cc: Sricharan R Signed-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/rpmsg/Makefile

026dad47 - rpmsg: Move rpmsg_device API to new file

Thu, 01 Sep 2016 22:27:59 +0000

rpmsg: Move rpmsg_device API to new fileExtract the now indirect rpmsg_create_ept() interface to a separatefile and start building up a rpmsg core.Signed-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/rpmsg/Makefile

bcabbcca - rpmsg: add virtio-based remote processor messaging bus

Thu, 20 Oct 2011 19:10:55 +0000

rpmsg: add virtio-based remote processor messaging busAdd a virtio-based inter-processor communication bus, which enableskernel drivers to communicate with entities, running on remoteprocessors, over shared memory using a simple messaging protocol.Every pair of AMP processors share two vrings, which are used to sendand receive the messages over shared memory.The header of every message sent on the rpmsg bus contains src and dstaddresses, which make it possible to multiplex several rpmsg channels onthe same vring.Every rpmsg channel is a device on this bus. When a channel is added,and an appropriate rpmsg driver is found and probed, it is also assigneda local rpmsg address, which is then bound to the driver's callback.When inbound messages carry the local address of a bound driver,its callback is invoked by the bus.This patch provides a kernel interface only; user space interfaceswill be later exposed by kernel users of this rpmsg bus.Designed with Brian Swetland .Signed-off-by: Ohad Ben-Cohen Acked-by: Rusty Russell (virtio_ids.h)Cc: Brian Swetland Cc: Arnd Bergmann Cc: Grant Likely Cc: Tony Lindgren Cc: Russell King Cc: Andrew Morton Cc: Greg KH Cc: Stephen Boyd List of files: /linux-6.15/drivers/rpmsg/Makefile