Add logic to the wcnss module so that it can either be statically
built into the kernel or built as a dynamically loaded module. Up to
this point the wcnss driver only supported dynamic loading, however an
upcoming wcnss subsystem restart change requires that it be statically
linked into the kernel. The major difference between these two modes
is that when the module is dynamically loaded it can assume upon
module init that userspace is available to service the peripheral
image loader (PIL), whereas when the module is statically linked it
cannot assume that userspace is available. Therefore when the module
is statically linked, during module init it instantiates a sysfs file
node, and only after userspace has indicated it is available by
touching that sysfs node can the module perform its "normal"
initialization including triggering the PIL.
Change-Id: I2b88b358d45bc8f9c4e603173d7c2b72ea7bac0c
Signed-off-by: Jeff Johnson <jjohnson@codeaurora.org>
b3377e32af