From: Krzysztof Kozlowski <krzk@kernel.org>
To: Umer Uddin <umer.uddin@mentallysanemainliners.org>
Cc: alim.akhtar@samsung.com, conor+dt@kernel.org,
devicetree@vger.kernel.org,
igor.belwon@mentallysanemainliners.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
robh@kernel.org
Subject: Re: [PATCH v2 0/4] Add minimal Samsung Galaxy S20 Series board, SM-G981B and SM-G980F support
Date: Mon, 21 Oct 2024 08:41:46 +0200 [thread overview]
Message-ID: <3d313537-2bad-4a18-9fd3-b641351a2361@kernel.org> (raw)
In-Reply-To: <20241018162003.21648-1-umer.uddin@mentallysanemainliners.org>
On 18/10/2024 18:20, Umer Uddin wrote:
> On Fri, 18 Oct 2024 09:14:01 +0200, Krzysztof Kozlowski wrote:
>
>> What about remaining 4 GB on X1S?
>
> On x1s, the remaining memory is mapped in the device specific dtsi.
Then it proves that this is not correctly placed - not a shared part of
boards. Remove it from DTSI.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-21 6:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 16:43 Umer Uddin
2024-10-17 16:43 ` [PATCH v2 1/4] dt-bindings: arm: samsung: samsung-boards: Add bindings for SM-G981B and SM-G980F board Umer Uddin
2024-10-18 6:29 ` Krzysztof Kozlowski
2024-10-17 16:43 ` [PATCH v2 2/4] arm64: dts: exynos: Add initial support for Samsung Galaxy S20 Series boards (hubble) Umer Uddin
2024-10-18 6:32 ` Krzysztof Kozlowski
2024-10-17 16:43 ` [PATCH v2 3/4] arm64: dts: exynos: Add initial support for Samsung Galaxy S20 5G (x1s) Umer Uddin
2024-10-17 16:43 ` [PATCH v2 4/4] arm64: dts: exynos: Add initial support for Samsung Galaxy S20 (x1slte) Umer Uddin
2024-10-18 6:30 ` Krzysztof Kozlowski
2024-10-18 6:48 ` Re: [PATCH v2 0/4] Add minimal Samsung Galaxy S20 Series board, SM-G981B and SM-G980F support Umer Uddin
2024-10-18 7:14 ` Krzysztof Kozlowski
2024-10-18 16:20 ` Umer Uddin
2024-10-21 6:41 ` Krzysztof Kozlowski [this message]
2024-10-18 12:52 ` Rob Herring (Arm)
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=3d313537-2bad-4a18-9fd3-b641351a2361@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=igor.belwon@mentallysanemainliners.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 \
--cc=umer.uddin@mentallysanemainliners.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
all inboxes | Powered by JetHome®