Changes in Makefile

4419644b - soc: samsung: Move power-domain driver to the genpd dir

Wed, 05 Jul 2023 16:08:50 +0000

soc: samsung: Move power-domain driver to the genpd dirTo simplify with maintenance let's move the samsung power-domain driver tothe new genpd directory. Going forward, patches are intended to be managedthrough a separate git tree, according to MAINTAINERS.Cc: Krzysztof Kozlowski Cc: Alim Akhtar Cc: Reviewed-by: Krzysztof Kozlowski Acked-by: Marek Szyprowski Signed-off-by: Ulf Hansson List of files: /linux-6.15/drivers/soc/samsung/Makefile

2e3ee090 - soc: s3c: remove pm-debug hack

Fri, 30 Sep 2022 14:19:56 +0000

soc: s3c: remove pm-debug hackCONFIG_SAMSUNG_PM_DEBUG was only used on s3c24xx because of theDEBUG_S3C24XX_UART dependency. Since s3c24xx is now gone, and nobodyever noticed this option being missing from s3c64xx, it can be safelyremoved as well.Reviewed-by: Krzysztof Kozlowski Signed-off-by: Arnd Bergmann List of files: /linux-6.15/drivers/soc/samsung/Makefile

b603377e - soc: samsung: Add USI driver

Sat, 04 Dec 2021 19:57:54 +0000

soc: samsung: Add USI driverUSIv2 IP-core is found on modern ARM64 Exynos SoCs (like Exynos850) andprovides selectable serial protocol (one of: UART, SPI, I2C). USIv2registers usually reside in the same register map as a particularunderlying protocol it implements, but have some particular offset. E.g.on Exynos850 the USI_UART has 0x13820000 base address, where UARTregisters have 0x00..0x40 offsets, and USI registers have 0xc0..0xdcoffsets. Desired protocol can be chosen via SW_CONF register from SystemRegister block of the same domain as USI.Before starting to use a particular protocol, USIv2 must be configuredproperly: 1. Select protocol to be used via System Register 2. Clear "reset" flag in USI_CON 3. Configure HWACG behavior (e.g. for UART Rx the HWACG must be disabled, so that the IP clock is not gated automatically); this is done using USI_OPTION register 4. Keep both USI clocks (PCLK and IPCLK) running during USI registers modificationThis driver implements the above behavior. Of course, USIv2 drivershould be probed before UART/I2C/SPI drivers. It can be achieved byembedding UART/I2C/SPI nodes inside of the USI node (in Device Tree);driver then walks underlying nodes and instantiates those. Driver alsohandles USI configuration on PM resume, as register contents can be lostduring CPU suspend.This driver is designed with different USI versions in mind. So itshould be relatively easy to add new USI revisions to it later.Signed-off-by: Sam Protsenko Link: https://lore.kernel.org/r/20211204195757.8600-3-semen.protsenko@linaro.orgTested-by: Chanho Park Signed-off-by: Krzysztof Kozlowski List of files: /linux-6.15/drivers/soc/samsung/Makefile

1e3e559f - soc: samsung: exynos-chipid: convert to a module

Sun, 19 Sep 2021 09:31:13 +0000

soc: samsung: exynos-chipid: convert to a moduleExynos ChipID and ASV (Adaptive Supply Voltage) driver is not essentialto system boot and it can successfully be built and loaded as module.This makes core kernel image smaller and reduces the memory footprintwhen multi-platform kernel is booted on non-Exynos board. Usually it isalso distro-friendly.Add multiple authors of the driver since its conversion frommach-exynos, ordered alphabetically by first name.Signed-off-by: Krzysztof Kozlowski Reviewed-by: Sylwester Nawrocki Tested-by: Sylwester Nawrocki Reviewed-by: Alim Akhtar Tested-by: Alim Akhtar Link: https://lore.kernel.org/r/20210919093114.35987-3-krzysztof.kozlowski@canonical.com List of files: /linux-6.15/drivers/soc/samsung/Makefile

352bfbb3 - soc: samsung: exynos-chipid: convert to driver and merge exynos-asv

Mon, 07 Dec 2020 18:54:57 +0000

