Changes in Makefile

ebcf9008 - remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem

Fri, 02 Aug 2024 15:21:03 +0000

remoteproc: k3-m4: Add a remoteproc driver for M4F subsystemThe AM62x and AM64x SoCs of the TI K3 family has a Cortex M4F core inthe MCU domain. This core is typically used for safety applications in astand alone mode. However, some application (non safety related) maywant to use the M4F core as a generic remote processor with IPC to thehost processor. The M4F core has internal IRAM and DRAM memories and areexposed to the system bus for code and data loading.A remote processor driver is added to support this subsystem, includingbeing able to load and boot the M4F core. Loading includes to M4Finternal memories and predefined external code/data memories. Thecarve outs for external contiguous memory is defined in the M4F devicenode and should match with the external memory declarations in the M4Fimage binary. The M4F subsystem has two resets. One reset is for theentire subsystem i.e including the internal memories and the other, alocal reset is only for the M4F processing core. When loading the image,the driver first releases the subsystem reset, loads the firmware imageand then releases the local reset to let the M4F processing core run.Signed-off-by: Martyn Welch Signed-off-by: Hari Nagalla Signed-off-by: Andrew Davis Tested-by: Wadim Egorov Link: https://lore.kernel.org/r/20240802152109.137243-4-afd@ti.comSigned-off-by: Mathieu Poirier List of files: /linux-6.15/drivers/remoteproc/Makefile

6b291e80 - drivers: remoteproc: Add Xilinx r5 remoteproc driver

Mon, 14 Nov 2022 23:39:40 +0000

drivers: remoteproc: Add Xilinx r5 remoteproc driverThis driver enables r5f dual core Real time Processing Unit subsystemavailable on Xilinx Zynq Ultrascale MPSoC Platform. RPU subsystem(cluster) can be configured in different modes e.g. split mode in whichtwo r5f cores work independent of each other and lock-step mode in whichboth r5f cores execute same code clock-for-clock and notify if theresult is different.The Xilinx r5 Remoteproc Driver boots the RPU cores via calls to the XilinxPlatform Management Unit that handles the R5 configuration, memory accessand R5 lifecycle management. The interface to this manager is done in thisdriver via zynqmp_pm_* function calls.Signed-off-by: Ben Levinsky Signed-off-by: Tanmay Shah Reported-by: kernel test robot Link: https://lore.kernel.org/r/20221114233940.2096237-7-tanmay.shah@amd.comSigned-off-by: Mathieu Poirier List of files: /linux-6.15/drivers/remoteproc/Makefile

285892a7 - remoteproc: Add Renesas rcar driver

Tue, 07 Dec 2021 16:58:29 +0000

remoteproc: Add Renesas rcar driverRenesas Gen3 platform includes a Cortex-r7 processor.Both: the application cores (A5x) and the realtime core (CR7)share access to the RAM and devices with the same address map,so device addresses are equal to the Linux physical addresses.In order to initialize this remote processor we need to:- power on the realtime core- put the firmware in a RAM area- set the boot address for this firmware (reset vector)- Deassert the resetThis initial driver allows to start and stop the Cortex R7processor.Signed-off-by: Julien Massot Link: https://lore.kernel.org/r/20211207165829.195537-3-julien.massot@iot.bzhSigned-off-by: Mathieu Poirier List of files: /linux-6.15/drivers/remoteproc/Makefile

ec0e5549 - remoteproc: imx_dsp_rproc: Add remoteproc driver for DSP on i.MX

Mon, 11 Oct 2021 09:20:14 +0000

remoteproc: imx_dsp_rproc: Add remoteproc driver for DSP on i.MXProvide a basic driver to control DSP processor found on NXP i.MX8QM,i.MX8QXP, i.MX8MP and i.MX8ULP.Currently it is able to resolve addresses between DSP and main CPU,start and stop the processor, suspend and resume.The communication between DSP and main CPU is based on mailbox, thereare three mailbox channels (tx, rx, rxdb).This driver was tested on NXP i.MX8QM, i.MX8QXP, i.MX8MP and i.MX8ULP.Signed-off-by: Shengjiu Wang Link: https://lore.kernel.org/r/1633944015-789-4-git-send-email-shengjiu.wang@nxp.comSigned-off-by: Mathieu Poirier List of files: /linux-6.15/drivers/remoteproc/Makefile

