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
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
|
Multimedia-chat-meeting-2019-06-06
10:05 < pinchartl> welcome to the multimedia meeting
10:05 < pinchartl> Topic 1. Status Check for the Multimedia Tasks
10:05 < pinchartl> * Jacopo
10:05 < pinchartl> Since last meeting:
10:05 < pinchartl> - CMM driver upport
10:05 < pinchartl> Work in progress, can srt LUT on the CMM using KMS properties.
10:05 < pinchartl> - Patch review
10:05 < pinchartl> Until next meeting:
10:05 < pinchartl> - Send v2 of the CMM series
10:05 < pinchartl> - Face to face Meeting with Sakari Ailus
10:05 < pinchartl> Will discuss V4L2 multiplexed streams support using GMSL as an example.
10:05 < pinchartl> Issues and blockers: None
10:05 < pinchartl> jmondi: any comment ?
10:06 < jmondi> pinchartl: not really
10:06 < jmondi> apart that I plan to send CMM patches this morning after the cleanup
10:07 < pinchartl> nice !
10:07 < pinchartl> thank you
10:07 < jmondi> I welcome comments from you and anyone in the MM team on the v4l2-multiplexing issue since I will have to meet Sakari
10:07 < jmondi> and I will have some question for you on DRM/KMS APIs, but we can bring them offline
10:07 < jmondi> and that was a "not really" not really comment
10:07 < pinchartl> let's schedule a discussion for that before you meet with Sakari then. could you send a mail to propose a date and time ?
10:07 < jmondi> indeed
10:08 < pinchartl> thanks
10:08 < pinchartl> * Kieran
10:08 < pinchartl> Since last meeting: None
10:08 < pinchartl> Until next meeting:
10:08 < pinchartl> - Post a new (final?) PA-Phase series
10:08 < pinchartl> - Fix DU group refactoring series
10:08 < pinchartl> - Review the LVDS dual-link mode series
10:08 < pinchartl> Issues and blockers: None
10:08 < pinchartl> kbingham: any comment ?
10:09 < kbingham[m]> No, that's fine
10:09 < pinchartl> thank you
10:09 < pinchartl> * Morimoto-san
10:09 < pinchartl> Since last meeting:
10:09 < pinchartl> - ALSA SoC modern device support
10:09 < pinchartl> The patches seem to be blocked due to the ongoing USA-China trade war
10:09 < pinchartl> and export control restrictions related to Huawei.
10:09 < pinchartl> Until next meeting:
10:09 < pinchartl> - Continue with ALSA SoC work
10:09 < pinchartl> Issues and Blockers: None
10:10 < pinchartl> morimoto: any comment ?
10:10 < pinchartl> do you have more details on this Huawei-related issue ?
10:10 < pinchartl> were there discussions on a public mailing list ?
10:10 < morimoto> pinchartl: no I hear
10:10 < morimoto> I heared it at off-line
10:11 < morimoto> ALSA SoC maintatenor said the reason why he can't push new branch was related to it.
10:11 < morimoto> I'm not sure detail...
10:12 < pinchartl> it would be useful to get more information
10:12 < morimoto> and thanks. no comment for me
10:13 < morimoto> s/for/from
10:13 < pinchartl> if you receive any extra information, could you please share it ?
10:13 < morimoto> pinchartl: of course
10:13 < pinchartl> thank you
10:13 < pinchartl> * Laurent
10:13 < pinchartl> Since last meeting:
10:13 < pinchartl> - Vacation
10:13 < pinchartl> Until next meeting:
10:13 < pinchartl> - Get the LVDS dual-link prototype merged
10:13 < pinchartl> Issues and blockers: None
10:13 < pinchartl> (I had forgotten myself...)
10:13 < pinchartl> any question ?
10:14 * kbingham wonders how far the huawaei blockade will escalate.
10:14 < pinchartl> * Niklas
10:14 < pinchartl> Since last meeting:
10:14 < pinchartl> - Vacation
10:14 < pinchartl> Until next meeting:
10:14 < pinchartl> - Keep cleaning up the VIN crop and compose code
10:14 < pinchartl> This is needed to merge UDS and PM support.
10:14 < pinchartl> Issues and blockers: None
10:14 < pinchartl> neg: any comment ?
10:15 < neg> kbingham: you will no longer be allowed to use leaked datasheets in your work if the leak is from China... ;-P
10:15 < neg> no comment, thanks
10:15 < pinchartl> * Simon
10:15 < pinchartl> Since last meeting: None
10:15 < pinchartl> Until next meeting:
10:15 < pinchartl> - Upport of DT patches from the BSP (Kaneko-san)
10:15 < pinchartl> Issues and Blockers: None
10:15 < pinchartl> horms: any comment ?
10:15 < horms> I had hoped to report some progress, but there is none. I've pinged Kaneko-san again this morning
10:16 < pinchartl> * Ulrich
10:16 < pinchartl> Since last meeting: None
10:16 < pinchartl> Until next meeting: None
10:16 < pinchartl> Issues and Blockers: None
10:16 < pinchartl> uli_: any comment ?
10:16 < uli_> nope
10:16 < kbingham> neg, Until China buys softbank, and then owns Arm, and restricts all licenses of Arm products to prevent american companies from using it ... and then ...
10:16 < pinchartl> that's it for the status report then
10:17 < wsa> kbingham: that would be an interesting move!
10:17 < pinchartl> any discussion topic ?
10:17 < kbingham> wsa, I don't think Trump realises the scale of things he's playing with :)
10:18 < kbingham> No current mm topic for me at the moment.
10:18 < pinchartl> if there's nothing else to discuss, I propose adjourning this meeting. does anyone second ?
10:18 < neg> I have one quick
10:18 < pinchartl> sure
10:19 < neg> are you OK with me pushing periject patches for VIN + CSI-2 upporting status? Basically dropping all tasks not related to them from the periject patch I posted a few months back
10:20 < pinchartl> I'm totally fine with pushing the tasks we work on to periject, of course :-)
10:20 < neg> Or do you wish us to handle MM periupport -> periject in a more coordinated fashion ?
10:20 < jmondi> ah right, I should have asked how to handle CMM upporting too, with periject or periupport....
10:21 < pinchartl> jmondi: it's hardly an upporting task, you're more or less rewriting it :-)
10:21 < pinchartl> neg: I think everybody should manage the tickets related to the tasks they're working on
10:21 < neg> cool then I will push such patches before end of month per .jp request, thanks
10:22 < neg> No more questions from me
10:22 < jmondi> pinchartl: yeah, but it's something that's in BSP and that we're brining to mainline
10:22 < jmondi> but it's not in the periupport ticket
10:22 < pinchartl> neg: please make sure that the tasks are worded as tasks, not as an upport request
10:22 < pinchartl> jmondi: it's still not an upport :-)
10:23 < pinchartl> the fact that someone, somewhere, sometime, developed an out-of-tree driver doesn't make your new driver an upport
10:23 < jmondi> pinchartl: I see... to bad, I'm sure Japan would be happy if it was an upport :)
10:24 < pinchartl> they should be happier that it's not ;-)
10:24 < jmondi> (if you're referring to the Bosh patches, they're an "upport" from the Renesas 4.19 based BSP
10:25 < pinchartl> I'm referring to the fact that what we will upstream should be better than an upport
10:25 < jmondi> hopefully yes :)
10:26 < jmondi> anyway, I'm fine not having to create a periject task for it if not necessary!
10:26 < pinchartl> no, please create a periject task
10:27 < pinchartl> you're working on it, so it should have a task
10:27 * jmondi confused :)
10:27 < pinchartl> what's confusing ?
10:27 < jmondi> I thought it was to track upport only, but I'll do it anyhow!
10:27 < jmondi> sorry, I'm stealing time for nothing here
10:27 < pinchartl> no, periject is not about tracking upporting, it's a task manager
10:27 < pinchartl> unless I completely misunderstood it
10:28 < jmondi> I'm sure I did
10:28 < pinchartl> any other discussion topic, or should we adjourn this meeting ?
10:28 < morimoto> Yeah
10:28 < jmondi> please adjurn the meeting if you want to, I'll stop blathering
10:29 < pinchartl> morimoto: yeah to other discussion topic, or yeah to adjourning the meeting ?
10:29 < morimoto> for adjourning, sorry
10:29 < pinchartl> :-)
10:29 < pinchartl> meeting adjourned, thank you all for attending
|
