From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: video4linux-list@redhat.com
Subject: Re: [PATCH, RFC] mt9m111: allow data to be received on pixelclock falling edge?
Date: Mon, 10 Nov 2008 20:06:34 +0100 [thread overview]
Message-ID: <878wrr9z9h.fsf@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.64.0811101946200.8315@axis700.grange> (Guennadi Liakhovetski's message of "Mon\, 10 Nov 2008 19\:55\:53 +0100 \(CET\)")
Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
> I would prefer not to disregard camera flags. If we don't find a better
> solution, I would introduce platform inverter flags, and, I think, we
> better put them in camera platform data - not host platform data, to
> provide a finer granularity. In the end, inverters can also be located on
> camera boards, then you plug-in a different camera and, if your
> inverter-flags were in host platform data, it doesn't work again.
I'm of the same opinion.
I was thinking of another case : imagine the host needs to be configured on
rising edge, and camera on falling edge. Your patch wouldn't cover that devious
case.
I can't think of a better solution than an inverter flag as well. As this would
be very board specific, let it go in something board code sets up.
That's how it's already done for inverted gpio Vbus sensing in the USB stack for
the pxa for example.
--
Robert
--
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-10 19:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 11:59 [PATCH, RFC] mt9m111: allow data to be received on pixelclock falling edge? Antonio Ospite
2008-11-07 18:03 ` Robert Jarzmik
2008-11-08 20:36 ` Guennadi Liakhovetski
2008-11-09 22:59 ` Antonio Ospite
2008-11-10 18:55 ` Guennadi Liakhovetski
2008-11-10 19:06 ` Robert Jarzmik [this message]
2008-11-12 18:27 ` Antonio Ospite
2008-12-01 20:54 ` Guennadi Liakhovetski
2008-12-03 18:51 ` Antonio Ospite
2009-02-17 10:28 ` 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=878wrr9z9h.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=g.liakhovetski@gmx.de \
--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