1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
Multimedia-chat-meeting-2017-08-17
10:04 < pinchartl> let's start with status updates
10:05 < pinchartl> kbingham: I've submitted my update to myself way ahead of everybody else ;-)
10:05 < kbingham> hehe
10:05 < pinchartl> I'll start by reporting for Niklas
10:05 < pinchartl> since last meeting:
10:06 < pinchartl> - - Working Virtual channel prototype for both onboard ADV748x and MAX9286 board. - [PATCH 0/4] 8 camera setup fixes - [PATCH 00/20] Add multiplexed media pads to support CSI-2 virtual channels - [PATCH 0/8] v4l: max9286: enable virtual channels
10:06 < pinchartl> - New base for onboard VIN component development tag, rcar-vin-elinux-v12.
10:06 < pinchartl> (apoogies for the weird copy and paste)
10:06 < pinchartl> until next meeting:
10:06 < pinchartl> - Keep pushing for the incremental async and other dependencies for the CSI-2 patches to be pushed up.
10:06 < pinchartl> - Make another drive to try and get attention to the VIN patches (will post new version once I'm back from my vacation).
10:06 < pinchartl> issues and blockers: none
10:07 < pinchartl> that's it
10:07 < pinchartl> next, uli___
10:07 < uli___> tl;dr: chromebook works, headlessly
10:08 < uli___> funny DT that expects one device to be probed twice does not
10:08 < pinchartl> you mentioned that the culprit was an incorrect regulator voltage in DT. will you submit a patch for that ?
10:08 < uli___> that's in the elm board dts, that's not upstream
10:09 < pinchartl> will you submit the elm board dts upstream ? :-)
10:09 < uli___> i would submit that in its entirety once i have figured out how the mmsys probing is supposed to work
10:09 < pinchartl> sounds good to me
10:09 < geertu> uli___: For one device to be probed twice, you should either have a single driver that registers both driver typesm or use mfd
10:09 < geertu> s/typesm/types,/
10:10 < uli___> any ideas why the dsi defers, but is never retried?
10:11 < pinchartl> uli___: no, but that should be easy to debug
10:12 < pinchartl> you mentioned that the mmsys device is both a DRM device and a clock controller
10:12 < uli___> yes
10:13 < pinchartl> that's pretty strange
10:14 < uli___> i know :) it provides clocks for the various display-related devices
10:14 < geertu> Looks like the simplest is to move the clock driver into the DRM device driver?
10:14 < pinchartl> there's no mention of that in the mediatek DRM DT bindings
10:14 < pinchartl> please contact upstream developers to sort it out
10:15 < uli___> the upstream stuff doesn't have the display-related things
10:15 < pinchartl> I mean the upstream mediatek developers
10:16 < pinchartl> the same compat string is indeed used by both the clock driver and the DRM driver
10:16 < pinchartl> and the display DT bindings don't document that compat string
10:16 < uli___> it looks like half of the display support made it in, there is also a lone drm regulator in the dts that is not used anywhere
10:16 < pinchartl> it's a big WTF, you can ask the DRM driver maintainers and CC the dri-devel mailing list
10:17 < uli___> i'll check the archives, there must have been some discussion on that
10:18 < pinchartl> I wouldn't be surprised if it had been overlooked
10:18 < pinchartl> DRM maintainers are x86-centered
10:19 < pinchartl> anything else to report ?
10:19 < uli___> that's it
10:19 < pinchartl> thank you
10:19 < pinchartl> kbingham: you're next
10:19 < kbingham> Well, I've only had 5 working days since the last meeting,
10:19 < kbingham> In that time I got the display list caching implementation working, and based on top of the tlb-optimise patchset. Then posted for renesas-drivers.
10:19 < kbingham> My 'next' task will be dependant upon the additional tasks disucssion :)
10:19 < kbingham> --
10:19 < kbingham> EOT.
10:19 < kbingham> Ahh preprepared statement. Such fast.
10:20 < kbingham> :D
10:20 < pinchartl> thank you :-)
10:20 < pinchartl> my turn
10:20 -!- Irssi: Pasting 11 lines to #periperi. Press Ctrl-K if you wish to do this or Ctrl-C to cancel.
10:20 < pinchartl> Since last meeting:
10:20 < pinchartl> - Extended the DU test suite
10:20 < pinchartl> - DU and VSP fixes for issues found by the DU test suite
10:20 < pinchartl> - MAX9286 support for multiple CSI-2 virtual channel streams
10:20 < pinchartl> For the next two weeks:
10:20 < pinchartl> - Patch review
10:20 < pinchartl> - Next additional tasks (to be decided)
10:20 < pinchartl> Issues and Blockers: None
10:20 < pinchartl> that's it for me as well :-)
10:21 < pinchartl> that's it for status updates
10:21 < pinchartl> I wanted to discuss the face to face meeting agenda as the next topic
10:21 < pinchartl> but we don't have the quorum
10:22 < pinchartl> so I propose moving that discussion to e-mail
10:22 < kbingham> +1
10:22 < kbingham> Do I recall that we won't have a meeting on #PeriPeri now before San Seb?
10:22 < pinchartl> that's what I was going to propose
10:22 < wsa_> I'd vote for that
10:22 < pinchartl> the next meeting should in theory be on the 31st of August, I propose skipping it
10:23 < kbingham> At this stage that seems to be reasonable.
10:23 < geertu> +1
10:23 < kbingham> In terms of our F2F ... I see we have a disucssion on what to bring. Would you like me to bring the 8 camera setup ?
10:24 < pinchartl> I'm afraid I'd like you to
10:24 < kbingham> Ok - I'll do what I can.
10:24 < kbingham> :D
10:24 < pinchartl> the last topic to discuss today is additional tasks for Q3/2
10:24 < pinchartl> I've submitted proposals to Magnus and I'm waiting for his reply
10:25 < pinchartl> I expect at least DU suspend/resume to be included
10:25 < wsa_> ditto
10:25 < pinchartl> uli___: do you have slots assigned to the I/O or core group for Q3/2 ?
10:26 < uli___> i/o, sort of; we still have to check if that task is viable, but let's assume it is
10:26 < pinchartl> how much time do you have left unassigned ?
10:26 < uli___> wsa_: what's the plan for the sampling point task?
10:26 < uli___> 5 days?
10:27 < wsa_> yup
10:27 < uli___> 10 days left then
10:27 < pinchartl> ok
10:27 < pinchartl> as usual, if there are items you would like to work on, please let let know
10:27 < pinchartl> that comment is valid for all members of course
10:28 < pinchartl> but Jacopo, Kieran, and Niklas already tell me about what they'd like to work on :-)
10:28 < pinchartl> I'd like to have your feedback on that too
10:28 < wsa_> uli___: if it doesn't take 5 days alone on the test setup procedure ;)
10:29 < uli___> that is something i'm still in the process of figuring out...
10:29 < wsa_> uli___: but that's the on-going investigation, right?
10:29 < uli___> yes
10:29 < pinchartl> any other topic we should discuss ?
10:30 < kbingham> None here.
10:30 < pinchartl> that's it for multimedia then. thank you all for attending
|