6cb58ea8 - remoteproc: meson-mx-ao-arc: Add a driver for the AO ARC remote procesor

Tue, 21 Sep 2021 19:25:57 +0000

remoteproc: meson-mx-ao-arc: Add a driver for the AO ARC remote procesorAmlogic Meson6, Meson8, Meson8b and Meson8m2 embed an ARC core in theAlways-On (AO) power-domain. This is typically used for waking up theARM cores after system suspend.The configuration is spread across three different registers:- AO_REMAP_REG0 which must be programmed to zero, it's actual purpose is unknown. There is a second remap register which is not used in the vendor kernel (which served as reference for this driver).- AO_CPU_CNTL is used to start and stop the ARC core.- AO_SECURE_REG0 in the SECBUS2 register area with unknown purpose.To boot the ARC core we also need to enable it's gate clock and triggera reset.The actual code for this ARC core can come from an ELF binary, forexample by building the Zephyr RTOS for an ARC EM4 core and then taking"zephyr.elf" as firmware. This executable does not have any "rsc table"so we are skipping rproc_elf_load_rsc_table (rproc_ops.parse_fw) andrproc_elf_find_loaded_rsc_table (rproc_ops.find_loaded_rsc_table).Signed-off-by: Martin Blumenstingl Link: https://lore.kernel.org/r/20210921192557.1610709-3-martin.blumenstingl@googlemail.com[Fixed header file order]Signed-off-by: Mathieu Poirier Signed-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/remoteproc/Makefile

d4ce2de7 - remoteproc: pru: Add a PRU remoteproc driver

Tue, 08 Dec 2020 14:09:58 +0000

remoteproc: pru: Add a PRU remoteproc driverThe Programmable Real-Time Unit Subsystem (PRUSS) consists ofdual 32-bit RISC cores (Programmable Real-Time Units, or PRUs)for program execution. This patch adds a remoteproc platformdriver for managing the individual PRU RISC cores life cycle.The PRUs do not have a unified address space (have an InstructionRAM and a primary Data RAM at both 0x0). The PRU remoteproc drivertherefore uses a custom remoteproc core ELF loader ops. The added.da_to_va ops is only used to provide translations for the PRUData RAMs. This remoteproc driver does not have support for errorrecovery and system suspend/resume features. Different compatiblesare used to allow providing scalability for instance-specific devicedata if needed. The driver uses a default firmware-name retrievedfrom device-tree for each PRU core, and the firmwares are expectedto be present in the standard Linux firmware search paths. They canalso be adjusted by userspace if required through the sysfs interfaceprovided by the remoteproc core.The PRU remoteproc driver uses a client-driven boot methodology: itdoes _not_ support auto-boot so that the PRU load and boot is dictatedby the corresponding client drivers for achieving various usecases.This allows flexibility for the client drivers or applications to seta firmware name (if needed) based on their desired functionality andboot the PRU. The sysfs bind and unbind attributes have also beensuppressed so that the PRU devices cannot be unbound and therebyshutdown a PRU from underneath a PRU client driver.The driver currently supports the AM335x, AM437x, AM57xx and 66AK2GSoCs, and support for other TI SoCs will be added in subsequentpatches.Co-developed-by: Andrew F. Davis Signed-off-by: Andrew F. Davis Signed-off-by: Suman Anna Co-developed-by: Grzegorz Jaszczyk Signed-off-by: Grzegorz Jaszczyk Reviewed-by: Mathieu Poirier Link: https://lore.kernel.org/r/20201208141002.17777-3-grzegorz.jaszczyk@linaro.orgSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/remoteproc/Makefile

6dedbd1d - remoteproc: k3-r5: Add a remoteproc driver for R5F subsystem

Fri, 02 Oct 2020 23:42:32 +0000

