[07:52] <sailus> hverkuil: Would you be happy with me considering adv748x a sensor driver? :-)
[08:00] <hverkuil> sailus: no, it's definitely distinct from a sensor. Bridge drivers will need to explicitly support such devices by supporting the right ops and being able to handle connect/disconnect/EDID.
[08:09] <sailus> hverkuil: You'll then continue to handle patches related to it, right?
[08:35] <hverkuil> sailus: yes
[08:35] <hverkuil> Anything HDMI related is mine :-)
[09:06] <sailus> hverkuil: I'd like to say the same about CSI-2.
[09:06] <sailus> This chip does both.
[09:07] <sailus> I'd like to review the patches first before you apply them if there are CSI-2 related changes.
[09:08] <hverkuil> Ah, CSI. Yes, this should be a co-production then. You look at the CSI-2 change, I look at the HDMI part.
[09:10] <hverkuil> Why these questions? Are there any outstanding adv7482 patches that touch on csi2?
[09:20] <sailus> hverkuil: No. I was just wondering whether I should look into the adv748x patches in general.
[09:20] <sailus> Well, they're relevant to me from async / fwnode point of view, too.
[09:20] <sailus> It's a single device with multiple source pads, therefore also multiple ports.
[09:44] <hverkuil> sailus: what do you prefer: keep an eye out for such patches yourself, or do you want me to ping you when I think you need to review as well?
[10:44] <sailus> hverkuil: I'll try to review them, sure. But I could miss them, too.
[10:44] <sailus> I'd be happy to be pinged.
[15:57] *** benjiG has left