From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v3] arm64: dts: renesas: r8a779a0: Add and connect all CSI-2, ISP and VIN nodes
Date: Wed, 13 Oct 2021 16:28:34 +0200 [thread overview]
Message-ID: <CAMuHMdXO+Ne1JLw_VbjNmVDzMaanw20MRvMqxphxhBzk9=UcKA@mail.gmail.com> (raw)
In-Reply-To: <20211012100038.375289-1-niklas.soderlund+renesas@ragnatech.se>
Hi Niklas,
On Tue, Oct 12, 2021 at 12:00 PM Niklas Söderlund
<niklas.soderlund+renesas@ragnatech.se> wrote:
> The V3U have 32 VIN, 4 CSI-2 and 4 ISP nodes that interact with each
> other for video capture. Add all nodes and record how they are
> interconnected.
>
> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> ---
> * Changes since v2
> - Add empty port@0 nodes to all CSI-2 nodes.
Thanks for the update!
> Hello Geert,
>
> The last binding document for the CSI-2 nodes are now merged in the
> media-tree and this completes the coverage for the nodes in this patch.
>
> I fixed the missing port@0 nodes for CSI-2 and actually ran make
> dtbs_check ontop of the media-tree instead of on v5.14-rc4 to include
> the CSI-2 binding update for V3U. Thanks for spotting that.
>
> If you are happy with the corrections I think this is ready to be
> consumed.
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
i.e. will queue in renesas-devel for v5.16.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2021-10-13 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 10:00 [PATCH v3] arm64: dts: renesas: r8a779a0: Add and connect all CSI-2, ISP and VIN nodes Niklas Söderlund
2021-10-13 14:28 ` Geert Uytterhoeven [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='CAMuHMdXO+Ne1JLw_VbjNmVDzMaanw20MRvMqxphxhBzk9=UcKA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
/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.