From: Alex Bee <knaerzche@gmail.com>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: devicetree@vger.kernel.org, heiko@sntech.de, jonas@kwiboo.se,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
ziyao@disroot.org
Subject: Re: [PATCH v3 0/6] arm64: dts: rockchip: Add ROCK 2A/2F, Sige1 and NanoPi Zero2
Date: Sat, 19 Jul 2025 18:07:45 +0200 [thread overview]
Message-ID: <24ef5e60-dcea-4102-b87f-8a5572c7497f@gmail.com> (raw)
In-Reply-To: <20250719143008.54288-1-amadeus@jmu.edu.cn>
> Hi,
>
>> The issue I was seeing is that there actually *is* a variant called
>> 'RK3528' which at least according to the latest datasheets slightly differs
>> from 'RK3528A'. We are doing development based on 'RK3528A' and calling it
>> 'rockchip,rk3528' which might make it hard to add the non-A-variant in
>> future (unless we call it 'rockchip,the-actual-rk3528').
> I think this can be ignored, because rockchip only provides RK3528A chip.
> RK3528A should be a revised version of RK3528, which solves some bugs,
> so we have never seen the silk screen printed with RK3528.
Thanks for sharing that inside.
I wonder why there's an v1.4 of "Rockchip RK3528 Datasheet" dated
2024-05-12 which differs from v1.4 "Rockchip RK3528A Datasheet" dated
2025-05-12. Anyway: If everybody is happy as-is I guess it's fine.
> Thanks,
> Chukun
>
> --
> 2.25.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Alex Bee <knaerzche@gmail.com>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: devicetree@vger.kernel.org, heiko@sntech.de, jonas@kwiboo.se,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
ziyao@disroot.org
Subject: Re: [PATCH v3 0/6] arm64: dts: rockchip: Add ROCK 2A/2F, Sige1 and NanoPi Zero2
Date: Sat, 19 Jul 2025 18:07:45 +0200 [thread overview]
Message-ID: <24ef5e60-dcea-4102-b87f-8a5572c7497f@gmail.com> (raw)
In-Reply-To: <20250719143008.54288-1-amadeus@jmu.edu.cn>
> Hi,
>
>> The issue I was seeing is that there actually *is* a variant called
>> 'RK3528' which at least according to the latest datasheets slightly differs
>> from 'RK3528A'. We are doing development based on 'RK3528A' and calling it
>> 'rockchip,rk3528' which might make it hard to add the non-A-variant in
>> future (unless we call it 'rockchip,the-actual-rk3528').
> I think this can be ignored, because rockchip only provides RK3528A chip.
> RK3528A should be a revised version of RK3528, which solves some bugs,
> so we have never seen the silk screen printed with RK3528.
Thanks for sharing that inside.
I wonder why there's an v1.4 of "Rockchip RK3528 Datasheet" dated
2024-05-12 which differs from v1.4 "Rockchip RK3528A Datasheet" dated
2025-05-12. Anyway: If everybody is happy as-is I guess it's fine.
> Thanks,
> Chukun
>
> --
> 2.25.1
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-07-19 16:10 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-12 17:37 [PATCH v3 0/6] arm64: dts: rockchip: Add ROCK 2A/2F, Sige1 and NanoPi Zero2 Jonas Karlman
2025-07-12 17:37 ` Jonas Karlman
2025-07-12 17:37 ` [PATCH v3 1/6] dt-bindings: arm: rockchip: Add Radxa ROCK 2A/2F Jonas Karlman
2025-07-12 17:37 ` Jonas Karlman
2025-07-12 17:37 ` [PATCH v3 2/6] arm64: dts: " Jonas Karlman
2025-07-12 17:37 ` Jonas Karlman
2025-07-13 13:39 ` Yao Zi
2025-07-13 13:39 ` Yao Zi
2025-07-14 9:44 ` Nicolas Frattaroli
2025-07-14 9:44 ` Nicolas Frattaroli
2025-07-14 10:49 ` Jonas Karlman
2025-07-14 10:49 ` Jonas Karlman
2025-07-14 11:15 ` Nicolas Frattaroli
2025-07-14 11:15 ` Nicolas Frattaroli
2025-07-12 17:37 ` [PATCH v3 3/6] dt-bindings: arm: rockchip: Add ArmSoM Sige1 Jonas Karlman
2025-07-12 17:37 ` Jonas Karlman
2025-07-12 17:37 ` [PATCH v3 4/6] arm64: dts: " Jonas Karlman
2025-07-12 17:37 ` Jonas Karlman
2025-07-15 14:01 ` Chukun Pan
2025-07-15 14:01 ` Chukun Pan
2025-07-15 14:21 ` Jonas Karlman
2025-07-15 14:21 ` Jonas Karlman
2025-07-16 7:00 ` Chukun Pan
2025-07-16 7:00 ` Chukun Pan
2025-07-12 17:37 ` [PATCH v3 5/6] dt-bindings: arm: rockchip: Add FriendlyElec NanoPi Zero2 Jonas Karlman
2025-07-12 17:37 ` Jonas Karlman
2025-07-12 17:37 ` [PATCH v3 6/6] arm64: dts: " Jonas Karlman
2025-07-12 17:37 ` Jonas Karlman
2025-07-13 19:13 ` [PATCH v3 0/6] arm64: dts: rockchip: Add ROCK 2A/2F, Sige1 and " Alex Bee
2025-07-13 19:13 ` Alex Bee
2025-07-13 20:13 ` Jonas Karlman
2025-07-13 20:13 ` Jonas Karlman
2025-07-13 20:56 ` Alex Bee
2025-07-13 20:56 ` Alex Bee
2025-07-14 0:04 ` Jonas Karlman
2025-07-14 0:04 ` Jonas Karlman
2025-07-14 5:53 ` Alex Bee
2025-07-14 5:53 ` Alex Bee
2025-07-15 18:56 ` Heiko Stübner
2025-07-15 18:56 ` Heiko Stübner
2025-07-19 9:58 ` Alex Bee
2025-07-19 9:58 ` Alex Bee
2025-07-19 14:30 ` Chukun Pan
2025-07-19 14:30 ` Chukun Pan
2025-07-19 16:07 ` Alex Bee [this message]
2025-07-19 16:07 ` Alex Bee
2025-07-20 9:45 ` Alex Bee
2025-07-20 9:45 ` Alex Bee
2025-07-20 13:40 ` Chukun Pan
2025-07-20 13:40 ` Chukun Pan
2025-07-20 15:51 ` Alex Bee
2025-07-20 15:51 ` Alex Bee
2025-07-21 14:00 ` Chukun Pan
2025-07-21 14:00 ` Chukun Pan
2025-07-21 18:07 ` Alex Bee
2025-07-21 18:07 ` Alex Bee
2025-07-23 13:40 ` Chukun Pan
2025-07-23 13:40 ` Chukun Pan
2025-07-26 11:07 ` Alex Bee
2025-07-26 11:07 ` Alex Bee
2025-07-14 1:00 ` Yao Zi
2025-07-14 1:00 ` Yao Zi
2025-07-14 8:52 ` Nicolas Frattaroli
2025-07-14 8:52 ` Nicolas Frattaroli
2025-07-14 15:24 ` Rob Herring (Arm)
2025-07-14 15:24 ` 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=24ef5e60-dcea-4102-b87f-8a5572c7497f@gmail.com \
--to=knaerzche@gmail.com \
--cc=amadeus@jmu.edu.cn \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=ziyao@disroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.