Hi!
> > Plus you might want to describe which port correspond to which gpio
> > state/bitfield values...
> >
> > > +struct vidsw {
> >
> > I knew it: it is secretely a switch! :-).
>
> This driver started as a two-input gpio controlled bus switch.
> I changed the name when adding support for bitfield controlled
> multiplexers with more than two inputs.
We had discussion with Sakari / Rob whether gpio controlled thing is a
switch or a multiplexer :-).
> > > + if (!pad) {
> > > + /* Mirror the input side on the output side */
> > > + cfg->type = vidsw->endpoint[vidsw->active].bus_type;
> > > + if (cfg->type == V4L2_MBUS_PARALLEL ||
> > > + cfg->type == V4L2_MBUS_BT656)
> > > + cfg->flags = vidsw->endpoint[vidsw->active].bus.parallel.flags;
> > > + }
> >
> > Will this need support for other V4L2_MBUS_ values?
>
> To support CSI-2 multiplexers, yes.
Can you stick switch () { .... default: dev_err() } there, to help
future hackers?
Thank,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
