Em Wed, 31 May 2017 09:44:53 +0100 Ramesh Shanmugasundaram <ramesh.shanmugasundaram@xxxxxxxxxxxxxx> escreveu: > +++ b/Documentation/media/v4l-drivers/max2175.rst > @@ -0,0 +1,60 @@ > +Maxim Integrated MAX2175 RF to bits tuner driver > +================================================ > + > +The MAX2175 driver implements the following driver-specific controls: > + > +``V4L2_CID_MAX2175_I2S_ENABLE`` > +------------------------------- > + Enable/Disable I2S output of the tuner. > + > +.. flat-table:: > + :header-rows: 0 > + :stub-columns: 0 > + :widths: 1 4 > + > + * - ``(0)`` > + - I2S output is disabled. > + * - ``(1)`` > + - I2S output is enabled. Hmm... There are other drivers at the subsystem that use I2S (for audio - not for SDR - but I guess the issue is similar). On such drivers, the bridge driver controls it directly, being sure that I2S is enabled when it is expecting some data coming from the I2S bus. On some drivers, there are both I2S and A/D inputs at the bridge chipset. On such drivers, enabling/disabling I2S is done via VIDIOC_S_INPUT (and optionally via ALSA mixer), being transparent to the user if the stream comes from a tuner via I2S or from a directly connected A/D input. I don't think it is a good idea to enable it via a control, as, if the bridge driver is expecting data via I2S, disabling it will cause timeouts at the videobuf handling. Thanks, Mauro -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html