Changes in Makefile

2eeb74c4 - bus: etzpc: introduce ETZPC firewall controller driver

Fri, 05 Jan 2024 13:04:00 +0000

bus: etzpc: introduce ETZPC firewall controller driverETZPC is a peripheral and memory firewall controller that filter accessesbased on Arm TrustZone secure state and Arm CPU privilege execution level.It handles MCU isolation as well.Signed-off-by: Gatien Chevallier Signed-off-by: Alexandre Torgue List of files: /linux-6.15/drivers/bus/Makefile

a1820845 - bus: rifsc: introduce RIFSC firewall controller driver

Fri, 05 Jan 2024 13:03:58 +0000

bus: rifsc: introduce RIFSC firewall controller driverRIFSC is a peripheral firewall controller that filter accesses based onArm TrustZone secure state, Arm CPU privilege execution level andCompartment IDentification of the STM32 SoC subsystems.Signed-off-by: Gatien Chevallier Signed-off-by: Alexandre Torgue List of files: /linux-6.15/drivers/bus/Makefile

5c9668cf - firewall: introduce stm32_firewall framework

Fri, 05 Jan 2024 13:03:56 +0000

firewall: introduce stm32_firewall frameworkIntroduce a STM32 firewall framework that offers to firewall consumersdifferent firewall services such as the ability to check their accessrights against their firewall controller(s).The STM32 firewall framework offers a generic API for STM32 firewallcontrollers that is defined in their drivers to best fit thespecificity of each firewall.There are various types of firewalls:-Peripheral firewalls that filter accesses to peripherals-Memory firewalls that filter accesses to memories or memory regions-No type for undefined type of firewallSigned-off-by: Gatien Chevallier Signed-off-by: Alexandre Torgue List of files: /linux-6.15/drivers/bus/Makefile

97d485ed - bus: add driver for initializing the SSC bus on (some) qcom SoCs

Mon, 11 Apr 2022 07:21:55 +0000

bus: add driver for initializing the SSC bus on (some) qcom SoCsAdd bindings for the AHB bus which exposes the SSC (Snapdragon Sensor Core)block in the global address space. This bus (and the SSC block itself) ispresent on certain qcom SoCs.In typical configuration, this bus (as some of the clocks and registersthat we need to manipulate) is not accessible to Linux, and the resourceson this bus are indirectly accessed by communicating with a hexagon CPUcore residing in the SSC block. In this configuration, the hypervisor isthe one performing the bus initialization for the purposes of bringingthe hexagon CPU core out of reset.However, it is possible to change the configuration, in which case thisdriver will initialize the bus.In combination with drivers for resources on the SSC bus, this driver canaid in debugging, and for example with a TLMM driver can be used todirectly access SSC-dedicated GPIO pins, removing the need to committo a particular usecase during hw design.Finally, until open firmware for the hexagon core is available, thisapproach allows for using sensors hooked up to SSC-dedicated GPIO pinson mainline Linux simply by utilizing the existing in-tree drivers forthese sensors.Signed-off-by: Michael Srba Reviewed-by: Jeffrey Hugo Signed-off-by: Bjorn Andersson Link: https://lore.kernel.org/r/20220411072156.24451-5-michael.srba@seznam.cz List of files: /linux-6.15/drivers/bus/Makefile

a0f5a630 - bus: mhi: Move host MHI code to "host" directory

Tue, 01 Mar 2022 16:03:02 +0000

bus: mhi: Move host MHI code to "host" directoryIn preparation of the endpoint MHI support, let's move the host MHI codeto its own "host" directory and adjust the toplevel MHI Kconfig & Makefile.While at it, let's also move the "pci_generic" driver to "host" directoryas it is a host MHI controller driver.Reviewed-by: Hemant Kumar Reviewed-by: Alex Elder Signed-off-by: Manivannan Sadhasivam Link: https://lore.kernel.org/r/20220301160308.107452-5-manivannan.sadhasivam@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/bus/Makefile

81967efb - drivers: bus: Delete CONFIG_SIMPLE_PM_BUS

Wed, 29 Sep 2021 00:07:34 +0000

