On Wed, 2014-11-19 at 05:58 -0800, Amitkumar Karwar wrote: > >The more intended use case for this was to trigger it when the driver > >detected a crash, but I guess a debugfs file works as well, just not > >sure when you'd want it. > > When user encounters a case when firmware doesn't respond or got hang, > firmware dump can be triggered via debugfs command. Sure, but do you want to hand-hold users through it? and do they even have debugfs? At least for us we intentionally made this a general framework so if it crashes/hangs and we detect it we can automatically trigger it and collect it for bug reports. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
