Changes in Makefile

e4b3cbd8 - firmware: thead: Add AON firmware protocol driver

Tue, 11 Mar 2025 17:18:57 +0000

firmware: thead: Add AON firmware protocol driverThe T-Head TH1520 SoC uses an E902 co-processor running Always-On (AON)firmware to manage power, clock, and other system resources [1]. Thispatch introduces a driver implementing the AON firmware protocol,allowing the Linux kernel to communicate with the firmware via mailboxchannels. Through an RPC-based interface, the kernel can initiate powerstate transitions, update resource configurations, and perform otherAON-related tasks.[1]Link: https://openbeagle.org/beaglev-ahead/beaglev-ahead/-/blob/main/docs/TH1520%20System%20User%20Manual.pdfSigned-off-by: Michal Wilczynski Acked-by: Drew Fustini Link: https://lore.kernel.org/r/20250311171900.1549916-3-m.wilczynski@samsung.comSigned-off-by: Ulf Hansson List of files: /linux-6.15/drivers/firmware/Makefile

a88927b5 - firmware: add Exynos ACPM protocol driver

Thu, 13 Feb 2025 13:05:15 +0000

firmware: add Exynos ACPM protocol driverAlive Clock and Power Manager (ACPM) Message Protocol is defined forthe purpose of communication between the ACPM firmware and masters(AP, AOC, ...). ACPM firmware operates on the Active Power Management(APM) module that handles overall power activities.ACPM and masters regard each other as independent hardware component andcommunicate with each other using mailbox messages and shared memory.This protocol driver provides the interface for all the client driversmaking use of the features offered by the APM. Add ACPM protocol support.Signed-off-by: Tudor Ambarus Link: https://lore.kernel.org/r/20250213-gs101-acpm-v9-2-8b0281b93c8b@linaro.orgSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/drivers/firmware/Makefile

ec5b0f11 - firmware: microchip: add PolarFire SoC Auto Update support

Fri, 20 Oct 2023 13:18:43 +0000

firmware: microchip: add PolarFire SoC Auto Update supportAdd support for Auto Update reprogramming of the FPGA fabric onPolarFire SoC, using the fw_upload mechanism a la theintel-m10-bmc-sec-update driver.This driver only writes the image to the spi flash & performsvalidation on it, as the entire FPGA becomes unusable during the actualreprogramming of a bitstream. To initiate the reprogramming itself, adevice reset is required. The SBI SRST extension's "cold reboot" cantrigger such a device reset, provided corresponding support has beenenabled in the HSS (Hart Software Services), the provider of SBI runtimeservices on PolarFire SoC.While this is a driver responsible for the reprogramming of an FPGA,there is no dynamic discovery of devices involved, as runtimereconfiguration is not possible due to the device reset requirements.Therefore FPGA manager subsystem is not used by this driver and the FPGAsubsystem maintainers were unwilling to accept it there.Signed-off-by: Conor Dooley List of files: /linux-6.15/drivers/firmware/Makefile

62b14b9e - firmware: arm_scpi: Move power-domain driver to the pmdomain dir

Thu, 23 Nov 2023 12:08:47 +0000

firmware: arm_scpi: Move power-domain driver to the pmdomain dirTo simplify with maintenance let's move the Arm SCPI power-domain driverto the new pmdomain directory. Note this is different from and precedesthe new Arm SCMI protocol.Signed-off-by: Sudeep Holla Link: https://lore.kernel.org/r/20231123120847.2825444-2-sudeep.holla@arm.comSigned-off-by: Ulf Hansson List of files: /linux-6.15/drivers/firmware/Makefile

bdac188e - firmware: qcom: move Qualcomm code into its own directory

Tue, 17 Oct 2023 09:27:18 +0000

firmware: qcom: move Qualcomm code into its own directoryWe're getting more and more qcom specific .c files in drivers/firmware/and about to get even more. Create a separate directory for Qualcommfirmware drivers and move existing sources in there.Signed-off-by: Bartosz Golaszewski Acked-by: Elliot Berman Reviewed-by: Krzysztof Kozlowski Reviewed-by: Maximilian Luz Tested-by: Andrew Halaney # sc8280xp-lenovo-thinkpad-x13sLink: https://lore.kernel.org/r/20231017092732.19983-2-brgl@bgdev.plSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/firmware/Makefile

