Return-path: Received: from mail-la0-f54.google.com ([209.85.215.54]:60479 "EHLO mail-la0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757334AbaGWIex (ORCPT ); Wed, 23 Jul 2014 04:34:53 -0400 Received: by mail-la0-f54.google.com with SMTP id el20so649971lab.27 for ; Wed, 23 Jul 2014 01:34:52 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <1406070154-6614-1-git-send-email-greearb@candelatech.com> Date: Wed, 23 Jul 2014 11:34:52 +0300 Message-ID: (sfid-20140723_103501_379773_308F4D64) Subject: Re: [PATCH v3 1/5] ath10k: provide firmware crash info via debugfs. From: Emmanuel Grumbach To: Michal Kazior Cc: Ben Greear , linux-wireless , "ath10k@lists.infradead.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, Jul 23, 2014 at 11:25 AM, Michal Kazior wrote: > On 23 July 2014 01:02, wrote: >> From: Ben Greear >> >> Store the firmware crash registers and last 128 or so >> firmware debug-log ids and present them to user-space >> via debugfs. >> >> Should help with figuring out why the firmware crashed. >> Do we plan to have a common place for all the drivers? I'd suggest to have mac80211 / cfg80211 link to a file created by the driver. This would allow us to have this file even if we haven't registered to mac80211 yet - although it'd be under a different place. What do you think?