Changes in Kconfig

02c24a12 - pmdomain: ti: Move and add Kconfig options to the pmdomain subsystem

Tue, 12 Sep 2023 13:35:25 +0000

pmdomain: ti: Move and add Kconfig options to the pmdomain subsystemThe TI_SCI_PM_DOMAINS Kconfig option belongs closer to its correspondingimplementation, hence let's move it from the soc subsystem to the pmdomainsubsystem.While at it, let's also add a Kconfig option the omap_prm driver, ratherthan using ARCH_OMAP2PLUS directly.Cc: Nishanth Menon Cc: Santosh Shilimkar Cc: Tero Kristo Cc: Tony Lindgren Reviewed-by: Dhruva Gole Signed-off-by: Ulf Hansson List of files: /linux-6.15/drivers/soc/ti/Kconfig

e752f9b9 - soc: ti: pruss: Allow compile-testing

Thu, 11 May 2023 14:54:36 +0000

soc: ti: pruss: Allow compile-testingAllow compile testing of TI PRU-ICSS Subsystem Platform drivers.This allows for improved build-test coverage.No functional change intended.Signed-off-by: Simon Horman Link: https://lore.kernel.org/r/20230511-ti-pruss-compile-testing-v1-1-56291309a60c@kernel.orgSigned-off-by: Nishanth Menon List of files: /linux-6.15/drivers/soc/ti/Kconfig

13e7accb - genirq: Get rid of GENERIC_MSI_IRQ_DOMAIN

Fri, 11 Nov 2022 13:54:40 +0000

genirq: Get rid of GENERIC_MSI_IRQ_DOMAINAdjust to reality and remove another layer of pointless Kconfigindirection. CONFIG_GENERIC_MSI_IRQ is good enough to serveall purposes.Signed-off-by: Thomas Gleixner Reviewed-by: Jason Gunthorpe Link: https://lore.kernel.org/r/20221111122014.524842979@linutronix.de List of files: /linux-6.15/drivers/soc/ti/Kconfig

c07f216a - soc: ti: k3-ringacc: Allow the driver to be built as module

Sat, 29 Oct 2022 07:53:56 +0000

soc: ti: k3-ringacc: Allow the driver to be built as moduleThe ring accelerator driver can be built as module since all dependingfunctions are exported.Signed-off-by: Peter Ujfalusi Signed-off-by: Nishanth Menon Tested-by: Nicolas Frayer Reviewed-by: Nicolas Frayer Link: https://lore.kernel.org/r/20221029075356.7296-1-peter.ujfalusi@gmail.com List of files: /linux-6.15/drivers/soc/ti/Kconfig

e83b2358 - soc: ti: Kconfig: Drop ARM64 SoC specific configs

Sun, 22 Nov 2020 03:22:01 +0000

soc: ti: Kconfig: Drop ARM64 SoC specific configsWith the integration of chip-id detection scheme in kernel[1], thereis no specific need to maintain multitudes of SoC specific configoptions, discussed as per [2], we have deprecated the usage in otherplaces for v5.10-rc1. Drop the configuration for the follow on kernel.[1] drivers/soc/ti/k3-socinfo.c commit 907a2b7e2fc7 ("soc: ti: add k3 platforms chipid module driver")Signed-off-by: Nishanth Menon Signed-off-by: Santosh Shilimkar List of files: /linux-6.15/drivers/soc/ti/Kconfig

6530cd9b - soc: ti: pruss: Enable support for ICSSG subsystems on K3 AM65x SoCs

Sat, 12 Sep 2020 04:43:36 +0000

