User Tools

Site Tools


todo_tasks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
todo_tasks [2019/01/15 11:25]
Krzysztof Kozlowski ARM_LPAE
todo_tasks [2019/09/06 07:51] (current)
Krzysztof Kozlowski add "cpuidle big_little driver on Odroid-xu4"
Line 5: Line 5:
   - Use one cooling map for all cooling devices (follow up on [[https://​lore.kernel.org/​lkml/​cover.1530766981.git.viresh.kumar@linaro.org/​T/#​u|dt:​ thermal: Fix broken cooling-maps]]) //(reported by: krzk)//   - Use one cooling map for all cooling devices (follow up on [[https://​lore.kernel.org/​lkml/​cover.1530766981.git.viresh.kumar@linaro.org/​T/#​u|dt:​ thermal: Fix broken cooling-maps]]) //(reported by: krzk)//
   - [[https://​patchwork.kernel.org/​patch/​10528823/​|Remove TMU alias from DT bindings and driver because it looks unneeded]] //(reported by: krzk)//   - [[https://​patchwork.kernel.org/​patch/​10528823/​|Remove TMU alias from DT bindings and driver because it looks unneeded]] //(reported by: krzk)//
-  - Bring Suspend to RAM to Exynos5422 Odroid XU3/XU4/HC1 boards 
   - Artik5: add support for AX88796C SPI Ethernet driver (kernel driver is there, but lacks DT support) //(reported by: Marek Szyprowski)//​   - Artik5: add support for AX88796C SPI Ethernet driver (kernel driver is there, but lacks DT support) //(reported by: Marek Szyprowski)//​
   - Lack of REGULATOR_ARIZONA_LDO1 in .config on TM2 causes endless loop: //(reported by: Marek Szyprowski)//​   - Lack of REGULATOR_ARIZONA_LDO1 in .config on TM2 causes endless loop: //(reported by: Marek Szyprowski)//​
Line 18: Line 17:
   - FIMD: trashed display (or even DMA freeze) on too narrow planes (i.e. cursor on right screen border), workaround in Chromebook kernel: https://​chromium.googlesource.com/​chromiumos/​third_party/​kernel/​+/​chromeos-3.8/​drivers/​gpu/​drm/​exynos/​exynos_drm_cursor.c#​31 //(reported by: Marek Szyprowski)//​   - FIMD: trashed display (or even DMA freeze) on too narrow planes (i.e. cursor on right screen border), workaround in Chromebook kernel: https://​chromium.googlesource.com/​chromiumos/​third_party/​kernel/​+/​chromeos-3.8/​drivers/​gpu/​drm/​exynos/​exynos_drm_cursor.c#​31 //(reported by: Marek Szyprowski)//​
   - All non-timer IRQs are always triggered on CPU0, not distributed over all active CPUs. This hurts performance especially on systems, where CPU0 is a LITTLE core. //(reported by: Marek Szyprowski)//​   - All non-timer IRQs are always triggered on CPU0, not distributed over all active CPUs. This hurts performance especially on systems, where CPU0 is a LITTLE core. //(reported by: Marek Szyprowski)//​
-  - Odroid XU3 with exynos_defconfig reports following warning"CPU: WARNING: CPU(sstarted ​in wrong/inconsistent modes (primary CPU mode 0x1a)" +  - Improve support for Exynos5420 Arndale Octa //(in progress: krzk)// 
-  Add support ​for blending properties ​to Exynos DRM CRTC drivers (FIMDMixerDecon), see https://​www.spinics.net/​lists/​dri-devel/msg186919.html for reference ​//(reported by: Marek Szyprowski)// +  - Add support for inl1-inl6 supplies to S2MPS11 (Odroid XU3/XU4 family), just like Odroid XU and Documentation/​devicetree/​bindings/​regulator/​max77802.txt //​(suggested-bykrzk)// 
-  - Odroid U3 fails to boot if kernel is build with ARM_LPAE=y+  - Fix entering AFTR (cpuidlewhen some power domains are off. 
 +    - The problem is in PMU driver which unconditionally writes certain values into power management registers. These values - depending on sleep mode (AFTR, LPA, sleep) - might conflict with regular power domain state. For example, ISP power domain on Exynos4412 might be turned off by runtime power management and PMU while entering AFTR will store there value of 0x1 - turn on. 
 +    - Suggested fixes: 
 +      - Move power domain handling code into PMU and make PMU/AFTR code aware of current state of power domains. PMU driver will be providing power domains in the same way as clock provider ​(so no separate nodes for power domains). 
 +      Optionally, simpler approach might be just reading current value of power domain register when entering AFTR and using it for other registers of this block. 
 +      - Another temporary workaround might be to remove power domain registers from PMU  when entering (only) AFTR. 
 +    - See also [[https://​patchwork.kernel.org/​patch/​10875053/​|initial patch by Marek which was not accepted]] //(reported by: Marek Szyprowski)//​ 
 +  - Test Mali drivers (ARM Mali400ARM MidgardLima and Panfrostwith kernel DTS settings on Exynos3250, Exynos4210, Exynos4412, Exynos5250, Exynos542x and Exynos5433. Resources: [[https://​gitlab.freedesktop.org/​lima/​web/​wikis/​home|Lima status, tools and doc]], [[https://​github.com/​yuq/​gfx|off screen rendering Lima tool]] 
 +  - Add Mali GPU cooling devices for all SoCs and test DVFS, [[https://​review.tizen.org/​git/?​p=platform/​kernel/​linux-exynos.git;​a=blob;​f=drivers/​gpu/​arm/​mali400/​r5p2_rel0/​platform/​exynos/​exynos.c;​h=cf3d03e9d89595d434518c0b74a1756347d83f60;​hb=5679a56b3a3bf2e8aed668e663464cd0281f8970|DVFS values and Exynos specifics on Tizen with Mali400]] 
 +  - Fix DTC warnings (//make dtbs W=1//) 
 +  - Convert bindings to json-schema //(for some of them in progress - krzk, see [[https://​patchwork.kernel.org/​project/​linux-samsung-soc/​list/?​series=164545&​state=%2A&​archive=both| dt-bindings:​ arm: samsung: Convert Samsung board/soc bindings to json-schema]])//​ 
 +  - Fix DT schema errors (//make dtbs_check//​) 
 +  - XU4 hangs with big.LITTLE cpuidle [[https://​www.spinics.net/​lists/​linux-samsung-soc/msg67238.html|cpuidle big_little driver on Odroid-xu4]] ​//(reported by: Jaafar Ali)//
  
-Please let us know if you pick up working on specific task to avoid duplicating efforts. Feel free to contact the person mentioned as "//​Reported by//" for more details. Also consider credits (//​Reported-by//​ or //​Suggested-by//​) when developing patch.+Please let us know if you pick up working on specific task to avoid duplicating efforts. Especially before picking up item in progress, please get in touch with mentioned person. Feel free to contact the person mentioned as "//​Reported by//" ​or mailing list for more details. Also consider credits (//​Reported-by//​ or //​Suggested-by//​) when developing patch.
todo_tasks.1547551548.txt.gz · Last modified: 2019/01/15 11:25 by Krzysztof Kozlowski