From: Sota4Ever <wachiturroxd150@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] Add support for Samsung Galaxy S20 FE (SM-G780F/r8s) [SoC Exynos990]
Date: Sat, 9 Nov 2024 23:04:00 +0000 [thread overview]
Message-ID: <20241109230402.831-1-wachiturroxd150@gmail.com> (raw)
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 :)
Sota4Ever (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
next reply other threads:[~2024-11-09 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 23:04 Sota4Ever [this message]
2024-11-09 23:04 ` [PATCH v1 1/2] dt-bindings: arm: samsung: Add compatible for Samsung Galaxy S20 FE (SM-G780F) Sota4Ever
2024-11-11 20:18 ` Conor Dooley
2024-11-09 23:04 ` [PATCH v1 2/2] arm64: dts: Add initial support for Samsung Galaxy S20 FE (r8s) Sota4Ever
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241109230402.831-1-wachiturroxd150@gmail.com \
--to=wachiturroxd150@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox