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
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
|
<html>
<link rel="stylesheet" type="text/css" href="../../wiki/css">
<h1>Core-periperi-meeting-2017-09-06</h1>
<h2>PeriPeriCon – Core Group Meeting</h2>
<ul>
<li><i>Request from other team (for <span class="caps">KVM</span>)</i></li>
<li><span class="caps">IPMMU</span> features
<ul>
<li><span class="caps">IPMMU</span> current status
<ul>
<li>Context limitation not yet handled</li>
<li>Still many errata on H3/M3-W. D3 may be OK</li>
<li><span class="caps">TODO</span>
<ul>
<li>Upstream <span class="caps">DTS</span> part</li>
<li>Put driver code in renesas-drivers, nothing whitelisted</li>
<li>People interested in playing with it can add devices to the whitelist</li>
</ul></li>
</ul></li>
<li>Support for more than 32-bits <span class="caps">IOVA</span> space
<ul>
<li><span class="caps">GSX</span> needs it.</li>
<li><span class="caps">GSX</span> uses <span class="caps">OSID</span> for isolation</li>
<li>32-bit <span class="caps">IOVA</span> space limitation is a limitation of the <span class="caps">IPMMU</span> driver</li>
<li>It can be tested with other devices than <span class="caps">GSX</span></li>
</ul></li>
<li>Support for multiple guests
<ul>
<li>The current <span class="caps">IPMMU</span> implementation on Gen3 <span class="caps">BSP</span>, second guest OS cannot use <span class="caps">GSX</span>. (#3448, #3486)
<ul>
<li>Need more informtation about the use-case.</li>
</ul></li>
<li>Needs <span class="caps">GSX</span> for testing</li>
<li>Depends on D3</li>
</ul></li>
<li>Support “16.5.2 <span class="caps">IPMMU</span> configuration for <span class="caps">FCP</span>-CS”.
<ul>
<li><span class="caps">IPMMU</span>-PVn also need such handling (Rev.0.55 doesn’t mention it though).</li>
<li>Depends on H3/M3-W (or H3/M3-N, cfr. table 16.14?)</li>
</ul></li>
<li>Overlap with work done by <span class="caps">IGEL</span>?</li>
<li>Main <span class="caps">IPMMU</span> development target aim is D3</li>
</ul></li>
</ul>
<ul>
<li><i>How to add support for R-Car D3?</i>
<ul>
<li>Smaller integration and binding tasks broken out to the ‘smalller tasks’ list.</li>
</ul></li>
</ul>
<ul>
<li><i>How to add support for R-Car H3N?</i>
<ul>
<li>H3 ES3.0 and H3N ES3.0 are the same SoC</li>
<li>Different wire bonding:
<ul>
<li>H3 ES3.0 <span class="caps">PFC</span> is the same as H3 ES2.0 <span class="caps">PFC</span> (r8a77951)</li>
<li>H3N ES3.0 <span class="caps">PFC</span> is the same as M3-W</li>
<li><span class="caps">PRR</span> will be the same, Identify based on compatible value (H3N = r8a77955?)</li>
</ul></li>
<li>Use new “renesas,r8a77955” compatible value.
<ul>
<li>To avoid complication of using r8a7795 for both H3 and H3N.</li>
</ul></li>
</ul></li>
</ul>
<ul>
<li>How to add support for R-Car M3-N?
<ul>
<li>For initial support, remote access env is ok</li>
<li>The HW is coming in Oct or Nov ’17</li>
</ul></li>
</ul>
<ul>
<li>How to add support for R-Car V3M?
<ul>
<li>Cogent is working on this</li>
<li>PeriPeri has no schematics (yet)</li>
</ul></li>
</ul>
<ul>
<li><i>R-Car Gen2 <span class="caps">DTS</span> Update Flag Day</i>
<ul>
<li>CMT driver upstreaming is the main blocker => take over from Magnus</li>
</ul></li>
</ul>
<ul>
<li><i>U-Boot</i>
<ul>
<li>Currently support
<ul>
<li>Salvator-X M3-W and H3 ES2.0</li>
<li><span class="caps">ULCB</span> M3-W and H3 ES2.0</li>
</ul></li>
<li>We need
<ul>
<li>Buy M3-W and H3 <span class="caps">ULCB</span></li>
<li>Add D3 Draak support (remote access only)</li>
<li>Add V3M support (remote access only)</li>
<li>Gen3 <span class="caps">USB</span> <span class="caps">XHCI</span> support (medium prio)
<ul>
<li>needs firmware downloading</li>
</ul></li>
<li>Gen3 <span class="caps">SDMMC</span> HS200/400 and SDR104 modes (higher prio than <span class="caps">XHCI</span> support)
<ul>
<li><a href="https://lists.denx.de/pipermail/u-boot/2017-May/290986.html.html">https://lists.denx.de/pipermail/u-boot/2017-May/290986.html</a></li>
</ul></li>
<li>Finish <span class="caps">PFC</span> support</li>
<li>Submit <span class="caps">RPC</span> support</li>
<li>Mainline U-Boot support for Gen2 (low prio)</li>
<li>Disable <span class="caps">CONFIG</span>_ARCH_FIXUP_FDT_MEMORY to fix Xen breakage [for v2017.09]</li>
<li>Support for massive kernels (128 MiB) [for v2017.11]</li>
<li>Enable Distro environment variables [for v2017.11]</li>
</ul></li>
</ul></li>
</ul>
<h2><i>Additional Tasks for Q4</i></h2>
<ul>
<li>Candidates:
<ul>
<li>Support for more than 32-bits <span class="caps">IOVA</span> space (non-working prototype posted by Magnus)</li>
<li><span class="caps">IPMMU</span> DT binding and integration on various R-Car Gen3 SoCs [S?]</li>
<li>Check fallback compatible values (rcar-gen2-*, rcar-gen3-*); Especially <span class="caps">SDHI</span></li>
<li>Extend U-Boot support to more R-Car Gen3 platforms [MV]</li>
<li>DevFreq,?,noplan,?,GPU needs DevFreq, as <span class="caps">DVFS</span> is shared between <span class="caps">CPU</span> and <span class="caps">GPU</span></li>
<li>genpd,?,noplan,?,Fix handling of devices used as wake-up source</li>
<li>renesas-drivers maintenance</li>
</ul></li>
</ul>
<ul>
<li>Smaller tasks:
<ul>
<li><span class="caps">GPIO</span>,v4.15,plan,shimoda, add D3 binding</li>
<li><span class="caps">SYS</span>-<span class="caps">DMAC</span>,v4.15,plan,?, add D3 binding</li>
<li><span class="caps">SYSC</span>,?,noplan,?,Keep I/O power areas powered on H3 ES1.x/ES2.0 and M3-W ES1.x</li>
<li>r8a77995,v4.15,plan,shimoda, integration for <span class="caps">GPIO</span></li>
<li>r8a77995,v4.15,plan,shimoda, integration for EthernetAVB</li>
<li>r8a77995,v4.15,plan,shimoda, integration for <span class="caps">USBPHY</span>/USB2-Host</li>
<li>r8a77995,v4.15,plan,?, integration for eMMC</li>
<li>r8a77995,v4.15,plan,?, integration for I2C/IIC</li>
<li>r8a77995,v4.15,plan,?, integration for {SYS,Audio}-<span class="caps">DMAC</span></li>
<li>r8a77995,v4.16,plan,?, integration for <span class="caps">IPMMU</span>s</li>
<li>r8a77995,v4.16,plan,?, integration for <span class="caps">RSND</span></li>
<li>r8a77995,v4.16,plan,?, integration for DU</li>
<li>r8a77995,v4.16,plan,?, integration for <span class="caps">VIN</span></li>
<li>Add power-supply to backlight in salvator-common <span class="caps">DTSI</span>: <a href="https://patchwork.kernel.org/patch/9702957/.html">https://patchwork.kernel.org/patch/9702957/</a></li>
<li><span class="caps">CMT</span> driver upstreaming [G]</li>
<li><span class="caps">RPC</span> Hyperflash Linux driver</li>
<li>Enable <span class="caps">EFI</span> library support in U-Boot (?) (check with Shimoda-san if needed) <a href="https://www.suse.com/docrep/documents/a1f0ledpbe/UEFI%20on%20Top%20of%20U-Boot.pdf.html">https://www.suse.com/docrep/documents/a1f0ledpbe/UEFI%20on%20Top%20of%20U-Boot.pdf</a></li>
</ul></li>
</ul>
</html>
|
