Changes in Kconfig

51f0b891 - firmware: thead: add CONFIG_MAILBOX dependency

Fri, 14 Mar 2025 15:48:13 +0000

firmware: thead: add CONFIG_MAILBOX dependencyWithout this, the driver fails to build:ld: drivers/firmware/thead,th1520-aon.o: in function `th1520_aon_call_rpc':thead,th1520-aon.c:(.text+0x28): undefined reference to `mbox_send_message'ld: drivers/firmware/thead,th1520-aon.o: in function `th1520_aon_deinit':thead,th1520-aon.c:(.text+0x17e): undefined reference to `mbox_free_channel'ld: drivers/firmware/thead,th1520-aon.o: in function `th1520_aon_init':thead,th1520-aon.c:(.text+0x1d9): undefined reference to `mbox_request_channel_byname'Fixes: e4b3cbd840e5 ("firmware: thead: Add AON firmware protocol driver")Signed-off-by: Arnd Bergmann Reviewed-by: Michal Wilczynski Link: https://lore.kernel.org/r/20250314154816.4045334-1-arnd@kernel.orgSigned-off-by: Ulf Hansson List of files: /linux-6.15/drivers/firmware/Kconfig

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/Kconfig

9a9b7cd7 - firmware: config: ti-sci: Default set to ARCH_K3 for the ti sci driver

Thu, 20 Feb 2025 13:31:17 +0000

firmware: config: ti-sci: Default set to ARCH_K3 for the ti sci driverWith ARCH_K3=y we cannot enable TI_SCI_PROTOCOL=m becauseARCH_K3 selects TI_SCI_PROTOCOL.Modify the logic to enable TI_SCI_PROTOCOL by default when ARCH_K3=yallowing us to submit a future patch to remove select on ARCH_K3 withoutbreaking existing users.Signed-off-by: Guillaume La Roque Reviewed-by: Kevin Hilman Link: https://lore.kernel.org/r/20250220-ti-firmware-v2-1-ff26883c6ce9@baylibre.comSigned-off-by: Nishanth Menon List of files: /linux-6.15/drivers/firmware/Kconfig

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/Kconfig

e1e17a17 - firmware: iscsi_ibft: fix ISCSI_IBFT Kconfig entry

Mon, 11 Mar 2024 10:51:22 +0000

firmware: iscsi_ibft: fix ISCSI_IBFT Kconfig entryFix ISCSI_IBFT Kconfig entry, replace tab with a space character.Fixes: 138fe4e0697 ("Firmware: add iSCSI iBFT Support")Signed-off-by: Prasad Pandit Signed-off-by: Konrad Rzeszutek Wilk List of files: /linux-6.15/drivers/firmware/Kconfig

75fa9b7e - video: Add helpers for decoding screen_info

Mon, 12 Feb 2024 09:06:09 +0000

video: Add helpers for decoding screen_infoThe plain values as stored in struct screen_info need to be decodedbefore being used. Add helpers that decode the type of video outputand the framebuffer I/O aperture.Old or non-x86 systems may not set the type of video directly, butonly indicate the presence by storing 0x01 in orig_video_isVGA. Thedecoding logic in screen_info_video_type() takes this into account.It then follows similar code in vgacon's vgacon_startup() to detectthe video type from the given values.A call to screen_info_resources() returns all known resources of thegiven screen_info. The resources' values have been taken from existingcode in vgacon and vga16fb. These drivers can later be converted touse the new interfaces.v2: * return ssize_t from screen_info_resources() * don't call __screen_info_has_lfb() unnecessarilySigned-off-by: Thomas Zimmermann Reviewed-by: Javier Martinez Canillas Link: https://patchwork.freedesktop.org/patch/msgid/20240212090736.11464-2-tzimmermann@suse.de List of files: /linux-6.15/drivers/firmware/Kconfig

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/Kconfig

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/Kconfig

f2de37a5 - riscv, qemu_fw_cfg: Add support for RISC-V architecture

Thu, 12 Oct 2023 10:28:52 +0000

riscv, qemu_fw_cfg: Add support for RISC-V architectureQemu fw_cfg support was missing for RISC-V, which made it hard to doproper vmcore dumps from qemu.Add the missing RISC-V arch-defines.You can now do vmcore dumps from qemu. Add "-device vmcoreinfo" to theqemu command-line. From the qemu monitor: (qemu) dump-guest-memory vmcoreThe vmcore can now be used, e.g., with the "crash" utility.Acked-by: "Michael S. Tsirkin" Acked-by: Alistair Francis Tested-by: Clément Léger Signed-off-by: Björn Töpel Message-Id: <20231012102852.234442-1-bjorn@kernel.org>Signed-off-by: Michael S. Tsirkin List of files: /linux-6.15/drivers/firmware/Kconfig

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/Kconfig

d74612b6 - firmware: qcom: qseecom: Add missing AUXILIARY_BUS dependency

Fri, 15 Sep 2023 22:50:14 +0000

