<amitk>
Hi all, I'm trying to get wifi working on the Exynos 5800-based Chromebook2 (http://linux-exynos.org/wiki/Samsung_Chromebook_2_XE503C32) with a mainline kernel. Compiling in the mwifiex sdio driver and copying the sd8897 firmware in /lib/firmware doesn't do the trick.
<Wizzup>
Too bad that the initial idea of the channel -- to centralise some efforts hasn't worked out too much, but I guess that's also because of a huge lack of time :)
<javier__>
and disable CONFIG_FB_SIMPLE if you have a u-boot that injects the simplefb device node
<Wizzup>
I think I did that last time but it didn't work yet
<Wizzup>
I think I applied that
<javier__>
amitk: I haven't tested wifi myself but yes I believe the DTS snippet you shared are needed too
<javier__>
amitk: also you need to grab the max77802 en32khz_cp clock or boot with clk_ignore_unused
<javier__>
amitk: since in the patch you posted it mentions "vin-supply = <&en32khz_cp>" but that is because the chromeos kernel didn't have a proper clock driver for the max77802 clocks
<javier__>
so that DTS needs some mangling, I've testing wifi in my (very long) TODO list
<amitk>
javier__: hmm, let me check if there is already DT bindings for the max77802 clocks
<javier__>
amitk: yes, there is in Documentation/devicetree/bindings/clock/maxim,max77802.txt
<javier__>
amitk: MAX77802_CLK_32K_AP is used as the source clock of the s3c RTC in arch/arm/boot/dts/exynos5800-peach-pi.dts
<javier__>
MAX77802_CLK_32K_CP is used by the wifi chip but since there is no DTS snippet for that is of course unused
* amitk
can't figure out how to download that patch w/o locally cloning the tree from github, bah
<javier__>
amitk: and you also need to enable CONFIG_COMMON_CLK_MAX77802=y which is not enabled in 3.18
<javier__>
amitk: sorry if I'm telling you obvious things but just saying what I believe may save you some time :)
<amitk>
javier__: no, this is very useful. My main focus is to work on the big.LITTLE chip on the device, so getting the device enablement out of the way quickly is a lot of help.
<javier__>
amitk: great, let me know if you find any issues since I've been hacking on the Exynos5420 version of the chromebook2 (the 11" one) so I may help
<amitk>
javier__: did we talk before on #linaro? about not being able to get all 8 cores booting on the 5420?
<jnettlet>
amitk, if you are looking at a commit in github go up to the url location and add .patch to the end. That will then download the commit as a standard patch that will work with git am
<amitk>
jnettlet: nifty, I ended up cloning the tree though :)
<jnettlet>
amitk, okay. good to know for future endeavors
<amitk>
jnettlet: indeed
<javier__>
amitk: yes we did. I disabled the b.L switcher and I got the 8 cores working on my 5420 chromebook, I know is not working on arndale octa board
<javier__>
amitk: olof said that it may work but if you start stressing you may find issues. I don't know what is the problem though
<javier__>
but afaiu whatever the stability problem is, it was fixed in the Exynos5422
<amitk>
javier__: it is a HW bug
<jnettlet>
you are bringing the cores on and off individually or just have all of them on all the time?
<amitk>
and yes, it was fixed in 5422/5800
<amitk>
jnettlet: all 8 active at the same time
<jnettlet>
what was doing the scheduling?
<javier__>
amitk: yeah, I know is a HW bug but I meant that I don't know what the bug really is and why is working on the chromebook but not in arndale octa
<javier__>
seems that some bootloader magic is needed but I also don't know what that is :)
<amitk>
jnettlet: the scheduler is what we're trying to fix upstream
<jnettlet>
does the 13" chromebook with the 5800 in it have all 8 cores enabled? Or any big.LITTLE switching for that matter?
<amitk>
jnettlet: the chromeos kernel has cluster switching enabled
<jnettlet>
amitk, for the 11" ?
<amitk>
jnettlet: I'm using mainline with all 8 cores enabled and changes to the scheduler
<amitk>
jnettlet: the 11" has the 5420, right?
<jnettlet>
yes
<sjoerd>
13" on mainline boots all cores properly
<amitk>
jnettlet: that one uses cluster switching as well, and getting all cores working is a problem on that one
<sjoerd>
which is a 5422.. But there are some folks having issues owth the odroid XU3 to get all cores going
<amitk>
its not stable
<amitk>
sjoerd: yeah, though there seems to be some solutions for the 6/8 cores bug now
<sjoerd>
Right, some writes to magical registers :/
<jnettlet>
I will need to look at their kernel code then. Nothing in linux reports anything other the big cores being used.
<javier__>
jnettlet: do you have the 11" (Exynos 5420 Peach Pit)?
<jnettlet>
javier__, yep
<javier__>
jnettlet: peach pit boots with 8 cores but there are reports that has stability issues
<javier__>
I didn't have any issues but didn't stress all the cores either
<jnettlet>
I need to get some time to test that out.
<jnettlet>
been too busy with other hardware.
<javier__>
jnettlet: -next with CONFIG_BL_SWITCHER disabled should be enough
<sjoerd>
javier__: Is that due to the little cores not getting a high enough voltage like what was going on the 13"
<jnettlet>
javier__, did you see a major difference in battery usage?
<javier__>
sjoerd: I don't really know, seems to be a hw bug in 5420 that got fixed in 5422/5800 but don't have more details
<javier__>
sjoerd: maybe amitk knows more
<sjoerd>
ah different issue then
<javier__>
jnettlet: I didn't measure consumption, sorry
<sjoerd>
jnettlet: last time i played with these things mainline didn't do voltage scaling yet for the cpus, so power usage was high anyway
* sjoerd
has to wait for a new 13" one to arrive as he managed to break his board when re-soldering the serial console :/
<javier__>
sjoerd: oh, I thought you could unbrick that one :(
<amitk>
javier__: sjoerd: SoC bug related to CCI
<sjoerd>
javier__: i might try again, but i doubt it
<sjoerd>
javier__: I don't even see power on the debug pads where it should have reference volgae & the power led just turns of right away
<javier__>
sjoerd: I see, so seems to be worse than we thought...
<sjoerd>
well i can't really work out what went wrong which is a tad annoying
<sjoerd>
my best theory is that i accidentally screwed up the ec ro firmware
* jnettlet
thought that the 5420 fixed the problems with the CCI that existed in the 5410
<amitk>
jnettlet: that was supposed to be the case, yet
<amitk>
*yes
afaerber has quit [Ping timeout: 245 seconds]
afaerber has joined #linux-exynos
liquidAcid has joined #linux-exynos
liquidAcid has quit [Ping timeout: 258 seconds]
liquidAcid has joined #linux-exynos
MrBIOS has joined #linux-exynos
liquidAcid has quit [Quit: Leaving]
dsodman_ has quit [Remote host closed the connection]