Commit graph

5 commits

Author SHA1 Message Date
Adam Bickett
27009ef53b Revert "techpack: replace type with xtype while searching for sub-dirs"
Support build environments where find -xtype is not supported.

This reverts commit 5081f16b3d.

Change-Id: Ibb4a9f2429bad5e0bae690f60605887f01623a16
Signed-off-by: Adam Bickett <abickett@codeaurora.org>
2019-11-19 07:06:17 -08:00
Prakruthi Deepak Heragu
776ec744ee techpack: Kbuild: Fix to compile the techpack completely
Due to path being inaccurate, the techpack folder was not being
compiled completely. Using techpack fixes this issue.

Change-Id: Id06927e5b4bfad0d5c8208b199d9d217abbf6306
Signed-off-by: Prakruthi Deepak Heragu <pheragu@codeaurora.org>
Signed-off-by: Adam Bickett <abickett@codeaurora.org>
2019-11-18 18:26:04 -08:00
Satya Durga Srinivasu Prabhala
5081f16b3d techpack: replace type with xtype while searching for sub-dirs
To make sure sym links (if any) gets detected during search,
switch to xtype.

Change-Id: Idc0584b134f2ca4b395e53696e079337ff377f82
Signed-off-by: Satya Durga Srinivasu Prabhala <satyap@codeaurora.org>
2019-07-09 17:43:13 -07:00
Bryan Huntsman
8082260ee5 techpack: set configuration default to yes
Tech packages default configuration should be on.

Change-Id: I3cdf9276103f08db7130535aab1206a95a03b5a7
Signed-off-by: Bryan Huntsman <bryanh@codeaurora.org>
2019-06-04 10:59:26 -07:00
Bryan Huntsman
917caa9433 techpack: add tech package support
Enable tech packages to have kernel drivers that are physically
located in the kernel source tree but not present in the kernel
repository. This is done via a manifest line item to fetch a
techpackage-module into $KERNEL/techpack/$techpackage-module.
$KERNEL/techpack/Kbuild will automatically detect any
subdirectories and link them to the kernel's kbuild system.

The resulting layout of techpack within kernel source would be as
follows :-

    kernel/
    ├── techpack/
        ├── Kbuild
        └── stub
        │    ├── Makefile
        │    ├── include
        │    │   └── uapi
        │    │       └── Kbuild
             └── stub.c
        ├── techpackage-module
            ├── Makefile
            ├── include
            │   └── uapi
            │       ├── Kbuild

$KERNEL/techpack only contains Kbuild (no Makefile) at the
toplevel and this Kbuild takes care of both compiling the
subdirectories and of exporting the needed header files therein.
The reason for having only Kbuild at the top is that Kbuild
and Makefile cannot exist together in same directory and Makefile
doesn't cater to uapi header installation.

stub is an empty techpackage-module which serves both as a sample
layout and satisfies the requirement of kernel build system, by
providing necessary buit-in.o, when no other techpackage-module has
been pulled under techpack/.

$KERNEL/techpack/techpackage-module should have a Makefile at the
top and Kbuild under $KERNEL/techpack/techpackage-module/include/uapi
directory. The uapi headers pertaining to a techpackage-module
should reside under $KERNEL/techpack/techpackage-module/include/uapi
and associated Kbuild should have necessary rules to export it.

Change-Id: I0d0ced38566907d2074831edde0934833f666eff
Signed-off-by: Bryan Huntsman <bryanh@codeaurora.org>
Signed-off-by: Imran Khan <kimran@codeaurora.org>
[satyap@codeaurora.org: fix trivial merge conflict and add SPDX-License-Identifier]
Signed-off-by: Satya Durga Srinivasu Prabhala <satyap@codeaurora.org>
2019-03-21 10:18:12 -07:00