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