From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Hans de Goede <hdegoede@redhat.com>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Weird default vblank value in ov5693
Date: Mon, 29 Jan 2024 12:54:18 +0000 [thread overview]
Message-ID: <170653285818.2407440.7940034493930024656@ping.linuxembedded.co.uk> (raw)
In-Reply-To: <77162309-ed79-42ed-a715-d8a0ce1af56d@redhat.com>
Quoting Hans de Goede (2024-01-29 10:43:33)
> Hi,
> >
> > Would you be interested in reviewing
> > https://patchwork.kernel.org/project/linux-media/list/?series=697777&state=%2A&archive=both
> Documentation: media: camera_sensor: Document blankings handling
> >
> > and discuss there what the desired behaviour should be ?
>
> I'm definitely interested in discussing this and in
> helping with reviewing the documentation patches,
> good timing wrt writing those patches :)
>
> but Dan already replied in this thread, so lets
> keep the discussion in this thread for now ?
>
> Also I think this will probably make a good agenda
> item for the libcamera workshop coming Friday ?
Added to the existing Sensor Modes topic that was added by Nicolas
--
Kieran
next prev parent reply other threads:[~2024-01-29 12:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 20:58 Weird default vblank value in ov5693 Hans de Goede
2024-01-29 8:58 ` Jacopo Mondi
2024-01-29 10:43 ` Hans de Goede
2024-01-29 12:54 ` Kieran Bingham [this message]
2024-01-29 9:53 ` Dan Scally
2024-01-29 10:30 ` Hans de Goede
2024-01-29 12:05 ` Jacopo Mondi
2024-01-29 12:24 ` Hans de Goede
2024-01-29 13:07 ` Dan Scally
2024-01-29 14:45 ` Jacopo Mondi
2024-01-29 17:18 ` Hans de Goede
2024-01-29 18:40 ` Sakari Ailus
2024-01-30 10:29 ` Hans de Goede
2024-01-30 12:00 ` Sakari Ailus
2024-01-30 12:37 ` Hans de Goede
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=170653285818.2407440.7940034493930024656@ping.linuxembedded.co.uk \
--to=kieran.bingham@ideasonboard.com \
--cc=hdegoede@redhat.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=linux-media@vger.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