ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
leezu has joined #aarch64-laptops
klardotsh has joined #aarch64-laptops
<leezu> Is it expected that Night Light features / xrandr --gamma do not work on Lazor / sc7180? There are no errors, but the color temperature remains unchanged
shawnguo has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
klardotsh has quit [Read error: No route to host]
klardotsh has joined #aarch64-laptops
Lucanis0 has joined #aarch64-laptops
<Dylanger> msm is a Qualcomm term
<steev> yes
klardotsh has quit [Ping timeout: 480 seconds]
flowriser has joined #aarch64-laptops
<macc24> leezu: i'm not sure if that would be related to soc
<macc24> what de/compositor/whatever are you using?
<javierm> macc24: I expect that Hans will ack and merge your panel-orientation-quirks patch, but if nothing happens in a week or so let me know and I can push it to drm-misc-next branch
<macc24> javierm: ok, thanks
<leezu> macc24: I observe the gamma issue on both Gnome X11 and Wayland sessions. For X11, the issue is independent from Gnome, as xrandr --gamma does not work either. Does it work for you? Could there be a driver issue causing the gpu not to be notified correctly about the gamma change?
<macc24> leezu: lemme just install gnome on my lazor to try it
<leezu> macc24: Thank you. Let's see if it works on your end. Btw, is your panel-orientation-quirks patch related to lazor?
<macc24> leezu: it's for entirely different device - x86 handheld gaming console
<leezu> Ok, nice. Lazor also has some orientation issues. For Wayland, the laptop screen will be inverted if an external monitor is connected. (On X11 the screen would be always inverted.) I haven't looked into it more closely, but in some cases I would see msm errors in the kernel log
<macc24> leezu: try stopping iio-sensor-proxy
<leezu> I think that resolves the X11 issue, but it doesn't help with the Wayland issue
<leezu> (I haven't tried with X11 + stopped iio-sensor-proxy + external screen connected; need to try that)
<macc24> night light is broken for me too
<leezu> Thanks for trying. Only on Gnome?
<macc24> i tried only on gnome on wayland
<leezu> Ok. Do you have any idea how to debug this further? It seems that the Gamma property is simply ignored by the driver (?)
<macc24> no idea
<macc24> sorry
<leezu> Do you usually use a X11 or Wayland session, besides your try with Gnome Wayland now?
<leezu> Regarding the orientation and external screen issue, I gave it a quick try with X11 and that causes lots of artifacts on the screen as well as the following two kernel log messages: "[drm:dp_ctrl_read_link_status.isra.0] *ERROR* DP link status read failed, err: -110" "[drm:dp_ctrl_setup_main_link] *ERROR* link training #1 failed. ret=-110".
<leezu> Nevermind, above artifacts only occur when switching from Wayland to X11. On a fresh boot, external screen works with X11 and orientation issue can be avoided by disabling iio-sensor-proxy. In fact, connecting the external screen while on Wayland crashes the session and GDM does not allow to start a Wayland session while the external screen is connected, so my prior
<leezu> observation with inverted laptop screen while external screen connected was likely on X11
<leezu> The only way to get the external screen working in a Wayland session is to disable the internal screen in Gnome settings for the case of external screen is connected
<macc24> javierm: Hans put his R-b onto the orientation patch and said "it would be good if someone else can push this to drm-misc-fixes"
<robclark> leezu: on CrOS we use display CTM (CRTC property) on internal display.. one could also use the GPU for that.. not sure off the top of my head what different de's support
<macc24> javierm: \o/. thanks!
<javierm> macc24: yw
<macc24> javierm: do you know around what point will it be in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/ ?
<bamse> Dylanger: anyone is free to submit the initial, or any subsequent, patches for anything...
<bamse> Dylanger: so if you have something that works and you would like to contribute, go for it!
Lucanis has joined #aarch64-laptops
Lucanis0 has quit [Ping timeout: 480 seconds]
<steev> bamse: oh wow, we're really down to only 10 patches (ignoring the defconfig dump) for sc8180x outside the kernel with 5.19? very nice
<steev> oh, 9, with rc2 since the 10th patch is pulled in
<steev> random stuff from the recovery for the flex 5g (in their xml file....) <Modules RDVDVersion="8" ProductName="Yoga 8 5G/Flex 8 5G" ProjectName="Skynet" SWListName="SWLIST-Yoga C850-14-Win10 for ARM-C1" SWListVersion="42" OSGroup="Win10 for ARM">
<steev> i guess at some point it was a) Skynet (amazing), and b) they were maybe gonna call it the Yoga C850 ?
<leezu> robclark: Thank you. I've opened a Gnome issue to track the Night Light problem https://gitlab.gnome.org/GNOME/mutter/-/issues/2318 If you have further information or a pointer to the CRoS implementation, that would be great
<qzed> bamse: is it possible that gcc-sc8180x is missing some resets and clocks? specifically for the multiport-usb-controller-thingy?
<qzed> the QcXhciFilter8180 driver on Windows seems to write to some GCC registers that aren't defined in the linux driver
<javierm> macc24: the goal is to land in the current -rc cycle (https://people.freedesktop.org/~jani/html/drm-misc.html#drm-misc-fixes)
<javierm> macc24: so for v5.19
<macc24> ooooooooooh nice!
<javierm> macc24: I was targetting drm-misc-next (for v5.20) but Hans said drm-misc-fixes, that's why I pushed there