From: Dragan Simic <dsimic@manjaro.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: FUKAUMI Naoki <naoki@radxa.com>,
heiko@sntech.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-rockchip@lists.infradead.org,
Jonas Karlman <jonas@kwiboo.se>
Subject: Re: [RFC v2 1/2] dt-bindings: arm: rockchip: add Radxa E52C
Date: Thu, 08 Aug 2024 15:43:04 +0200 [thread overview]
Message-ID: <28dec8ac1cb3f8495fd9ef5e6008a066@manjaro.org> (raw)
In-Reply-To: <291b87b0-4701-4743-aed9-adbef7cf3b77@kernel.org>
Hello Krzysztof,
(I'm adding Jonas to the Cc list.)
On 2024-08-08 12:57, Krzysztof Kozlowski wrote:
> On 08/08/2024 11:04, FUKAUMI Naoki wrote:
>> Add devicetree binding for the Radxa E52C.
>>
>> Radxa E52C is a compact network computer using the Rockchip RK3582
>> chip.
>>
>> Signed-off-by: FUKAUMI Naoki <naoki@radxa.com>
>> ---
>> Changes in v2:
>> - none
>
> Why this is not ready for review? Why this is RFC?
AFAIK, there's still no official downstream kernel code from Rockchip
that we can use to add support for the new Rockchip RK3582 (and RK3583)
SoC variants. These new variants seem to be like the RK3588(s), but
with some IP cores (i.e. CPU and GPU cores) disabled in software, due
to them being marked as defunct in efuses, as part of the manufacturing
and testing processes. Using the efuses, defunct IP cores get disabled
in U-Boot by patching the DT.
Thus, we still need to figure out precisely how to do that in U-Boot
first, before we can move on to adding the new bindings for the new SoC
variants. Jonas is already working on the U-Boot patches.
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2024-08-08 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 9:04 [RFC v2 1/2] dt-bindings: arm: rockchip: add Radxa E52C FUKAUMI Naoki
2024-08-08 9:04 ` [RFC v2 2/2] arm64: dts: " FUKAUMI Naoki
2024-08-08 10:57 ` [RFC v2 1/2] dt-bindings: arm: " Krzysztof Kozlowski
2024-08-08 13:43 ` Dragan Simic [this message]
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=28dec8ac1cb3f8495fd9ef5e6008a066@manjaro.org \
--to=dsimic@manjaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=naoki@radxa.com \
--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