From: Andreas Oberritter <obi@xxxxxxxxxxx> > > The best would be to create independent adapters for each independent CA > > device (ca0/caio0 pair) - they are independent after all (physically and > > in the way they're used). > > Physically, it's a general purpose TS I/O interface of the nGene > chipset. It just happens to be connected to a CI slot. On another board, > it might be connected to a modulator or just to some kind of socket. > > If the next version gets a connector for two switchable CI modules, then > the physical independence is gone. You'd have two ca nodes but only one > caio node. Or two caio nodes, that can't be used concurrently. > > Maybe the next version gets the ability to directly connect the TS input > from the frontend to the TS output to the CI slot to save copying around > the data, by using some kind of pin mux. Not physically independent either. > > It just looks physically independent in the one configuration > implemented now. When I read the cxd2099ar datasheet, I can see that in dual slot configuration, there is still one communication channel for the TS and one for the control. Also, it seems linux en50221 stack provides for the slot selection. So, why would you need two ca nodes ? -- 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
