public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: "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>,
	"Théo Lebrun" <theo.lebrun@bootlin.com>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v7 00/14] Add support for the Mobileye EyeQ5 SoC
Date: Thu, 8 Feb 2024 13:18:27 +0100	[thread overview]
Message-ID: <ZcTGk/iJO2wZlRxT@alpha.franken.de> (raw)
In-Reply-To: <20240205153503.574468-1-gregory.clement@bootlin.com>

On Mon, Feb 05, 2024 at 04:34:46PM +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.
> 
> One peculiarity of this SoC is that the physical address of the DDDR
> exceeds 32 bits. Given that the architecture is 64 bits, this is not
> an issue, but it requires some changes in how the mips64 is currently
> managed during boot.
> 
> In this seventh version, I removed the OLB related part as it is not
> used yet. I have left it to Théo to handle in his series. Another
> notable change is the Kconfig modification to remove the selection of
> unused configurations.
> [..]

thank you for your work on this patch set. I've commented on the
two patches, where is see need for changes. Other than that it's
looking good.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      parent reply	other threads:[~2024-02-08 12:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 15:34 [PATCH v7 00/14] Add support for the Mobileye EyeQ5 SoC Gregory CLEMENT
2024-02-05 15:34 ` [PATCH v7 01/14] MIPS: spaces: Define a couple of handy macros Gregory CLEMENT
2024-02-08 12:14   ` Thomas Bogendoerfer
2024-02-14 16:44     ` Gregory CLEMENT
2024-02-05 15:34 ` [PATCH v7 02/14] MIPS: Fix set_uncached_handler for ebase in XKPHYS Gregory CLEMENT
2024-02-05 15:34 ` [PATCH v7 03/14] MIPS: Allows relocation exception vectors everywhere Gregory CLEMENT
2024-02-08 12:11   ` Thomas Bogendoerfer
2024-02-14 16:48     ` Gregory CLEMENT
2024-02-14 19:14       ` Thomas Bogendoerfer
2024-02-05 15:34 ` [PATCH v7 04/14] MIPS: traps: Give more explanations if ebase doesn't belong to KSEG0 Gregory CLEMENT
2024-02-05 15:34 ` [PATCH v7 05/14] MIPS: cps-vec: Use macros for 64bits access Gregory CLEMENT
2024-02-05 15:34 ` [PATCH v7 06/14] dt-bindings: Add vendor prefix for Mobileye Vision Technologies Ltd Gregory CLEMENT
2024-02-05 15:34 ` [PATCH v7 07/14] dt-bindings: mips: cpus: Sort the entries Gregory CLEMENT
2024-02-05 15:34 ` [PATCH v7 08/14] dt-bindings: mips: cpu: Add I-Class I6500 Multiprocessor Core Gregory CLEMENT
2024-02-05 15:34 ` [PATCH v7 09/14] dt-bindings: mips: Add bindings for Mobileye SoCs Gregory CLEMENT
2024-02-05 15:34 ` [PATCH v7 10/14] MIPS: mobileye: Add EyeQ5 dtsi Gregory CLEMENT
2024-02-05 15:34 ` [PATCH v7 11/14] MIPS: mobileye: Add EPM5 device tree Gregory CLEMENT
2024-02-05 15:34 ` [PATCH v7 12/14] MIPS: Share generic kernel code with other architecture Gregory CLEMENT
2024-02-08  9:38   ` Jiaxun Yang
2024-02-05 15:34 ` [PATCH v7 13/14] MIPS: Add support for Mobileye EyeQ5 Gregory CLEMENT
2024-02-08  9:38   ` Jiaxun Yang
2024-02-05 15:35 ` [PATCH v7 14/14] MAINTAINERS: Add entry for Mobileye MIPS SoCs Gregory CLEMENT
2024-02-08 12:18 ` 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=ZcTGk/iJO2wZlRxT@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