Hello again,
> Ok. I²C is CPU-hungry, as it involves busy-loops on kernel level for most
> I²C
> hosts. Bitbanging hosts are most annoying as they need the kernel to stop
> for
> 10µs after each bit. Nothing useful to do in such a short time.
I'm using an iMX.257 CPU. According the Feature list there is hardware
supporting the I²C bus. I hope it is not so CPU-hungry
Nevertheless, I've tested the USB adapter DS9490R which even took more CPU
load as the DS2482
>> At time of the previous posting I used 5s loop delay accessing the
>> "uncached" values
>>
>That isn't too tight. When scanning for new chips ("Search ROM"), 5s ist
tight
>on I²C. If you only access chips by "Match ROM", it should go down to 100ms
>without problems.
Hmm, I never looked into the OWFS details, but I use the CAPI with one
OW_init() and an OW_get() per loop & device. So I hope it never uses "Search
ROM" and only uses "Match ROM"
> At least with the PentiumM I use in my embedded system.
OK, this is the benefit of this faster CPU
> I haven't checked the temperature sensors, though. Are you
> sampling/reading
> them directy, or do you trigger /simultaneous/temperature before, then
> delay
> the loop, then read?
I'm reading them directly and guessing I have to, because they are not
powered (2-wires connection only, no Vcc). But it's a good idea to try it...
Thanks
Achim
--
View this message in context:
http://old.nabble.com/High-CPU-load-on-owserver-tp32667209p32673695.html
Sent from the OWFS - Dev mailing list archive at Nabble.com.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers