Am 31.03.2016 um 13:58 schrieb Tomi Valkeinen tomi.valkeinen@ti.com:
On 29/03/16 03:26, Michael Mrozek wrote:
Am Tue, 29 Mar 2016 01:15:13 +0200 hat Michael Mrozek EvilDragon@openpandora.org geschrieben:
Ah, one thing I forgot to mention: I was testing this using Nikolaus' testing card. The CPU was set to 500MHz, but X was using 7 - 8% CPU power when idling (probably because the X.Org driver he uses is "omap").
X on the Pandora uses 0,1 - 0,7% CPU power when idling, and that CPU has a lot less power, so that's quite a huge difference.
So I guess that's more a fotware thig.
Also, there are some other CPU hungry things running:
irq/298-4807200 (about 3,3%) kworker/0:1 (about 2%) kworker/0:4 (about 2%) irq/301-4807c00 (about 1,3%) kworker/1:3 (about 0,7%) kworker/0:5 (about 0,7%) kworker/1:1 (about 0,7%) kworker/1:2 (about 0,7%)
What are those? On the Pandora, only X is using a bit of CPU, all the irq and kworker stay at 0%.
See "cat /proc/interrupts" for the irq numbers. If I'm not mistaken, those irq processes are for i2c2 and i2c5.
that is what I just wanted to check but was interrupted by a broken PC...
Now I can test again. Yes, they are
298: 724 0 WUGEN 57 Level 48072000.i2c 301: 43384 0 WUGEN 60 Level 4807c000.i2c
This is indeed i2c2 and i2c5,
i2c2 activity is most likely from the Nubs. AFAIK we still use polling for the as5013 chips:
http://git.goldelico.com/?p=gta04-kernel.git;a=shortlog;h=refs/heads/work/hn...
Patches (and cleanup) are welcome.
i2c5 may be the polling activity by my ts3a225e driver hack which just allows to poll the chip and report plug/unplug events and status:
http://git.goldelico.com/?p=gta04-kernel.git;a=shortlog;h=refs/heads/work/hn...
We will replace this chip with a ts3227e in the final hardware, which already has a better driver. AFAIK it can be operated interrupt driven.
BR, Nikolaus