Hi, > -----Original Message----- > From: linux-media-owner@xxxxxxxxxxxxxxx [mailto:linux-media- > owner@xxxxxxxxxxxxxxx] On Behalf Of Sylwester Nawrocki > Sent: Friday, March 11, 2011 4:44 AM > To: jtp.park@xxxxxxxxxxx > Cc: linux-media@xxxxxxxxxxxxxxx; laurent.pinchart@xxxxxxxxxxxxxxxx > Subject: Re: [PATCH/RFC 0/2] Support controls at the subdev file handler > level > > Hi, > > On 03/10/2011 10:56 AM, Jeongtae Park wrote: > > Hi, all. > > > > Some hardware need to handle per-filehandle level controls. > > Hans suggests add a v4l2_ctrl_handler struct v4l2_fh. It will be work > fine. > > Although below patch series are for subdev, but it's great start point. > > I will try to make a patch. > > > > If v4l2 control framework can be handle per-filehandle controls, > > a driver could be handle per-buffer level controls also. (with VB2 > callback > > operation) > > > > Can you elaborate to what kind of per buffer controls are you referring to? > Using optional meta data planes is expected to be a proper way to do such > things. Either to pass meta data from application to driver or in the > opposite > direction. > > I can't see how the per buffer controls can be dependent on a per file > handle > control support. Perhaps this is only specific to some selected devices. > There might be some missing point about this issue. To support full feature of codec, hierarchy should be done as below Per-node(decoder or encoder) | |---- Per-file for multi-instance | |--------Per-buffer control for setting dynamic configuration Some cases are using per-node handling is enough, but some cases are for per-file And because of codec characteristics, we need to support per-buffer at this hierarchy as above. Let's talk more about this at Warsaw. > -- > Regards, > Sylwester Nawrocki > > -- > To unsubscribe from this list: send the line "unsubscribe linux-media" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
