From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Théo Lebrun" <theo.lebrun@bootlin.com>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Vladimir Kondratiev" <vladimir.kondratiev@mobileye.com>,
"Grégory Clement" <gregory.clement@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Tawfik Bayouk" <tawfik.bayouk@mobileye.com>
Subject: Re: [PATCH 0/3] MIPS: Add Mobileye EyeQ OLB system-controller
Date: Wed, 3 Jul 2024 16:35:27 +0200 [thread overview]
Message-ID: <ZoVhry8VFRx8x3w/@alpha.franken.de> (raw)
In-Reply-To: <20240628-mbly-mips-v1-0-f53f5e4c422b@bootlin.com>
On Fri, Jun 28, 2024 at 06:11:49PM +0200, Théo Lebrun wrote:
> This is a new iteration on the Mobileye system-controller series [0].
> It has been split into separate series to facilitate merging.
>
> This series contains a dt-bindings defining the system-controller
> (called OLB) used on EyeQ5, EyeQ6L and EyeQ6H. It then modifies the
> EyeQ5 devicetree to exploit that system-controller.
just to be sure, this replaces the v3 series ? And it's the only
series, which should go through the MIPS tree ?
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2024-07-03 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 16:11 [PATCH 0/3] MIPS: Add Mobileye EyeQ OLB system-controller Théo Lebrun
2024-06-28 16:11 ` [PATCH 1/3] dt-bindings: soc: mobileye: add EyeQ OLB system controller Théo Lebrun
2024-06-28 16:11 ` [PATCH 2/3] MIPS: mobileye: eyeq5: add OLB system-controller node Théo Lebrun
2024-06-28 16:11 ` [PATCH 3/3] MAINTAINERS: Mobileye: add OLB drivers and dt-bindings Théo Lebrun
2024-07-03 14:35 ` Thomas Bogendoerfer [this message]
2024-07-03 14:52 ` [PATCH 0/3] MIPS: Add Mobileye EyeQ OLB system-controller Théo Lebrun
2024-07-03 15:19 ` Thomas Bogendoerfer
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=ZoVhry8VFRx8x3w/@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=robh@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