linux-kernel - Re: [PATCH v3 RESEND] media: i2c: Add OV05C10 camera sensor driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <37eec3b5-1e57-498d-8ead-891d1e5f96d4@linaro.org>
Date: Fri, 13 Jun 2025 13:05:56 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Kieran Bingham <kieran.bingham@...asonboard.com>,
 Hao Yao <hao.yao@...el.com>, Pratap Nirujogi <pratap.nirujogi@....com>,
 sakari.ailus@...ux.intel.com
Cc: mchehab@...nel.org, laurent.pinchart@...asonboard.com,
 hverkuil@...all.nl, krzk@...nel.org, dave.stevenson@...pberrypi.com,
 hdegoede@...hat.com, jai.luthra@...asonboard.com,
 tomi.valkeinen@...asonboard.com, linux-media@...r.kernel.org,
 linux-kernel@...r.kernel.org, benjamin.chan@....com, bin.du@....com,
 grosikop@....com, king.li@....com, dantony@....com, vengutta@....com,
 dongcheng.yan@...el.com, jason.z.chen@...el.com, jimmy.su@...el.com
Subject: Re: [PATCH v3 RESEND] media: i2c: Add OV05C10 camera sensor driver

On 13/06/2025 12:02, Kieran Bingham wrote:
> Quoting Hao Yao (2025-06-13 05:55:46)
>> Hi Pratap,
>>
>> Thanks for your patch.
>>
>> This patch is written for your camera sensor module, which seems very
>> different from those already applied on Dell laptops (some of "Dell Pro"
>> series). Looking into the driver, I think this version will break the
> Have there been existing efforts from Intel to upstream support for that
> device?

FWIW +1

Qualcomm devices - Acer Swift 14 AI, HP OmniBook x14 both use this sensor.

I'd expect though that aside from OF bindings, regulators and clocks 
that any upstream configuration with the right number of lanes would 
"just work", including this one from AMD.

That has been the experience picking up OV02E10 and OV02C10 from the 
IPU6 repository where its ACPI binding and repurposing to OF/Qcom.

So how incompatible could OV05C10 be between different x86/ACPI systems 
? Less than the gap between x86/ACPI and Arm/OF you'd imagine.

Getting any OV05C10 driver upstream would be great, we can work from 
there to bridge whatever gap needs be for !AMD.

---
bod