From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Zhu, Mingcheng" <mingchen@quicinc.com>
Cc: Sakari Ailus <sakari.ailus@iki.fi>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: query video dev node name using the V4L2 device driver name
Date: Mon, 19 Dec 2011 11:31:22 +0100 [thread overview]
Message-ID: <201112191131.23195.laurent.pinchart@ideasonboard.com> (raw)
In-Reply-To: <3D233F78EE854A4BA3D34C11AD4FAC1FDEF5E3@nasanexd01b.na.qualcomm.com>
Hi Mingcheng,
On Monday 19 December 2011 11:21:03 Zhu, Mingcheng wrote:
> Hi Laurent and Sakari,
>
> Current media entity contains a few fields to identify a dev node (name,
> type, group_id). The entity name is the v4l2 dev node name such as
> "/dev/video0" "/dev/video1". There is no information who is "/dev/video0"
> and who is /dev/video1". This makes that, after query the media_entity the
> application still could not figure out who is /dev/video1".
The media controller framework sets the video devnode entities names to the
video device name, as provided in the video_device name field. That's
automatic, so you should just ensure that your video_device name is properly
set.
> However in V4L2 devices, there is a driver name that the vendor can assign
> a specific name such "WIFI CAPTURE" or BACK_CAMERA" to the driver name. Is
> it possible to add the driver name into the media_entity? This makes that,
> if the userspace application knows the driver name it can use the driver
> name to find the dev node.
Using the driver name isn't optimal, as a driver could create several video
device nodes for the same hardware device. Those nodes should have different
names, so you should use the video_device name field as explained above.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2011-12-19 10:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 9:50 [RFC 0/4] OMAP 3 ISP driver improvements Sakari Ailus
2011-12-15 9:50 ` [RFC 1/4] omap3isp: Implement validate_pipeline Sakari Ailus
2011-12-15 10:18 ` Laurent Pinchart
2011-12-15 11:53 ` Sakari Ailus
2011-12-15 9:50 ` [RFC 2/4] omap3isp: Add lane configuration to platform data Sakari Ailus
2011-12-15 9:50 ` [RFC 3/4] omap3isp: Configure CSI-2 phy based on " Sakari Ailus
2011-12-15 10:28 ` Laurent Pinchart
2011-12-15 11:53 ` Sakari Ailus
2011-12-15 12:54 ` Laurent Pinchart
2011-12-15 21:50 ` Sakari Ailus
2011-12-19 0:31 ` Laurent Pinchart
2011-12-19 7:17 ` Sakari Ailus
2011-12-19 10:21 ` query video dev node name using the V4L2 device driver name Zhu, Mingcheng
2011-12-19 10:31 ` Laurent Pinchart [this message]
2011-12-19 18:09 ` Zhu, Mingcheng
2011-12-21 0:34 ` Laurent Pinchart
2011-12-15 9:50 ` [RFC 4/4] omap3isp: Use pixel clock from sensor media bus frameformat Sakari Ailus
2011-12-15 10:29 ` Laurent Pinchart
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=201112191131.23195.laurent.pinchart@ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mingchen@quicinc.com \
--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