ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
davidinux has quit [Ping timeout: 480 seconds]
Core8365 has joined #aarch64-laptops
Core8718 has joined #aarch64-laptops
tstachecki has quit [Ping timeout: 480 seconds]
Core8365 has quit [Ping timeout: 480 seconds]
Core8718 has quit [Read error: Connection reset by peer]
tstachecki has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
tobhe has quit [Ping timeout: 480 seconds]
Caterpillar has quit [Read error: Connection reset by peer]
Caterpillar has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
erebion has left #aarch64-laptops [Disconnected: Replaced by new connection]
erebion has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
jhovold has joined #aarch64-laptops
agl has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
agl has joined #aarch64-laptops
alexVinarskis has quit [Read error: No route to host]
alexVinarskis has joined #aarch64-laptops
alexVinarskis has quit [Read error: No route to host]
alexVinarskis has joined #aarch64-laptops
alexVinarskis has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
ravikant_ has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alexVinarskis has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
srinik has quit [Remote host closed the connection]
Kelsar has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
Kelsar has joined #aarch64-laptops
Grabunhold has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
Grabunhold has joined #aarch64-laptops
alexVinarskis has quit [Read error: No route to host]
alexVinarskis has joined #aarch64-laptops
alexVinarskis has quit [Ping timeout: 480 seconds]
ravikant_ has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
shoragan has quit [Read error: Connection reset by peer]
shoragan has joined #aarch64-laptops
tstachecki has quit [Ping timeout: 480 seconds]
krei-se has quit [Quit: ZNC 1.9.1 - https://znc.in]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
krei-se has joined #aarch64-laptops
xroumegue has quit [Ping timeout: 480 seconds]
ravikant_ has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<JeromedeBretagne[m]> Progress report on the Surface Pro 9 5G (sc8280xp-based), I've been able to get the built-in display backlight working, reusing the similar nodes from the Lenovo Thinkpad X13s, thanks jhovold: !
<JeromedeBretagne[m]> However, I still haven't found how to get the built-in display detected, despite quite a few attempts (testing mdss0_dp3 and mdss0_dp2)
<JeromedeBretagne[m]> @konradybcio: Any clue about this, since you've done the bring-up of the Surface Laptop 7 family (if I'm not mistaken)? How did you find the correct gpio for the vreg_edp_3p3 regulator and how to choose the right mdds node?
iivanov has joined #aarch64-laptops
<JeromedeBretagne[m]> Here is what I've tried to enable mdss0_dp3 for instance:
<JeromedeBretagne[m]> is something obvious missing?
SpieringsAE has quit [Quit: SpieringsAE]
iivanov has quit [Quit: Leaving]
<JeromedeBretagne[m]> Here is the corresponding dmesg output:
<JeromedeBretagne[m]> I can see these 2 lines that don't look very good:
<JeromedeBretagne[m]> [ 12.105304] panel-simple-dp-aux aux-aea0000.displayport-controller: Prepare timeout after 5 tries
<JeromedeBretagne[m]> [ 12.107089] panel-simple-dp-aux aux-aea0000.displayport-controller: Couldn't power on panel to ID it; using conservative timings: -110
<JeromedeBretagne[m]> do I need to load some specific modules, in addition to panel_edp ?
<JeromedeBretagne[m]> Jens Glathe: do you have some suggestions maybe? I've also tried mdss_dp2 for your info, with a similar patch, I'm a bit out of ideas
alexVinarskis has joined #aarch64-laptops
pbrobinson has quit [Ping timeout: 480 seconds]
alexVinarskis has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
cyrinux9490 has quit []
cyrinux9490 has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]> can I see your dt somewhere
<JeromedeBretagne[m]> The full devicetree? Sure, here you go:
chrisl has joined #aarch64-laptops
<JensGlathe[m]> Try just 2 lanes? I don't know the res, but isn't 2 lanes enough?
<JensGlathe[m]> And I guess You need a power supply
<JeromedeBretagne[m]> Shouldn't I see some messages in dmesg if it was the link training that was failing, due to 4 lanes instead of 2 ?
<JensGlathe[m]> it says can't power up
<JeromedeBretagne[m]> the screen has this resolution : 2880 x 1920
<JensGlathe[m]> ok this could be 4 lanes
chrisl has quit [Ping timeout: 480 seconds]
<JeromedeBretagne[m]> a missing power supply ? in which node ? I think I've stayed as close as possible to the nodes from the X13s dt
<JeromedeBretagne[m]> I have the vreg_edp_3p3 power supply in the panel node
<JeromedeBretagne[m]> but maybe it's the wrong gpio
<JeromedeBretagne[m]> I've tried both GPIO 25 (as on the X13s) and GPIO 70 (as used on the Surface Laptop 7 and the Surface Pro 11)
<JensGlathe[m]> X13s is the nearest (except for the Blackrock devkit)
flokli has quit [Quit: WeeChat 4.5.1]
flokli has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
jhovold has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
martiert has quit [Ping timeout: 480 seconds]
alexVinarskis has joined #aarch64-laptops
alexVinarskis has left #aarch64-laptops [#aarch64-laptops]
martiert has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
todi has quit []
ravikant_ has quit [Ping timeout: 480 seconds]
pbrobinson has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]> Huh. This fingerprint thing works
pbrobinson has quit [Ping timeout: 480 seconds]
arj[m] has joined #aarch64-laptops
<kuruczgy[m]> How do kernel maintainers usually apply patch series with conflicts? I know about b4 and it seems to have this magic b4 am -3 flag to generate some fake base commits for 3way merges, but it doesn't seem be able to find the base commit for the whole patch series to begin with.
<kuruczgy[m]> Is getting git am to generate conflict markers without having the base commits for a 3way merge possible somehow? Otherwise it seems pretty hopeless to apply the whole series basically manually...
<kuruczgy[m]> (I am trying the MSM MST series btw (https://lore.kernel.org/all/20241205-dp_mst-v1-0-f8618d42a99a@quicinc.com/ ), it's from December so having quite a few conflicts is expected I guess.)
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tobhe[m] has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
todi has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<robclark> depends on how bad the conflicts are.. I'll normally try to resolve them but if they are too bad I'll ask poster to rebase