On Tue 29 Mar 11:32 PDT 2016, Nicolas Dechesne wrote: > On Tue, Mar 29, 2016 at 4:51 PM, Bjorn Andersson > <bjorn.andersson@xxxxxxxxxx> wrote: > >> Am ok, to change, did you get activity leds works with any of these strings > >> with WLAN or BT? > >> > > > > I did test them; rx, assoc and radio seems to work. Tx does not tickle > > the led, but should probably. > > > > I didn't find the spec for the baord, so I'm not sure what the LEDs > > should indicate. But it feels like radio or assoc makes most sense, and > > follows what we can do with the BT led. > > this is in the 96boards 'specs' at [1], which states > > - > The User LEDs shall be directly programmable from the SoC. > 1. WiFi activity LED > 2. Bluetooth activity LED > - > > [1] http://www.96boards.org/ce-specification Thanks Nico. I presume "activity" here means it should be off and blink upon data being transmitted in either direction? Sounds like we need to plan some work to extend the existing triggers with a phyXactivity and hciX-activity. For now I think we should go with phy0assoc and hci-power though, so we have something related to WiFi and BT. Regards, Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
