Linux kernel regressions
 help / color / mirror / Atom feed
From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: Martijn Braam <martijn@brixit.nl>
Cc: regressions@lists.linux.dev, jernej.skrabec@gmail.com,
	sakari.ailus@linux.intel.com, mchehab@kernel.org,
	linux-media@vger.kernel.org
Subject: Re: [REGRESSION] breakage in sun6i-csi media api
Date: Fri, 2 Jun 2023 11:16:21 +0200	[thread overview]
Message-ID: <ZHmzZUkcFK8Gq_JL@aptenodytes> (raw)
In-Reply-To: <f13c27fb-2afe-b94e-aad9-ed5ecc818183@brixit.nl>

[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

Hi Martijn,

On Thu 01 Jun 23, 23:19, Martijn Braam wrote:
> It seems like this commit:
> 
> media: sun6i-csi: Add bridge v4l2 subdev with port management
> 
> Has changed the way the media pipeline on a64 devices, in my case the PINE64
> PinePhone works. Since this is an API towards userspace and there's active
> applications that use it I think this counts as a regression.

Do you have more details on what changed specifically?

The commit added a bridge subdev in addition to the video node, which is
generally a better description of the CSI hardware and also a necessity
to support the ISP data flow.

Maybe your userspace application is not configuring the bridge media block with
the right format, which results in a mismatch?

Some work was started to achieve automatic format propagation, perhaps it
would be enough to solve your issue.

Cheers,

Paul

> #regzbot introduced: 0d2b746b1bef73de62d2d311e594a7ffed4ca43
> 
> Greetings,
> Martijn Braam

-- 
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-06-02  9:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 21:19 [REGRESSION] breakage in sun6i-csi media api Martijn Braam
2023-06-02  9:16 ` Paul Kocialkowski [this message]
     [not found]   ` <e168d246-528d-b615-aa50-af8f17af4442@brixit.nl>
2023-06-02  9:39     ` Paul Kocialkowski
2023-06-02 10:03       ` Laurent Pinchart
2023-06-26 12:23         ` Linux regression tracking (Thorsten Leemhuis)
2023-06-28 22:08           ` Mauro Carvalho Chehab
2023-07-12 14:47             ` Paul Kocialkowski
2023-08-29 11:33               ` Linux regression tracking #update (Thorsten Leemhuis)
2023-07-12 14:55         ` Paul Kocialkowski
2023-07-12 17:00           ` 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=ZHmzZUkcFK8Gq_JL@aptenodytes \
    --to=paul.kocialkowski@bootlin.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=martijn@brixit.nl \
    --cc=mchehab@kernel.org \
    --cc=regressions@lists.linux.dev \
    --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