mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frederic Stuyk <fstuyk@runbox.com>
To: hansg@kernel.org
Cc: bod@kernel.org, mchehab@kernel.org, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [BUG] OV02C10: image upside down in kernel 6.16
Date: Fri, 8 Aug 2025 11:03:43 +0200	[thread overview]
Message-ID: <b6df9ae7-ea9f-4e5a-8065-5b130f534f37@runbox.com> (raw)
In-Reply-To: <7d38cf46-670e-462e-b7c2-78f9aaa9eb43@runbox.com>

Hello,

I'm using the OV02C10 camera sensor on a system running Linux kernel 
6.16 (CachyOS, Arch-based).
I assume CachyOS customizations do not affect camera handling.

The sensor is detected and streams video correctly, but the image 
appears upside down by default.
Tested with GNOME Camera, qcam, and Firefox using an online webcam test 
page.

Querying the sensor orientation metadata shows:

     $ v4l2-ctl -d /dev/v4l-subdev6 -C camera_sensor_rotation
     camera_sensor_rotation: 0

This control is read-only and cannot be changed.

This suggests that either the driver incorrectly reports the orientation 
as 0, or that the platform is missing a quirk to reflect the actual 
physical mounting of the sensor.

I’d be happy to provide more details (e.g., logs, info...) if needed.

Here is some information about my system:

     Vendor:      LENOVO
     Product:     ThinkBook 13x G4 IMH (model: 21KR)
     BIOS:        MTCN51WW
     Kernel:      6.16.0-5-cachyos
     Arch:        x86_64

I’m reporting this to you as the driver maintainer. Please let me know 
if I should follow a different process — this is my first time reporting 
a kernel issue.

Note: Hans, we briefly exchanged emails on March 24th regarding early 
testing of this driver (as Kernel patch), and the same orientation issue 
was already visible at that time.

Best regards,
Frédéric

       reply	other threads:[~2025-08-08  9:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7d38cf46-670e-462e-b7c2-78f9aaa9eb43@runbox.com>
2025-08-08  9:03 ` Frederic Stuyk [this message]
2025-08-08  9:27   ` Bryan O'Donoghue
2025-08-08  9:33     ` Bryan O'Donoghue
2025-08-08 14:49       ` Frederic Stuyk

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=b6df9ae7-ea9f-4e5a-8065-5b130f534f37@runbox.com \
    --to=fstuyk@runbox.com \
    --cc=bod@kernel.org \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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

all inboxes | Powered by JetHome®