soc: ti: pruss: Enable support for ICSSG subsystems on K3 AM65x SoCsThe K3 AM65x family of SoCs have the next generation of the PRU-ICSSprocessor subsystem capable of supporting Gigabit Ethernet, and iscommonly referred to as ICSSG. These SoCs contain typically threeICSSG instances named ICSSG0, ICSSG1 and ICSSG2. The three ICSSGs areidentical to each other for the most part with minor SoC integrationdifferences and capabilities. The ICSSG2 supports slightly enhancedfeatures like SGMII mode Ethernet, while the ICSS0 and ICSSG1 instancesare limited to MII mode only.The ICSSGs on K3 AM65x SoCs are in general super-sets of the PRUSS on theAM57xx/66AK2G SoCs. They include two additional auxiliary PRU cores calledRTUs and few other additional sub-modules. The interrupt integration isalso different on the K3 AM65x SoCs and are propagated through variousSoC-level Interrupt Router and Interrupt Aggregator blocks. Other IP leveldifferences include different constant tables, differences in system eventinterrupt input sources etc. They also do not have a programmable modulereset line like those present on AM33xx/AM43xx SoCs. The modules are resetjust like any other IP with the SoC's global cold/warm resets.The existing pruss platform driver has been updated to support these newICSSG instances through new AM65x specific compatibles. A build dependencywith ARCH_K3 is added to enable building all the existing PRUSS platformdrivers for this ARMv8 platform.Signed-off-by: Suman Anna Signed-off-by: Grzegorz Jaszczyk Signed-off-by: Santosh Shilimkar List of files: /linux-6.15/drivers/soc/ti/Kconfig

3227c8da - soc: ti: pruss: Add support for PRU-ICSS subsystems on 66AK2G SoC

Sat, 12 Sep 2020 04:43:36 +0000

soc: ti: pruss: Add support for PRU-ICSS subsystems on 66AK2G SoCThe 66AK2G SoC supports two PRU-ICSS instances, named PRUSS0 and PRUSS1,each of which has two PRU processor cores. The two PRU-ICSS instancesare identical to each other with few minor SoC integration differences,and are very similar to the PRU-ICSS1 of AM57xx/AM43xx. The Shared DataRAM size is larger and the number of interrupts coming into MPU INTCis like the instances on AM437x. There are also few other differencesattributing to integration in Keystone architecture (like no SYSCFGregister or PRCM handshake protocols). Other IP level differencesinclude different constant table, differences in system event interruptinput sources etc. They also do not have a programmable module resetline like those present on AM33xx/AM43xx SoCs. The modules are resetjust like any other IP with the SoC's global cold/warm resets.The existing PRUSS platform driver has been enhanced to support these66AK2G PRU-ICSS instances through new 66AK2G specific compatible forproperly probing and booting all the different PRU cores in eachPRU-ICSS processor subsystem. A build dependency with ARCH_KEYSTONEis added to enable the driver to be built in K2G-only configuration.Signed-off-by: Andrew F. Davis Signed-off-by: Suman Anna Signed-off-by: Grzegorz Jaszczyk Signed-off-by: Santosh Shilimkar List of files: /linux-6.15/drivers/soc/ti/Kconfig

ae19b8a1 - soc: ti: pruss: Add support for PRU-ICSS subsystems on AM57xx SoCs

Sat, 12 Sep 2020 04:43:35 +0000

soc: ti: pruss: Add support for PRU-ICSS subsystems on AM57xx SoCsThe AM57xx family of SoCs supports two PRU-ICSS instances, each ofwhich has two PRU processor cores. The two PRU-ICSS instances areidentical to each other, and are very similar to the PRU-ICSS1 ofAM33xx/AM43xx except for a few minor differences like the RAM sizesand the number of interrupts coming into the MPU INTC. They donot have a programmable module reset line unlike those present onAM33xx/AM43xx SoCs. The modules are reset just like any other IPwith the SoC's global cold/warm resets. Each PRU-ICSS's INTC is alsopreceded by a Crossbar that enables multiple external events to berouted to a specific number of input interrupt events. Any interruptevent directed towards PRUSS needs this crossbar to be setup properlyon the firmware side.The existing PRUSS platform driver has been enhanced to supportthese AM57xx PRU-ICSS instances through new AM57xx specificcompatible for properly probing and booting all the different PRUcores in each PRU-ICSS processor subsystem. A build dependency withSOC_DRA7XX is also added to enable the driver to be built inAM57xx-only configuration (there is no separate Kconfig optionfor AM57xx vs DRA7xx).Signed-off-by: Suman Anna Signed-off-by: Grzegorz Jaszczyk Signed-off-by: Santosh Shilimkar List of files: /linux-6.15/drivers/soc/ti/Kconfig