drivers: bus: Delete CONFIG_SIMPLE_PM_BUSThe simple-pm-bus driver is mandatory for CONFIG_OF based platforms to workwith fw_devlink. So, always compile it in for CONFIG_OF and delete theconfig since it's no longer necessary.Tested-by: Ulf Hansson Tested-by: Geert Uytterhoeven Tested-by: Damien Le Moal Cc: Rob Herring Signed-off-by: Saravana Kannan Link: https://lore.kernel.org/r/20210929000735.585237-3-saravanak@google.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/bus/Makefile

1c953bda - bus: ixp4xx: Add a driver for IXP4xx expansion bus

Thu, 15 Jul 2021 23:53:34 +0000

bus: ixp4xx: Add a driver for IXP4xx expansion busThe Intel IXP4xx SoCs have an expansion bus that is usually justused for flash memory and configured by the boot loaders and canbe accessed using the "simple-bus".However some devices need more elaborate configuration and then weneed to provide a proper 3-unit address space indicating chipselect for each device and provide timing and similar information.Cc: Marc Zyngier Signed-off-by: Linus Walleij List of files: /linux-6.15/drivers/bus/Makefile

8f93662d - bus: Add Baikal-T1 APB-bus driver

Tue, 26 May 2020 12:59:27 +0000

bus: Add Baikal-T1 APB-bus driverBaikal-T1 AXI-APB bridge is used to access the SoC subsystem CSRs.IO requests are routed to this bus by means of the DW AMBA 3 AXIInterconnect. In case if an attempted APB transaction stays with noresponse for a pre-defined time an interrupt occurs and the bus getsfreed for a next operation. This driver provides the interrupt handlerto detect the erroneous address, prints an error message about theaddress fault, updates an errors counter. The counter and the APB-busoperations timeout can be accessed via corresponding sysfs nodes.A dedicated sysfs-node can be also used to artificially cause thebus errors described above.[arnd: fix build warnings for missing includes and wrong return types]Link: https://lore.kernel.org/r/20200526125928.17096-6-Sergey.Semin@baikalelectronics.ruSigned-off-by: Serge Semin Cc: Alexey Malahov Cc: Paul Burton Cc: Olof Johansson Cc: Rob Herring Cc: linux-mips@vger.kernel.orgCc: soc@kernel.orgCc: devicetree@vger.kernel.orgReported-by: kbuild test robot Reported-by: kbuild test robot Signed-off-by: Arnd Bergmann List of files: /linux-6.15/drivers/bus/Makefile

63cb7713 - bus: Add Baikal-T1 AXI-bus driver

Tue, 26 May 2020 12:59:26 +0000

bus: Add Baikal-T1 AXI-bus driverAXI3-bus is the main communication bus connecting all high-speedperipheral IP-cores with RAM controller and MIPS P5600 cores on Baikal-T1SoC. Bus traffic arbitration is done by means of DW AMBA 3 AXIInterconnect (so called AXI Main Interconnect) routing IO requests fromone SoC block to another. This driver provides a way to detect any busprotocol errors and device not responding situations by means of anembedded on top of the interconnect errors handler block (EHB). AXIInterconnect QoS arbitration tuning is currently unsupported.The bus doesn't provide a way to detect the interconnected devices,so they are supposed to be statically defined like by means of thesimple-bus sub-nodes.[arnd: fix build warnings for missing includes and wrong return types]Link: https://lore.kernel.org/r/20200526125928.17096-5-Sergey.Semin@baikalelectronics.ruSigned-off-by: Serge Semin Cc: Alexey Malahov Cc: Paul Burton Cc: Olof Johansson Cc: Rob Herring Cc: linux-mips@vger.kernel.orgCc: soc@kernel.orgCc: devicetree@vger.kernel.orgReported-by: kbuild test robot Reported-by: kbuild test robot Signed-off-by: Arnd Bergmann List of files: /linux-6.15/drivers/bus/Makefile

ccea5e8a - bus: Add driver for Integrator/AP logic modules

Thu, 13 Feb 2020 12:41:23 +0000

bus: Add driver for Integrator/AP logic modulesThe logic modules on the Integrator/AP (Application Platform)are logic tiles with (typically) one or a few peripheraldevices. They are most commonly used for FPGA prototyping.Using the device tree node for logic tiles, we probe themin order and check if the special system controller registerconfirm their presence before populating the node for a tile.This supercedes the code in arch/arm/mach-integrator/lm.[c|h]and makes it possible to populate the tiles using the devicetree instead of boardfile-based descriptions.Tested with all peripherals including graphics and MMC cardworking fine with the IM-PD1 example tile from Arm.Signed-off-by: Linus Walleij List of files: /linux-6.15/drivers/bus/Makefile

