dddddd has quit [Remote host closed the connection]
TheSeven has quit [Ping timeout: 252 seconds]
TheSeven has joined #linux-sunxi
skiboy has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
msevo has joined #linux-sunxi
cristian_c has quit [Read error: Connection reset by peer]
cristian__c has joined #linux-sunxi
ldevulder_ has joined #linux-sunxi
ldevulder has quit [Ping timeout: 246 seconds]
airwind has joined #linux-sunxi
Mylene has joined #linux-sunxi
Mylene has quit [Client Quit]
Mylene has joined #linux-sunxi
_0x5eb_ has quit [Ping timeout: 258 seconds]
_0x5eb_ has joined #linux-sunxi
reinforce has joined #linux-sunxi
tl_lim has quit [Read error: Connection reset by peer]
TheSeven has quit [Ping timeout: 252 seconds]
TheSeven has joined #linux-sunxi
nashpa_ has joined #linux-sunxi
nashpa has quit [Read error: Connection reset by peer]
nashpa_ has quit [Ping timeout: 272 seconds]
nashpa has joined #linux-sunxi
nashpa has quit [Read error: Connection reset by peer]
NeuroScr has joined #linux-sunxi
nashpa has joined #linux-sunxi
<superprower>
Hi! I've been trying to figure out why my device can't use CLOCK_REALTIME_ALARM clockid for some time now. I narrowed search down to the rtc-sun6i driver, specifically, the function call `device_may_wakeup` returns false. It is a simple inline function : dev->power.can_wakeup && !!dev->power.wakeup . I'm not sure where exactly those parameters are set, though. In driver source code, I can see SUN6I_ALARM_CONFIG(_WAKEUP) macros.
<superprower>
I presume first is an address of a register, and second is the value, and is set to be BIT(0). Address used twice in the code, first time to set 0, and second time to set value macros (which is also 0?). So where should I look? Can or should I affect this BIT(0) macro in any way? Or should I look in different place? Sorry for the long question, and thanks in advance.
jrg has quit [Ping timeout: 272 seconds]
nashpa has quit [Read error: Connection reset by peer]
nashpa has joined #linux-sunxi
arti_ is now known as arti
nashpa has quit [Ping timeout: 245 seconds]
warpme_ has joined #linux-sunxi
nashpa has joined #linux-sunxi
AneoX has joined #linux-sunxi
jrg has joined #linux-sunxi
<bshah>
Hey there, do anyone have idea about, [ 3.485007] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 ? There are some references all over internet about this, but I can't seem to find solution
<wens>
what are you using it for?
<wens>
it's likely that you are missing pull-ups for the I2C lines, or something is pulling them down (such as an unpowered I2C client)
<bshah>
wens: it is being used for touchscreen on A64 (pinephone devkit)
nashpa_ has joined #linux-sunxi
nashpa has quit [Read error: Connection reset by peer]
Mangy_Dog has joined #linux-sunxi
warpme_ has quit [Quit: warpme_]
nashpa_ has quit [Ping timeout: 248 seconds]
warpme_ has joined #linux-sunxi
nashpa has joined #linux-sunxi
yann has quit [Ping timeout: 246 seconds]
NeuroScr has quit [Quit: NeuroScr]
warpme_ has quit [Quit: warpme_]
warpme_ has joined #linux-sunxi
<wens>
check pull-ups and that the touchscreen is actually powered
cnxsoft has quit [Ping timeout: 258 seconds]
Putti has joined #linux-sunxi
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-sunxi
ldevulder_ is now known as ldevulder
rah has joined #linux-sunxi
rah has quit [Client Quit]
rah has joined #linux-sunxi
<MoeIcenowy>
yes usually "I2C bus locked" is due to not correctly configured I2C bus
<MoeIcenowy>
pinmux error
<MoeIcenowy>
or not pulled up
<bshah>
this is so weird that only I am facing this error and not others :(
<fALSO>
yoo good morning
warpme__ has joined #linux-sunxi
warpme_ has quit [Ping timeout: 248 seconds]
warpme__ has quit [Read error: Connection reset by peer]
warpme_ has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
matthias_bgg has joined #linux-sunxi
<MoeIcenowy>
bshah: HW manufacturing problem?
<bshah>
at least other who have 1.1 version of devkit, for them touchscreen works ... but then I might be just that unlucky guy
<suprothunderbolt>
I'm attempting to work out the easiest way to get an image to display instead of the console on boot, any hints? u-boot looks hard, though obviously the correct long term plan
lurchi__ is now known as lurchi_
<KotCzarny>
doesnt uboot already supports disply on a few socs?
<KotCzarny>
and there is support/patches for boot logo
<KotCzarny>
in which case it setups simple fb you can use, even without linux
<KotCzarny>
i think it passes address/params as a memory struct somewhere
warpme_ has joined #linux-sunxi
megi has quit [Ping timeout: 246 seconds]
<gnarface>
i thought i saw it in build options....
<gnarface>
near the boot penguins
<gnarface>
oh maybe i'm thinking of the kernel though
<gnarface>
not uboot
<gnarface>
not sure now
<fALSO>
the penguins are in te kernel
Mangy_Dog has quit [Remote host closed the connection]
<suprothunderbolt>
KotCzarny: i'm running a DSI connected panel on pine64
<suprothunderbolt>
i don't see anything until console starts displaying after the kernel driver has loaded.
<KotCzarny>
work on/pay somone to add dsi support in uboot?
<KotCzarny>
or minimize kernel startup time, some folks reduced boot time to 1-2s
<KotCzarny>
but that was on x86
warpme_ has quit [Quit: warpme_]
<suprothunderbolt>
yeah, might do both of those eventually :) jaganteki has patches for it.
airwind has quit [Quit: airwind]
lurchi_ has quit [Ping timeout: 245 seconds]
suprothunderbolt has quit [Ping timeout: 246 seconds]
msevo has quit [Quit: Leaving]
dddddd has joined #linux-sunxi
SopaXorzTaker has quit [Remote host closed the connection]
gnarface has quit [Remote host closed the connection]
<superprower>
Should rtc-sun6i driver support waking device up (being used as an alarm, you name it), or hardware it covers is incapable of it? I can't see it using any functions from the list of device_set_wakeup_capable, device_wakeup_attach, device_init_wakeup, which other drivers call.
<mripard>
superprower: there's no suspend support yet, so there's no code to deal with the wakeup and resume either
<superprower>
mripard: where can I read more about that? Maybe there is an ongoing discussion somewhere?
<mripard>
I don't recall any effort on this
<superprower>
mripard: I see. Can you please tell me a bit more on which components lack support for suspend?
cnxsoft has quit [Quit: cnxsoft]
<mripard>
all of them
Mangy_Dog has joined #linux-sunxi
<mripard>
there's exactly 0 support for suspend
<fALSO>
sirs sorry to bother
<fALSO>
but has anyone written a guide on getting the mali driver working ?