From: Domenico Andreoli <cavokz@gmail.com>
To: David Brownell <david-b@pacbell.net>
Cc: video4linux-list@redhat.com, Michael Buesch <mb@bu3sch.de>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [PATCH v3] Add bt8xxgpio driver
Date: Mon, 14 Jul 2008 07:25:56 +0200 [thread overview]
Message-ID: <20080714052556.GA3470@ska.dandreoli.com> (raw)
In-Reply-To: <200807131300.35126.david-b@pacbell.net>
On Sun, Jul 13, 2008 at 01:00:34PM -0700, David Brownell wrote:
> On Sunday 13 July 2008, Domenico Andreoli wrote:
> > Something respecting these conditions clearly conflicts with bttv
> > and looks like your bt8xxgpio driver. Indeed I do not see the need of
> > dropping it.
> >
> > Currently my patch requires the bttv functionality, since it is done
> > to work toghether with bttv. Surely one must be able to use bttv only,
> > without gpiolib.
>
> Just an idea ... I tend to agree that Michael's GPIO-only scenario
> is atypical for these chips.
I am facing another atipical scenario (I am writing the initialization
of bttv gpiolib sub-driver).
Say that a given card has 4 relays attached to its GPIOs. Only the
card's driver may know about these relays and only the driver should
be able to set those GPIO directions. Moreover, driver should prevent
direction change for them, which are intended for output only.
While I figure out how to prevent user direction tampering, how about
making gpiolib know which are the initial directions?
cheers,
Domenico
-----[ Domenico Andreoli, aka cavok
--[ http://www.dandreoli.com/gpgkey.asc
---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50
--
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-07-14 5:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200807101914.10174.mb@bu3sch.de>
[not found] ` <20080710160258.4ddb5c61@gaivota>
2008-07-13 0:42 ` [PATCH v3] Add bt8xxgpio driver Domenico Andreoli
[not found] ` <200807131215.12082.mb@bu3sch.de>
2008-07-13 15:43 ` Domenico Andreoli
[not found] ` <200807131808.35599.mb@bu3sch.de>
2008-07-13 16:39 ` Domenico Andreoli
2008-07-15 8:46 ` Trent Piepho
[not found] ` <200807131300.35126.david-b@pacbell.net>
2008-07-14 5:25 ` Domenico Andreoli [this message]
[not found] ` <200807132259.54360.david-b@pacbell.net>
2008-07-14 7:27 ` Domenico Andreoli
[not found] ` <200807141558.29582.mb@bu3sch.de>
2008-07-14 15:25 ` Domenico Andreoli
[not found] ` <200807140926.28592.david-b@pacbell.net>
2008-07-14 17:08 ` Domenico Andreoli
[not found] ` <200807141951.39810.mb@bu3sch.de>
2008-07-14 19:21 ` Domenico Andreoli
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=20080714052556.GA3470@ska.dandreoli.com \
--to=cavokz@gmail.com \
--cc=david-b@pacbell.net \
--cc=mb@bu3sch.de \
--cc=mchehab@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox