Added myself as a collaborator to the areas I frequently contribute or
review code. List includes:
- Display drivers
- Documentation
- Kscan drivers
- Sensor drivers
- Power management
- STM32 platform
- Pinmux/pinctrl drivers
- PWM drivers
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
Add risc-v maintainers and update collaborators.
Signed-off-by: Filip Kokosinski <fkokosinski@antmicro.com>
Signed-off-by: Karol Gugala <kgugala@antmicro.com>
Signed-off-by: Peter Gielda <pgielda@antmicro.com>
Signed-off-by: Tomasz Gorochowik <tgorochowik@antmicro.com>
This is an area that is quickly growing and changing. Better having
someone taking a look at the incoming patches.
Set myself and Arnaud as maintainers.
Signed-off-by: Carlo Caione <ccaione@baylibre.com>
This CL renames 'Nuvoton Platform' as 'Nuvoton_NPCX Platform' and
modifies the relevant files used by this platform. It also changes
status from 'orphaned' to 'maintained' since we do maintain npcx drivers
continuously.
Signed-off-by: Mulin Chao <mlchao@nuvoton.com>
I cannot invest the time required for maintaining the networking
stack anymore, so I am stepping down from the maintainer role.
I am proposing Rober Lubos to be a new network maintainer.
I have been working with him for several years, and he is always
very helpful and knowledgeable to review and comment patches and
issues. He knows the network stack well and will for sure be able
to handle the task as he has been doing the maintenance already
for a long time.
Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Acked-by: Robert Lubos <robert.lubos@nordicsemi.no>
Add C++ area, which covers the C++ language support subsystem and the
relevant tests and samples, with myself as a maintainer.
Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
Add "CMSIS-DSP integration" area, which covers the module configs and
tests for the CMSIS-DSP library, with myself as a maintainer.
Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
Adding myself as a maintainer for the "C library" area covering both
the minimal libc and newlib, and updating the list of the relevant
files.
Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
Currently the Cortex-R platform has no one watching over it. Submitting
myself to help with the Cortex-R parts of the ARM architecture.
Signed-off-by: Bradley Bolen <bbolen@lexmark.com>
- Move PM related APIs to `include/pm` so that it follows API `pm_`
prefix namespace. In order to make transition easier
`include/power/power.h` is kept pointing to `include/pm/pm.h`.
- Move most of device PM related content from `include/device.h` to
`include/pm/device.h` and `include/pm/runtime.h`.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
This adds support to generate SPDX 2.2 tag-value documents via the
new west spdx command. The CMake file-based APIs are leveraged to
create relationships from source files to the corresponding
generated build files. SPDX-License-Identifier comments in source
files are scanned and filled into the SPDX documents.
Before `west build` is run, a specific file must be created in the
build directory so that the CMake API reply will run. This can be
done by running:
west spdx --init -d BUILD_DIR
After `west build` is run, SPDX generation is then activated by
calling `west spdx`; currently this requires passing the build
directory as a parameter again:
west spdx -d BUILD_DIR
This will generate three SPDX documents in `BUILD_DIR/spdx/`:
1) `app.spdx`: This contains the bill-of-materials for the
application source files used for the build.
2) `zephyr.spdx`: This contains the bill-of-materials for the
specific Zephyr source code files that are used for the build.
3) `build.spdx`: This contains the bill-of-materials for the built
output files.
Each file in the bill-of-materials is scanned, so that its hashes
(SHA256 and SHA1) can be recorded, along with any detected licenses
if an `SPDX-License-Identifier` appears in the file.
SPDX Relationships are created to indicate dependencies between
CMake build targets; build targets that are linked together; and
source files that are compiled to generate the built library files.
`west spdx` can be called with optional parameters for further
configuration:
* `-n PREFIX`: specifies a prefix for the Document Namespaces that
will be included in the generated SPDX documents. See SPDX spec 2.2
section 2.5 at
https://spdx.github.io/spdx-spec/2-document-creation-information/.
If -n is omitted, a default namespace will be generated according
to the default format described in section 2.5 using a random UUID.
* `-s SPDX_DIR`: specifies an alternate directory where the SPDX
documents should be written. If not specified, they will be saved
in `BUILD_DIR/spdx/`.
* `--analyze-includes`: in addition to recording the compiled
source code files (e.g. `.c`, `.S`) in the bills-of-materials, if
this flag is specified, `west spdx` will attempt to determine the
specific header files that are included for each `.c` file. This
will take longer, as it performs a dry run using the C compiler
for each `.c` file (using the same arguments that were passed to it
for the actual build).
* `--include-sdk`: if `--analyze-includes` is used, then adding
`--include-sdk` will create a fourth SPDX document, `sdk.spdx`,
which will list any header files included from the SDK.
Signed-off-by: Steve Winslow <steve@swinslow.net>
No area can have 'status: maintained' without a maintainer.
Mark such areas as 'orphaned' instead.
Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
Add Alexandre and François as collaborators on STM32 Platforms.
Additionally, add one naming for stm32 boards.
Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
Update collaborators and maintainer of some orphaned areas. Also update
path for some of the areas to include tests and samples.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Move ptp_clock.h out of the top level include/ dir into
include/drivers/ptp_clock.h and deprecated the old location.
Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