remoteproc: k3-r5: Add a remoteproc driver for R5F subsystemThe TI K3 family of SoCs typically have one or more dual-core Arm CortexR5F processor clusters/subsystems (R5FSS). This R5F subsystem/clustercan be configured at boot time to be either run in a LockStep mode or inan Asymmetric Multi Processing (AMP) fashion in Split-mode. This subsystemhas 64 KB each Tightly-Coupled Memory (TCM) internal memories for eachcore split between two banks - TCMA and TCMB (further interleaved intotwo banks). The subsystem does not have an MMU, but has a Region AddressTranslater (RAT) module that is accessible only from the R5Fs for providingtranslations between 32-bit CPU addresses into larger system bus addresses.Add a remoteproc driver to support this subsystem to be able to load andboot the R5F cores primarily in LockStep mode. The code also includes thebase support for Split mode. Error Recovery and Power Management featuresare not currently supported. Loading support includes the internal TCMsand DDR. RAT support is left for a future patch, and as such the reservedmemory carveout regions are all expected to be using memory regions withinthe first 2 GB.The R5F remote processors do not have an MMU, and so require fixed memorycarveout regions matching the firmware image addresses. Support for thisis provided by mandating multiple memory regions to be attached to theremoteproc device. The first memory region will be used to serve as theDMA pool for all dynamic allocations like the vrings and vring buffers.The remaining memory regions are mapped into the kernel at device probetime, and are used to provide address translations for firmware imagesegments without the need for any RSC_CARVEOUT entries. Any firmwareimage using memory outside of the supplied reserved memory carveoutregions will be errored out.The R5F processors on TI K3 SoCs require a specific sequence for bootingand shutting down the processors. This sequence is also dependent on themode (LockStep or Split) the R5F cluster is configured for. The R5F coreshave a Memory Protection Unit (MPU) that has a default configuration thatdoes not allow the cores to run out of DDR out of reset. This is resolvedby using the TCMs for boot-strapping code that applies the appropriateexecutable permissions on desired DDR memory. The loading into the TCMsrequires that the resets be released first with the cores in halted state.The Power Sleep Controller (PSC) module on K3 SoCs requires that the coresbe in WFI/WFE states with no active bus transactions before the cores canbe put back into reset. Support for this is provided by using the newlyintroduced .prepare() and .unprepare() ops in the remoteproc core. The.prepare() ops is invoked before any loading, and the .unprepare() opsis invoked after the remoteproc resource cleanup. The R5F core resetsare deasserted in .prepare() and asserted in .unprepare(), and the coresthemselves are started and halted in .start() and .stop() ops. Thisensures symmetric usage and allows the R5F cores state machine to bemaintained properly between using the sysfs 'state' variable, bind/unbindand regular module load/unload flows.The subsystem is represented as a single remoteproc in LockStep mode, andas two remoteprocs in Split mode. The driver uses various TI-SCI interfacesto talk to the System Controller (DMSC) for managing configuration, powerand reset management of these cores. IPC between the A53 cores and the R5cores is supported through the virtio rpmsg stack using shared memory andOMAP Mailboxes.The AM65x SoCs typically have a single R5FSS in the MCU voltage domain. TheJ721E SoCs uses a slightly revised IP and typically have three R5FSSs, withone cluster present within the MCU voltage domain (MCU_R5FSS0), and theremaining two clusters present in the MAIN voltage domain (MAIN_R5FSS0 andMAIN_R5FSS1). The integration of these clusters on J721E SoC is alsoslightly different in that these IPs do support an actual local reset line,while they are a no-op on AM65x SoCs.Signed-off-by: Suman Anna Reviewed-by: Mathieu Poirier Link: https://lore.kernel.org/r/20201002234234.20704-3-s-anna@ti.comSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/remoteproc/Makefile

44767708 - remoteproc: Add remoteproc character device interface

Wed, 29 Jul 2020 17:40:00 +0000

remoteproc: Add remoteproc character device interfaceAdd the character device interface into remoteproc framework.This interface can be used in order to boot/shutdown remotesubsystems and provides a basic ioctl based interface to implementsupplementary functionality. An ioctl call is implemented to enablethe shutdown on release feature which will allow remote processors tobe shutdown when the controlling userspace application crashes or hangs.Reviewed-by: Bjorn Andersson Reviewed-by: Mathieu Poirier Signed-off-by: Rishabh Bhatnagar Signed-off-by: Siddharth Gupta Link: https://lore.kernel.org/r/1596044401-22083-2-git-send-email-sidgup@codeaurora.org[bjorn: s/int32_t/s32/ per checkpatch]Signed-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/remoteproc/Makefile

2f3ee5e4 - remoteproc: kill IPA notify code

Fri, 24 Jul 2020 18:11:42 +0000

remoteproc: kill IPA notify codeThe IPA code now uses the generic remoteproc SSR notificationmechanism. This makes the original IPA notification code unusedand unnecessary, so get rid of it.This is effectively a revert of commit d7f5f3c89c1a ("remoteproc:add IPA notification to q6v5 driver").Reviewed-by: Bjorn Andersson Signed-off-by: Alex Elder Link: https://lore.kernel.org/r/20200724181142.13581-3-elder@linaro.orgSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/remoteproc/Makefile