78251639 - soc: ti: pruss: Add support for PRU-ICSSs on AM437x SoCs

Sat, 12 Sep 2020 04:43:35 +0000

soc: ti: pruss: Add support for PRU-ICSSs on AM437x SoCsThe AM437x SoCs have two different PRU-ICSS subsystems: PRU-ICSS1and a smaller PRU-ICSS0. Enhance the PRUSS platform driver to supportboth the PRU-ICSS sub-systems on these SoCs.The PRU-ICSS1 on AM437x is very similar to the PRU-ICSS on AM33xxexcept for few minor differences - increased Instruction RAM, increasedShared Data RAM2, and 1 less interrupt (PRUSS host interrupt 7 which isredirected to the other PRUSS) towards the MPU INTC. The PRU-ICSS0 isa cut-down version of the IP, with less DRAM per PRU, no Shared DRAM etc.It also does not have direct access to L3 bus regions, there is a singleinterface to L3 for both PRUSS0 and PRUSS1, and it would have to gothrough the PRUSS1's interface. The PRUSS_SYSCFG register is reserved onPRUSS0, so any external access requires the programming the correspondingPRUSS_SYSCFG register in PRUSS1. It does have its own dedicated I/O linesthough. Note that this instance does not support any PRU Ethernet relateduse cases.The adaptation uses SoC-specific compatibles in the driver and usesa newly introduced pruss_match_private_data structure and thepruss_get_private_data() function to retrieve a PRUSS instance specificdata using a device-name based lookup logic. The reset and the L3 externalaccess are managed by the parent interconnect ti-sysc bus driver so thatPRUSS1 and PRUSS0 can be independently supported.Signed-off-by: Suman Anna Signed-off-by: Andrew F. Davis Signed-off-by: Grzegorz Jaszczyk Signed-off-by: Santosh Shilimkar List of files: /linux-6.15/drivers/soc/ti/Kconfig

dc112956 - soc: ti: pruss: Add a platform driver for PRUSS in TI SoCs

Sat, 12 Sep 2020 04:43:34 +0000

soc: ti: pruss: Add a platform driver for PRUSS in TI SoCsThe Programmable Real-Time Unit - Industrial CommunicationSubsystem (PRU-ICSS) is present on various TI SoCs such asAM335x or AM437x or the Keystone 66AK2G. Each SoC can haveone or more PRUSS instances that may or may not be identical.For example, AM335x SoCs have a single PRUSS, while AM437x hastwo PRUSS instances PRUSS1 and PRUSS0, with the PRUSS0 beinga cut-down version of the PRUSS1.The PRUSS consists of dual 32-bit RISC cores called theProgrammable Real-Time Units (PRUs), some shared, data andinstruction memories, some internal peripheral modules, andan interrupt controller. The programmable nature of the PRUsprovide flexibility to implement custom peripheral interfaces,fast real-time responses, or specialized data handling.The PRU-ICSS functionality is achieved through three differentplatform drivers addressing a specific portion of the PRUSS.Some sub-modules of the PRU-ICSS IP reuse some of the existingdrivers (like davinci mdio driver or the generic syscon driver).This design provides flexibility in representing the differentmodules of PRUSS accordingly, and at the same time allowing thePRUSS driver to add some instance specific configuration withinan SoC.The PRUSS platform driver deals with the overall PRUSS and isused for managing the subsystem level resources like variousmemories and the CFG module. It is responsible for the creationand deletion of the platform devices for the child PRU devicesand other child devices (like Interrupt Controller, MDIO nodeand some syscon nodes) so that they can be managed by specificplatform drivers. The PRUSS interrupt controller is managed byan irqchip driver, while the individual PRU RISC cores aremanaged by a PRU remoteproc driver.The driver currently supports the AM335x SoC, and support forother TI SoCs will be added in subsequent patches.Signed-off-by: Suman Anna Signed-off-by: Andrew F. Davis Signed-off-by: Tero Kristo Signed-off-by: Grzegorz Jaszczyk Signed-off-by: Santosh Shilimkar List of files: /linux-6.15/drivers/soc/ti/Kconfig

