atrusd: start with extended diagnostics |
||||
Issue descriptionThe expected behavior of atrusd is to poll all extended diagnostic commands immediately after the device is connected.
,
Jun 28 2017
,
Jul 6 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/atrusctl/+/7ebbdb5f3d3d0b843cb170437e47608d2dc352f7 commit 7ebbdb5f3d3d0b843cb170437e47608d2dc352f7 Author: Emil Lundmark <lndmrk@chromium.org> Date: Thu Jul 06 10:26:32 2017 Start with doing an extended diagnostic Immediately after the device is connected, perform a extended diagnostic. BUG= chromium:737499 TEST=Connected a device and verified that extended diagnostic messages immediately appeared in the logs. Change-Id: I8f3bce609603ad7fc398a362c578449a39ce6a9b Reviewed-on: https://chromium-review.googlesource.com/552151 Commit-Ready: Emil Lundmark <lndmrk@chromium.org> Tested-by: Emil Lundmark <lndmrk@chromium.org> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Karl Petersson <karl@limesaudio.com> [modify] https://crrev.com/7ebbdb5f3d3d0b843cb170437e47608d2dc352f7/src/diagnostics.cc
,
Jul 6 2017
,
Jul 18 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by lndmrk@chromium.org
, Jun 28 2017