759e7a2b - firmware: Add support for Qualcomm UEFI Secure Application

Sun, 27 Aug 2023 21:14:06 +0000

firmware: Add support for Qualcomm UEFI Secure ApplicationOn platforms using the Qualcomm UEFI Secure Application (uefisecapp),EFI variables cannot be accessed via the standard interface in EFIruntime mode. The respective functions return EFI_UNSUPPORTED. On theseplatforms, we instead need to talk to uefisecapp. This commit providessupport for this and registers the respective efivars operations toaccess EFI variables from the kernel.Communication with uefisecapp follows the Qualcomm QSEECOM / Secure OSconventions via the respective SCM call interface. This is also thereason why variable access works normally while boot services areactive. During this time, said SCM interface is managed by the bootservices. When calling ExitBootServices(), the ownership is transferredto the kernel. Therefore, UEFI must not use that interface itself (asmultiple parties accessing this interface at the same time may lead tocomplications) and cannot access variables for us.Signed-off-by: Maximilian Luz Acked-by: Ard Biesheuvel Reviewed-by: Johan Hovold Link: https://lore.kernel.org/r/20230827211408.689076-4-luzmaximilian@gmail.comSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/firmware/Makefile

00b12486 - firmware: qcom_scm: Add support for Qualcomm Secure Execution Environment SCM interface

Sun, 27 Aug 2023 21:14:05 +0000

firmware: qcom_scm: Add support for Qualcomm Secure Execution Environment SCM interfaceAdd support for SCM calls to Secure OS and the Secure ExecutionEnvironment (SEE) residing in the TrustZone (TZ) via the QSEECOMinterface. This allows communication with Secure/TZ applications, forexample 'uefisecapp' managing access to UEFI variables.For better separation, make qcom_scm spin up a dedicated child(platform) device in case QSEECOM support has been detected. Thecorresponding driver for this device is then responsible for managingany QSEECOM clients. Specifically, this driver attempts to automaticallydetect known and supported applications, creating a client (auxiliary)device for each one. The respective client/auxiliary driver is thenresponsible for managing and communicating with the application.While this patch introduces only a very basic interface without the moreadvanced features (such as re-entrant and blocking SCM calls andlisteners/callbacks), this is enough to talk to the aforementioned'uefisecapp'.Signed-off-by: Maximilian Luz Reviewed-by: Johan Hovold Link: https://lore.kernel.org/r/20230827211408.689076-3-luzmaximilian@gmail.comSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/firmware/Makefile

cf8e8658 - arch: Remove Itanium (IA-64) architecture

Thu, 20 Oct 2022 13:54:33 +0000

arch: Remove Itanium (IA-64) architectureThe Itanium architecture is obsolete, and an informal survey [0] revealsthat any residual use of Itanium hardware in production is mostly HP-UXor OpenVMS based. The use of Linux on Itanium appears to be limited toenthusiasts that occasionally boot a fresh Linux kernel to see whetherthings are still working as intended, and perhaps to churn out somedistro packages that are rarely used in practice.None of the original companies behind Itanium still produce or supportany hardware or software for the architecture, and it is listed as'Orphaned' in the MAINTAINERS file, as apparently, none of the engineersthat contributed on behalf of those companies (nor anyone else, for thatmatter) have been willing to support or maintain the architectureupstream or even be responsible for applying the odd fix. The Intelfirmware team removed all IA-64 support from the Tianocore/EDK2reference implementation of EFI in 2018. (Itanium is the originalarchitecture for which EFI was developed, and the way Linux supports itdeviates significantly from other architectures.) Some distros, such asDebian and Gentoo, still maintain [unofficial] ia64 ports, but many havedropped support years ago.While the argument is being made [1] that there is a 'for the commongood' angle to being able to build and run existing projects such as theGrid Community Toolkit [2] on Itanium for interoperability testing, thefact remains that none of those projects are known to be deployed onLinux/ia64, and very few people actually have access to such a system inthe first place. Even if there were ways imaginable in which Linux/ia64could be put to good use today, what matters is whether anyone isactually doing that, and this does not appear to be the case.There are no emulators widely available, and so boot testing Itanium isgenerally infeasible for ordinary contributors. GCC still supports IA-64but its compile farm [3] no longer has any IA-64 machines. GLIBC wouldlike to get rid of IA-64 [4] too because it would permit some overduecode cleanups. In summary, the benefits to the ecosystem of having IA-64be part of it are mostly theoretical, whereas the maintenance overheadof keeping it supported is real.So let's rip off the band aid, and remove the IA-64 arch code entirely.This follows the timeline proposed by the Debian/ia64 maintainer [5],which removes support in a controlled manner, leaving IA-64 in a knowngood state in the most recent LTS release. Other projects will followonce the kernel support is removed.[0] https://lore.kernel.org/all/CAMj1kXFCMh_578jniKpUtx_j8ByHnt=s7S+yQ+vGbKt9ud7+kQ@mail.gmail.com/[1] https://lore.kernel.org/all/0075883c-7c51-00f5-2c2d-5119c1820410@web.de/[2] https://gridcf.org/gct-docs/latest/index.html[3] https://cfarm.tetaneutral.net/machines/list/[4] https://lore.kernel.org/all/87bkiilpc4.fsf@mid.deneb.enyo.de/[5] https://lore.kernel.org/all/ff58a3e76e5102c94bb5946d99187b358def688a.camel@physik.fu-berlin.de/Acked-by: Tony Luck Signed-off-by: Ard Biesheuvel List of files: /linux-6.15/drivers/firmware/Makefile

