From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 2/2] v4l: Add support for STD ioctls on subdev nodes
Date: Thu, 28 Jun 2018 08:37:32 -0300 [thread overview]
Message-ID: <20180628083732.3679d730@coco.lan> (raw)
In-Reply-To: <20180517143016.13501-3-niklas.soderlund+renesas@ragnatech.se>
Em Thu, 17 May 2018 16:30:16 +0200
Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se> escreveu:
> There is no way to control the standard of subdevices which are part of
> a media device. The ioctls which exists all target video devices
> explicitly and the idea is that the video device should talk to the
> subdevice. For subdevices part of a media graph this is not possible and
> the standard must be controlled on the subdev device directly.
Why isn't it possible? A media pipeline should have at least a video
devnode where the standard ioctls will be issued.
So, I don't see why you would need to explicitly set the standard inside
a sub-device.
The way I see, inside a given pipeline, all subdevs should be using the
same video standard (maybe except for a m2m device with would have some
coded that would be doing format conversion).
Am I missing something?
Thanks,
Mauro
next prev parent reply other threads:[~2018-06-28 11:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 14:30 [PATCH v2 0/2] v4l: Add support for STD ioctls on subdev nodes Niklas Söderlund
2018-05-17 14:30 ` [PATCH v2 1/2] v4l2-ioctl: create helper to fill in v4l2_standard for ENUMSTD Niklas Söderlund
2018-05-17 14:30 ` [PATCH v2 2/2] v4l: Add support for STD ioctls on subdev nodes Niklas Söderlund
2018-06-28 11:37 ` Mauro Carvalho Chehab [this message]
2018-06-28 12:47 ` Hans Verkuil
2018-06-29 10:06 ` Mauro Carvalho Chehab
2018-06-29 10:26 ` Hans Verkuil
2018-06-29 12:28 ` Mauro Carvalho Chehab
2018-06-29 12:32 ` Hans Verkuil
2018-07-04 6:33 ` Niklas Söderlund
2018-07-04 6:33 ` Niklas Söderlund
2018-07-05 12:44 ` Mauro Carvalho Chehab
2018-07-05 13:12 ` Hans Verkuil
2018-07-08 13:11 ` Javier Martinez Canillas
2018-07-11 10:39 ` Marco Felsch
2018-07-11 10:39 ` Marco Felsch
2018-07-13 9:18 ` Javier Martinez Canillas
2018-07-13 10:54 ` Marco Felsch
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=20180628083732.3679d730@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.