* H. Nikolaus Schaller [off-list ref] [160927 23:50]:

Hi,

quoted

Am 28.09.2016 um 05:37 schrieb Tony Lindgren [off-list ref]:

* H. Nikolaus Schaller [off-list ref] [160927 13:11]:

quoted

quoted

Am 27.09.2016 um 21:49 schrieb Tony Lindgren [off-list ref]:
How about this for defaults:

- heartbeat for led3
- cpu0 for led4
- cpu1 for led5

Good idea. Will try.

What I don't exactly know is if these gpios based on an I2C-expander
can handle cpu activity triggers or if they are locked up if this i2c
processing triggers another cpu activity...

Oh right, if the GPIOs are on the i2c bus

yes, they are all gpio9 which is the tca6424 on i2c5.

quoted

it's probably not a good
idea :) Or at least will be inaccurate if the bus can sleep.

I have tested a little by writing to /sys/class/leds/.../trigger.

If I make one LED trigger by "cpu0" it is always on and if I make
a second one triggered by "cpu1" the heartbeat becomes irregular.

So indeed this does not work.

So should we just leave the default trigger unpopulated then?

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html