From: Alex Bee <knaerzche@gmail.com>
To: Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Alex Bee <knaerzche@gmail.com>
Subject: [PATCH v2 0/4] Enable SMP bring-up and cpu frequency-scaling for RK3128
Date: Tue, 29 Aug 2023 23:40:01 +0200 [thread overview]
Message-ID: <20230829214004.314932-2-knaerzche@gmail.com> (raw)
This series aims to enable bring-up of the non-boot cpu-cores by the
Rockchip platsmp driver and enables cpu frequency-scaling by defining
appropriate operating points.
Please see commit messages of the individual patches for details.
These patches have been part of the pretty huge RK3128 bring-up/fix-up
series [0] which I've splitted-up now, as suggested.
[0] https://lore.kernel.org/linux-rockchip/20230829171647.187787-1-knaerzche@gmail.com
Alex Bee (4):
ARM: dts: rockchip: Add SRAM node for RK3128
ARM: dts: rockchip: Add CPU resets for RK3128
ARM: dts: rockchip: Enable SMP bring-up for RK3128
ARM: dts: rockchip: Switch to operating-points-v2 for RK3128's CPU
arch/arm/boot/dts/rockchip/rk3128.dtsi | 61 ++++++++++++++++++++++++--
1 file changed, 57 insertions(+), 4 deletions(-)
base-commit: 2dde18cd1d8fac735875f2e4987f11817cc0bc2c
--
2.42.0
next reply other threads:[~2023-08-29 21:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 21:40 Alex Bee [this message]
2023-08-29 21:40 ` [PATCH v2 1/4] ARM: dts: rockchip: Add SRAM node " Alex Bee
2023-08-29 21:40 ` [PATCH v2 2/4] ARM: dts: rockchip: Add CPU resets " Alex Bee
2023-08-29 21:40 ` [PATCH v2 3/4] ARM: dts: rockchip: Enable SMP bring-up " Alex Bee
2023-08-29 21:40 ` [PATCH v2 4/4] ARM: dts: rockchip: Switch to operating-points-v2 for RK3128's CPU Alex Bee
2023-10-04 21:32 ` [PATCH v2 0/4] Enable SMP bring-up and cpu frequency-scaling for RK3128 Heiko Stuebner
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=20230829214004.314932-2-knaerzche@gmail.com \
--to=knaerzche@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®