From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Thanh Quan <thanh.quan.xn@renesas.com>
Subject: Re: [PATCH 1/2] dt-bindings: spi: renesas,sh-msiof: Add support for R-Car X5H
Date: Tue, 22 Sep 2026 13:27:00 +0200 [thread overview]
Message-ID: <arJmAGhRbhEc7VMu@shikoro> (raw)
In-Reply-To: <b8f4648eb1151b75d41e561c6b2adbd9bc4c0782.1790065451.git.geert+renesas@glider.be>
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
On Tue, Sep 22, 2026 at 10:27:00AM +0200, Geert Uytterhoeven wrote:
> From: Thanh Quan <thanh.quan.xn@renesas.com>
>
> Document support for Clock-Synchronized Serial Interfaces with FIFO
> (MSIOF) in the Renesas R-Car X5H (R8A78000) SoC, which is the first
> member of the R-Car Gen5 family.
>
> On R-Car X5H, MSIOF modules are wired to three DMACs, hence increase the
> maximum number of DMA channels to six.
>
> Signed-off-by: Thanh Quan <thanh.quan.xn@renesas.com>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-09-22 11:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 8:26 [PATCH 0/2] spi: sh-msiof: Add support for R-Car X5H Geert Uytterhoeven
2026-09-22 8:27 ` [PATCH 1/2] dt-bindings: spi: renesas,sh-msiof: " Geert Uytterhoeven
2026-09-22 11:27 ` Wolfram Sang [this message]
2026-09-22 11:46 ` Mark Brown
2026-09-22 8:27 ` [PATCH 2/2] spi: sh-msiof: Add support for R-Car Gen5 Geert Uytterhoeven
2026-09-22 11:27 ` Wolfram Sang
2026-09-22 12:56 ` [PATCH 0/2] spi: sh-msiof: Add support for R-Car X5H Mark Brown
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=arJmAGhRbhEc7VMu@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--cc=thanh.quan.xn@renesas.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