907a2b7e - soc: ti: add k3 platforms chipid module driver

Thu, 28 May 2020 03:39:14 +0000

soc: ti: add k3 platforms chipid module driverThe Texas Instruments K3 Multicore SoC platforms have chipid module whichis represented by CTRLMMR_xxx_JTAGID register and contains informationabout SoC id and revision. Bits: 31-28 VARIANT Device variant 27-12 PARTNO Part number 11-1 MFG Indicates TI as manufacturer (0x17) 1 Always 1This patch adds corresponding driver to identify the TI K3 SoC family andrevision, and registers this information with the SoC bus. It is availableunder /sys/devices/soc0/ for user space, and can be checked, where needed,in Kernel using soc_device_match().Identification is done by:- checking MFG to be TI ID - retrieving Device variant (revision) - retrieving Part number and convert it to the family - retrieving machine from DT "/model"Example J721E: # cat /sys/devices/soc0/{machine,family,revision} Texas Instruments K3 J721E SoC J721E SR1.0Example AM65x: # cat /sys/devices/soc0/{machine,family,revision} Texas Instruments AM654 Base Board AM65X SR1.0Cc: Arnd Bergmann Signed-off-by: Grygorii Strashko Reviewed-by: Lokesh Vutla Reviewed-by: Tero Kristo Signed-off-by: Santosh Shilimkar List of files: /linux-6.15/drivers/soc/ti/Kconfig

3277e8aa - soc: ti: k3: add navss ringacc driver

Wed, 15 Jan 2020 18:07:27 +0000

soc: ti: k3: add navss ringacc driverThe Ring Accelerator (RINGACC or RA) provides hardware acceleration toenable straightforward passing of work between a producer and a consumer.There is one RINGACC module per NAVSS on TI AM65x SoCs.The RINGACC converts constant-address read and write accesses to equivalentread or write accesses to a circular data structure in memory. The RINGACCeliminates the need for each DMA controller which needs to access ringelements from having to know the current state of the ring (base address,current offset). The DMA controller performs a read or write access to aspecific address range (which maps to the source interface on the RINGACC)and the RINGACC replaces the address for the transaction with a new addresswhich corresponds to the head or tail element of the ring (head for reads,tail for writes). Since the RINGACC maintains the state, multiple DMAcontrollers or channels are allowed to coherently share the same rings asapplicable. The RINGACC is able to place data which is destined towardssoftware into cached memory directly.Supported ring modes:- Ring Mode- Messaging Mode- Credentials Mode- Queue Manager ModeTI-SCI integration:Texas Instrument's System Control Interface (TI-SCI) Message Protocol nowhas control over Ringacc module resources management (RM) and Ringsconfiguration.The corresponding support of TI-SCI Ringacc module RM protocolintroduced as option through DT parameters:- ti,sci: phandle on TI-SCI firmware controller DT node- ti,sci-dev-id: TI-SCI device identifier as per TI-SCI firmware specif both parameters present - Ringacc driver will configure/free/reset Ringsusing TI-SCI Message Ringacc RM Protocol.The Ringacc driver manages Rings allocation by itself now and requestsTI-SCI firmware to allocate and configure specific Rings only. It's donethis way because, Linux driver implements two stage Rings allocation andconfiguration (allocate ring and configure ring) while TI-SCI MessageProtocol supports only one combined operation (allocate+configure).Signed-off-by: Grygorii Strashko Signed-off-by: Peter Ujfalusi Reviewed-by: Tero Kristo Tested-by: Keerthy Signed-off-by: Santosh Shilimkar List of files: /linux-6.15/drivers/soc/ti/Kconfig

521a503f - soc: ti: fix irq-ti-sci link error

