summaryrefslogtreecommitdiff
path: root/wiki/Chat_log/20170906-core-chatlog
diff options
context:
space:
mode:
Diffstat (limited to 'wiki/Chat_log/20170906-core-chatlog')
-rw-r--r--wiki/Chat_log/20170906-core-chatlog163
1 files changed, 163 insertions, 0 deletions
diff --git a/wiki/Chat_log/20170906-core-chatlog b/wiki/Chat_log/20170906-core-chatlog
new file mode 100644
index 0000000..b22eea8
--- /dev/null
+++ b/wiki/Chat_log/20170906-core-chatlog
@@ -0,0 +1,163 @@
+<html>
+<link rel="stylesheet" type="text/css" href="../../wiki/css">
+ <h1>Core-periperi-meeting-2017-09-06</h1>
+
+ <h2>PeriPeriCon &#8211; 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 &#8220;16.5.2 <span class="caps">IPMMU</span> configuration for <span class="caps">FCP</span>-CS&#8221;.
+ <ul>
+ <li><span class="caps">IPMMU</span>-PVn also need such handling (Rev.0.55 doesn&#8217;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 &#8216;smalller tasks&#8217; 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 &#8220;renesas,r8a77955&#8221; 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 &#8217;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>