• Abhishek Pandit-Subedi's avatar
    Bluetooth: Add support for hci devcoredump · 9695ef87
    Abhishek Pandit-Subedi authored
    Add devcoredump APIs to hci core so that drivers only have to provide
    the dump skbs instead of managing the synchronization and timeouts.
    
    The devcoredump APIs should be used in the following manner:
     - hci_devcoredump_init is called to allocate the dump.
     - hci_devcoredump_append is called to append any skbs with dump data
       OR hci_devcoredump_append_pattern is called to insert a pattern.
     - hci_devcoredump_complete is called when all dump packets have been
       sent OR hci_devcoredump_abort is called to indicate an error and
       cancel an ongoing dump collection.
    
    The high level APIs just prepare some skbs with the appropriate data and
    queue it for the dump to process. Packets part of the crashdump can be
    intercepted in the driver in interrupt context and forwarded directly to
    the devcoredump APIs.
    
    Internally, there are 5 states for the dump: idle, active, complete,
    abort and timeout. A devcoredump will only be in active state after it
    has been initialized. Once active, it accepts data to be appended,
    patterns to be inserted (i.e. memset) and a completion event or an abort
    event to generate a devcoredump. The timeout is initialized at the same
    time the dump is initialized (defaulting to 10s) and will be cleared
    either when the timeout occurs or the dump is complete or aborted.
    Signed-off-by: default avatarAbhishek Pandit-Subedi <abhishekpandit@chromium.org>
    Signed-off-by: default avatarManish Mandlik <mmandlik@google.com>
    Reviewed-by: default avatarAbhishek Pandit-Subedi <abhishekpandit@chromium.org>
    Signed-off-by: default avatarLuiz Augusto von Dentz <luiz.von.dentz@intel.com>
    9695ef87
coredump.c 12.8 KB