From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: linux-media@vger.kernel.org,
Jean-Francois Moine <moinejf@free.fr>,
linux-input@vger.kernel.org,
Johann Deneux <johann.deneux@gmail.comx>,
Anssi Hannula <anssi.hannula@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 0/3] gspca - ov534: saturation and hue (using fixp-arith.h)
Date: Mon, 23 Apr 2012 09:17:34 -0700 [thread overview]
Message-ID: <20120423161734.GB29290@core.coreip.homeip.net> (raw)
In-Reply-To: <1335187267-27940-1-git-send-email-ospite@studenti.unina.it>
On Mon, Apr 23, 2012 at 03:21:04PM +0200, Antonio Ospite wrote:
> Hi,
>
> here are a couple more of controls for the gspca ov534 subdriver.
>
> In order to control the HUE value the sensor expects sin(HUE) and
> cos(HUE) to be set so I decided to reuse the fixed point implementation
> of sine and cosine from drivers/input/fixp-arith.h, see patches 2 and 3.
>
> Dmitry, can the movement of fixp-arith.h in patch 2 go via the media
> tree? That should ease up the integration of patch 3 in this series
> I think.
Yep, this is fine with me.
>
> Jonathan, maybe fixp_sin() and fixp_cos() can be used in
> drivers/media/video/ov7670.c too where currently ov7670_sine() and
> ov7670_cosine() are defined, but I didn't want to send a patch I could
> not test.
>
> BTW What is the usual way to communicate these cross-subsystem stuff?
> I CC-ed everybody only on the cover letter and on patches 2 and 3 which
> are the ones concerning somehow both "input" and "media".
>
> Thanks,
> Antonio
>
>
> Antonio Ospite (3):
> [media] gspca - ov534: Add Saturation control
> Input: move drivers/input/fixp-arith.h to include/linux
> [media] gspca - ov534: Add Hue control
>
> drivers/input/ff-memless.c | 3 +-
> drivers/input/fixp-arith.h | 87 ------------------------------------
> drivers/media/video/gspca/ov534.c | 89 ++++++++++++++++++++++++++++++++++++-
> include/linux/fixp-arith.h | 87 ++++++++++++++++++++++++++++++++++++
> 4 files changed, 176 insertions(+), 90 deletions(-)
> delete mode 100644 drivers/input/fixp-arith.h
> create mode 100644 include/linux/fixp-arith.h
>
> --
> Antonio Ospite
> http://ao2.it
>
> A: Because it messes up the order in which people normally read text.
> See http://en.wikipedia.org/wiki/Posting_style
> Q: Why is top-posting such a bad thing?
--
Dmitry
next prev parent reply other threads:[~2012-04-23 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 13:21 [PATCH 0/3] gspca - ov534: saturation and hue (using fixp-arith.h) Antonio Ospite
2012-04-23 13:21 ` [PATCH 2/3] Input: move drivers/input/fixp-arith.h to include/linux Antonio Ospite
2012-04-23 16:16 ` Dmitry Torokhov
2012-04-23 13:21 ` [PATCH 3/3] [media] gspca - ov534: Add Hue control Antonio Ospite
2012-04-23 13:31 ` [PATCH 0/3] gspca - ov534: saturation and hue (using fixp-arith.h) Antonio Ospite
2012-04-23 16:17 ` Dmitry Torokhov [this message]
2012-04-23 20:16 ` Jonathan Corbet
2012-04-30 13:51 ` Antonio Ospite
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=20120423161734.GB29290@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=anssi.hannula@gmail.com \
--cc=corbet@lwn.net \
--cc=johann.deneux@gmail.comx \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=moinejf@free.fr \
--cc=ospite@studenti.unina.it \
/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;
as well as URLs for NNTP newsgroup(s).