<tmlind>
so this should work for gpio_115 padconf interrupt, untested: interrupts-extended = <&omap4_pmx_core 0xc0>;
<tmlind>
if that interrupt is common for modem uart and usb, then it could be set up as a generic wakeirq that ends up calling the runtime pm resume function
<tmlind>
if it's specific to the usb only, then it should have a separate threaded irq handler like you already have
<tmlind>
not sure if the powerup sequence with the gpio pins needs to be redone, i think the modem can watchdog reboot and return online, not sure. so maybe just detecting a modem reboot can be used to rescan the usb bus for devices
<tmlind>
maybe there's some way to do a modem reset or reboot over qmi?
joerg has quit [Ping timeout: 244 seconds]
joerg has joined #maemo-leste
hm has quit [Read error: Connection reset by peer]
fab_ has joined #maemo-leste
<freemangordon>
tmlind: so, I should not add another gpio, but just interrupt, right?
<freemangordon>
lets try it
Anasko has quit [Remote host closed the connection]
sch has joined #maemo-leste
Anasko has joined #maemo-leste
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
Anasko has quit [Remote host closed the connection]
<freemangordon>
yeah, this also make it incompatible with older kernels (at least cannot compile on even 5.10)
<sicelo>
heh, at least we're mainline
<freemangordon>
yeah
<freemangordon>
but had to upgrade VM
<freemangordon>
and my PC
<dsc_>
so the keyboard we have right now (that works with GTK apps)
<dsc_>
its via him (hildon input method)
<dsc_>
correct?
<freemangordon>
yes
<Wizzup>
sorry, yes
<dsc_>
and it needs to be build into the maemo qt plugin
<Wizzup>
dsc_: basically what needs to happen in the qt side is to implement all the dbus calls, so even when sending a single key you need to send that over dbus and him will send the input
<dsc_>
right
<Wizzup>
and if you want to provide 'context' - eg. line editing that also has to go over dbus
<Wizzup>
it's not ideal really, but it's what it is currently
<Wizzup>
there's also the at-spi2 stuff, but I don't know much about it
<Wizzup>
uvos has said at some point he thinks that might be a better way to go about this, but I don't know enough
<Wizzup>
this is hooking into the accessibility frameworks
<freemangordon>
IIUC that's the proper way, however, uvos said there are some issues
<freemangordon>
don;t remember the details
<Wizzup>
yeah
<dsc_>
ok cool
Twig has joined #maemo-leste
pere has quit [Ping timeout: 265 seconds]
g4rrgl3n0m4d has joined #maemo-leste
xmn has quit [Ping timeout: 248 seconds]
narodnik has joined #maemo-leste
<freemangordon>
hmm modem uart is waking-up device hundred times more than usb
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
<dsc_>
(hello:9849): sapwood-engine-WARNING **: 11:25:25.732: sapwood-theme: Failed to load pixmap file /usr/share/themes/alpha/images/TextInput.png: Failed to connect to sapwood server using `/var/tmp/sapwood-:0.0': Connection refused
<dsc_>
is there an env. var to supress sapwood-engine messages?
<dsc_>
some technicalities with key combos to sort out
<dsc_>
modifiers
<dsc_>
im just trying to create a standalone application so its easier to test
hexnewbie has quit [Ping timeout: 244 seconds]
hexnewbie has joined #maemo-leste
arno11 has joined #maemo-leste
<Wizzup>
freemangordon: yes I can make a kernel release today
<dsc_>
hmm
<dsc_>
might be more difficult, sending HILDON_IM_SHOW does not show the keyboard
<freemangordon>
it should, iirc
<Wizzup>
yes, there's bugs in the qt code for sure :)
<dsc_>
btw
<dsc_>
xcb_connection
<dsc_>
this is a x11 connection right
<dsc_>
does it use unix sockets for that?
<dsc_>
well doesnt matter
<Wizzup>
depends on DISPLAY I think
<dsc_>
i have not come across any dbus stuff yet Wizzup
<Wizzup>
sorry, bbiab
<dsc_>
freemangordon: (hello:11016): hildon-1-WARNING **: 14:03:14.533: Tried to initialized Hildon more than once.
<dsc_>
can I ignore this?
<dsc_>
omg, I had "Enable Virtualkeyboard" disabled @ settings
<freemangordon>
yes
<freemangordon>
:)
<dsc_>
k it works now ;p
fab_ has quit [Quit: fab_]
arno11 has left #maemo-leste [#maemo-leste]
Livio has joined #maemo-leste
Livio has quit [Ping timeout: 264 seconds]
<tmlind>
freemangordon: nice looks good to me, not sure if you need the wakeup-source though, maybe check with suspend/resume if it keeps some stuff enabled unnecessarily
<tmlind>
freemangordon: are you seeing events now also for incoming sms on the usb qmi?
<freemangordon>
yes
<freemangordon>
tmlind: without wakeup-source it does not work
<freemangordon>
what to check if properly suspended?
<tmlind>
i think the wakeup-source might have an effect of keeping things enabled, but maybe usb needs it
joerg has quit [Ping timeout: 260 seconds]
joerg has joined #maemo-leste
<freemangordon>
I did't see increase of power usage
<tmlind>
hmm maybe it's needed to keep the interrupt active though
<tmlind>
ok
<freemangordon>
yeah, no interrupt without it
<tmlind>
ok
<tmlind>
so incoming sms working?
<freemangordon>
yes
<freemangordon>
and call
<tmlind>
great!
<tmlind>
also seeing it on the qmi and not just ttyUSB4?
<freemangordon>
ther is at least one more I will have to make, location related
<freemangordon>
also, back then I promised to implement better API for call forwarding
<freemangordon>
but those are details
<sicelo>
great, i understand
<freemangordon>
Dec 11 21:03:38 localhost ofonod[2291]: drivers/qmimodem/voicecall.c:all_call_status_ind() Call 1 in state QMI_VOICE_CALL_STATE_SETUP(10)
<freemangordon>
Dec 11 21:04:38 localhost ofonod[2291]: drivers/qmimodem/sms.c:event_notify() msg format 6 PDU length 35
<freemangordon>
:)
hexnewbie has quit [Ping timeout: 252 seconds]
hexnewbie has joined #maemo-leste
Twig has quit [Remote host closed the connection]
akossh has joined #maemo-leste
arno11 has joined #maemo-leste
arno11 has quit [Ping timeout: 246 seconds]
<freemangordon>
tmlind: if anything, at least we can drop dtmf support from motmdm codec
arno11 has joined #maemo-leste
<Wizzup>
does qmi support dtmf?
<freemangordon>
looks like
<freemangordon>
by the looks of eQMI_VOICE_START_CONT_DTMF and friends
<Wizzup>
ok
<freemangordon>
d4 modem also supports +VTS command
xmn has joined #maemo-leste
<freemangordon>
AT+VTS=?
<freemangordon>
+VTS: (0-9,A-D,*,#)
<freemangordon>
so that's not an issue
<Wizzup>
cool
<freemangordon>
volume control is the issue :)
fab_ has quit [Quit: fab_]
Livio has quit [Ping timeout: 264 seconds]
<arno11>
do you know guys why we can't stop (and restart) tone-generator ? it fails to find the correct pid
<arno11>
and pgrep returns no pid
<arno11>
i ask because i lost alerting tone again
<Wizzup>
is tone generator used for this?
<Wizzup>
(it might be, I don't know)
<arno11>
iirc yes
<arno11>
but that s a bit confusing
<arno11>
Wizzup: i got troubles with 2g calls as well at the same time (after dist-upgrade). Is new debian rules in libcmtspeechdata possibly the root cause ?
<arno11>
(with port to dh 10+)
<Wizzup>
could be, but I don't think I built any of my changes for chimaera
<arno11>
ok
<arno11>
it s late, i ll try tomorrow a local cmt build i have, to see if it works better
<arno11>
indeed you didn t build it to chimaera so the problem is elsewhere