From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alim Akhtar <alim.akhtar@samsung.com>,
Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Lukas Timmermann <linux@timmermann.space>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
Alexandre Marquet <tb@a-marquet.fr>,
Henrik Grimler <henrik@grimler.se>
Subject: Re: (subset) [PATCH v4 3/3] ARM: samsung: exynos5250: Allow CPU1 to boot
Date: Thu, 26 Feb 2026 22:14:04 +0100 [thread overview]
Message-ID: <177214044450.341643.10542668846868518849.b4-ty@kernel.org> (raw)
In-Reply-To: <20260127-lat3st-staging-v4-3-797469aaaf9d@timmermann.space>
On Tue, 27 Jan 2026 21:40:58 +0100, Lukas Timmermann wrote:
> The firmware trustzone needs a special call to bring up the secondary
> cpu core on the Manta board. This seems to be not needed on other
> exynos5 boards and comes down to the available firmware on
> a particular board.
>
>
Applied, thanks!
[3/3] ARM: samsung: exynos5250: Allow CPU1 to boot
https://git.kernel.org/krzk/linux/c/32d4b991f25eeffac7568ef51367f924394fbdc5
Best regards,
--
Krzysztof Kozlowski <krzk@kernel.org>
next prev parent reply other threads:[~2026-02-26 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 20:40 [PATCH v4 0/3] Add support for exynos5250-manta (Google Nexus 10) Lukas Timmermann
2026-01-27 20:40 ` [PATCH v4 1/3] dt-bindings: ARM: samsung: Add Google Manta (Nexus 10) Lukas Timmermann
2026-01-27 20:40 ` [PATCH v4 2/3] ARM: dts: exynos: " Lukas Timmermann
2026-01-27 20:40 ` [PATCH v4 3/3] ARM: samsung: exynos5250: Allow CPU1 to boot Lukas Timmermann
2026-02-26 21:14 ` Krzysztof Kozlowski [this message]
2026-01-28 10:58 ` [PATCH v4 0/3] Add support for exynos5250-manta (Google Nexus 10) Krzysztof Kozlowski
2026-02-26 21:13 ` (subset) " Krzysztof Kozlowski
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=177214044450.341643.10542668846868518849.b4-ty@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=henrik@grimler.se \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@timmermann.space \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tb@a-marquet.fr \
/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®