qcacld-3.0: Enable wlan bazel compilation for Netrani.LA.2.5

Add support to enable wlan bazel compilation on
Netrani.LA.2.5 for qca6750.

Change-Id: Ida90bf07459e578c41ae969d54f4ed8f234d4f08
CRs-Fix

qcacld-3.0: Enable wlan bazel compilation for Netrani.LA.2.5

Add support to enable wlan bazel compilation on
Netrani.LA.2.5 for qca6750.

Change-Id: Ida90bf07459e578c41ae969d54f4ed8f234d4f08
CRs-Fixed: 3834651

show more ...

qcacld-3.0: Enable wlan BAZEL compilation for volcano

Enable wlan BAZEL compilation for volcano.

Change-Id: I5da7d1546607dd57e66b76f6925b424953ec8a3c
CRs-Fixed: 3744660

qcacld-3.0: Update hardcoded path for BOARD_OPENSOURCE_DIR

Some targets use a different location for the build scripts and
set the BOARD_OPENSOURCE_DIR build variable accordingly.
If this variable i

qcacld-3.0: Update hardcoded path for BOARD_OPENSOURCE_DIR

Some targets use a different location for the build scripts and
set the BOARD_OPENSOURCE_DIR build variable accordingly.
If this variable is set, pick up WLAN source code from this location.

Change-Id: I3ff09ac25ab6ce627f658182b395371de1a1969e
CRs-Fixed: 3636187

show more ...

qcacld-3.0: Add changes to compile qcacld for Niobe target

- Add defconfigs for consoilidated and GKI variants.
- Add Niobe target to wlan bazel config.

Change-Id: I4d3ccee42a1d05fd77ecf791c4d4e4

qcacld-3.0: Add changes to compile qcacld for Niobe target

- Add defconfigs for consoilidated and GKI variants.
- Add Niobe target to wlan bazel config.

Change-Id: I4d3ccee42a1d05fd77ecf791c4d4e48505e0f716
CRs-Fixed: 3614371

show more ...

qcacld-3.0: cld sun changes

Changes needed to build cld driver
on sun.

Change-Id: I3bbb0180b070a65364b6768f4e4fd8c4b3fbee4f
CRs-Fixed: 3601936

qcacld-3.0: Add peach target for bazel

Current wlan bazel implementation does
not support peach chipset.
Fix this by adding peach chipset support.

Change-Id: Ic3cffeebd030db928a4d427b5e3fb03f8e776d

qcacld-3.0: Add peach target for bazel

Current wlan bazel implementation does
not support peach chipset.
Fix this by adding peach chipset support.

Change-Id: Ic3cffeebd030db928a4d427b5e3fb03f8e776d4d
CRs-Fixed: 3590359

show more ...

qcacld-3.0: Append secondary wlan number to LOCAL_MOD_NAME

For dual wlan chip, local module name will be same once TARGET_MULTI_WLAN
is set to true. For example, for dual HST, two wlan driver module

qcacld-3.0: Append secondary wlan number to LOCAL_MOD_NAME

For dual wlan chip, local module name will be same once TARGET_MULTI_WLAN
is set to true. For example, for dual HST, two wlan driver modules will
be created. If TARGET_MULTI_WLAN is true, two modules qca6390 will be
created.

So append number to secondary module. One is qca6390, the other is
qca6390_2.

Change-Id: Icbf51e278ced30b90ce4c726ba812d15b7aee7a2
CRs-Fixed: 3578003

show more ...

qcacld-3.0: Fix ddk enable check

Current code checks vendor version not target to determine
whether or not to enable bazel ddk. Fix this by checking
both vendor version and target to enable DDK.

Ch

qcacld-3.0: Fix ddk enable check

Current code checks vendor version not target to determine
whether or not to enable bazel ddk. Fix this by checking
both vendor version and target to enable DDK.

Change-Id: I7503ce966d128d9a1350426eb8a9aee6dd013a1d
CRs-Fixed: 3581963

show more ...

qcacld-3.0: Enable DDK build system

Will allow DDK to be enabled and generate required
symlinks for DDK build.

Change-Id: Iadba338b1b74fa0be187ac17b22e1c2ed89f4a4d
CRs-Fixed: 3533892

qcacld-3.0: Use dynamic symbolic links for multi-ko support

