mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen+renesas@ideasonboard.com>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Subject: Re: [PATCH v4 00/15] media: rcar: Streams support
Date: Mon, 26 Jan 2026 16:01:36 +0200	[thread overview]
Message-ID: <9878845f-c403-492c-a673-90c91472ecc2@ideasonboard.com> (raw)
In-Reply-To: <20251231095739.GA3091492@ragnatech.se>

Hi,

On 31/12/2025 11:57, Niklas Söderlund wrote:
> Hi Tomi,
> 
> Thanks for your persistent work on this series!
> 
> On 2025-12-16 17:18:17 +0200, Tomi Valkeinen wrote:
>> Add streams support to Renesas rcar platform driver.
>>
>> The series keaps compatibility with the current upstream for a single
>> stream use case. However, in upstream there's a limited custom
>> multi-stream support implemented to the rcar driver, which will be
>> replaced with the upstream's Streams API.
>>
>> I have tested this series on Sparrow-Hawk board, with a few different
>> setups:
>>
>> IMX219 connected to the CSI0 connector
>> - The following patches applied to my test branch in addition to this
>>   series:
>>   1) The v4l2_subdev_get_frame_desc_passthrough dependency
>>   2) Revert of commit e7376745ad5c8548e31d9ea58adfb5a847e017a4 ("media:
>>      rcar-vin: Fix stride setting for RAW8 formats"), as that commit
>>      breaks RAW8
> 
> That is so odd, I do grab RAW8 on V4H with a IMX219. In what way is do 
> you see RAW8 breaking?
I think I found it. It's broken for all formats and resolutions, based
on luck:

VNIS_REG has the lowest 4 bits always 0. From the doc: "These bits
specify the width of the transfer destination memory in 16-pixel
unit."

We do nothing to comply with that.

 Tomi


  parent reply	other threads:[~2026-01-26 14:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16 15:18 Tomi Valkeinen
2025-12-16 15:18 ` [PATCH v4 01/15] media: rcar-isp: Improve ISPPROCMODE_DT_PROC_MODE_VC Tomi Valkeinen
2025-12-16 15:18 ` [PATCH v4 02/15] media: rcar-csi2: Improve FLD_FLD_EN macros Tomi Valkeinen
2025-12-16 15:18 ` [PATCH v4 03/15] media: rcar-csi2: Move rcsi2_calc_mbps() Tomi Valkeinen
2025-12-16 15:18 ` [PATCH v4 04/15] media: rcar-csi2: Simplify rcsi2_calc_mbps() Tomi Valkeinen
2025-12-16 15:18 ` [PATCH v4 05/15] media: rcar-csi2: Optimize rcsi2_calc_mbps() Tomi Valkeinen
2025-12-16 15:18 ` [PATCH v4 06/15] media: rcar-vin: Link VINs on Gen3 to a single channel on each CSI-2 Tomi Valkeinen
2025-12-16 15:18 ` [PATCH v4 07/15] media: rcar-isp: Move {enable|disable}_streams() calls Tomi Valkeinen
2025-12-16 15:18 ` [PATCH v4 08/15] media: rcar-csi2: " Tomi Valkeinen
2025-12-16 15:18 ` [PATCH v4 09/15] media: rcar-csi2: Switch to Streams API Tomi Valkeinen
2025-12-16 15:18 ` [PATCH v4 10/15] media: rcar-isp: " Tomi Valkeinen
2025-12-16 15:18 ` [PATCH v4 11/15] media: rcar-csi2: Add .get_frame_desc op Tomi Valkeinen
2025-12-16 15:18 ` [PATCH v4 12/15] media: rcar-isp: Call get_frame_desc to find out VC & DT Tomi Valkeinen
2025-12-16 15:18 ` [PATCH v4 13/15] media: rcar-csi2: Call get_frame_desc to find out VC & DT (Gen3) Tomi Valkeinen
2025-12-16 15:18 ` [PATCH v4 14/15] media: rcar-csi2: Add full streams support Tomi Valkeinen
2025-12-16 15:18 ` [PATCH v4 15/15] media: rcar-isp: " Tomi Valkeinen
2025-12-31  9:57 ` [PATCH v4 00/15] media: rcar: Streams support Niklas Söderlund
2026-01-08 13:57   ` Tomi Valkeinen
2026-01-11 17:31     ` Niklas Söderlund
2026-01-26 14:01   ` Tomi Valkeinen [this message]
2026-01-26 19:39     ` Niklas Söderlund
2026-01-27  8:59       ` Tomi Valkeinen
2026-01-27  9:25         ` Niklas Söderlund

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=9878845f-c403-492c-a673-90c91472ecc2@ideasonboard.com \
    --to=tomi.valkeinen+renesas@ideasonboard.com \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=niklas.soderlund@ragnatech.se \
    --cc=sakari.ailus@linux.intel.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

all inboxes | Powered by JetHome®