[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241114143636.374-1-wachiturroxd150@gmail.com>
Date: Thu, 14 Nov 2024 14:36:34 +0000
From: Sota4Ever <wachiturroxd150@...il.com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
Alim Akhtar <alim.akhtar@...sung.com>,
Rob Herring <robh@...nel.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org,
devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH v3 0/2] Add support for Samsung Galaxy S20 FE (SM-G780F/r8s) [SoC Exynos990]
From: Denzeel Oliva <wachiturroxd150@...il.com>
Hello :),
I'm a newbie and I started getting interested 1 year ago.
Well, that's the beginning,
until I learn more about kernels and the C language,
which is important in that.
Well, bluntly, here it is:
That Samsung Galaxy S20 FE device is part of the Exynos990 SoC family,
I saw that Igor supported that processor,
I took advantage of it.
It has the same functions of:
* CPU
* pintrl
* gpio-keys
* simple-framebuffer
Just enough to reach a shell in an initramfs.
The preferred way to boot the upstream kernel is by using a
shim bootloader, called uniLoader.
Changes: - Simply add dts from S20 FE device
Special thanks to Igor for helping me with that :)
Changes in v2:
- Change author name
Changes in v3:
- Adjusted value <0x08 0x80000000 0x0 0x0c000000> to
<0x8 0x80000000 0x0 0xc0000000>
Honestly I was wrong in the parameter and the other one is
not necessary to put another "0"
Denzeel Oliva (2):
dt-bindings: arm: samsung: Add compatible for Samsung Galaxy S20 FE
(SM-G780F)
arm64: dts: Add initial support for Samsung Galaxy S20 FE (r8s)
.../bindings/arm/samsung/samsung-boards.yaml | 1 +
arch/arm64/boot/dts/exynos/Makefile | 1 +
arch/arm64/boot/dts/exynos/exynos990-r8s.dts | 115 ++++++++++++++++++
3 files changed, 117 insertions(+)
create mode 100644 arch/arm64/boot/dts/exynos/exynos990-r8s.dts
--
2.34.1
Powered by blists - more mailing lists