From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Subject: Re: [PATCH v3 0/4] renesas: r8a779g0: Enable VSPX on R-Car V4H
Date: Thu, 19 Dec 2024 17:12:18 +0100 [thread overview]
Message-ID: <Z2RF4vGtTd1wDjJS@shikoro> (raw)
In-Reply-To: <20241219-rcar-v4h-vspx-v3-0-8fe8d2afb268@ideasonboard.com>
[-- Attachment #1: Type: text/plain, Size: 232 bytes --]
Hi Jacopo,
> Compile-tested only series.
Can't this go ...
> Changes in v3:
> - Test on an actual board and fix the VSPX and FCPVX power domains to
> use the ISP power domains
... because of this?
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-12-19 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 15:24 [PATCH v3 0/4] renesas: r8a779g0: Enable VSPX on R-Car V4H Jacopo Mondi
2024-12-19 15:24 ` [PATCH v3 1/4] clk: renesas: r8a779g0: Add FCPVX clocks Jacopo Mondi
2024-12-19 15:24 ` [PATCH v3 2/4] arm64: dts: renesas: r8a779g0: Add FCPVX instances Jacopo Mondi
2024-12-19 15:24 ` [PATCH v3 3/4] clk: renesas: r8a779g0: Add VSPX clocks Jacopo Mondi
2024-12-19 15:24 ` [PATCH v3 4/4] arm64: dts: renesas: r8a779g0: Add VSPX instances Jacopo Mondi
2024-12-19 16:12 ` Wolfram Sang [this message]
2024-12-19 17:15 ` [PATCH v3 0/4] renesas: r8a779g0: Enable VSPX on R-Car V4H Jacopo Mondi
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=Z2RF4vGtTd1wDjJS@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jacopo.mondi@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.