This reverts Change-Id I7d75bb6a82fd27d8925d53529b4252b782457bc8
("qcacld-3.0: Use static symbolic links for multi-ko support") along
with

qcacld-3.0: Use dynamic symbolic links for multi-ko support

This reverts Change-Id I7d75bb6a82fd27d8925d53529b4252b782457bc8
("qcacld-3.0: Use static symbolic links for multi-ko support") along
with removing per-chipset symbolic links added after that patch.

The original patch was created to allow the qcacld-3.0 driver to
conform to the Hermetic Build feature which required that the source
directory not be modified during the build process. However,
qcacld-3.0 is transitioning to the Bazel DDK, and the presence of the
symbolic links is interfering with Bazel. In addition, the Bazel
build system won't use these symbolic links. So the support both the
legacy build system (in a non-hermetic manner) as well as the Bazel
DDK (in a hermetic manner), revert back to dynamically creating the
symbolic links.

Change-Id: I2b6a0ed19f7f4b3ae31d28e2b4683afd0671f19a
CRs-Fixed: 3495618

show more ...

qcacld-3.0: Android mk change for out of tree IPA

The IPA component has now been moved out of
the kernel. This change supports WLAN dependency
on IPA to access the IPA header files and
exported modu

qcacld-3.0: Android mk change for out of tree IPA

The IPA component has now been moved out of
the kernel. This change supports WLAN dependency
on IPA to access the IPA header files and
exported module symbols.

Change-Id: I0eb1b9ca49108cf27cec2895696d2517acb7d18e
CRs-Fixed: 3458960

show more ...

qcacld-3.0: add support for dual wlan modules on Android platform

Update Android makefile to support dual wlan driver modules.
Define the secondary wlan chip with postfix string "cnss2".
Use differe

qcacld-3.0: add support for dual wlan modules on Android platform

Update Android makefile to support dual wlan driver modules.
Define the secondary wlan chip with postfix string "cnss2".
Use different wlan ctrl name parameter for secondary wlan module.

Change-Id: I62fd7f258b3b8944e2b731d00d413d7a1a0d4290
CRs-Fixed: 3248293

show more ...

qcacld-3.0: compilation fix for ks sync path change

For SDW5100 release branch path for common dir is changed to
device/qcom/common/monaco which is being specified in target mk file.
This change ens

qcacld-3.0: compilation fix for ks sync path change

For SDW5100 release branch path for common dir is changed to
device/qcom/common/monaco which is being specified in target mk file.
This change ensures other SI compilation will not break.

Change-Id: If8aa35a2e2da0e42b34c77ff8097c26aa2aa83d1
CRs-Fixed: 3020014

show more ...

qcacld-3.0: Support compile driver with out-of-tree CNSS drivers

When sources of CNSS family drivers are compiled out of kernel tree,
all necessary config flags will come from upper level Makefile f

qcacld-3.0: Support compile driver with out-of-tree CNSS drivers

When sources of CNSS family drivers are compiled out of kernel tree,
all necessary config flags will come from upper level Makefile files
like wlan.mk instead of kernel defconfig. Also module symbol file will
not be part of kernel build output directory anymore. Hence add changes
in Android.mk to handle such case in oreder to compile WLAN host driver.

Change-Id: I3f104ddb7495ca2dfb797adbc7dc982d2f24d30c
CRs-fixed: 3022579

show more ...

qcacld-3.0: Use makefile flag to select DLKM makefile

The kernel is transitioning from AndroidKernelModule.mk to
Build_external_kernelmodule.mk as the helper makefile for building
DLKMs. As the new

qcacld-3.0: Use makefile flag to select DLKM makefile

The kernel is transitioning from AndroidKernelModule.mk to
Build_external_kernelmodule.mk as the helper makefile for building
DLKMs. As the new makefile was introduced for the "taro" platform,
initially a platform check was introduced to determine which makefile
to include. However this is not a scalable approach.

Recently the flag TARGET_USES_KERNEL_PLATFORM was added to the build
system, so update the logic such that when this flag is set to 'true'
we will use Build_external_kernelmodule.mk.

Change-Id: I2200b27753263b931cebdbff5445d50b1fc2b94f
CRs-Fixed: 2913254

show more ...

qcacld-3.0: Use $(call symlink-file) to create symlinks

Currently Android.mk uses $(shell) to create symlinks. Due to the way
this is used these commands will run for every build, even if the
symlin

