From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Gregory CLEMENT" <gregory.clement@bootlin.com>,
"Vladimir Kondratiev" <vladimir.kondratiev@mobileye.com>,
"Théo Lebrun" <theo.lebrun@bootlin.com>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Tawfik Bayouk <tawfik.bayouk@mobileye.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH 2/3] MIPS: mobileye: Add EyeQ6H device tree
Date: Wed, 8 May 2024 09:28:41 +0200 [thread overview]
Message-ID: <7c4689c9-34a8-454a-a514-8ff0c77d74a8@kernel.org> (raw)
In-Reply-To: <20240506-eyeq6h-v1-2-f29b5269cc43@bootlin.com>
On 06/05/2024 18:16, Gregory CLEMENT wrote:
> EyeQ6H (or “High”) is an other SoC from Mobileye still based on the
> MIPS I6500 architecture as the EyeQ5. The 2 clusters of this SoC
> contains 4 cores which are capable of running 4 threads. Besides this,
> it features multiple controllers such as the classic UART, high speed
> I2C, SPI, as well as CAN-FD, PCIe Gen4, Octal/Quad SPI Flash
> interface, Gigabit Ethernet, MIPI CSI-2, MIPI DSI, and eMMC 5.1. It
> also includes a Hardware Security Module, Functional Safety Hardware,
> and video encoders and more.
>
> This commit provides the initial device tree files with support for
> UART, GPIO and pinctrl, as well as fixed clocked.
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
> ---
> arch/mips/boot/dts/mobileye/eyeq6h-epm6.dts | 22 +++++
> .../boot/dts/mobileye/eyeq6h-fixed-clocks.dtsi | 52 ++++++++++++
> arch/mips/boot/dts/mobileye/eyeq6h-pins.dtsi | 88 +++++++++++++++++++
> arch/mips/boot/dts/mobileye/eyeq6h.dtsi | 99 ++++++++++++++++++++++
> 4 files changed, 261 insertions(+)
>
> diff --git a/arch/mips/boot/dts/mobileye/eyeq6h-epm6.dts b/arch/mips/boot/dts/mobileye/eyeq6h-epm6.dts
> new file mode 100644
> index 000000000000..ebc0d363fbf8
> --- /dev/null
> +++ b/arch/mips/boot/dts/mobileye/eyeq6h-epm6.dts
> @@ -0,0 +1,22 @@
> +// SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +/*
> + * Copyright 2024 Mobileye Vision Technologies Ltd.
> + */
> +
> +/dts-v1/;
> +
> +#include "eyeq6h.dtsi"
> +
> +/ {
> + compatible = "mobileye,eyeq6-epm6", "mobileye,eyeq6";
> + model = "Mobile EyeQ6H MP6 Evaluation board";
> +
> + chosen {
> + stdout-path = "serial0:921600n8";
> + };
> +
> + memory@0 {
> + device_type = "memory";
> + reg = <0x1 0x00000000 0x1 0x00000000>;
> + };
> +};
> diff --git a/arch/mips/boot/dts/mobileye/eyeq6h-fixed-clocks.dtsi b/arch/mips/boot/dts/mobileye/eyeq6h-fixed-clocks.dtsi
> new file mode 100644
> index 000000000000..8bb806eb567e
> --- /dev/null
> +++ b/arch/mips/boot/dts/mobileye/eyeq6h-fixed-clocks.dtsi
> @@ -0,0 +1,52 @@
> +// SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +/*
> + * Copyright 2023 Mobileye Vision Technologies Ltd.
> + */
> +
> +#include <dt-bindings/clock/mobileye,eyeq5-clk.h>
> +
> +/ {
> + xtal: xtal {
You should use common prefixes or even preferred clock node name.
https://lore.kernel.org/all/20240430180415.657067-1-robh@kernel.org/
...
> +
> + soc: soc {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> + compatible = "simple-bus";
compatible is *always* the first property. This applies to all your
patches. See DTS coding style for the order.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-05-08 7:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 16:16 [PATCH 0/3] Add support for the Mobileye EyeQ6H SoC Gregory CLEMENT
2024-05-06 16:16 ` [PATCH 1/3] dt-bindings: mips: Add bindings for a new Mobileye SoC EyeQ6H Gregory CLEMENT
2024-05-07 15:07 ` Conor Dooley
2024-05-06 16:16 ` [PATCH 2/3] MIPS: mobileye: Add EyeQ6H device tree Gregory CLEMENT
2024-05-08 7:28 ` Krzysztof Kozlowski [this message]
2024-05-06 16:16 ` [PATCH 3/3] MIPS: mobileye: Add EyeQ6H support Gregory CLEMENT
2024-05-07 9:07 ` Jiaxun Yang
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=7c4689c9-34a8-454a-a514-8ff0c77d74a8@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--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=tsbogend@alpha.franken.de \
--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