Linux Media Controller development
 help / color / mirror / Atom feed
From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
	"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: [PATCH v2 0/2] rcar-vin: Add support for R-Car V4M
Date: Mon, 10 Jun 2024 13:31:22 +0200	[thread overview]
Message-ID: <20240610113124.2396688-1-niklas.soderlund+renesas@ragnatech.se> (raw)

Hello,

This small series adds bindings and support to rcar-vin for R-Car V4M.

The V4M capture pipeline is similar to the other Gen4 SoC supported 
upstream already V4H. Currently all futures supported for VIN on V4M are 
also supported by V4H and the driver code can be shared. But as done for 
other R-Car IP bindings a new dedicated binding for V4M is created.  
This have proved prudent in the past where quirks are found even within 
the same generation as more advance use-cases are enabled.

The two patches where previously posted separately as v1, but are now 
collected in a single series. I wold be happy if the bindings could go 
thru the DT-tree.

See individual patches for changes since previous version.

Niklas Söderlund (2):
  dt-bindings: media: renesas,vin: Add binding for V4M
  media: rcar-vin: Add support for R-Car V4M

 Documentation/devicetree/bindings/media/renesas,vin.yaml | 1 +
 drivers/media/platform/renesas/rcar-vin/rcar-core.c      | 8 ++++++--
 2 files changed, 7 insertions(+), 2 deletions(-)

-- 
2.45.2


             reply	other threads:[~2024-06-10 11:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10 11:31 Niklas Söderlund [this message]
2024-06-10 11:31 ` [PATCH v2 1/2] dt-bindings: media: renesas,vin: Add binding for V4M Niklas Söderlund
2024-06-10 16:03   ` Conor Dooley
2024-06-10 16:59     ` Niklas Söderlund
2024-06-10 21:32       ` Conor Dooley
2024-06-11 11:06         ` Niklas Söderlund
2024-06-13 16:51           ` Rob Herring
2024-06-13 19:35             ` Geert Uytterhoeven
2024-06-18 13:57               ` Niklas Söderlund
2024-06-18 14:31                 ` Conor Dooley
2024-06-10 11:31 ` [PATCH v2 2/2] media: rcar-vin: Add support for R-Car V4M Niklas Söderlund
2024-06-10 12:14   ` Geert Uytterhoeven
2024-06-19  1:35   ` Laurent Pinchart

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=20240610113124.2396688-1-niklas.soderlund+renesas@ragnatech.se \
    --to=niklas.soderlund+renesas@ragnatech.se \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox