Hi, If MFC(encoder/decoder) has a single node, how to know application's object before VIDIOC_S_FMT calling ? VIDIOC_S_CTRL can be called before VIDIOC_S_FMT. For example user wants to use MFC as an *encoder*, but user calls VIDIOC_S_CTRL with *decoder* command by mistake. In that case driver cannot return fail because it cannot know the purpose before VIDIOC_S_FMT calling. When VIDIOC_S_FMT is called to use MFC as an *encoder* after VIDIOC_S_CTRL, driver will be confused how to handle it. But in two nodes solution decoder command via VIDIOC_S_CTRL will be failed on encoder device node. -- Best regards, Jonghun Han -- > -----Original Message----- > From: linux-media-owner@xxxxxxxxxxxxxxx [mailto:linux-media- > owner@xxxxxxxxxxxxxxx] On Behalf Of Pawel Osciak > Sent: Sunday, December 05, 2010 7:55 AM > To: Kamil Debski > Cc: Hans Verkuil; Jonghun Han; Laurent Pinchart; jaeryul.oh@xxxxxxxxxxx; linux- > media@xxxxxxxxxxxxxxx > Subject: Re: RFC: Problem of using v4l2 spec with codec function > > Hi all, > I would side with Laurent on this. Judging by formats seems to be > enough for this driver and it has great, in my opinion, advantages of > a) not overcomplicating things for applications b) not adding new > pieces to the API... > > -- > Best regards, > Pawel Osciak > -- > 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
