From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Théo Lebrun" <theo.lebrun@bootlin.com>
Cc: Gregory CLEMENT <gregory.clement@bootlin.com>,
Paul Burton <paulburton@kernel.org>,
linux-mips@vger.kernel.org, Jiaxun Yang <jiaxun.yang@flygoat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Vladimir Kondratiev <vladimir.kondratiev@mobileye.com>,
Tawfik Bayouk <tawfik.bayouk@mobileye.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v8 00/14] Add support for the Mobileye EyeQ5 SoC
Date: Fri, 1 Mar 2024 10:39:47 +0100 [thread overview]
Message-ID: <ZeGiYyiQQ7pwpECE@alpha.franken.de> (raw)
In-Reply-To: <CZGOPF51JA1R.2YN65K6WUH9N4@bootlin.com>
On Wed, Feb 28, 2024 at 12:44:09PM +0100, Théo Lebrun wrote:
> Hello Thomas,
>
> On Tue Feb 20, 2024 at 2:44 PM CET, Thomas Bogendoerfer wrote:
> > On Fri, Feb 16, 2024 at 06:42:09PM +0100, Gregory CLEMENT wrote:
> > > Hello,
> > >
> > > The EyeQ5 SoC from Mobileye is based on the MIPS I6500 architecture
> > > and features multiple controllers such as the classic UART, I2C, SPI,
> > > as well as CAN-FD, PCIe, Octal/Quad SPI Flash interface, Gigabit
> > > Ethernet, MIPI CSI-2, and eMMC 5.1. It also includes a Hardware
> > > Security Module, Functional Safety Hardware, and MJPEG encoder.
>
> [...]
>
> > series applied to mips-next.
> >
> > I've fixed generic|ingenic|realtek builds by adding select MACH_GENERIC_CORE
> > in arch/mips/Kconfig.
>
> Would it be possible to provide an immutable branch containing the two
> series? I've got quite a few series that depend on them as they target
> EyeQ5 devicetrees and defconfig.
that's IMHO too late, as I've merged it already to mips-next. mips-linux
itself is immutable, but contains other mips related stuff.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2024-03-01 10:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 17:42 [PATCH v8 00/14] Add support for the Mobileye EyeQ5 SoC Gregory CLEMENT
2024-02-16 17:42 ` [PATCH v8 01/14] MIPS: spaces: Define a couple of handy macros Gregory CLEMENT
2024-02-16 17:42 ` [PATCH v8 02/14] MIPS: Fix set_uncached_handler for ebase in XKPHYS Gregory CLEMENT
2024-02-16 17:42 ` [PATCH v8 03/14] MIPS: Allows relocation exception vectors everywhere Gregory CLEMENT
2024-02-16 17:42 ` [PATCH v8 04/14] MIPS: traps: Give more explanations if ebase doesn't belong to KSEG0 Gregory CLEMENT
2024-02-16 17:42 ` [PATCH v8 05/14] MIPS: cps-vec: Use macros for 64bits access Gregory CLEMENT
2024-02-16 17:42 ` [PATCH v8 06/14] dt-bindings: Add vendor prefix for Mobileye Vision Technologies Ltd Gregory CLEMENT
2024-02-16 17:42 ` [PATCH v8 07/14] dt-bindings: mips: cpus: Sort the entries Gregory CLEMENT
2024-02-16 17:42 ` [PATCH v8 08/14] dt-bindings: mips: cpu: Add I-Class I6500 Multiprocessor Core Gregory CLEMENT
2024-02-16 17:42 ` [PATCH v8 09/14] dt-bindings: mips: Add bindings for Mobileye SoCs Gregory CLEMENT
2024-02-16 17:42 ` [PATCH v8 10/14] MIPS: mobileye: Add EyeQ5 dtsi Gregory CLEMENT
2024-02-16 17:42 ` [PATCH v8 11/14] MIPS: mobileye: Add EPM5 device tree Gregory CLEMENT
2024-02-16 17:42 ` [PATCH v8 12/14] MIPS: Share generic kernel code with other architecture Gregory CLEMENT
2024-02-16 17:42 ` [PATCH v8 13/14] MIPS: Add support for Mobileye EyeQ5 Gregory CLEMENT
2024-02-16 17:42 ` [PATCH v8 14/14] MAINTAINERS: Add entry for Mobileye MIPS SoCs Gregory CLEMENT
2024-02-20 13:44 ` [PATCH v8 00/14] Add support for the Mobileye EyeQ5 SoC Thomas Bogendoerfer
2024-02-28 11:44 ` Théo Lebrun
2024-03-01 9:39 ` Thomas Bogendoerfer [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=ZeGiYyiQQ7pwpECE@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=jiaxun.yang@flygoat.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tawfik.bayouk@mobileye.com \
--cc=theo.lebrun@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.kondratiev@mobileye.com \
/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).