Hi Tomi, On Thu, Sep 5, 2024 at 10:11 AM Tomi Valkeinen <tomi.valkeinen@xxxxxxxxxxxxxxxx> wrote: > <snip> > > I think you actually want 1/0->0/0 routing. The error says that the sink > > side device has routing which does not have a stream at stream ID 1, or > > no routing support at all, which implies a single stream at stream ID 0. > > Looking at patch 12, there's something wrong with the approach here. Are > you perhaps trying to define the CSI-2 VC with the streams? > Yes, based on the previous feedback received, I am implementing virtual channels as streams. If this isn't the correct approach can you please guide me on what we should be using to support virtual channels? > If you have a camera with a single image stream coming from an internal > pad, you should have one hardcoded route, 1/0->0/0. The > .get_frame_desc() should return the CSI-2 VC (most likely always 0) and > DT (based on the format) for that stream. > Agreed. > If you also have embedded data, then you'd have another internal pad > (pad number 2), and the routing would be: > > 1/0->0/0 > 2/0->0/1 > > And here .get_frame_desc() would also handle the second stream, and most > likely for that stream the VC would also be 0. > Ok agreed. > The stream ID in the routing table is a software level concept, not > related to the VC. > > Also, the internal pad should use the sensor's native format, not > UYVY8_1X16. > Ok, I will update it to MEDIA_BUS_FMT_SBGGR10_1X10. Cheers, Prabhakar
