linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <yuji2.ishikawa@toshiba.co.jp>
To: <sakari.ailus@iki.fi>
Cc: <hverkuil@xs4all.nl>, <laurent.pinchart@ideasonboard.com>,
	<mchehab@kernel.org>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
	<nobuhiro1.iwamatsu@toshiba.co.jp>, <linux-media@vger.kernel.org>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v9 4/5] documentation: media: add documentation for Toshiba Visconti Video Input Interface driver
Date: Mon, 22 Apr 2024 06:45:20 +0000	[thread overview]
Message-ID: <TYCPR01MB10196F6969BDAE599FF536E4F92122@TYCPR01MB10196.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <ZbyQgkGicrnP-XZL@valkosipuli.retiisi.eu>

Hello Sakari,

> -----Original Message-----
> From: Sakari Ailus <sakari.ailus@iki.fi>
> Sent: Friday, February 2, 2024 3:50 PM
> To: ishikawa yuji(石川 悠司 ○RDC□AITC○EA開)
> <yuji2.ishikawa@toshiba.co.jp>
> Cc: hverkuil@xs4all.nl; laurent.pinchart@ideasonboard.com;
> mchehab@kernel.org; robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org;
> conor+dt@kernel.org; iwamatsu nobuhiro(岩松 信洋 ○DITC□DIT○O
> ST) <nobuhiro1.iwamatsu@toshiba.co.jp>; linux-media@vger.kernel.org;
> devicetree@vger.kernel.org; linux-arm-kernel@lists.infradead.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v9 4/5] documentation: media: add documentation for
> Toshiba Visconti Video Input Interface driver
> 
> Hi Yuji,
> 
> On Mon, Dec 04, 2023 at 04:32:40AM +0000, yuji2.ishikawa@toshiba.co.jp
> wrote:
> > > > +Vendor specific v4l2 controls
> > > > +=============================
> > > > +
> > > > +.. _V4L2_CID_VISCONTI_VIIF_MAIN_SET_RAWPACK_MODE:
> > > > +
> > > > +V4L2_CID_VISCONTI_VIIF_MAIN_SET_RAWPACK_MODE
> > > > +--------------------------------------------
> > > > +
> > > > +This control sets the format to pack multiple RAW pixel values into a
> word.
> > > > +
> > > > +This control accepts a __u32 value defined as `enum
> viif_rawpack_mode`.
> > > > +
> > > > +This control should be set before ioctl(S_FMT) and should not be
> > > > +changed
> > > after that.
> > >
> > > Why do you need this? Doesn't the V4L2 pixelformat already
> > > explicitly define the format, including packing?
> > >
> >
> > This control value affects the unpacker between CSI2 receiver and ISP.
> > The rawpack mode is an option to receive from Wide-Dynamic-Range image
> > sensors, whose output bit width is larger than standard format (RAW20,
> > RAW24). For example, some WDR image sensors split 20 bit value into
> > upper/lower 10bit values, then put them into consective pixels to make
> > a double-width RAW10 format image.
> 
> Do you have a sensor that really does this? Which one is it?

Our HW specialist has indicated that the VIIF HDR input expects some SONY HDR sensors as its source.

Because the VIIF was developed prior to the official release of RAW20 and RAW24 formats in the MIPI CSI2 specification,
its HDR RAW input feature is controlled by a vendor specific "rawpack" register.
Also, the proprietary software stack has "rawpack" flag.
The expected bitstream formats associated with "rawpack" align with the official RAW20 and RAW24 formats.

I now understand that rawpack flag is not used for non-standard pixel formats.
I'll remove rawpack flag in the v10 patch of the driver. 
HDR RAW input feature should be controlled by V4L2 pixelformat or media bus format.
However, RAW20, RAW24 support will be dropped in the v10 patch because modified part is not fully tested.

> 
> >
> > This option is only related to the interpretation of CSI2 input data.
> > Therefore, I think V4L2 pixel format (for resulting image) is not
> > related to it. The media bus format seems more relevant, but there is
> > no corresponding definition to this case.
> 
> --
> Regards,
> 
> Sakari Ailus

Regards,

Yuji Ishikawa


  reply	other threads:[~2024-04-22  7:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12  7:13 [PATCH v9 0/5] Add Toshiba Visconti Video Input Interface driver Yuji Ishikawa
2023-10-12  7:13 ` [PATCH v9 1/5] dt-bindings: media: platform: visconti: Add Toshiba Visconti Video Input Interface Yuji Ishikawa
2023-10-12 19:24   ` Krzysztof Kozlowski
2023-10-12  7:13 ` [PATCH v9 2/5] media: platform: visconti: Add Toshiba Visconti Video Input Interface driver Yuji Ishikawa
2023-10-12  7:13 ` [PATCH v9 3/5] media: platform: visconti: add V4L2 vendor specific control handlers Yuji Ishikawa
2023-11-14  9:02   ` Hans Verkuil
2023-11-14  9:10     ` Hans Verkuil
2023-11-14  9:53       ` Laurent Pinchart
2023-11-27  0:46         ` yuji2.ishikawa
2023-12-06 11:08           ` Hans Verkuil
2023-12-11  0:35           ` yuji2.ishikawa
2023-11-27  0:45       ` yuji2.ishikawa
2023-12-06 11:03         ` Hans Verkuil
2023-11-27  0:43     ` yuji2.ishikawa
2023-10-12  7:13 ` [PATCH v9 4/5] documentation: media: add documentation for Toshiba Visconti Video Input Interface driver Yuji Ishikawa
2023-11-14  8:49   ` Hans Verkuil
2023-11-27  0:39     ` yuji2.ishikawa
2023-11-22 11:40   ` Sakari Ailus
2023-12-04  4:32     ` yuji2.ishikawa
2024-02-02  6:49       ` Sakari Ailus
2024-04-22  6:45         ` yuji2.ishikawa [this message]
2023-10-12  7:13 ` [PATCH v9 5/5] MAINTAINERS: Add entries for Toshiba Visconti Video Input Interface Yuji Ishikawa
2023-11-14  8:40   ` Hans Verkuil
2023-11-27  0:38     ` yuji2.ishikawa
2023-12-06 10:59       ` Hans Verkuil

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=TYCPR01MB10196F6969BDAE599FF536E4F92122@TYCPR01MB10196.jpnprd01.prod.outlook.com \
    --to=yuji2.ishikawa@toshiba.co.jp \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil@xs4all.nl \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=robh+dt@kernel.org \
    --cc=sakari.ailus@iki.fi \
    /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;
as well as URLs for NNTP newsgroup(s).