From: kpursoty@proton.me
To: "openwrt-devel@lists.openwrt.org" <openwrt-devel@lists.openwrt.org>
Cc: "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"tsbogend@alpha.franken.de" <tsbogend@alpha.franken.de>,
"cjd@cjdns.fr" <cjd@cjdns.fr>
Subject: Re: [PATCH] mips: econet: add EN751627 SoC Kconfig entry
Date: Thu, 16 Apr 2026 07:20:06 +0000 [thread overview]
Message-ID: <-sv9JxeX2cGKwZjY8mDH4WskIKOXfbsD_7ZcziekWVCIS83Lu7MjK_baP7ycyvzHkWx9B6SQyxiaCJ37G8B-YCi-Vxy_9fdbeaYIMwF1pew=@proton.me> (raw)
In-Reply-To: <E5Pgm6Vp9MRV0KHJ_KOh8hEjTukhx1F2X5nlmbJeG-EW0j44NRslk1EuiB6AQt7zLQykmY_QzPU0haPtiH7Yb3fd7QhMFxWBxxx4_2684RA=@proton.me>
Thanks for your notes. Patch withdrawn.
On Wednesday, 15 April 2026 at 20:48, kpursoty@proton.me <kpursoty@proton.me> wrote:
>
> The EN751627 family (EN7516 DSL, EN7527 xPON) is a big-endian dual-core
> MIPS 1004Kc SoC (2 VPEs per core, NR_CPUS=4) used in DSL/WiFi gateway
> devices such as the ZyXEL EX3301-T0. It shares the MIPS GIC interrupt
> controller with EN7528 but is big-endian.
>
> Key differences from existing SoCs:
> - EN751221: BE, single-core 34Kc, custom INTC
> - EN7528: LE, dual-core 1004Kc, MIPS GIC
> - EN751627: BE, dual-core 2-VPE 1004Kc, MIPS GIC
>
> The SMP plumbing (CM/CPC probe + CPS SMP ops) is shared with EN7528 and
> lives in patch 100 (device_tree_init). This patch adds only the Kconfig
> entry.
>
> Note: on EN751627, mips_cpc_probe() must be called before
> register_cps_smp_ops(). Without it, core 1 never comes online because
> write_gcr_co_reset_release(0) is insufficient on this SoC. This is
> different from EN7528 where CPC probe behaves identically. Both SoCs
> are covered by the shared #if in device_tree_init().
>
> Signed-off-by: Kervin Pursoty <kpursoty@proton.me>
> ---
> arch/mips/econet/Kconfig | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/arch/mips/econet/Kconfig b/arch/mips/econet/Kconfig
> --- a/arch/mips/econet/Kconfig
> +++ b/arch/mips/econet/Kconfig
> @@ -41,3 +41,28 @@ choice
> The EN7528 family with dual-core MIPS 1004Kc.
> Requires MIPS_RAW_APPENDED_DTB=y for boot.
> +
> + config SOC_ECONET_EN751627
> + bool "EN751627 family"
> + select COMMON_CLK
> + select CPU_BIG_ENDIAN
> + select HAVE_PCI
> + select IRQ_MIPS_CPU
> + select MIPS_CM
> + select MIPS_CPC
> + select MIPS_CPS
> + select MIPS_CPU_SCACHE
> + select MIPS_GIC
> + select MIPS_MT_SMP
> + select PCI_DRIVERS_GENERIC
> + select SMP
> + select SMP_UP
> + select SYS_SUPPORTS_HIGHMEM
> + select SYS_SUPPORTS_MIPS_CPS
> + select SYS_SUPPORTS_MULTITHREADING
> + select SYS_SUPPORTS_SMP
> + help
> + The EN751627 family (EN7516 DSL, EN7527 xPON) with big-endian
> + dual-core, 2-VPE-per-core MIPS 1004Kc and MIPS GIC. Used in
> + DSL+WiFi gateways. Requires MIPS_RAW_APPENDED_DTB=y for boot.
> endchoice
>
prev parent reply other threads:[~2026-04-16 7:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 19:48 [PATCH] mips: econet: add EN751627 SoC Kconfig entry kpursoty
2026-04-16 7:20 ` kpursoty [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='-sv9JxeX2cGKwZjY8mDH4WskIKOXfbsD_7ZcziekWVCIS83Lu7MjK_baP7ycyvzHkWx9B6SQyxiaCJ37G8B-YCi-Vxy_9fdbeaYIMwF1pew=@proton.me' \
--to=kpursoty@proton.me \
--cc=cjd@cjdns.fr \
--cc=linux-mips@vger.kernel.org \
--cc=openwrt-devel@lists.openwrt.org \
--cc=tsbogend@alpha.franken.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).