0cbf2608 - bus: mhi: core: Add support for registering MHI controllers

Thu, 20 Feb 2020 09:58:40 +0000

bus: mhi: core: Add support for registering MHI controllersThis commit adds support for registering MHI controller drivers withthe MHI stack. MHI controller drivers manages the interaction with theMHI client devices such as the external modems and WiFi chipsets. Theyare also the MHI bus master in charge of managing the physical linkbetween the host and client device.This is based on the patch submitted by Sujeev Dias:https://lkml.org/lkml/2018/7/9/987Signed-off-by: Sujeev Dias Signed-off-by: Siddartha Mohanadoss [jhugo: added static config for controllers and fixed several bugs]Signed-off-by: Jeffrey Hugo [mani: removed DT dependency, splitted and cleaned up for upstream]Signed-off-by: Manivannan Sadhasivam Link: https://lore.kernel.org/r/20200220095854.4804-3-manivannan.sadhasivam@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/bus/Makefile

7cabf925 - bus/ti-pwmss: move TI PWMSS driver from PWM to bus subsystem

Sun, 01 Sep 2019 22:58:22 +0000

bus/ti-pwmss: move TI PWMSS driver from PWM to bus subsystemThe TI PWMSS driver is a simple bus driver for providing powerpower management for the PWM peripherals on TI AM33xx SoCs, namelyeCAP, eHRPWM and eQEP. The eQEP is a counter rather than a PWM, soit does not make sense to have the bus driver in the PWM subsystemsince the PWMSS is not exclusive to PWM devices.Signed-off-by: David Lechner Signed-off-by: Jonathan Cameron List of files: /linux-6.15/drivers/bus/Makefile

5bc7f990 - bus: Add support for Moxtet bus

Mon, 12 Aug 2019 16:11:14 +0000

bus: Add support for Moxtet busOn the Turris Mox router different modules can be connected to the mainCPU board: currently a module with a SFP cage, a module with MiniPCIeconnector, a PCIe pass-through MiniPCIe connector module, a 4-portswitch module, an 8-port switch module, and a 4-port USB3 module.For example: [CPU]-[PCIe-pass-through]-[PCIe]-[8-port switch]-[8-port switch]-[SFP]Each of this modules has an input and output shift register, and theseare connected via SPI to the CPU board.Via SPI we are able to discover which modules are connected, in whichorder, and we can also read some information about the modules (eg.their interrupt status), and configure them.From each module 8 bits can be read (of which low 4 bits identify themodule) and 8 bits can be written.For example from the module with a SFP cage we can read the LOS,TX-FAULT and MOD-DEF0 signals, while we can write TX-DISABLE andRATE-SELECT signals.This driver creates a new bus type, called "moxtet". For each Mox moduleit finds via SPI, it creates a new device on the moxtet bus so thatdrivers can be written for them.It also implements a virtual interrupt controller for the modules whichsend their interrupt status over the SPI shift register. These modulesdo this in addition to sending their interrupt status via the sharedinterrupt line. When the shared interrupt is triggered, we read from theshift register and handle IRQs for all devices which are in interrupt.The topology of how Mox modules are connected can then be read bylisting /sys/bus/moxtet/devices.Link: https://lore.kernel.org/r/20190812161118.21476-2-marek.behun@nic.czSigned-off-by: Marek Behún Reviewed-by: Linus Walleij Signed-off-by: Arnd Bergmann List of files: /linux-6.15/drivers/bus/Makefile

8818e865 - bus: add bus driver for accessing Allwinner A64 DE2

Fri, 22 Jun 2018 12:45:36 +0000

bus: add bus driver for accessing Allwinner A64 DE2The "Display Engine 2.0" (usually called DE2) on the Allwinner A64 SoCis different from the ones on other Allwinner SoCs. It requires a SRAMregion to be claimed, otherwise all DE2 subblocks won't be accessible.Add a bus driver for the Allwinner A64 DE2 part which claims the SRAMregion when probing.Signed-off-by: Icenowy Zheng Signed-off-by: Maxime Ripard List of files: /linux-6.15/drivers/bus/Makefile

adf38bb0 - HISI LPC: Support the LPC host on Hip06/Hip07 with DT bindings

Wed, 21 Mar 2018 22:23:02 +0000

