config USB_ISP1760 tristate "NXP ISP 1760/1761 support" depends on USB || USB_GADGET help Say Y or M here if your system as an ISP1760 USB host controller or an ISP1761 USB dual-role controller. This driver does not support isochronous transfers or OTG. This USB controller is usually attached to a non-DMA-Master capable bus. NXP's eval kit brings this chip on PCI card where the chip itself is behind a PLB to simulate such a bus. To compile this driver as a module, choose M here: the module will be called isp1760. config USB_ISP1760_HCD bool config USB_ISP1761_UDC bool if USB_ISP1760 choice bool "ISP1760 Mode Selection" default USB_ISP1760_DUAL_ROLE if (USB && USB_GADGET) default USB_ISP1760_HOST_ROLE if (USB && !USB_GADGET) default USB_ISP1760_GADGET_ROLE if (!USB && USB_GADGET) config USB_ISP1760_HOST_ROLE bool "Host only mode" depends on USB=y || USB=USB_ISP1760 select USB_ISP1760_HCD help Select this if you want to use the ISP1760 in host mode only. The gadget function will be disabled. config USB_ISP1760_GADGET_ROLE bool "Gadget only mode" depends on USB_GADGET=y || USB_GADGET=USB_ISP1760 select USB_ISP1761_UDC help Select this if you want to use the ISP1760 in peripheral mode only. The host function will be disabled. config USB_ISP1760_DUAL_ROLE bool "Dual Role mode" depends on USB=y || USB=USB_ISP1760 depends on USB_GADGET=y || USB_GADGET=USB_ISP1760 select USB_ISP1760_HCD select USB_ISP1761_UDC help Select this if you want to use the ISP1760 in both host and peripheral modes. endchoice endif f='/cgit.cgi/linux/net-next.git/refs/?h=nds-private-remove&id=79c6f448c8b79c321e4a1f31f98194e4f6b6cae7'>refslogtreecommitdiff
path: root/sound/soc/txx9
diff options
context:
space:
mode:
authorSteven Rostedt (VMware) <rostedt@goodmis.org>2017-01-30 19:27:10 -0500
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2017-01-31 09:13:49 -0500
commit79c6f448c8b79c321e4a1f31f98194e4f6b6cae7 (patch)
tree370efda701f03cccf21e02bb1fdd3b852547d75c /sound/soc/txx9
parent0c744ea4f77d72b3dcebb7a8f2684633ec79be88 (diff)
tracing: Fix hwlat kthread migration
The hwlat tracer creates a kernel thread at start of the tracer. It is pinned to a single CPU and will move to the next CPU after each period of running. If the user modifies the migration thread's affinity, it will not change after that happens. The original code created the thread at the first instance it was called, but later was changed to destroy the thread after the tracer was finished, and would not be created until the next instance of the tracer was established. The code that initialized the affinity was only called on the initial instantiation of the tracer. After that, it was not initialized, and the previous affinity did not match the current newly created one, making it appear that the user modified the thread's affinity when it did not, and the thread failed to migrate again. Cc: stable@vger.kernel.org Fixes: 0330f7aa8ee6 ("tracing: Have hwlat trace migrate across tracing_cpumask CPUs") Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'sound/soc/txx9')