qcacld-3.0: Use $(call symlink-file) to create symlinks

Currently Android.mk uses $(shell) to create symlinks. Due to the way
this is used these commands will run for every build, even if the
symlinks are already present. Per the Hermetic Build feature we should
not execute any unnecessary commands, especially for incremental
builds where no changes are present from the prior build. Therefore
change the symlink logic to use the Android symlink-file rule-based
mechanism.

Change-Id: I47b9de34eec0faa193263765a0a86befb5e92ced
CRs-Fixed: 2907684

show more ...

qcacld-3.0: Use static symbolic links for multi-ko support

The current multi-ko support is achieved by creating, during the
actual build process, target-specific .<chip> symbolic links beneath
the q

qcacld-3.0: Use static symbolic links for multi-ko support

The current multi-ko support is achieved by creating, during the
actual build process, target-specific .<chip> symbolic links beneath
the qcacld-3.0 folder. Unfortunately this mechanism violates the
requirements of the Hermetic Build feature which requires that the
source directory not be modified during the build process.

To satisfy this requirement remove the dynamic creation of symbolic
links from Android.mk, and instead staticially instantiate all of the
required symbolic links in the git project.

Change-Id: I7d75bb6a82fd27d8925d53529b4252b782457bc8
CRs-Fixed: 2896976

show more ...

qcacld-3.0: Decouple state control file from module name

wlan_hdd_state_ctrl_param_create() creates a control file that is
used to synchronize the wlan driver with the Wi-Fi HAL in
userspace.

Curre

qcacld-3.0: Decouple state control file from module name

wlan_hdd_state_ctrl_param_create() creates a control file that is
used to synchronize the wlan driver with the Wi-Fi HAL in
userspace.

Currently the driver creates the file at the path /dev/<module>.

The WIFI_DRIVER_STATE_CTRL_PARAM configuration item defines the path
that the Wi-Fi HAL uses, and this is /dev/wlan.

So when the driver is built with a module name of "wlan" the file is
created at the expected path. However when the driver is built with a
different name, as is done when TARGET_MULTI_WLAN is enabled, the file
is not created at the expected path.

Therefore change the driver to always create the file at the path
specified in the WIFI_DRIVER_STATE_CTRL_PARAM configuration item.

In addition do not even enable the functionality if the
WIFI_DRIVER_STATE_CTRL_PARAM configuration item is not set
(i.e. on non-Android platforms).

Change-Id: I8a7f0a9b22e3f49d02f896150bd452f80af9c022
CRs-Fixed: 2905381

show more ...

qcacld-3.0: Update multi-ko support for hermetic builds

The current multi-ko support is achieved by creating, during the
actual build process, target-specific .<chip> folders beneath the
qcacld-3.0

qcacld-3.0: Update multi-ko support for hermetic builds

The current multi-ko support is achieved by creating, during the
actual build process, target-specific .<chip> folders beneath the
qcacld-3.0 folder, and then populating those folders with a variety of
symbolic links. Unfortunately this mechanism violates the requirements
of the Hermetic Build feature which requires that the source directory
not be modified during the build process.

One solution to this problem is to actually add the target-specific
folders, along with the included symlinks, to the qcacld-3.0 git
project. But one maintenance issue with this approach is that these
folders of symlinks would require update when the qcacld-3.0 directory
structure changes.

An alternative solution is that instead of having each .<chip> file be
a folder of symlinks, let each .<chip> file be symbolic link. This
approach reduces the maintenance issue since you only need to add a
new .<chip> symbolic link when a new target is added; no changes are
required to the symbolic links when a new qcacld-3.0 folder is added.

As a precursor to transitioning to this alternate solution, update the
current build mechanism such that only .<chip> symbolic links are
created in the source directory, and update the remainder of the
multi-ko logic to align with the resulting change in pathnames.

A subsequent change can remove the dynamic symbolic link creation, and
instead add the symbolic links to the git project.

Change-Id: Ie3df49217ffec260085285b1ae25113c3a943e9b
CRs-Fixed: 2889020

show more ...

qcacld-3.0: Use symbolic link to reference qca-wifi-host-cmn

A recurring issue is that, due to the large number of object files and
the long pathnames to those files, a build of the qca_cld3_wlan.ko

qcacld-3.0: Use symbolic link to reference qca-wifi-host-cmn

