There is a typo (s/ares/area/).
More importantly, there are examples of areas with this status that do
not have any collaborators:
- Drivers: Interrupt controllers
- Little FS
Fix the text to reflect reality.
Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
an area without maintainer is still considered active, calling it orphan
is a bit extreme. We have some areas that can be considered "orphaned",
those now will be covered with 'odd fixes' status, meaning that they
might have one or more collaborator and getting some changes from time
to time, but nothing beyond fixes and nobody driving the area beyond
where it is right now.
Even an area with a dedicated maintainer can be have the status of 'odd
fixes', i.e. there is a maintainer but the area is stale and no further
development is happening.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
The random subsystem was not included in the maintainers file. Just add
a new entry for it and add myself (Flavio) as collaborator.
Signed-off-by: Flavio Ceolin <flavio.ceolin@intel.com>
This contains accessor macros for getting the maximum bitrate supported
by a CAN controller/transceiver combination.
Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
Add a Bluetooth Audio section in the maintainers
file for the Bluetooth Audio (sub)subsystem.
The Bluetooth Audio stack is a significant size, and
there's a signficant amount of people working on it,
where many do not have proper review rights and
many that do not get automatically assigned
for reviews.
I've included Vudentz as he has been very active in
the early days.
I've excluded szymon-czapracki as he has not yet
contributed a significant amount, even if he is
involved.
Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
Remove myself as maintainer due to planned sabbatical and add Joakim
as TF-M maintainer in my place.
Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
Start using the upstream Kconfig from LVGL and move the glue code out
of the zephyr tree and put it under lvgl/zephyr/ in modules.
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@huawei.com>
We don't have a formal maintainer for this and we should.
I nominate gmarull as the original author and designer of the API,
especially given his continued work reviewing incoming
implementations.
Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
While Kumar (@galak) is away, I'm de facto DT maintainer. Might as
well make it official. Kumar can always take the reins again when he
returns, if he wants them back.
Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
Adding UART samples to "Drivers: Serial/UART" so that the maintainer
will be notified for relevant PRs in the future.
Signed-off-by: Martin Jäger <martin@libre.solar>
Add RISC-V GD32 official boards (e.g. gd32vf103v_eval) to the file list
in the GD32 Platforms section.
Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
The Bluetooth Controller and the Bluetooth Mesh have separate maintainer
entries, and should not be covered by the Bluetooth entry itself, as
this causes jhedberg to get assigned to all PRs for these directories,
instead of cvinayak and trond-snekvik.
Adds a files-exclude list for the Bluetooth section of MAINTAINERS.yml
to ensure that PRs that only change any of these folders stop matching
the Bluetooth entry. Also adds "area: Bluetooth" to these directories,
as we'd still like all controller and mesh PRs to be labeled Bluetooth.
Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
Promote the Controller Area Network (CAN) subsystem reference
documentation from being part of the networking subsystem documentation
to having its own section.
The networking subsystem primarily deals with IP-based networking,
whereas CAN is a subsystem of its own.
Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
Removing maintainer and/or collaborator status on
- nRF platforms
- TF-M
- userspace
- cmsis-dsp
- MAINTAINERS file
for ioannisg. Replace with @anangl or others, where applicable.
Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
I'm taking over for joerchan at Nordic Semiconductor as a Zephyr
Bluetooth host collaborator.
Signed-off-by: Aleksander Wasaznik <aleksander.wasaznik@nordicsemi.no>
Adding myself as build collaborator as requested by Carles.
Will hopefully let code review go smoother.
Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
Add myself (original author) as the maintainer of the task watchdog.
Also including myself as a collaborator to the hardware watchdog
driver, as task watchdog and hardware watchdog are closely related.
Signed-off-by: Martin Jäger <martin@libre.solar>
Include the CANopenNode module integration files in the CAN bus
maintainers group and assign ownership to me.
Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
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>
I won't be supporting Zephyr for the foreseeable future, so remove my
association with specific subsystems.
Signed-off-by: Peter A. Bigot <pab@pabigot.com>
I have not had time to work with USB recently, so removing myself from
MAINTAINERS and CODEOWNERS for the USB subsystem.
Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
Add Thalley (emil.gydesen@nordicsemi.no) and asbjornsabo
(asbjorn.sabo@nordicsemi.no) as additional maintainers/codeowners for
bluetooth audio.
(Also adds empty audio.h file, that will later be expanded, so that
the include/bluetooth/audio directory now listed in CODEOWNERS
actually exists.)
Signed-off-by: Asbjørn Sæbø <asbjorn.sabo@nordicsemi.no>
AArch64 has support for PSCI. This is especially useful for SMP because
PSCI is used to power on the secordary cores.
When the PSCI driver was introduced in Zephyr it was designed to rely on
a very PSCI-centric subsystem / interface.
There are two kinds of problems with this choice:
1. PSCI is only defined for the non-secure world and it is designed to
boot CPU cores into non-secure state (that means that PSCI is only
supposed to work if Zephyr is running in non-secure state)
2. There can be other ways or standards used to start / stop a core
different from PSCI
This patch is trying to fix the original wrong assumption by making the
interface / subsystem a generic one, called 'pm_cpu_ops', and using PSCI
only as an actual driver that is a user of this new interface /
subsystem.
For now the new subsystem is only exposing two methods: cpu_on and
cpu_off, others will probably follow according to the needs.
Signed-off-by: Carlo Caione <ccaione@baylibre.com>
Add Nuvoton developers, ChiHuaL and WealianLiao, as collaborators for
Nuvoton platforms in MAINTAINERS.yaml.
Signed-off-by: Mulin Chao <mlchao@nuvoton.com>
The changes here are the result of running all open pull-requests
through a script to identify the assignee and findi ng many gaps or old
data. Some of the changes here are coming from pending PRs that were
waiting for some TSC confirm ation, others are done based on pending
maintainer and collaborator changes that were not submitting yet.
Two noteable changes:
- CMake/Build system: This is now limited to just the infrastructure and
not every single Cmake file in the tree. - Documentation: ditto, this
is just for the doc infrastructure and not for every RST file in the
tree.
The reason for the above two changes is the fact that most PRs would
have some cmake or doc changes and assignees in this case should not be
the owners of the build system or the doc infra, instead we should
assign to the subsystem being changed. (Otherwise majority of PRs would
be assigned to the doc and build system maintainers).
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Firmware implementing the PSCI functions described in ARM document
number ARM DEN 0022A ("Power State Coordination Interface System
Software on ARM processors") can be used by Zephyr to initiate various
CPU-centric power operations.
It is needed for virtualization, it is used to coordinate OSes and
hypervisors and it provides the functions used for SMP bring-up such as
CPU_ON and CPU_OFF.
A new PSCI driver is introduced to setup a proper subsystem used to
communicate with the PSCI firmware, implementing the basic operations:
get_version, cpu_on, cpu_off and affinity_info.
The current implementation only supports PSCI 0.2 and PSCI 1.0
The PSCI conduit (SMC or HVC) is setup reading the corresponding
property in the DTS node.
Signed-off-by: Carlo Caione <ccaione@baylibre.com>
Do not include every single Kconfig file as part of this area, Kconfigs
in different areas are maintained by the repective component
maintainers.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
- Status is now orphaned.
- There has been a bit of activity in this area over the last
few months and I'm sure one or more of these new stake holders
would make a fine maintainer.
Signed-off-by: Michael Scott <mike@foundries.io>
Commit: 11de84a6b4ec4be23bed92bf2d8d36f3876189b6 moved shell core
tests from tests/shell to tests/subsys/shell. Remove obsolete path
from MAINTAINERS.yml accordingly.
Signed-off-by: Jakub Rzeszutko <jakub.rzeszutko@nordicsemi.no>
Currently there is no maintainer and active collaborator in watchdog
subsystem area. I hope this helps to encourage Zephyr developments.
Signed-off-by: Katsuhiro Suzuki <katsuhiro@katsuster.net>
This patch gathers and adds all RISCV related directories into
'RISCV arch' entry.
It is preliminary modification until suitable maintainer (or entry)
for each RISCV boards or sub-architecture appears in the future.
Signed-off-by: Katsuhiro Suzuki <katsuhiro@katsuster.net>
Cleanup comments: # Provisional entry, subject to approval
That's because the MAINTAINERS file was reviewed in the
last TSC F2F and the entries are not provisional any more.
Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
Currently there is no maintainer and active collaborator in RISCV
subsys area. I hope this helps to encourage RISCV developments.
Signed-off-by: Katsuhiro Suzuki <katsuhiro@katsuster.net>
There are two issues in MAINTAINERS.yml.
tests/subsys/fs/littlefs/ specified under Little FS doesn't have the
trailing slash (/).
The commit 0eaa495ccb renamed
samples/drivers/CAN to can but MAINTAINERS.yml wasn't.
Signed-off-by: Yasushi SHOJI <yasushi.shoji@gmail.com>
In order to be able to add more entries under 'subsys/mgmt', move the
current contents of it, which relate exclusively to MCUMgr, to its own
folder.
Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
