ioctl VIDIOC_DBG_G_CHIP_NAME &manvol; VIDIOC_DBG_G_CHIP_NAME Identify the chips on a TV card int ioctl int fd int request struct v4l2_dbg_chip_name *argp fd &fd; request VIDIOC_DBG_G_CHIP_NAME argp This is an experimental interface and may change in the future. For driver debugging purposes this ioctl allows test applications to query the driver about the chips present on the TV card. Regular applications must not use it. When you found a chip specific bug, please contact the linux-media mailing list (&v4l-ml;) so it can be fixed. To query the driver applications must initialize the match.type and match.addr or match.name fields of a &v4l2-dbg-chip-name; and call VIDIOC_DBG_G_CHIP_NAME with a pointer to this structure. On success the driver stores information about the selected chip in the name and flags fields. On failure the structure remains unchanged. When match.type is V4L2_CHIP_MATCH_BRIDGE, match.addr selects the nth bridge 'chip' on the TV card. You can enumerate all chips by starting at zero and incrementing match.addr by one until VIDIOC_DBG_G_CHIP_NAME fails with an &EINVAL;. The number zero always selects the bridge chip itself, ⪚ the chip connected to the PCI or USB bus. Non-zero numbers identify specific parts of the bridge chip such as an AC97 register block. When match.type is V4L2_CHIP_MATCH_SUBDEV_NAME, match.name contains the name of a sub-device. For instance "saa7127 6-0044" will match the saa7127 sub-device at the given i2c bus. This match type is not very useful for this ioctl and is here only for consistency. When match.type is V4L2_CHIP_MATCH_SUBDEV_IDX, match.addr selects the nth sub-device. This allows you to enumerate over all sub-devices. On success, the name field will contain a chip name and the flags field will contain V4L2_CHIP_FL_READABLE if the driver supports reading registers from the device or V4L2_CHIP_FL_WRITABLE if the driver supports writing registers to the device. We recommended the v4l2-dbg utility over calling this ioctl directly. It is available from the LinuxTV v4l-dvb repository; see http://linuxtv.org/repo/ for access instructions. &cs-ustr; __u32 type See for a list of possible types. union (anonymous) __u32 addr Match a chip by this number, interpreted according to the type field. char name[32] Match a chip by this name, interpreted according to the type field. &cs-str; struct v4l2_dbg_match match How to match the chip, see . char name[32] The name of the chip. __u32 flags Set by the driver. If V4L2_CHIP_FL_READABLE is set, then the driver supports reading registers from the device. If V4L2_CHIP_FL_WRITABLE is set, then it supports writing registers. __u32 reserved[8] Reserved fields, both application and driver must set these to 0. &cs-def; V4L2_CHIP_MATCH_BRIDGE 0 Match the nth chip on the card, zero for the bridge chip. Does not match sub-devices. V4L2_CHIP_MATCH_I2C_DRIVER 1 Match an &i2c; chip by its driver name. Can't be used with this ioctl. V4L2_CHIP_MATCH_I2C_ADDR 2 Match a chip by its 7 bit &i2c; bus address. Can't be used with this ioctl. V4L2_CHIP_MATCH_AC97 3 Match the nth anciliary AC97 chip. Can't be used with this ioctl. V4L2_CHIP_MATCH_SUBDEV_NAME 4 Match the sub-device by name. V4L2_CHIP_MATCH_SUBDEV_IDX 5 Match the nth sub-device. &return-value; EINVAL The match_type is invalid or no device could be matched.