A recurring issue is that, due to the large number of object files and
the long pathnames to those files, a build of the qca_cld3_wlan.ko may
fail with an E2BIG error. This can occur when a shell command created
by the build system exceeds the max size of a command that the shell
can handle. This usually occurs when linking all of the individual
object files into the final wlan.o.

Object files from the qcacld-3.0 project begin with:
<prefix>/vendor/qcom/opensource/wlan/qcacld-3.0

Object files from the qca-wifi-host-cmn project begin with:
<prefix>/vendor/qcom/opensource/wlan/qcacld-3.0/../qca-wifi-host-cmn

To shorten the qca-wifi-host-cmn paths add the following symbolic link:
qcacld-3.0/cmn => ../qca-wifi-host-cmn

With this in place object files from the qca-wifi-host-cmn project
will begin with:
<prefix>/vendor/qcom/opensource/wlan/qcacld-3.0/cmn

This will save 17 characters per qca-wifi-host-cmn object file.

Change-Id: I104afdc48e5335aa232bac988c4c652144cd4e58
CRs-Fixed: 2893361

show more ...

qcacld-3.0: Enable single-target SPF support

Currently the SPF support is triggered when there is more than one
target specified in TARGET_WLAN_CHIP. For taro we know we need
multi-target support in

qcacld-3.0: Enable single-target SPF support

Currently the SPF support is triggered when there is more than one
target specified in TARGET_WLAN_CHIP. For taro we know we need
multi-target support in the future, but we only want to support a
single target during bringup. However we want all procedures
established during the bringup process to be applicable to the final
product. Therefore update the logic such that SPF support is triggered
whenever the TARGET_WLAN_CHIP is anything other than the default value
of 'wlan'.

Change-Id: I0a0671d2ebbdb85985bc57376b4acd2bd79a16ae
CRs-Fixed: 2890488

show more ...

qcacld-3.0: Add debugging infrastructure to Android.mk

The qcacld-3.0 Android.mk is unique in that it can be called
recursively. This behavior can make it difficult to debug build
issues. To help al

qcacld-3.0: Add debugging infrastructure to Android.mk

The qcacld-3.0 Android.mk is unique in that it can be called
recursively. This behavior can make it difficult to debug build
issues. To help alleviate this problem, add a user function to
Android.mk to allow debug information to be logged, and add a few logs
which will be useful in debugging recursion issues. In addition change
a few $(warning) calls to use the infrastructure since under normal
use the Android.mk should be silent.

Change-Id: I660ceddaf53e42c331deba5d33b32360b549cfc7
CRs-Fixed: 2890484

show more ...

qcacld-3.0: Update Android.mk for GKI module installation

For Generic Kernel Image builds kernel scripts take care of module
installation on required parition. Thus update wlan driver Android.mk
to

qcacld-3.0: Update Android.mk for GKI module installation

For Generic Kernel Image builds kernel scripts take care of module
installation on required parition. Thus update wlan driver Android.mk
to not create symlink if WIFI_DRIVER_INSTALL_TO_KERNEL_OUT is set to
true by GKI enabled android build system.

Change-Id: Ie0b6de98ead5f7e5eba106f0a98901f6c7ee3861
CRs-fixed: 2881952

show more ...

qcacld-3.0: Add flags to the BUILD_TAG

Pass a new flag to the Kbuild and add a compile flag
to enable the BUILD_TAG information.

Change-Id: Ic9bc331b64e7cbf627f5f99758f4d556328cda10
CRs-Fixed: 2865

qcacld-3.0: Add flags to the BUILD_TAG

Pass a new flag to the Kbuild and add a compile flag
to enable the BUILD_TAG information.

Change-Id: Ic9bc331b64e7cbf627f5f99758f4d556328cda10
CRs-Fixed: 2865654

show more ...

qcacld-3.0: Add support for Build_external_kernelmodule.mk

The Android build infrastructure is transitioning to a new
mechansim for building external modules. Update the qcacld-3.0
driver to use tha

qcacld-3.0: Add support for Build_external_kernelmodule.mk

The Android build infrastructure is transitioning to a new
mechansim for building external modules. Update the qcacld-3.0
driver to use that mechanism for toro builds.

Change-Id: I7d73bc1ccbde5ecc74c661fd6e31525b266413cd
CRs-Fixed: 2852877

show more ...