Messages in this thread | | | Date | Wed, 21 Feb 2018 14:59:05 -0800 | From | Brian Norris <> | Subject | Re: [PATCH 2/3] mwifiex: support sysfs initiated device coredump |
| |
On Wed, Feb 21, 2018 at 11:50:19AM +0100, Arend van Spriel wrote: > Since commit 3c47d19ff4dc ("drivers: base: add coredump driver ops") > it is possible to initiate a device coredump from user-space. This > patch adds support for it adding the .coredump() driver callback. > As there is no longer a need to initiate it through debugfs remove > that code. > > Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com> > --- > drivers/net/wireless/marvell/mwifiex/debugfs.c | 31 +------------------------- > drivers/net/wireless/marvell/mwifiex/pcie.c | 19 ++++++++++++++-- > drivers/net/wireless/marvell/mwifiex/sdio.c | 13 +++++++++++ > drivers/net/wireless/marvell/mwifiex/usb.c | 14 ++++++++++++ > 4 files changed, 45 insertions(+), 32 deletions(-)
The documentation doesn't really say [1], but is the coredump supposed to happen synchronously? Because the mwifiex implementation is asynchronous, whereas it looks like the brcmfmac one is synchronous.
Brian
[1] In fact, the ABI documentation really just describes kernel internals, rather than documenting any user-facing details, from what I can tell.
| |