Caterpillar has quit [Quit: Konversation terminated!]
Caterpillar has joined #linux-msm
junari has joined #linux-msm
junari has quit [Remote host closed the connection]
junari has joined #linux-msm
jacobk_ has joined #linux-msm
jacobk is now known as Guest790
jacobk_ is now known as jacobk
Guest790 has quit [Ping timeout: 480 seconds]
svarbanov__ has joined #linux-msm
svarbanov__ has quit []
svarbanov_ has quit [Ping timeout: 480 seconds]
junari has quit [Ping timeout: 480 seconds]
<Tofe_>
FYI, I have managed to get my SDIO card detected; however, it looks like pwrseq-simple is too simple for me, as I need to inialize an input gpio, an output low gpio, and an output high gpio...
<phh>
Tofe_: uh input? it rather sounds like it's a pinctrl?
<phh>
what do you need to do with that input pin?
<phh>
the low gpio and the high gpio are different gpios or the same?
<Tofe_>
phh: well I'm a bit over my head with this thing, so I might be doing things wrong :) I'm just following the downstream wifi initialization sequence
<phh>
you can safely ignore TENDERLOIN_GPIO_WL_HOST_WAKE and TENDERLOIN_GPIO_HOST_WAKE_WL_PIN until you have deep-suspend
<phh>
just put TENDERLOIN_GPIO_WLAN_RST_N_PIN in the mmc-pwrseq
<Tofe_>
I thought I tried that, but maybe not; however TENDERLOIN_GPIO_WLAN_RST_N_PIN seems to be defined as OUTL (low), isn't that an issue ?
<Tofe_>
current I savagely override with a call to gpiod_direction_output(wlan_reset_gpio, 0); but it's very hacky and I'd like to find a nicer way
<phh>
well, as I said before, just export the gpio through /sys, add broken-cd to the mmc node, and just try both options, setting the gpio to 0 or to 1
<phh>
(the timing should be irrelevant, but you do need to toggle it at least once)
<Tofe_>
I didn't succed in exporting anything through /sys
<Tofe_>
I get errors like: "echo: write error: Device or resource busy"
<Tofe_>
when exporting
<Tofe_>
but first let me try with just TENDERLOIN_GPIO_WLAN_RST_N_PIN, if that's enough it'll simplify things a bit
<phh>
i'm guessing pwrseq had already registered the gpio so you couldn't
<phh>
but you can check /sys/kernel/debug/gpio for more infos
<Tofe_>
ah, yes, I'll look there
<Tofe_>
(also it's an old tablet, takes forever to boot, so patience is required)
<Tofe_>
mmh now I've deactivated my hack, and it still works, weird
<Tofe_>
I've done a power-off / power-on cycle, and the SDIO MMC card is still detected
<phh>
it's possible that the -110 issue is just that it can't find any firmware
<Tofe_>
possible yes, I'll investigate
<phh>
93 and 337 are TENDERLOIN_GPIO_HOST_WAKE_WL_PIN and TENDERLOIN_GPIO_HOST_WAKE_WL_PIN ?
<phh>
137*
<Tofe_>
yes: #define TENDERLOIN_GPIO_WL_HOST_WAKE93 and #define TENDERLOIN_GPIO_HOST_WAKE_WL137
<Tofe_>
and there's a matching table afterwards, but for my board it's the same
<Tofe_>
so the firmware thing is just the ath6kl driver trying every fw-%d.bin downwards, until it finds one. I only have fw-3.bin. I guess it's for possible future upgrades. But I don't think it's related to the timeout here; I would rather thing that I messed up the mmc sdio configuration somehow
<Tofe_>
think*
jacobk_ has joined #linux-msm
jacobk is now known as Guest851
jacobk_ is now known as jacobk
Guest851 has quit [Ping timeout: 480 seconds]
jacobk_ has joined #linux-msm
jacobk is now known as Guest858
jacobk_ is now known as jacobk
Guest858 has quit [Ping timeout: 480 seconds]
Caterpillar has quit [Quit: Konversation terminated!]
irungentoo has quit [Quit: ZNC 1.8.2+deb3.1 - https://znc.in]