[PATCH v3 10/23] platform: generic: mips: add P8700 based "eyeq7h" and "boston"

[Conor Dooley]

On Mon, Feb 23, 2026 at 04:54:49PM +0200, Vladimir Kondratiev wrote:
> Refactor MIPS P8700 support, convert P8700 into a "CPU" and add
> 2 platforms using this CPU:
> - "boston" - FPGA platform developed by MIPS
> - "eyeq7h" - automotive platform by Mobileye
> 
> Signed-off-by: Vladimir Kondratiev <vladimir.kondratiev at mobileye.com>

> +config CPU_MIPS_P8700
> +	bool
> +	default n
> +
> +config PLATFORM_MIPS_P8700_EYEQ7H
> +	select CPU_MIPS_P8700
> +	bool "EyeQ7H"
> +
> +config PLATFORM_MIPS_P8700_BOSTON
> +	select CPU_MIPS_P8700
> +	bool "Boston"

> +static const struct fdt_match boston_match[] = {
> +	{ .compatible = "mips,p8700", .data = &boston_cm_info },

I'm not really too familiar with OpenSBI internals, but this looks wrong
to me. Why is a soc being matched on a cpu compatible? Shouldn't this be
something like "mips,boston"?

If this is a cpu, then I'd be expecting mips,m8700 to appear in cpu
nodes, and not in the board compatible entry at all.

> +static const struct fdt_match eyeq7h_match[] = {
> +	{ .compatible = "mobileye,eyeq7h", .data = &eyeq7h_cm_info },
> +	{ },
> +};
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/opensbi/attachments/20260225/43bf4853/attachment-0001.sig>