mirror of
https://github.com/torvalds/linux.git
synced 2026-03-08 03:04:51 +01:00
732af51910
GS101 is different (but also e850 and autov9 I assume) from the SoCs that are currently handled by the exynos-chipid driver because the chip ID info is part of the OTP registers. GS101 OTP has a clock, an interrupt line, a register space (that contains product and chip ID, TMU data, ASV, etc) and a 32Kbit memory space that can be read/program/locked with specific commands. On GS101 the "ChipID block" is just an abstraction, it's not a physical device. When the power-on sequence progresses, the OTP chipid values are loaded to the OTP registers. Add the GS101 chip ID support. The support is intentionally added in the exynos-chipid driver, and not in a dedicated Exynos OTP driver, because we estimate that there will not be any OTP consumers in the kernel other than the chip ID/SoC interface. The downstream GS101 drivers confirm this supposition. Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org> Reviewed-by: André Draszik <andre.draszik@linaro.org> Link: https://patch.msgid.link/20251222-gs101-chipid-v4-4-aa8e20ce7bb3@linaro.org Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org> |
||
|---|---|---|
| .. | ||
| exynos-asv.c | ||
| exynos-asv.h | ||
| exynos-chipid.c | ||
| exynos-pmu.c | ||
| exynos-pmu.h | ||
| exynos-regulator-coupler.c | ||
| exynos-usi.c | ||
| exynos4-pmu.c | ||
| exynos3250-pmu.c | ||
| exynos5250-pmu.c | ||
| exynos5420-pmu.c | ||
| exynos5422-asv.c | ||
| exynos5422-asv.h | ||
| gs101-pmu.c | ||
| Kconfig | ||
| Makefile | ||
| s3c-pm-check.c | ||