From: sashiko-bot@kernel.org
To: "Rui Cao" <i@udp0.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH v2 5/5] arm64: dts: mediatek: Add MT6833 and the Xiaomi Redmi Note 13 5G
Date: Tue, 17 Nov 2026 09:18:58 +0000 [thread overview]
Message-ID: <sashiko-outbox-218470@kernel.org> (raw)
In-Reply-To: <20261117-mt6833-base-v2-5-058a0685c40c@udp0.com>
> From: Rui Cao <i@udp0.com>
>
> Add a device tree for MediaTek's MT6833 (Dimensity 700): its eight
> cores, six Cortex-A55 and two Cortex-A76 in one DynamIQ cluster, with
> their caches and PMUs, PSCI, the architected timer, the GICv3, the
> watchdog and the first UART.
>
> Add the Xiaomi Redmi Note 13 5G (gold) on it, with the framebuffer the
> bootloader leaves the panel scanning out and a ramoops region. The
> memory size and the regions reserved for the firmware the bootloader
> starts depend on the RAM variant, so they are left to the bootloader:
> the memory node has no size, and reserved-memory holds only the regions
> the kernel uses itself.
>
> The cache sizes are the ones the cores report in CCSIDR_EL1. The
> bootloader programs CNTFRQ_EL0 (13 MHz), so the timer has no
> clock-frequency.
>
> Signed-off-by: Rui Cao <i@udp0.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261117-mt6833-base-v2-0-058a0685c40c@udp0.com?part=5
prev parent reply other threads:[~2026-11-17 9:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 9:11 [PATCH v2 0/5] arm64: dts: mediatek: Add MT6833 and the Xiaomi Redmi Note 13 5G Rui Cao via B4 Relay
2026-11-17 9:11 ` Rui Cao
2026-11-17 9:11 ` [PATCH v2 1/5] dt-bindings: arm: " Rui Cao via B4 Relay
2026-11-17 9:11 ` Rui Cao
2026-11-17 9:13 ` sashiko-bot
2026-11-17 9:11 ` [PATCH v2 2/5] dt-bindings: watchdog: mediatek,mtk-wdt: Add MT6833 Rui Cao via B4 Relay
2026-11-17 9:11 ` Rui Cao
2026-11-17 9:16 ` sashiko-bot
2026-11-17 11:15 ` AngeloGioacchino Del Regno
2026-11-17 9:11 ` [PATCH v2 3/5] watchdog: mediatek: " Rui Cao via B4 Relay
2026-11-17 9:11 ` Rui Cao
2026-11-17 9:15 ` sashiko-bot
2026-11-17 11:22 ` AngeloGioacchino Del Regno
2026-11-17 9:11 ` [PATCH v2 4/5] dt-bindings: serial: mediatek,uart: " Rui Cao via B4 Relay
2026-11-17 9:11 ` Rui Cao
2026-11-17 9:14 ` sashiko-bot
2026-11-17 9:11 ` [PATCH v2 5/5] arm64: dts: mediatek: Add MT6833 and the Xiaomi Redmi Note 13 5G Rui Cao via B4 Relay
2026-11-17 9:11 ` Rui Cao
2026-11-17 9:18 ` sashiko-bot [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=sashiko-outbox-218470@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=i@udp0.com \
--cc=linux-serial@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.