Hi Tomi On Thu, Mar 17, 2022 at 09:18:42AM +0200, Tomi Valkeinen wrote: > On 16/03/2022 11:04, Jacopo Mondi wrote: > > Hi Tomi > > > > On Tue, Mar 01, 2022 at 06:11:45PM +0200, Tomi Valkeinen wrote: > > > Add documentation related to multiplexed streams. > > > > > > Signed-off-by: Tomi Valkeinen <tomi.valkeinen@xxxxxxxxxxxxxxxx> > > > --- > > > .../driver-api/media/v4l2-subdev.rst | 8 + > > > .../userspace-api/media/v4l/dev-subdev.rst | 165 ++++++++++++++++++ > > > 2 files changed, 173 insertions(+) > > > > > > diff --git a/Documentation/driver-api/media/v4l2-subdev.rst b/Documentation/driver-api/media/v4l2-subdev.rst > > > index 115211cef4d1..80654f1bcac9 100644 > > > --- a/Documentation/driver-api/media/v4l2-subdev.rst > > > +++ b/Documentation/driver-api/media/v4l2-subdev.rst > > > @@ -593,6 +593,14 @@ before calling v4l2_subdev_init_finalize(): > > > > > > This shares the driver's private mutex between the controls and the states. > > > > > > +Streams, multiplexed media pads and internal routing > > > +---------------------------------------------------- > > > + > > > +A subdevice driver can implement support for multiplexed streams by setting > > > > Let me start by being picky with a minor thing: the rest of the > > documentation seems to use "sub-device". Here you have "sub-device", > > "subdevice" and "subdev". I think "sub-device" should be used > > everywhere > > I can see lots of all those three in the docs, so I don't really know which > one to pick... > You're right, the number of "subdev" entries is larger that what I first thought. Let's keep using whatever then :)