firmware: qcom: qseecom: Add missing AUXILIARY_BUS dependencyThe newly introduced QSEECOM driver fail to link if the system is builtwithout CONFIG_AUXILIARY_BUS, make sure it is selected.Fixes: 00b1248606ba ("firmware: qcom_scm: Add support for Qualcomm Secure Execution Environment SCM interface")Reported-by: Randy Dunlap Closes: https://lore.kernel.org/r/9f156fa6-e5aa-4cb2-ab2b-b67fd8fc4840%40infradead.orgSigned-off-by: Bjorn Andersson Acked-by: Randy Dunlap Tested-by: Randy Dunlap Link: https://lore.kernel.org/r/20230915-qseecom-auxiliary-fix-v1-1-38a46cfbfdb0@quicinc.comSigned-off-by: Bjorn Andersson List of files: /linux-6.15/drivers/firmware/Kconfig

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/Kconfig

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/Kconfig

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/Kconfig

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/Kconfig

8b766b0f - sysfb: Enable boot time VESA graphic mode selection

Fri, 25 Feb 2022 20:51:34 +0000

sysfb: Enable boot time VESA graphic mode selectionSince switch to simplefb/simpledrm VESA graphic mode selection with vga=kernel parameter is no longer available with legacy BIOS.The x86 realmode boot code enables the VESA graphic modes when optionFB_BOOT_VESA_SUPPORT is enabled.This option is selected by vesafb but not simplefb/simpledrm.To enable use of VESA modes with simplefb in legacy BIOS boot mode dropdependency of BOOT_VESA_SUPPORT on FB, also drop the FB_ prefix. Selectthe option from sysfb rather than the drivers that depend on it.The BOOT_VESA_SUPPORT is not specific to framebuffer but rather to x86platform, move it from fbdev to x86 Kconfig.Fixes: e3263ab389a7 ("x86: provide platform-devices for boot-framebuffers")Signed-off-by: Michal Suchanek Reviewed-by: Javier Martinez Canillas Acked-by: Borislav Petkov Signed-off-by: Thomas Zimmermann Link: https://patchwork.freedesktop.org/patch/msgid/948c39940a4e99f5b43bdbcbe537faae71a43e1d.1645822213.git.msuchanek@suse.de List of files: /linux-6.15/drivers/firmware/Kconfig

a4a072d9 - sysfb: Make config option dependencies explicit

Fri, 25 Feb 2022 20:51:33 +0000

sysfb: Make config option dependencies explicitefifb and vesafb requires sysfb implicitly but this is not stated inKconfig. Add the dependency.With that all drivers that require sysfb depend on it so it can defaultto disabled.Signed-off-by: Michal Suchanek Reviewed-by: Javier Martinez Canillas Signed-off-by: Thomas Zimmermann Link: https://patchwork.freedesktop.org/patch/msgid/a0fa41e9186653e4c41ad0a28259e5cdc71b1f66.1645822213.git.msuchanek@suse.de List of files: /linux-6.15/drivers/firmware/Kconfig

dc4e8c07 - ACPI: APEI: explicit init of HEST and GHES in apci_init()

Sun, 27 Feb 2022 12:25:45 +0000

ACPI: APEI: explicit init of HEST and GHES in apci_init()From commit e147133a42cb ("ACPI / APEI: Make hest.c manage the estatusmemory pool") was merged, ghes_init() relies on acpi_hest_init() to managethe estatus memory pool. On the other hand, ghes_init() relies onsdei_init() to detect the SDEI version and (un)register events. Thedependencies are as follows: ghes_init() => acpi_hest_init() => acpi_bus_init() => acpi_init() ghes_init() => sdei_init()HEST is not PCI-specific and initcall ordering is implicit and notwell-defined within a level.Based on above, remove acpi_hest_init() from acpi_pci_root_init() andconvert ghes_init() and sdei_init() from initcalls to explicit calls in thefollowing order: acpi_hest_init() ghes_init() sdei_init()Signed-off-by: Shuai Xue Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/firmware/Kconfig

424953cf - qcom_scm: hide Kconfig symbol

Tue, 28 Sep 2021 07:50:27 +0000

qcom_scm: hide Kconfig symbolNow that SCM can be a loadable module, we have to add anotherdependency to avoid link failures when ipa or adreno-gpu arebuilt-in:aarch64-linux-ld: drivers/net/ipa/ipa_main.o: in function `ipa_probe':ipa_main.c:(.text+0xfc4): undefined reference to `qcom_scm_is_available'ld.lld: error: undefined symbol: qcom_scm_is_available>>> referenced by adreno_gpu.c>>> gpu/drm/msm/adreno/adreno_gpu.o:(adreno_zap_shader_load) in archive drivers/built-in.aThis can happen when CONFIG_ARCH_QCOM is disabled and we don't selectQCOM_MDT_LOADER, but some other module selects QCOM_SCM. Ideally we'duse a similar dependency here to what we have for QCOM_RPROC_COMMON,but that causes dependency loops from other things selecting QCOM_SCM.This appears to be an endless problem, so try something different thistime: - CONFIG_QCOM_SCM becomes a hidden symbol that nothing 'depends on' but that is simply selected by all of its users - All the stubs in include/linux/qcom_scm.h can go away - arm-smccc.h needs to provide a stub for __arm_smccc_smc() to allow compile-testing QCOM_SCM on all architectures. - To avoid a circular dependency chain involving RESET_CONTROLLER and PINCTRL_SUNXI, drop the 'select RESET_CONTROLLER' statement. According to my testing this still builds fine, and the QCOM platform selects this symbol already.Acked-by: Kalle Valo Acked-by: Alex Elder Signed-off-by: Arnd Bergmann List of files: /linux-6.15/drivers/firmware/Kconfig

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/Kconfig