willmore has quit [Ping timeout: 246 seconds]
willmore has joined #linux-exynos
willmore has quit [Ping timeout: 245 seconds]
willy_ has joined #linux-exynos
wwilly has quit [Ping timeout: 246 seconds]
mszyprow has joined #linux-exynos
<memeka> mszyprow: ping
<memeka> I’ve tried your suspend patches on Xu4
<memeka> Ran pm-suspend
<memeka> It entered suspend, although power draw was quite High exactly 2W
<memeka> Then I could not bring it back :(
<memeka> Don’t have serial (yet) to check console
<memeka> mszyprow: was there any other requirement besides those 5-6 patches?
<mszyprow> memeka: v5.0-rcX or linux-next?
<memeka> 5.0 rc7-
<mszyprow> memeka: please try on top of linux-next
<mszyprow> memeka: although the linux-next is a bit broken now
<memeka> :|
<mszyprow> memeka: maybe I should send a complete list of the needed patches on top of v5.0-rcX
<mszyprow> memeka: here when it enters suspend, it consumes about 26mA @ 5V
<memeka> mszyprow: yes please
willy_ has quit [Read error: Connection reset by peer]
wwilly has joined #linux-exynos
<mszyprow> memeka: it works fine on XU3
<memeka> I’ll have a look thx!
<mszyprow> memeka: on XU4 there is still an issue with xhci busy looping for a while
<mszyprow> memeka: I will investigate it further
<memeka> mszyprow: I think I missed some of the first patches
<mszyprow> memeka: the dwc3 revert is probably the most critical
<mszyprow> memeka: I've already complained on linux-usb list, but nothing has been fixed so far
<memeka> mszyprow: yeah I figured something is keeping it
<mszyprow> memeka: the reverted change is obviously wrong, even maintainer admitted that, but still he didn't do anything with it
<mszyprow> memeka: I've developped and checked everything on eMMC root
<memeka> mszyprow: thx I’ll check when I get to the odroid - I’ll add the missing commits and hope it will work straightaway :)
PabloPL has joined #linux-exynos
wwilly has quit [Quit: Leaving]
wwilly has joined #linux-exynos
memeka has quit [Quit: Connection closed for inactivity]
wwilly has quit [Quit: Leaving]
PabloPL has quit [Quit: PabloPL]
krzk_ has quit [Quit: leaving]
krzk has joined #linux-exynos
willmore has joined #linux-exynos
afaerber has quit [Quit: Leaving]
afaerber has joined #linux-exynos
mszyprow has quit [Ping timeout: 250 seconds]
Putti has joined #linux-exynos
dllud has joined #linux-exynos
mszyprow|home has joined #linux-exynos
mszyprow|home has quit [Ping timeout: 255 seconds]
mszyprow|home has joined #linux-exynos
mszyprow|home has quit [Ping timeout: 245 seconds]
mszyprow|home has joined #linux-exynos
LiquidAcid has joined #linux-exynos
mszyprow|home has quit [Ping timeout: 245 seconds]
<Putti> is anybody working on abgr8888 (android) pixel format support for exynos drm fimd / is it available in some non-mainline repo?
<LiquidAcid> Putti, maybe you can get it working via the various swapping flags?
<Putti> LiquidAcid, maybe, if I get I will send a patch to mainline
<Putti> I first have to learn about pixel formats, and then figure out how the 2d graphics processor in exynos4412 works
<Putti> it is strange ABGR8888 is not already supported even though there is lots of Android devices with Exynos SoCs
<Putti> I feel like I'm not getting something here
<LiquidAcid> Putti, you sure you're not confusing g2d with fimd?
<LiquidAcid> fimd is a display controller, the g2d is the 2d blitter
<Putti> I probably am confusing them
<Putti> the error I'm trying to solve is
<Putti> <Putti> is anybody working on abgr8888 (android) pixel format support for exynos drm fimd / is it available in some non-mainline repo?
<Putti> <
<Putti> oops sorry
<Putti> [ 55.486568] [drm:drm_atomic_check_only] [PLANE:30:plane-0] invalid pixel format AB24 little-endian (0x34324241), modifier 0x0
<Putti> okay, so it seems like the SoC has 3 different piece of graphics hardware: 3d accelerator, 2d accelerator and then the display controller
<Putti> And I'm interested now only in the display controller
<LiquidAcid> Putti, then i would check those swap flags
<Putti> LiquidAcid, thanks, I actually had already that file open in my computer but it is nice to know I'm on the right track :)
mszyprow|home has joined #linux-exynos
dllud has quit [Ping timeout: 250 seconds]
<Putti> LiquidAcid, I got it working with the default case / DRM_FORMAT_ARGB8888
<Putti> that's probably not the right way to go around it but it was nice to get it at least somehow working so now we can work on other things on the device
<Putti> after I have studied this a bit I will submit the patch
<Putti> ..and hopefully if it is wrong someone wiser from me will point it out
<LiquidAcid> Putti, not sure how this should work, how do you swap B and R?
<Putti> I have seen now only two colors on the display so that could be a problem indeed
<LiquidAcid> i'm not sure you can swap channels with WINCONx, there is not a lot of flexibility there
<Putti> would WINCONx_BYTSWP work?
<LiquidAcid> VIDCON2 seems to have some rgb order settings, but it applies to all outputs
<LiquidAcid> byte swapping should give you ARGB -> RABG
<Putti> And I only had time to study pixel formats so I have no idea what I'm talking about regarding the FIMD/display controller.
<Putti> ok
<LiquidAcid> like i said, no arbitrary swizzling there
mszyprow|home has quit [Ping timeout: 250 seconds]
mszyprow|home has joined #linux-exynos
mszyprow|home has quit [Ping timeout: 246 seconds]
LiquidAcid has quit [Quit: Leaving]
willmore has quit [Ping timeout: 255 seconds]
willmore has joined #linux-exynos
afaerber has quit [Quit: Leaving]
dllud has joined #linux-exynos