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)
falk689_ has quit [Remote host closed the connection]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
djakov has quit [Remote host closed the connection]
djakov has joined #aarch64-laptops
SallyAhaj_ has quit []
SallyAhaj has joined #aarch64-laptops
<steev>
qzed: it compiles - i still haven't gotten around to reinstalling linux on it, hopefully this weekend sometime
Lucanis0 has quit []
Lucanis has joined #aarch64-laptops
<macc24>
is it me or did display on lazor broke on 5.19-rcsomething
SallyAhaj has quit [Quit: SallyAhaj]
iivanov has joined #aarch64-laptops
iivanov has quit []
<qzed>
bamse: what specifically is required to "properly" handle the combined pcie1 pcie2 4-lane thing?
<qzed>
just set num-lanes to 4 and make sure both pcieN_phys are properly turned on/off?
<qzed>
or do they need some special/different configuration to work together?
<qzed>
also is not setting is_dual_lane_phy=true for the sc8180x pcie phys on purpose? registers seem to be specd for dual-lane in the DT
<bamse>
qzed: there's a register which defines if the phys work separately or in tandem...in tandem the initialization sequence needs to initialize both phys, in a slightly different way from when they are separate
<qzed>
bamse: okay, thanks! has there been any work on this that I could have a look at?
<bamse>
jhovold has been spending some time on it, not sure if he has release anything yet though
<qzed>
thanks! I'll have a look around
<qzed>
I'm mostly concerned about it not retaining config from suspend, as at the moment it seems it keeps that from UEFI
<qzed>
at least it does work somehow...
<qzed>
alternatively I guess I could mabye set the controller into 2-lane mode and work with a single phy
<qzed>
that does seem to work as well
<qzed>
and with that change in the DT, lspci also reports it's actually x2, so that could get around the second phy
<steev>
qzed: going through the install now, will hopefully be able to test that stuff later today
<steev>
i'm probably gonna need to grab the mbns manually again to get things up and going but once i get it on the network, i'll be giving that kernel a test
SallyAhaj has joined #aarch64-laptops
<steev>
qzed: so, how do i test?
<steev>
it boots here
<qzed>
not sure, lsusb and check if there are some new devices?
<qzed>
it's some internal thing on the flex, right?
<qzed>
bamse mentioned something about webcams via usb, so maybe those could show up
<steev>
hm
<steev>
i need to poke more, i broke something, rmtfs isn't starting here
<steev>
blergh
<steev>
remote proc is being probe deferred because supplier c300000.power-controller not ready
<steev>
well the good news is, it's not your patches
<qzed>
yeah, that would have been weird... unfortunately I have no clue what the problem could be
<qzed>
there's some issue with dispcc timing out on defered probe, for which bamse has patches
<qzed>
but for the power-controller I have no clue
<steev>
i thought that was the postpone clk_set_rate until the pll is up
<steev>
then again, i haven't tested the flex5g in a while - and looking at the difference between my config and bamse' i don't see anything that would be causing it either
<qzed>
ah that might be possible, I'm still carrying some older patches... I need to update and compare stuff with bameses sc8180x-v5.19-rc1 branch
<steev>
maybe, but like, the only differences between bamse' 5.19 rc1 config and my 5.19 rc3 config is that he doesn't have the inline encryption stuff enabled
<qzed>
I only made that fragment because I eventually want to try and ship some distro-like kernels via github, once we have a bit more stability
<qzed>
the idea is that that contains the minimal(-ish) set of options to make things work
<steev>
makes sense
<steev>
"we" (really shawn) have the distro_defconfig in the aarch64-laptops and i've carried it over as well, occasionally doing a make savedefconfig and copying it into place and committing
<steev>
but that's more to do with what debian expects to be around for its installer
<steev>
qzed: interesting - you have the DISPCC_8250=m something about the display, but here i have it =y
<qzed>
yeah, I think that's a "specialty" of the spx...
<steev>
could be
<steev>
i remember there being *something* required
<steev>
that isn't 8180x, and i think it might hav ebeen that, on the flex
<qzed>
on the SPX there's some hand-off going on with who drives the panel and backlight, essentially the EC drives that during boot until you eventually pull the SoC pin for the backlight up or something... and I'm not sure if there's some interference or why I had to build that as module...
<qzed>
could also be something completely different