75ed63d9 - efi: clean up Kconfig dependencies on CONFIG_EFI

Sat, 28 May 2022 09:49:54 +0000

efi: clean up Kconfig dependencies on CONFIG_EFIGeert reports that the new option CONFIG_EFI_DISABLE_RUNTIME is uservisible even when EFI support is disabled, which is unnecessary andclutters the Kconfig interface.So let's move this option into the existing Kconfig submenu that alreadydepends on CONFIG_EFI, and while at it, give some other options the sametreatment.Also clean up a small wart where the efi/ subdirectory is listed twice.Let's just list it unconditionally so that both EFI and UEFI_CPER basedpieces will be built independently (the latter only depends on theformer on !X86)Signed-off-by: Ard Biesheuvel List of files: /linux-6.15/drivers/firmware/Makefile

9db69df4 - firmware: mediatek: Add adsp ipc protocol interface

Thu, 12 May 2022 08:22:13 +0000

firmware: mediatek: Add adsp ipc protocol interfaceSome of mediatek processors containthe Tensilica HiFix DSP for audio processing.The communication between Host CPU and DSP firmware istaking place using a shared memory area for message passing.ADSP IPC protocol offers (send/recv) interfaces usingmediatek-mailbox APIs.We use two mbox channels to implement a request-reply protocol.Signed-off-by: Allen-KH Cheng Signed-off-by: TingHan Shen Reviewed-by: Pierre-Louis Bossart Reviewed-by: Curtis Malainey Reviewed-by: Tzung-Bi Shih Reviewed-by: YC Hung Reviewed-by: AngeloGioacchino Del Regno Link: https://lore.kernel.org/r/20220512082215.3018-2-tinghan.shen@mediatek.comSigned-off-by: Mark Brown List of files: /linux-6.15/drivers/firmware/Makefile

f6bc909e - firmware: cs_dsp: add driver to support firmware loading on Cirrus Logic DSPs

Mon, 13 Sep 2021 16:00:57 +0000

firmware: cs_dsp: add driver to support firmware loading on Cirrus Logic DSPswm_adsp originally provided firmware loading on some audio DSP and wasimplemented as an ASoC codec driver. However, the firmware loading nowcovers a wider range of DSP cores and peripherals containing them,beyond just audio. So it needs to be available to non-audio drivers. Allthe core firmware loading support has been moved into a new drivercs_dsp, leaving only the ASoC-specific parts in wm_adsp.Signed-off-by: Simon Trimmer Signed-off-by: Charles Keepax Link: https://lore.kernel.org/r/20210913160057.103842-17-simont@opensource.cirrus.comSigned-off-by: Mark Brown List of files: /linux-6.15/drivers/firmware/Makefile

8633ef82 - drivers/firmware: consolidate EFI framebuffer setup for all arches

Fri, 25 Jun 2021 13:13:59 +0000

