From: "DongSoo(Nathaniel) Kim" <dongsoo.kim@gmail.com> To: "Aguirre Rodriguez, Sergio Alberto" <saaguirre@ti.com> Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>, "video4linux-list@redhat.com" <video4linux-list@redhat.com>, "Nagalla, Hari" <hnagalla@ti.com>, Sakari Ailus <sakari.ailus@nokia.com>, "Tuukka.O Toivonen" <tuukka.o.toivonen@nokia.com>, "linux-media@vger.kernel.org" <linux-media@vger.kernel.org> Subject: Re: [REVIEW PATCH 09/14] OMAP: CAM: Add ISP Core Date: Mon, 2 Mar 2009 17:09:54 +0900 [thread overview] Message-ID: <5e9665e10903020009y7fe7d0d0j356708e1c3149cac@mail.gmail.com> (raw) In-Reply-To: <A24693684029E5489D1D202277BE894416429F9F@dlee02.ent.ti.com> Hello, reviewing ISP driver, I found that we've got no querymenu support in ISP and also omap3 camera interface driver. +/** + * struct vcontrol - Video control structure. + * @qc: V4L2 Query control structure. + * @current_value: Current value of the control. + */ +static struct vcontrol { + struct v4l2_queryctrl qc; + int current_value; +} video_control[] = { <snip> + { + { + .id = V4L2_CID_PRIVATE_ISP_COLOR_FX, + .type = V4L2_CTRL_TYPE_INTEGER, + .name = "Color Effects", + .minimum = PREV_DEFAULT_COLOR, + .maximum = PREV_BW_COLOR, + .step = 1, + .default_value = PREV_DEFAULT_COLOR, + }, + .current_value = PREV_DEFAULT_COLOR, + } +}; I think we should make it menu type for this color FX control. If that kind of control has no menu information, user has no way to figure out what kind of FX supported by device. BTW if we make querymenu support in omap3 camera subsystem, we should make querymenu support for v4l2 int device also. I think I've seen before a patch which intent to use querymenu in v4l2 int device, but no patch for omap3 ISP and camera interface. Can I make a patch and post on linux-omap, linux-media list? of course if you don't mind. Or...am I digging wrong way? I mean.. querymenu for omap3 camera subsystem. Please let me know :) Cheers, Nate -- ======================================================== DongSoo(Nathaniel), Kim Engineer Mobile S/W Platform Lab. Telecommunication R&D Centre Samsung Electronics CO., LTD. e-mail : dongsoo.kim@gmail.com dongsoo45.kim@samsung.com ========================================================
WARNING: multiple messages have this Message-ID (diff)
From: "DongSoo(Nathaniel) Kim" <dongsoo.kim@gmail.com> To: "Aguirre Rodriguez, Sergio Alberto" <saaguirre@ti.com> Cc: "video4linux-list@redhat.com" <video4linux-list@redhat.com>, Sakari Ailus <sakari.ailus@nokia.com>, "Nagalla, Hari" <hnagalla@ti.com>, "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>, "Tuukka.O Toivonen" <tuukka.o.toivonen@nokia.com>, "linux-media@vger.kernel.org" <linux-media@vger.kernel.org> Subject: Re: [REVIEW PATCH 09/14] OMAP: CAM: Add ISP Core Date: Mon, 2 Mar 2009 17:09:54 +0900 [thread overview] Message-ID: <5e9665e10903020009y7fe7d0d0j356708e1c3149cac@mail.gmail.com> (raw) In-Reply-To: <A24693684029E5489D1D202277BE894416429F9F@dlee02.ent.ti.com> Hello, reviewing ISP driver, I found that we've got no querymenu support in ISP and also omap3 camera interface driver. +/** + * struct vcontrol - Video control structure. + * @qc: V4L2 Query control structure. + * @current_value: Current value of the control. + */ +static struct vcontrol { + struct v4l2_queryctrl qc; + int current_value; +} video_control[] = { <snip> + { + { + .id = V4L2_CID_PRIVATE_ISP_COLOR_FX, + .type = V4L2_CTRL_TYPE_INTEGER, + .name = "Color Effects", + .minimum = PREV_DEFAULT_COLOR, + .maximum = PREV_BW_COLOR, + .step = 1, + .default_value = PREV_DEFAULT_COLOR, + }, + .current_value = PREV_DEFAULT_COLOR, + } +}; I think we should make it menu type for this color FX control. If that kind of control has no menu information, user has no way to figure out what kind of FX supported by device. BTW if we make querymenu support in omap3 camera subsystem, we should make querymenu support for v4l2 int device also. I think I've seen before a patch which intent to use querymenu in v4l2 int device, but no patch for omap3 ISP and camera interface. Can I make a patch and post on linux-omap, linux-media list? of course if you don't mind. Or...am I digging wrong way? I mean.. querymenu for omap3 camera subsystem. Please let me know :) Cheers, Nate -- ======================================================== DongSoo(Nathaniel), Kim Engineer Mobile S/W Platform Lab. Telecommunication R&D Centre Samsung Electronics CO., LTD. e-mail : dongsoo.kim@gmail.com dongsoo45.kim@samsung.com ======================================================== -- video4linux-list mailing list Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2009-03-02 8:09 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <Acl1IyATAKAzUiSPQiOOAI2yzi0iWQ==> 2009-01-13 2:03 ` [REVIEW PATCH 09/14] OMAP: CAM: Add ISP Core Aguirre Rodriguez, Sergio Alberto 2009-03-02 8:09 ` DongSoo(Nathaniel) Kim [this message] 2009-03-02 8:09 ` DongSoo(Nathaniel) Kim 2009-03-02 19:37 ` Aguirre Rodriguez, Sergio Alberto 2009-03-02 23:12 ` DongSoo(Nathaniel) Kim 2009-03-02 23:12 ` DongSoo(Nathaniel) Kim 2009-03-03 7:09 ` Sakari Ailus 2009-03-03 7:09 ` Sakari Ailus
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=5e9665e10903020009y7fe7d0d0j356708e1c3149cac@mail.gmail.com \ --to=dongsoo.kim@gmail.com \ --cc=hnagalla@ti.com \ --cc=linux-media@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=saaguirre@ti.com \ --cc=sakari.ailus@nokia.com \ --cc=tuukka.o.toivonen@nokia.com \ --cc=video4linux-list@redhat.com \ /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: linkBe 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.