On Wed, 19 Jan 2011, Jarod Wilson wrote: > On Jan 19, 2011, at 8:20 AM, Mike Isely wrote: > > > This probing behavior does not happen for HVR-1950 (or HVR-1900) since > > there's only one possible IR configuration there. > > Just to be 100% clear, the device I'm poking it is definitely an > HVR-1950, using ir_scheme PVR2_IR_SCHEME_ZILOG, so the probe bits > shouldn't coming into play with anything I'm doing. Only just now > started looking at the pvrusb2 code. Wow, there's a LOT of it. ;)
Yes, and yes :-) The standalone driver version (which is loaded with ifdef's that allow compilation back to 2.6.11) makes the in-kernel driver look small by comparison. There is a fair degree of compartmentalization between the modules. The roadmap to what it does for just HVR-1950 you can find by first looking at the declarations in pvrusb2-devattr.h and then the device-specific configurations in pvrusb2-devattr.c. From there you can usually grep your way around to see how those configuration bits affect the rest of the driver. Most of the really fun stuff is in pvrusb2-hdw.c. Pretty much everything else supports or uses that central component. The actual stuff which deals with I2C is not that large. Beyond making the access possible at all, the driver largely just tries to stay out of the way of external logic that needs to reach the bus. -Mike -- Mike Isely isely @ isely (dot) net PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8 -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
