From: Prabhakar <prabhakar.csengg@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Prabhakar <prabhakar.csengg@gmail.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: [PATCH 0/2] RZ/V2L: Add CRU, CSI support
Date: Wed, 12 Apr 2023 19:56:06 +0100 [thread overview]
Message-ID: <20230412185608.64628-1-prabhakar.mahadev-lad.rj@bp.renesas.com> (raw)
From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Hi All,
This patch series adds support for CRU and CSI support to RZ/V2L SoC
and enables it on the RZ/V2L SMARC EVK. Also ov5645 node is added which
connects to the CSI2 node.
Cheers,
Prabhakar
Lad Prabhakar (2):
arm64: dts: renesas: r9a07g054: Add CSI and CRU nodes
arm64: dts: renesas: rzv2l-smarc: Enable CRU, CSI support
arch/arm64/boot/dts/renesas/Makefile | 1 +
.../r9a07g044l2-smarc-cru-csi-ov5645.dtso | 2 +-
arch/arm64/boot/dts/renesas/r9a07g054.dtsi | 79 +++++++++++++++++++
.../r9a07g054l2-smarc-cru-csi-ov5645.dtso | 1 +
4 files changed, 82 insertions(+), 1 deletion(-)
create mode 120000 arch/arm64/boot/dts/renesas/r9a07g054l2-smarc-cru-csi-ov5645.dtso
--
2.25.1
next reply other threads:[~2023-04-12 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 18:56 Prabhakar [this message]
2023-04-12 18:56 ` [PATCH 1/2] arm64: dts: renesas: r9a07g054: Add CSI and CRU nodes Prabhakar
2023-04-20 13:38 ` Geert Uytterhoeven
2023-04-12 18:56 ` [PATCH 2/2] arm64: dts: renesas: rzv2l-smarc: Enable CRU, CSI support Prabhakar
2023-04-17 8:56 ` Geert Uytterhoeven
2023-04-17 11:04 ` Lad, Prabhakar
2023-04-17 11:37 ` Geert Uytterhoeven
2023-04-20 13:50 ` Geert Uytterhoeven
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=20230412185608.64628-1-prabhakar.mahadev-lad.rj@bp.renesas.com \
--to=prabhakar.csengg@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@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.