soc: samsung: exynos-chipid: convert to driver and merge exynos-asvThe Exynos Chip ID driver on Exynos SoCs has so far only informationalpurpose - to expose the SoC device in sysfs. No other drivers depend onit so there is really no benefit of initializing it early.The code would be the most flexible if converted to a regular driver.However there is already another driver - Exynos ASV (Adaptive SupplyVoltage) - which binds to the device node of Chip ID.The solution is to convert the Exynos Chip ID to a built in driver andmerge the Exynos ASV into it.This has several benefits:1. Although the Exynos ASV driver binds to a device node present in all Exynos DTS (generic compatible), it fails to probe except on the supported ones (only Exynos5422). This means that the regular boot process has a planned/normal device probe failure. Merging the ASV into Chip ID will remove this probe failure because the final driver will always bind, just with disabled ASV features.2. Allows to use dev_info() as the SoC bus is present (since core_initcall).3. Could speed things up because of execution of Chip ID code in a SMP environment (after bringing up secondary CPUs, unlike early_initcall), This reduces the amount of work to be done early, when the kernel has to bring up critical devices.5. Makes the Chip ID code defer-probe friendly,Signed-off-by: Krzysztof Kozlowski Link: https://lore.kernel.org/r/20201207190517.262051-5-krzk@kernel.orgReviewed-by: Pankaj Dubey List of files: /linux-6.15/drivers/soc/samsung/Makefile

17132da7 - ARM: samsung: move pm check code to drivers/soc

Thu, 06 Aug 2020 18:20:33 +0000

ARM: samsung: move pm check code to drivers/socThis is the only part of plat-samsung that is reallyshared between the s3c and s5p ports. Moving it todrivers/soc/ lets us make them completely independent.Signed-off-by: Arnd Bergmann Link: https://lore.kernel.org/r/20200806182059.2431-16-krzk@kernel.orgSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/drivers/soc/samsung/Makefile

00067ca5 - soc: samsung: exynos-regulator-coupler: Add simple voltage coupler for Exynos5800

Tue, 21 Jul 2020 18:09:00 +0000

soc: samsung: exynos-regulator-coupler: Add simple voltage coupler for Exynos5800Add a simple custom voltage regulator coupler for Exynos5800 SoCs, whichrequire coupling between "vdd_arm" and "vdd_int" regulators. This couplerensures that the voltage values don't go below the bootloader-selectedoperation point during the boot process until the clients set theirconstraints. It is achieved by assuming minimal voltage value equal tothe current value if no constraints are set. This also ensures propervoltage balancing if any of the client driver is missing.The balancing code comes from the regulator/core.c with the additionallogic for handling regulators without client constraints applied added.Link: https://lore.kernel.org/r/20200721180900.13844-5-krzk@kernel.orgSigned-off-by: Marek Szyprowski Reviewed-by: Dmitry Osipenko Signed-off-by: Krzysztof Kozlowski Signed-off-by: Arnd Bergmann List of files: /linux-6.15/drivers/soc/samsung/Makefile

5ea42859 - soc: samsung: Add Exynos Adaptive Supply Voltage driver

Mon, 28 Oct 2019 15:15:33 +0000

soc: samsung: Add Exynos Adaptive Supply Voltage driverThe Adaptive Supply Voltage (ASV) driver adjusts CPU cluster operatingpoints depending on exact revision of an SoC retrieved from the CHIPIDblock or the OTP memory. This allows for some power saving as for someCPU clock frequencies we can lower CPU cluster's supply voltage comparingto safe values common to all the SoC revisions.This patch adds support for Exynos5422/5800 SoC, it is partially basedon code from https://github.com/hardkernel/linux repository,branch odroidxu4-4.14.y, files: arch/arm/mach-exynos/exynos5422-asv.[ch].Tested on Odroid XU3, XU4, XU3 Lite.Signed-off-by: Sylwester Nawrocki Signed-off-by: Krzysztof Kozlowski List of files: /linux-6.15/drivers/soc/samsung/Makefile

3253b7b7 - soc: samsung: Add exynos chipid driver support

Tue, 13 Aug 2019 15:08:19 +0000

soc: samsung: Add exynos chipid driver supportExynos SoCs have Chipid, for identification of product IDs and SoCrevisions. This patch intends to provide initialization code for allthese functionalities, at the same time it provides some sysfs entriesfor accessing these information to user-space.This driver uses existing binding for exynos-chipid.Changes by Bartlomiej:- fixed return values on errors- removed bogus kfree_const()- added missing Exynos4210 EVT0 id- converted code to use EXYNOS_MASK define- fixed np use after of_node_put()- fixed too early use of dev_info()- made driver fail for unknown SoC-s- added SPDX tag- updated CopyrightsSigned-off-by: Pankaj Dubey [m.szyprowski: for suggestion and code snippet of product_id_to_soc_id]Signed-off-by: Marek Szyprowski Signed-off-by: Bartlomiej Zolnierkiewicz [s.nawrocki: updated copyright date, removed uneeded headers inclusion]Signed-off-by: Sylwester Nawrocki Signed-off-by: Krzysztof Kozlowski List of files: /linux-6.15/drivers/soc/samsung/Makefile