6edbe024 - remoteproc: k3-dsp: Add a remoteproc driver of K3 C66x DSPs

Tue, 21 Jul 2020 22:36:16 +0000

remoteproc: k3-dsp: Add a remoteproc driver of K3 C66x DSPsThe Texas Instrument's K3 J721E SoCs have two C66x DSP Subsystems in MAINvoltage domain that are based on the TI's standard TMS320C66x DSP CorePacmodule. Each subsystem has a Fixed/Floating-Point DSP CPU, with 32 KB eachof L1P & L1D SRAMs that can be configured and partitioned as either RAMand/or Cache, and 288 KB of L2 SRAM with 256 KB of memory configurable aseither RAM and/or Cache. The CorePac also includes an Internal DMA (IDMA),External Memory Controller (EMC), Extended Memory Controller (XMC) with aRegion Address Translator (RAT) unit for 32-bit to 48-bit addressextension/translations, an Interrupt Controller (INTC) and a PowerdownController (PDC).A new remoteproc module is added to perform the device management ofthese DSP devices. The support is limited to images using only externalDDR memory at the moment, the loading support to internal memories andany on-chip RAM memories will be added in a subsequent patch. RAT supportis also left for a future patch, and as such the reserved memory carveoutregions are all expected to be using memory regions within the first 2 GB.Error Recovery and Power Management features are not currently supported.The C66x remote processors do not have an MMU, and so require fixed memorycarveout regions matching the firmware image addresses. Support for thisis provided by mandating multiple memory regions to be attached to theremoteproc device. The first memory region will be used to serve as theDMA pool for all dynamic allocations like the vrings and vring buffers.The remaining memory regions are mapped into the kernel at device probetime, and are used to provide address translations for firmware imagesegments without the need for any RSC_CARVEOUT entries. Any firmwareimage using memory outside of the supplied reserved memory carveoutregions will be errored out.The driver uses various TI-SCI interfaces to talk to the System Controller(DMSC) for managing configuration, power and reset management of thesecores. IPC between the A72 cores and the DSP cores is supported throughthe virtio rpmsg stack using shared memory and OMAP Mailboxes.Signed-off-by: Suman Anna Reviewed-by: Bjorn Andersson Reviewed-by: Mathieu Poirier Link: https://lore.kernel.org/r/20200721223617.20312-6-s-anna@ti.comSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/remoteproc/Makefile

2c010cc3 - remoteproc: Move coredump functionality to a new file

Thu, 16 Jul 2020 22:20:31 +0000

remoteproc: Move coredump functionality to a new fileMove all coredump functionality to an individual file. This isbeing done so that the current functionality can be extendedin future patchsets.Signed-off-by: Rishabh Bhatnagar Reviewed-by: Bjorn Andersson Reviewed-by: Mathieu Poirier Reviewed-by: Sibi Sankar Tested-by: Sibi Sankar Link: https://lore.kernel.org/r/1594938035-7327-2-git-send-email-rishabhb@codeaurora.orgSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/remoteproc/Makefile

549b67da - remoteproc: qcom: Introduce helper to store pil info in IMEM

Mon, 22 Jun 2020 19:19:39 +0000

remoteproc: qcom: Introduce helper to store pil info in IMEMA region in IMEM is used to communicate load addresses of remoteproc topost mortem debug tools. Implement a helper function that can be used tostore this information in order to enable these tools to processcollected ramdumps.Reviewed-by: Mathieu Poirier Reviewed-by: Vinod Koul Signed-off-by: Bjorn Andersson Link: https://lore.kernel.org/r/20200622191942.255460-3-bjorn.andersson@linaro.orgSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/remoteproc/Makefile

48f0a1bb - remoteproc: ingenic: Added remoteproc driver

Fri, 15 May 2020 10:43:39 +0000

remoteproc: ingenic: Added remoteproc driverThis driver is used to boot, communicate with and load firmwares to theMIPS co-processor found in the VPU hardware of the JZ47xx SoCs fromIngenic.Signed-off-by: Paul Cercueil Acked-by: Mathieu Poirier Link: https://lore.kernel.org/r/20200515104340.10473-4-paul@crapouillou.netSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/remoteproc/Makefile