HISI LPC: Support the LPC host on Hip06/Hip07 with DT bindingsThe low-pin-count (LPC) interface of Hip06/Hip07 accesses I/O port space ofperipherals.Implement the LPC host controller driver which performs the I/O operationson the underlying hardware. We don't want to touch existing drivers suchas ipmi-bt, so this driver applies the indirect-IO introduced in theprevious patch after registering an indirect-IO node to the indirect-IOdevices list which will be searched by the I/O accessors to retrieve thehost-local I/O port.The driver config is set as a bool instead of a tristate. The reason hereis that, by the very nature of the driver providing a logical PIO range, itdoes not make sense to have this driver as a loadable module. Another morespecific reason is that the Huawei D03 board which includes Hip06 SoCrequires the LPC bus for UART console, so should be built in.Tested-by: dann frazier Signed-off-by: Zou Rongrong Signed-off-by: Zhichang Yuan Signed-off-by: John Garry Signed-off-by: Bjorn Helgaas Reviewed-by: Andy Shevchenko Acked-by: Rob Herring # dts part List of files: /linux-6.15/drivers/bus/Makefile

1888d3dd - drivers/bus: Move Arm CCN PMU driver

Thu, 15 Feb 2018 18:51:41 +0000

drivers/bus: Move Arm CCN PMU driverThe arm-ccn driver is purely a perf driver for the CCN PMU, not a busdriver in the sense of the other residents of drivers/bus/, so let'smove it to the appropriate place for SoC PMU drivers. Not to mentionmoving the documentation accordingly as well.Acked-by: Pawel Moll Acked-by: Will Deacon Signed-off-by: Robin Murphy Signed-off-by: Arnd Bergmann List of files: /linux-6.15/drivers/bus/Makefile

6bd067c4 - staging: fsl-mc: Move core bus out of staging

Mon, 05 Feb 2018 14:07:42 +0000

staging: fsl-mc: Move core bus out of stagingMove the source files out of staging into their final locations: -mc.h include file in drivers/staging/fsl-mc/include go to include/linux/fsl -source files in drivers/staging/fsl-mc/bus go to drivers/bus/fsl-mc -overview.rst, providing an overview of DPAA2, goes to Documentation/networking/dpaa2/overview.rstUpdate or delete other remaining staging files -- Makefile, Kconfig, TODO.Update dpaa2_eth and dpio staging drivers.Add integration bits for the documentation build system.Signed-off-by: Stuart Yoder [rebased, add dpaa2_eth and dpio #include updates]Signed-off-by: Laurentiu Tudor [rebased, split irqchip to separate patch]Signed-off-by: Bogdan Purcareata Cc: Thomas Gleixner Cc: Jason Cooper Cc: Marc Zyngier Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/bus/Makefile

5b143d2a - bus: add driver for the Technologic Systems NBUS

Wed, 01 Nov 2017 17:14:33 +0000

bus: add driver for the Technologic Systems NBUSThis driver implements a GPIOs bit-banged bus, called the NBUS byTechnologic Systems. It is used to communicate with the peripherals inthe FPGA on the TS-4600 SoM.Signed-off-by: Sebastien Bourdelin Acked-by: Linus Walleij Signed-off-by: Arnd Bergmann List of files: /linux-6.15/drivers/bus/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/bus/Makefile

0eecc636 - bus: ti-sysc: Add minimal TI sysc interconnect target driver

Tue, 10 Oct 2017 21:23:43 +0000

bus: ti-sysc: Add minimal TI sysc interconnect target driverWe can handle the sysc interconnect target module in a generic wayfor many TI SoCs. Initially let's just enable runtime PM withautosuspend, and probe the children. This can already be used foridling interconnect target modules that don't have any device driveravailable for the child devices.For now, the "ti,hwmods" custom binding is still required. That willbe eventually deprecated in later patches. And more features will beadded, such as parsing for sysc capabilities so we can continueremoving the legacy platform data.Cc: Benoît Cousson Cc: Greg Kroah-Hartman Cc: Laurent Pinchart Cc: Nishanth Menon Cc: Matthijs van Duin Cc: Paul Walmsley Cc: Peter Ujfalusi Cc: Sakari Ailus Cc: Tero Kristo Cc: Tomi Valkeinen Cc: linux-kernel@vger.kernel.orgSigned-off-by: Tony Lindgren List of files: /linux-6.15/drivers/bus/Makefile