From: Chia-I Wu <olvaffe@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: video4linux-list@redhat.com, noodles@earth.li,
qce-ga-devel@lists.sourceforge.net
Subject: Re: Please test the gspca-stv06xx branch
Date: Fri, 28 Nov 2008 12:26:32 +0800 [thread overview]
Message-ID: <20081128042632.GA15343@m500.domain> (raw)
In-Reply-To: <492EE597.7010100@redhat.com>
On Thu, Nov 27, 2008 at 07:23:19PM +0100, Hans de Goede wrote:
> Exactly, so the functions belong in the bridge code, and if those
> functions are properly written and prototyped, then they should be
> directly usable from the sensor without requiring convoluting macros
> around them. The only reason and acceptable use I see for using macro's
> here would be to simplify the error handling as is currently done in the
> other 2 sensor code files.
Each sensor could have a slightly different way to access the registers.
The bridge is responsible to provide means to ease the work needed in
the sensor drivers.
When 046d:0850 tries to write to its registers, it could
* have a wrapper which calls the helper function _AND_ write to reg
0x1704 of the bridge (the extra packet). Or,
* simply call the helper function. The helper function checks the
product id and send a second control message automatically.
I see the logics belong to the sensor driver and prefer the first
method, while you might see the second method easier to use.
My point is, a wrapper is not a big *NO*. Instead, it is a good
practice, even if there is no sensor-specific logics involved.
> I greatly appreciate your efforts, but please try to constrain yourself
> the programming model / pragma's followed through out gspca.
I would like to rebase the patch against current tip, or your changes
once they are merged.
--
Regards,
olv
--
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:[~2008-11-28 4:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 21:00 Please test the gspca-stv06xx branch Erik Andrén
2008-11-25 8:20 ` Chia-I Wu
2008-11-25 11:22 ` Erik Andrén
2008-11-25 11:39 ` Chia-I Wu
2008-11-25 12:02 ` Erik Andrén
[not found] ` <492E7906.905@redhat.com>
2008-11-27 10:59 ` Chia-I Wu
2008-11-27 11:55 ` Erik Andrén
2008-11-27 16:00 ` Chia-I Wu
[not found] ` <492EE597.7010100@redhat.com>
2008-11-28 4:26 ` Chia-I Wu [this message]
2008-11-27 11:51 ` Erik Andrén
2008-11-27 18:08 ` Hans de Goede
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=20081128042632.GA15343@m500.domain \
--to=olvaffe@gmail.com \
--cc=hdegoede@redhat.com \
--cc=noodles@earth.li \
--cc=qce-ga-devel@lists.sourceforge.net \
--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: link
Be 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.