Franklin Meng wrote: > Devin, > >>> I'm actually not really concerned about it's >> interaction >>> with a demod. >>> I'm more worried about other products that have >>> saa711[345] that use >>> a bridge other than em28xx. The introduction of >> power >>> management >>> could always expose bugs in those bridges (I had this >>> problem in >>> several different cases where I had to fix problems >> in >>> other drivers >>> because of the introduction of power management). >>> > > I retested my device and tried several different GPIO sequences but so far every time I change between the Analog and digital interface, the SAA7113 needs to be reinitialized. This happens on several designs. In general, the gpio sequence will turn off either the analog or the digital part of the device, in order to save power and to avoid overheating the device. > I tried leaving both the digital and analog interfaces enabled by setting the GPIO to 7c but then the LG demod does not initialize. Don't do that. You may burn your device. > Either way it looks like I will have to reinitialize the device after switching between interfaces. The em28xx driver calls em28xx_set_mode(dev, EM28XX_ANALOG_MODE); when the device is opened in analog mode. It seems that we'll need some code there to also call the analog demod to re-initiate the device, after sending the gpio commands. > > Other than that do you want me to remove the suspend GPIO? Since I don't have the equipment to measure the power, > I don't know for a fact if the device really has been put in a suspend state or not. In suspend state, it will be cooler than when in normal state. It is better to keep the suspend state to increase the lifetime of the device. > > Thanks, > Franklin Meng > > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-media" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
