From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: Mehdi Djait <mehdi.djait@bootlin.com>
Cc: mchehab@kernel.org, hverkuil-cisco@xs4all.nl,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
conor+dt@kernel.org, laurent.pinchart@ideasonboard.com,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com,
alexandre.belloni@bootlin.com, maxime.chevallier@bootlin.com
Subject: Re: [PATCH v7 3/3] media: i2c: Introduce a driver for the Techwell TW9900 decoder
Date: Mon, 6 Nov 2023 18:58:51 +0100 [thread overview]
Message-ID: <ZUkpWzw_5SdqqL2X@aptenodytes> (raw)
In-Reply-To: <ZUkLHDH2Budi+zgc@pc-70.home>
[-- Attachment #1: Type: text/plain, Size: 2371 bytes --]
Hi,
On Mon 06 Nov 23, 16:49, Mehdi Djait wrote:
> Hi Paul,
>
> On Mon, Nov 06, 2023 at 04:25:18PM +0100, Paul Kocialkowski wrote:
> > > > > +static void tw9900_fill_fmt(const struct tw9900_mode *mode,
> > > > > + struct v4l2_mbus_framefmt *fmt)
> > > > > +{
> > > > > + fmt->code = MEDIA_BUS_FMT_UYVY8_2X8;
> > > > > + fmt->width = mode->width;
> > > > > + fmt->height = mode->height;
> > > > > + fmt->field = V4L2_FIELD_NONE;
> > > > > + fmt->quantization = V4L2_QUANTIZATION_DEFAULT;
> > > > > + fmt->colorspace = V4L2_COLORSPACE_SMPTE170M;
> > > > > + fmt->xfer_func = V4L2_MAP_XFER_FUNC_DEFAULT(V4L2_COLORSPACE_SMPTE170M);
> > > > > + fmt->ycbcr_enc = V4L2_MAP_YCBCR_ENC_DEFAULT(V4L2_COLORSPACE_SMPTE170M);
> > > > > +}
> > > > > +
> > > > > +static int tw9900_cfg_fmt(struct v4l2_subdev *sd,
> > > >
> > > > You might have to differentiate between set_fmt/get_fmt to return -EBUSY
> > > > if streaming is on in set_fmt. However I understand it will just copy the
> > > > current mode in both cases, but this might still be required to follow v4l2
> > > > semantics (please double-check).
> > > >
> > >
> > > This should be done in the driver calling the pad subdev_call set_fmt,
> > > right ?
> >
> > Well the two things are distinct, even though it's not obvious to think about
> > a case where you wouldn't have a video device to grab the frames.
> >
> > For instance you can see this being done here:
> > https://elixir.bootlin.com/linux/latest/source/drivers/media/i2c/ov5648.c#L2259
> >
> > I'm just not sure about what the V4L2 subdev API mandates. It would be useful
> > to find some piece of documentation that clarifies the requirement.
>
> Ok, I will split the functions then.
I was more interested in finding out the right answer rather than having you
follow an example from another driver. You can see the docs at:
https://www.kernel.org/doc/html/latest/userspace-api/media/v4l/vidioc-subdev-g-fmt.html#return-value
So I think it's a good measure to return -EBUSY here. You can just have set_fmt
call into get_fmt with an extra check before.
Also see the part about the which field. I'm not sure it should have
implications in your case but better double-check that too.
Cheers,
Paul
--
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-11-06 17:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 13:58 [PATCH v7 0/3] media: i2c: Introduce driver for the TW9900 video decoder Mehdi Djait
2023-10-16 13:58 ` [PATCH v7 1/3] dt-bindings: vendor-prefixes: Add techwell vendor prefix Mehdi Djait
2023-10-16 13:58 ` [PATCH v7 2/3] media: dt-bindings: media: i2c: Add bindings for TW9900 Mehdi Djait
2023-10-17 7:45 ` Conor Dooley
2023-10-17 19:48 ` Rob Herring
2023-10-16 13:58 ` [PATCH v7 3/3] media: i2c: Introduce a driver for the Techwell TW9900 decoder Mehdi Djait
2023-11-02 10:03 ` Paul Kocialkowski
2023-11-06 14:58 ` Mehdi Djait
2023-11-06 15:25 ` Paul Kocialkowski
2023-11-06 15:49 ` Mehdi Djait
2023-11-06 17:58 ` Paul Kocialkowski [this message]
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=ZUkpWzw_5SdqqL2X@aptenodytes \
--to=paul.kocialkowski@bootlin.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=mchehab@kernel.org \
--cc=mehdi.djait@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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