drivers/firmware: consolidate EFI framebuffer setup for all archesThe register_gop_device() function registers an "efi-framebuffer" platformdevice to match against the efifb driver, to have an early framebuffer forEFI platforms.But there is already support to do exactly the same by the Generic SystemFramebuffers (sysfb) driver. This used to be only for X86 but it has beenmoved to drivers/firmware and could be reused by other architectures.Also, besides supporting registering an "efi-framebuffer", this driver canregister a "simple-framebuffer" allowing to use the siple{fb,drm} driverson non-X86 EFI platforms. For example, on aarch64 these drivers can onlybe used with DT and doesn't have code to register a "simple-frambuffer"platform device when booting with EFI.For these reasons, let's remove the register_gop_device() duplicated codeand instead move the platform specific logic that's there to sysfb driver.Signed-off-by: Javier Martinez Canillas Acked-by: Borislav Petkov Acked-by: Daniel Vetter Signed-off-by: Thomas Zimmermann Link: https://patchwork.freedesktop.org/patch/msgid/20210625131359.1804394-1-javierm@redhat.com List of files: /linux-6.15/drivers/firmware/Makefile

d391c582 - drivers/firmware: move x86 Generic System Framebuffers support

Fri, 25 Jun 2021 13:09:46 +0000

drivers/firmware: move x86 Generic System Framebuffers supportThe x86 architecture has generic support to register a system framebufferplatform device. It either registers a "simple-framebuffer" if the configoption CONFIG_X86_SYSFB is enabled, or a legacy VGA/VBE/EFI FB device.But the code is generic enough to be reused by other architectures and canbe moved out of the arch/x86 directory.This will allow to also support the simple{fb,drm} drivers on non-x86 EFIplatforms, such as aarch64 where these drivers are only supported with DT.Signed-off-by: Javier Martinez Canillas Acked-by: Borislav Petkov Acked-by: Greg Kroah-Hartman Acked-by: Daniel Vetter Signed-off-by: Thomas Zimmermann Link: https://patchwork.freedesktop.org/patch/msgid/20210625130947.1803678-2-javierm@redhat.com List of files: /linux-6.15/drivers/firmware/Makefile

b42000e4 - firmware: qcom_scm: Allow qcom_scm driver to be loadable as a permenent module

Wed, 07 Jul 2021 04:53:20 +0000

firmware: qcom_scm: Allow qcom_scm driver to be loadable as a permenent moduleAllow the qcom_scm driver to be loadable as a permenent module.This still uses the "depends on QCOM_SCM || !QCOM_SCM" bit toensure that drivers that call into the qcom_scm driver arealso built as modules. While not ideal in some cases its theonly safe way I can find to avoid build errors without havingthose drivers select QCOM_SCM and have to force it on (asQCOM_SCM=n can be valid for those drivers).Reviving this now that Saravana's fw_devlink defaults to on,which should avoid loading troubles seen before.Acked-by: Kalle Valo Acked-by: Greg Kroah-Hartman Acked-by: Will Deacon Reviewed-by: Bjorn Andersson Signed-off-by: John Stultz Link: https://lore.kernel.org/r/20210707045320.529186-1-john.stultz@linaro.orgSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/firmware/Makefile

e7818584 - firmware: arm_ffa: Add initial FFA bus support for device enumeration

Fri, 21 May 2021 15:10:29 +0000

firmware: arm_ffa: Add initial FFA bus support for device enumerationThe Arm FF for Armv8-A specification has concept of endpoints orpartitions. In the Normal world, a partition could be a VM whenthe Virtualization extension is enabled or the kernel itself.In order to handle multiple partitions, we can create a FFA device foreach such partition on a dedicated FFA bus. Similarly, different driversrequiring FFA transport can be registered on the same bus. We can matchthe device and drivers using UUID. This is mostly for the in-kernelusers with FFA drivers.Link: https://lore.kernel.org/r/20210521151033.181846-2-sudeep.holla@arm.comTested-by: Jens Wiklander Signed-off-by: Sudeep Holla List of files: /linux-6.15/drivers/firmware/Makefile

8dc24866 - Revert "firmware: QCOM_SCM: Allow qcom_scm driver to be loadable as a permenent module"

Mon, 23 Nov 2020 12:33:20 +0000

Revert "firmware: QCOM_SCM: Allow qcom_scm driver to be loadable as a permenent module"This reverts commit d0511b5496c03cdbcda55a9b57c32cdd751920ed.After some time it was noticed that the Tegra186 among otherswere experiencing problems when making this into a module.Signed-off-by: Linus Walleij List of files: /linux-6.15/drivers/firmware/Makefile

