[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dpby4tvamvsk6437kngv4d6diq6pqh5fquptwy7p5325e6hb3j@ot6eaurn4bun>
Date: Fri, 6 Dec 2024 14:07:24 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Umer Uddin <umer.uddin@...tallysanemainliners.org>
Cc: Alim Akhtar <alim.akhtar@...sung.com>, Rob Herring <robh@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
igor.belwon@...tallysanemainliners.org
Subject: Re: [PATCH v4 0/4] Add minimal Samsung Galaxy S20 Series board,
SM-G981B and SM-G980F support
On Tue, Dec 03, 2024 at 08:03:22AM +0000, Umer Uddin wrote:
> Hi folks,
>
> This series adds initial support for the Samsung Galaxy S20 Series and also
> initial board support for the Samsung Galaxy S20 5G (SM-G981B)
> codenamed x1s.
>
> The S20 Series feature a lot of similarities in their configuration
> and internally Samsung named the common devicetrees in their
> downstream kernel 'hubble', please note hubble excludes the
> S20 FE series and Note20 series. To accomodate this, I've
> now named the device tree common's matching the codenames
> (x1s-common).
> The device trees have been tested with dtbs_check W=1
> and results in no warnings.
>
> This initial bringup consists of:
> * pinctrl
> * gpio-keys
> * simple-framebuffer
>
> This is enough to reach a shell in an initramfs. More platform support
> will be added in the future.
>
> Just like SM-N981B, the preferred way to boot the upstream kernel is
> by using a shim bootloader, called uniLoader [1], which works around
> some issues with the stock, non-replacable Samsung S-LK bootloader.
> For example, the stock bootloader leaves the decon trigger control
> unset, which causes the framebuffer not to refresh.
>
> Device functionality depends on the patch series from Igor Belwon:
> "Add minimal Exynos990 SoC and SM-N981B support"
>
> [1] https://github.com/ivoszbg/uniLoader
>
> Changes in v4:
> - Rebase from krzk's kernel tree to accomodate
> for the merge of r8s
> - Rename exynos990-hubble-common.dtsi
> to exynos990-x1s-common.dtsi
What else happened here?
b4 diff '20241203080327.4751-2-umer.uddin@...tallysanemainliners.org'
Checking for older revisions
Grabbing search results from lore.kernel.org
Added from v3: 9 patches
---
Analyzing 29 messages in the thread
WARNING: duplicate messages found at index 3
Subject 1: arm64: dts: exynos: Add initial support for Samsung Galaxy S20 5G (x1s)
Subject 2: arm64: dts: exynos: Add initial support for Samsung Galaxy S20 5G (x1s)
2 is not a reply... assume additional patch
WARNING: duplicate messages found at index 4
Subject 1: arm64: dts: exynos: Add initial support for Samsung Galaxy S20 (x1slte)
Subject 2: arm64: dts: exynos: Add initial support for Samsung Galaxy S20 5G (x1s)
2 is not a reply... assume additional patch
WARNING: duplicate messages found at index 1
Subject 1: dt-bindings: arm: samsung: samsung-boards: Add bindings for SM-G981B and SM-G980F board
Subject 2: dt-bindings: arm: samsung: samsung-boards: Add bindings for SM-G981B and SM-G980F board
2 is not a reply... assume additional patch
WARNING: duplicate messages found at index 2
Subject 1: arm64: dts: exynos: Add initial support for Samsung Galaxy S20 Series boards (hubble)
Subject 2: dt-bindings: arm: samsung: samsung-boards: Add bindings for SM-G981B and SM-G980F board
2 is not a reply... assume additional patch
Preparing fake-am for v3: dt-bindings: arm: samsung: samsung-boards: Add bindings for SM-G981B and SM-G980F board
ERROR: v3 series incomplete; unable to create a fake-am range
Working with these series is a pain.
Best regards,
Krzysztof
Powered by blists - more mailing lists