Mon, 17 Jun 2019 13:01:05 +0000

soc: ti: fix irq-ti-sci link errorThe irqchip driver depends on the SoC specific driver, but we wantto be able to compile-test it elsewhere:WARNING: unmet direct dependencies detected for TI_SCI_INTA_MSI_DOMAIN Depends on [n]: SOC_TI [=n] Selected by [y]: - TI_SCI_INTA_IRQCHIP [=y] && TI_SCI_PROTOCOL [=y]drivers/irqchip/irq-ti-sci-inta.o: In function `ti_sci_inta_irq_domain_probe':irq-ti-sci-inta.c:(.text+0x204): undefined reference to `ti_sci_inta_msi_create_irq_domain'Rearrange the Kconfig and Makefile so we build the soc driver wheneverits users are there, regardless of the SOC_TI option.Fixes: 49b323157bf1 ("soc: ti: Add MSI domain bus support for Interrupt Aggregator")Fixes: f011df6179bd ("irqchip/ti-sci-inta: Add msi domain support")Signed-off-by: Arnd Bergmann Reviewed-by: Lokesh Vutla Acked-by: Santosh Shilimkar Signed-off-by: Olof Johansson List of files: /linux-6.15/drivers/soc/ti/Kconfig

cff377f7 - soc: ti: Add Support for J721E SoC config option

Wed, 22 May 2019 16:19:19 +0000

soc: ti: Add Support for J721E SoC config optionAdd option to build J721E SoC specific componentsSigned-off-by: Nishanth Menon Signed-off-by: Tero Kristo List of files: /linux-6.15/drivers/soc/ti/Kconfig

ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig

Sun, 19 May 2019 12:07:45 +0000

treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is: GPL-2.0-onlySigned-off-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/soc/ti/Kconfig

49b32315 - soc: ti: Add MSI domain bus support for Interrupt Aggregator

Tue, 30 Apr 2019 10:12:28 +0000

soc: ti: Add MSI domain bus support for Interrupt AggregatorWith the system coprocessor managing the range allocation of theinputs to Interrupt Aggregator, it is difficult to representthe device IRQs from DT.The suggestion is to use MSI in such cases where devices wantsto allocate and group interrupts dynamically.Create a MSI domain bus layer that allocates and frees MSIs fora device.APIs that are implemented:- ti_sci_inta_msi_create_irq_domain() that creates a MSI domain- ti_sci_inta_msi_domain_alloc_irqs() that creates MSIs for the specified device and resource.- ti_sci_inta_msi_domain_free_irqs() frees the irqs attached to the device.- ti_sci_inta_msi_get_virq() for getting the virq attached to a specific event.Signed-off-by: Lokesh Vutla Signed-off-by: Marc Zyngier List of files: /linux-6.15/drivers/soc/ti/Kconfig

5a99ae00 - soc: ti: pm33xx: AM437X: Add rtc_only with ddr in self-refresh support

Wed, 03 Apr 2019 04:57:42 +0000

soc: ti: pm33xx: AM437X: Add rtc_only with ddr in self-refresh supportDuring RTC-only suspend, power is lost to the wkup domain, so we need tosave and restore the state of that domain. We also need to store someinformation within the RTC registers so that u-boot can do the right thingat powerup.The state is entered by getting the RTC to bring the pmic_power_en line lowwhich will instruct the PMIC to disable the appropriate power rails afterputting DDR into self-refresh mode. To bring pmic_power_en low, we need toget an ALARM2 event. Since we are running from SRAM at that point, it meanscalculating what the next second is (via ASM) and programming that into theRTC. This patch also adds support for wake up source detection.Signed-off-by: Keerthy Signed-off-by: Dave Gerlach Signed-off-by: Tony Lindgren List of files: /linux-6.15/drivers/soc/ti/Kconfig

a869b7b3 - soc: ti: Add Support for AM654 SoC config option

Tue, 26 Jun 2018 16:26:14 +0000

soc: ti: Add Support for AM654 SoC config optionAdd option to build AM6 SoC specific componentsReviewed-by: Tony Lindgren Signed-off-by: Benjamin Fair Signed-off-by: Nishanth Menon Signed-off-by: Tony Lindgren List of files: /linux-6.15/drivers/soc/ti/Kconfig

afe761f8 - soc: ti: Add pm33xx driver for basic suspend support

Fri, 23 Feb 2018 15:43:57 +0000

soc: ti: Add pm33xx driver for basic suspend supportAM335x and AM437x support various low power modes as documentedin section 8.1.4.3 of the AM335x Technical Reference Manual andsection 6.4.3 of the AM437x Technical Reference Manual.DeepSleep0 mode offers the lowest power mode with limitedwakeup sources without a system reboot and is mapped asthe suspend state in the kernel. In this state, MPU andPER domains are turned off with the internal RAM held inretention to facilitate the resume process. As part ofthe boot process, the assembly code is copied over to OCMCRAMso it can be executed to turn of the EMIF and put DDR into selfrefresh.Both platforms have a Cortex-M3 (WKUP_M3) which assists the MPUin DeepSleep0 entry and exit. WKUP_M3 takes careof the clockdomain and powerdomain transitions based on theintended low power state. MPU needs to load the appropriateWKUP_M3 binary onto the WKUP_M3 memory space before it canleverage any of the PM features like DeepSleep. This loadingis handled by the remoteproc driver wkup_m3_rproc.Communication with the WKUP_M3 is handled by a wkup_m3_ipcdriver that exposes the specific PM functionality to be usedthe PM code.In the current implementation when the suspend processis initiated, MPU interrupts the WKUP_M3 to let it know aboutthe intent of entering DeepSleep0 and waits for an ACK. Whenthe ACK is received MPU continues with its suspend processto suspend all the drivers and then jumps to assembly inOCMC RAM. The assembly code puts the external RAM in self-refreshmode, gates the MPU clock, and then finally executes the WFIinstruction. Execution of the WFI instruction with MPU clock gatedtriggers another interrupt to the WKUP_M3 which then continueswith the power down sequence wherein the clockdomain andpowerdomain transition takes place. As part of the sleep sequence,WKUP_M3 unmasks the interrupt lines for the wakeup sources. WFIexecution on WKUP_M3 causes the hardware to disable the mainoscillator of the SoC and from here system remains in sleep stateuntil a wake source brings the system into resume path.When a wakeup event occurs, WKUP_M3 starts the power-upsequence by switching on the power domains and finallyenabling the clock to MPU. Since the MPU gets powered downas part of the sleep sequence in the resume path ROM codestarts executing. The ROM code detects a wakeup from sleepand then jumps to the resume location in OCMC which waspopulated in one of the IPC registers as part of the suspendsequence.Code is based on work by Vaibhav Bedia.Signed-off-by: Dave Gerlach Acked-by: Santosh Shilimkar Signed-off-by: Tony Lindgren List of files: /linux-6.15/drivers/soc/ti/Kconfig

52835d59 - soc: ti: Add ti_sci_pm_domains driver

Tue, 04 Apr 2017 15:59:27 +0000

soc: ti: Add ti_sci_pm_domains driverIntroduce a ti_sci_pm_domains driver to act as a generic pm domainprovider to allow each device to attach and associate it's ti-sci-id sothat it can be controlled through the TI SCI protocol.This driver implements a simple genpd where each device node has aphandle to the power domain node and also must provide an index whichrepresents the ID to be passed with TI SCI representing the device usinga single phandle cell. The driver manually parses the phandle to get thecell value. Through this interface the genpd dev_ops start and stophooks will use TI SCI to turn on and off each device as determined bypm_runtime usage.Reviewed-by: Kevin Hilman Acked-by: Santosh Shilimkar Reviewed-by: Ulf Hansson Signed-off-by: Keerthy Signed-off-by: Nishanth Menon Signed-off-by: Dave Gerlach Signed-off-by: Santosh Shilimkar List of files: /linux-6.15/drivers/soc/ti/Kconfig