d0511b54 - firmware: QCOM_SCM: Allow qcom_scm driver to be loadable as a permenent module

Fri, 06 Nov 2020 04:27:10 +0000

firmware: QCOM_SCM: Allow qcom_scm driver to be loadable as a permenent moduleAllow the qcom_scm driver to be loadable as a permenent module.This still uses the "depends on QCOM_SCM || !QCOM_SCM" bit toensure that drivers that call into the qcom_scm driver arealso built as modules. While not ideal in some cases its theonly safe way I can find to avoid build errors without havingthose drivers select QCOM_SCM and have to force it on (asQCOM_SCM=n can be valid for those drivers).Signed-off-by: John Stultz Reviewed-by: Bjorn Andersson Acked-by: Kalle Valo Acked-by: Greg Kroah-Hartman Cc: Catalin Marinas Cc: Will Deacon Cc: Andy Gross Cc: Bjorn Andersson Cc: Joerg Roedel Cc: Thomas Gleixner Cc: Jason Cooper Cc: Marc Zyngier Cc: Linus Walleij Cc: Vinod Koul Cc: Kalle Valo Cc: Maulik Shah Cc: Lina Iyer Cc: Saravana Kannan Cc: Todd Kjos Cc: Greg Kroah-Hartman Cc: linux-arm-msm@vger.kernel.orgCc: iommu@lists.linux-foundation.orgCc: linux-gpio@vger.kernel.orgLink: https://lore.kernel.org/r/20201106042710.55979-3-john.stultz@linaro.orgSigned-off-by: Linus Walleij List of files: /linux-6.15/drivers/firmware/Makefile

66d90f6e - firmware: arm_scmi: Enable building as a single module

Mon, 07 Sep 2020 11:09:23 +0000

firmware: arm_scmi: Enable building as a single moduleNow, with all the plumbing in place to enable building scmi as a moduleinstead of built-in modules, let us enable the same.Link: https://lore.kernel.org/r/20200907195046.56615-5-sudeep.holla@arm.comTested-by: Cristian Marussi Signed-off-by: Sudeep Holla List of files: /linux-6.15/drivers/firmware/Makefile

f2ae9706 - firmware: smccc: Refactor SMCCC specific bits into separate file

Mon, 18 May 2020 09:12:20 +0000

firmware: smccc: Refactor SMCCC specific bits into separate fileIn order to add newer SMCCC v1.1+ functionality and to avoid clutteringPSCI firmware driver with SMCCC bits, let us move the SMCCC specificdetails under drivers/firmware/smccc/smccc.cWe can also drop conduit and smccc_version from psci_operations structureas SMCCC was the sole user and now it maintains those.No functionality change in this patch though.Signed-off-by: Sudeep Holla Tested-by: Etienne Carriere Reviewed-by: Etienne Carriere Acked-by: Mark Rutland Link: https://lore.kernel.org/r/20200518091222.27467-6-sudeep.holla@arm.comSigned-off-by: Will Deacon List of files: /linux-6.15/drivers/firmware/Makefile

9a434cee - firmware: qcom_scm: Dynamically support SMCCC and legacy conventions

Tue, 07 Jan 2020 21:04:26 +0000

firmware: qcom_scm: Dynamically support SMCCC and legacy conventionsDynamically support SMCCCC and legacy conventions by detecting whichconvention to use at runtime. qcom_scm_call_atomic and qcom_scm_call canthen be moved in qcom_scm.c and use underlying convention backend asappropriate. Thus, rename qcom_scm-64,-32 to reflect that they arebackends for -smc and -legacy, respectively.Also add support for making SCM calls earlier than when SCM driverprobes to support use cases such as qcom_scm_set_cold_boot_addr. Supportis added by lazily initializing the convention and guarding the querywith a spin lock. The limitation of these early SCM calls is that theycannot use DMA, as in the case of >4 arguments for SMC convention andany non-atomic call for legacy convention.Tested-by: Brian Masney # arm32Tested-by: Stephan Gerhold Signed-off-by: Elliot Berman Link: https://lore.kernel.org/r/1578431066-19600-18-git-send-email-eberman@codeaurora.orgSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/firmware/Makefile