06512c53 - soc: samsung: Add SPDX license identifiers

Mon, 25 Dec 2017 20:17:59 +0000

soc: samsung: Add SPDX license identifiersReplace GPL license statements with SPDX GPL-2.0 license identifiers.Signed-off-by: Krzysztof Kozlowski List of files: /linux-6.15/drivers/soc/samsung/Makefile

a0ebf662 - soc: samsung: Do not build ARMv7 PMU drivers on ARMv8

Tue, 14 Mar 2017 17:10:27 +0000

soc: samsung: Do not build ARMv7 PMU drivers on ARMv8The Exynos Power Management Unit (PMU) drivers contain quite largestatic arrays of register values necessary for given Exynos SoC to enterlow power mode. All this data is useless for ARMv8 SoC likeExynos5433, because the image will not be shared between ARMv7 andARMv8.Add additional Kconfig symbol for selecting the SoC-specific driveraddons thus skipping the useless data in the final image (this issimilar approach to chosen for Exynos clock controller drivers): - exynos-pmu driver will be compiled on both architectures ARMv7 and ARMv8, - additional driver_data for ARMv7 SoCs will not be built on ARMv8 and a macro will return NULL for them in of_device_id - this should be safe as these compatibles cannot match on ARMv7 and driver anyway handles NULL driver_data, - on ARMv8 compile only exynos-pmu driver which exposes the syscon-regmap for PMU address space.Signed-off-by: Krzysztof Kozlowski Reviewed-by: Bartlomiej Zolnierkiewicz Reviewed-by: Alim Akhtar List of files: /linux-6.15/drivers/soc/samsung/Makefile

9479f7cc - soc: samsung: pm_domains: Enable COMPILE_TEST for build coverage

Tue, 10 May 2016 14:31:26 +0000

soc: samsung: pm_domains: Enable COMPILE_TEST for build coverageIntroduce a platform selectable symbol EXYNOS_PM_DOMAINS which can bealso toggled on by COMPILE_TEST for some build coverage.Signed-off-by: Krzysztof Kozlowski List of files: /linux-6.15/drivers/soc/samsung/Makefile

e465007a - ARM: EXYNOS: Move pm_domains driver to drivers/soc/samsung

Tue, 10 May 2016 13:52:20 +0000

ARM: EXYNOS: Move pm_domains driver to drivers/soc/samsungExynos PM domains driver does not have mach-specific dependencies so itcan be safely moved out of arm/mach-exynos to drivers/soc. This infuture will allow re-using it on ARM64 boards.Signed-off-by: Krzysztof Kozlowski Reviewed-by: Javier Martinez Canillas List of files: /linux-6.15/drivers/soc/samsung/Makefile

bfce552d - drivers: soc: Add support for Exynos PMU driver

Fri, 18 Dec 2015 03:32:16 +0000

drivers: soc: Add support for Exynos PMU driverThis patch moves Exynos PMU driver implementation from "arm/mach-exynos"to "drivers/soc/samsung". This driver is mainly used for setting miscbits of register from PMU IP of Exynos SoC which will be required toconfigure before Suspend/Resume. Currently all these settings are donein "arch/arm/mach-exynos/pmu.c" but moving ahead for ARM64 based SoCsupport, there is a need of this PMU driver in driver/* folder.This driver uses existing DT binding information and there shouldbe no functionality change in the supported platforms.Signed-off-by: Amit Daniel Kachhap [tested on Peach-Pi (Exynos5880)]Signed-off-by: Pankaj Dubey Reviewed-by: Krzysztof Kozlowski [for testing on Trats2 (Exynos4412) and Odroid XU3 (Exynos5422)]Tested-by: Krzysztof Kozlowski [k.kozlowski: Rebased, add necessary infrastructure for building andselecting drivers/soc because original patchset was on top of movementSROMc to drivers/soc]Signed-off-by: Krzysztof Kozlowski List of files: /linux-6.15/drivers/soc/samsung/Makefile