[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZWCH5cT51XGky6d9@valkosipuli.retiisi.eu>
Date: Fri, 24 Nov 2023 11:24:21 +0000
From: Sakari Ailus <sakari.ailus@....fi>
To: Sebastian Reichel <sre@...nel.org>
Cc: Sakari Ailus <sakari.ailus@...ux.intel.com>,
Jacopo Mondi <jacopo.mondi@...asonboard.com>,
Alain Volmat <alain.volmat@...s.st.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
linux-media@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/6] GC0308 Camera Sensor
Hi Sebastian,
On Mon, Nov 13, 2023 at 11:57:19PM +0100, Sebastian Reichel wrote:
> Hi,
>
> I did the following tests on an i.MX6ULL based system [0]:
>
> * v4l2-compliance -u /dev/v4l-subdev1
> - v4l2-compliance 1.24.1, 32 bits, 32-bit time_t
> (from Debian testing)
> - Total for device /dev/v4l-subdev1: 44, Succeeded: 44
> * Using gstreamer + v4l2-ctl
> - Tried 640x480, 320x240, 160x120 YUYV8_2X8 formats
> - Tested effect of all exposed user controls
> * checkpatch does not report any driver issues
> * dt_binding_check does not report anything
> * rebinding driver works
I forgot to ask this earlier --- the sub-device state information access
functions have been reworked and that resulted in renaming the functions
this driver uses. Could you rebase this on the current stage tree?
The commit doing this for all merged drivers was
bc0e8d91feec72b19199298dca470c5816a52105 .
Could you also add Cc: stable for the v4l2-async list fix?
Thanks.
--
Kind regards,
Sakari Ailus
Powered by blists - more mailing lists