remarkable-linux/drivers/staging/btmtk_usb
Devendra Naga 51dd7d2995 staging: btmtk_usb: use GFP_KERNEL inplace of GFP_ATOMIC in _probe path
the _probe function doesn't run in interrupt context, so no need to use
the GFP_ATOMIC allocations, instead driver can request for GFP_KERNEL

Signed-off-by: Devendra Naga <devendra.aaru@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2013-06-03 12:35:53 -07:00
..
btmtk_usb.c staging: btmtk_usb: use GFP_KERNEL inplace of GFP_ATOMIC in _probe path 2013-06-03 12:35:53 -07:00
btmtk_usb.h Staging: add USB MTK bluetooth driver 2013-05-16 15:43:48 -07:00
Kconfig Staging: add USB MTK bluetooth driver 2013-05-16 15:43:48 -07:00
Makefile Staging: add USB MTK bluetooth driver 2013-05-16 15:43:48 -07:00
README Staging: add USB MTK bluetooth driver 2013-05-16 15:43:48 -07:00
TODO Staging: add USB MTK bluetooth driver 2013-05-16 15:43:48 -07:00

-build driver modules
	make

-install driver modules
	make install

-remove driver modules
	make clean

-dynamic debug message
	turn on CONFIG_DYNAMIC_DEBUG compiler flag for current kernel
	mount -t debugfs none /sys/kernel/debug/
	echo "module module_name +p" > /sys/kernel/debug/dynamic_debug/control(turn on debug messages, module name such as btmtk_usb)
	echo "module module_name -p" > /sys/kernel/debug/dynamic_debug/control(turn off debug messages, module name such as btmtk_usb)