d7f5f3c8 - remoteproc: add IPA notification to q6v5 driver

Fri, 06 Mar 2020 04:28:15 +0000

remoteproc: add IPA notification to q6v5 driverSet up a subdev in the q6v5 modem remoteproc driver that generatesevent notifications for the IPA driver to use for initialization andrecovery following a modem shutdown or crash.A pair of new functions provides a way for the IPA driver to registerand deregister a notification callback function that will be calledwhenever modem events (about to boot, running, about to shut down,etc.) occur. A void pointer value (provided by the IPA driver atregistration time) and an event type are supplied to the callbackfunction.One event, MODEM_REMOVING, is signaled whenever the q6v5 driver isabout to remove the notification subdevice. It requires the IPAdriver de-register its callback.This sub-device is only used by the modem subsystem (MSS) driver,so the code that adds the new subdev and allows registration andderegistration of the notifier is found in "qcom_q6v6_mss.c".Signed-off-by: Alex Elder Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/remoteproc/Makefile

63c13d61 - remoteproc/mediatek: add SCP support for mt8183

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

remoteproc/mediatek: add SCP support for mt8183Provide a basic driver to control Cortex M4 co-processorSigned-off-by: Erin Lo Signed-off-by: Nicolas Boichat Signed-off-by: Pi-Hsun Shih Link: https://lore.kernel.org/r/20191112110330.179649-3-pihsun@chromium.orgSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/remoteproc/Makefile

13140de0 - remoteproc: stm32: add an ST stm32_rproc driver

Tue, 14 May 2019 08:26:58 +0000

remoteproc: stm32: add an ST stm32_rproc driverThis patch introduces a new remoteproc driver to control Cortex-M4co-processor of the STM32 family.It provides with the following features:- start and stop- dedicated co-processor memory regions registration- coredump and recoverySigned-off-by: Fabien Dessenne Signed-off-by: Ludovic Barre Signed-off-by: Loic Pallardy Signed-off-by: Arnaud Pouliquen [bjorn: Fixup of dev_dbg types and cast of int to pointer in mbox send]Signed-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/remoteproc/Makefile

dc160e44 - remoteproc: qcom: Introduce Non-PAS ADSP PIL driver

Mon, 24 Sep 2018 11:07:50 +0000

remoteproc: qcom: Introduce Non-PAS ADSP PIL driverThis adds Non PAS ADSP PIL driver for Qualcomm Technologies Inc SoCs.Added initial support for SDM845 with ADSP bootup and shutdown operationhandled from Application Processor SubSystem(APSS).Reviewed-by: Sibi Sankar Tested-by: Sibi Sankar Signed-off-by: Rohit kumar [bjorn: Renamed driver and Kconfig from qcom_adsp_pil to qcom_q6v5_adsp]Signed-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/remoteproc/Makefile

ef73c22f - remoteproc: qcom: Rename Hexagon v5 modem driver

Mon, 24 Sep 2018 23:45:26 +0000

remoteproc: qcom: Rename Hexagon v5 modem driverThe qcom_q6v5_pil implements support for the self-authenticating modemsubsystem. With the introduction of other q6v5 based non-TZ basedremoteproc driver the current name is cause for confusion, so rename itto be more specific.No functional change.Reviewed-by: Niklas Cassel Signed-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/remoteproc/Makefile

9e004f97 - remoteproc: qcom: Rename Hexagon v5 PAS driver

Mon, 24 Sep 2018 23:45:25 +0000

remoteproc: qcom: Rename Hexagon v5 PAS driverThe Hexagon v5 ADSP driver is used for more than only the ADSP andthere's an upcoming non-PAS ADSP PIL for SDM845, so rename the driver toqcom_q6v5_pas in order to better suite this.Cc: Rohit kumar Reviewed-by: Niklas Cassel Signed-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/remoteproc/Makefile

3a3d4163 - remoteproc: qcom: Introduce Hexagon V5 based WCSS driver

Thu, 07 Jun 2018 17:27:11 +0000

remoteproc: qcom: Introduce Hexagon V5 based WCSS driverIPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan(Lithium) IP. An mdt type single image format is used for thefirmware. So the mdt_load function can be directly used to loadthe firmware. Also add the relevant resets required for this core.Acked-by: Rob Herring (bindings)Signed-off-by: Sricharan R [bjorn: Rewrote as a separate driver, intead of extending q6v5_pil.c]Signed-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/remoteproc/Makefile