s/System Power Management/System Managed Device Power Management/g
System Power Management is confusing and does not tell
anything about device. Change it for something more explicit.
Signed-off-by: Flavio Ceolin <flavio.ceolin@intel.com>
Deprecate CONFIG_NET_TCP_ACK_TIMEOUT as it is redundant with the
combination of CONFIG_NET_TCP_INIT_RETRANSMISSION_TIMEOUT and
CONFIG_NET_TCP_RETRY_COUNT. The total retransmission timeout (i. e.
waiting for ACK) should depend on the individual retransmission timeout
and retry count, having separate config is simply ambiguous and
confusing for users.
Moreover, the config was currently only used during TCP handshake, and
for that purpose we could use the very same timeout that is used for the
FIN timeout. Therefore, repurpose the fin_timeout_ms to be a generic,
maximum timeout at the TCP stack.
Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
Added clarification on AES-CMAC usage in DFU metadata, emphasizing its
sole role as a hashing function for the incoming composition data hash.
Notably, it utilizes a fixed key and is not employed for encryption
purposes.
Signed-off-by: Stine Åkredalen <stine.akredalen@nordicsemi.no>
Generate a sitemap.xml for the documentation.
This aims at helping search engines react faster to the addition/removal
of new pages.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
- Remove OS specific instructions, instructions depend on the shell and
are the same across OS;
- Add fish shell to the documentation.
Signed-off-by: Théo Battrel <theo.util@protonmail.ch>
`pthread_attr_getinheritsched()` and
`pthread_attr_setinheritsched()` are now implemented,
mark it so.
signed-off-by: Gaetan Perrot <gaetanperrotpro@gmail.com>
Instead of having a single config specifying the memory pool size for
variable-sized net buffers, have a separate one for TX and RX for better
configuration granularity when optimizing memory usage of the
application.
Deprecate the old configuration but use its value as a default (for now)
for the new configs. This will need to change when the config is
deleted.
Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
The currently used PyYaml version has some vulnerabilies as
described on the pull request description. It updates to
version 6.0, removing these supply chain vulnerabily.
The OSSF Scorecard was the tool used for discovering
these vulnerabilties.
Signed-off-by: Javan lacerda <javanlacerda@google.com>
Since I have integrated some samples into samples/drivers/led_strip,
seting up redirection from the deleted apa102, lpd8806, and ws2812.
Signed-off-by: TOKITA Hiroshi <tokita.hiroshi@gmail.com>
The Virtual LAN is changed to use the virtual network interfaces.
Add information what changes might be needed because of this.
Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
On the request of the maintainer.
Background:
We have recently had issues with tests timing out because of the
difference of speed between CI runners and a standard developer machine.
In that case, the logs are printed, and some tests (by yours truly) are
a bit on the chatty side. Github's UI chokes (for a good minute or more
lol) on more than a few hundred lines, so it's a bad experience for
contributors.
Signed-off-by: Jonathan Rico <jonathan.rico@nordicsemi.no>
Mark the POSIX_NETWORKING Option Group as supported. The
POSIX_NETWORKING Option Group is required for PSE53 Conformance.
Signed-off-by: Chris Friedt <chrisfriedt@gmail.com>
Update the presentation of the hardware hierarchy description so that it
does not appear to have missing words at the end of the bullet points,
by using a paragraph instead. And tweak the wording slightly.
Signed-off-by: Declan Snyder <declan.snyder@nxp.com>
It makes more sense that way:
A developer wants to know in order:
- what features we have
- if they are qualified/qualifiable
- how the stack is architected / what parts are where
- how to develop an app
- tools to develop said apps (+ shell)
Signed-off-by: Jonathan Rico <jonathan.rico@nordicsemi.no>
It adds unnecessary noise in the navigation pane.
We don't do this for other chapters (e.g. kernel services don't say
"Kernel Services System Threads" in the title, just "System Threads").
Signed-off-by: Jonathan Rico <jonathan.rico@nordicsemi.no>
This page only ever had one section: supported features.
Added links to the relevant sections for each layer.
Signed-off-by: Jonathan Rico <jonathan.rico@nordicsemi.no>
Add enum for `constant-charge-voltage-max-microvolt` property to
signalize improper values given with device tree at compile time.
Signed-off-by: Lukasz Madej <l.madej@grinn-global.com>
Maximum charging current is selected with an external resistor in
the MAX20335 charger. Therefore it is not possible to configure it
with software directly. There is only a capability to limit current
set with hardware but configuration of the limiter is not
straight-forward.
To reflect real functionality, drop usage of
`constant-charge-current-max-microamp` property as an required one and
use custom `chgin-to-sys-current-limit-microamp` instead.
Use enum in binding file to signalize improper values at compile time.
Drop support for `CHARGER_PROP_CONSTANT_CHARGE_CURRENT_UA` API property
since this cannot be handled.
The `max20335_get_constant_charge_current()` function become useless so
remove it.
Signed-off-by: Lukasz Madej <l.madej@grinn-global.com>
Quite many users do not know that it exists, as we
don't seem to have it documented anywhere.
Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
Support `zephyr-app-commands` being provided with a `snippets`,
option, to specify building with the listed snippets.
Signed-off-by: Jordan Yates <jordan.yates@data61.csiro.au>
Rework the data scaling algorithm for the "deadzone" mode so that the
deadzone is subtracted from the input rather than from the output. This
makes the whole output range usable rather than making the output jump
from the center value to the minimum deadzone range.
This changes the calibration data structure as well so now all values
refer to the input data, which is more coherent.
Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
Add support to coredump_gdbserver.py for running in a pipeline,
communicating through stdin/stdout instead of a socket.
This allows starting it from inside gdb, with:
target remote | coredump_gdbserver.py --pipe <elf_file> <log_file>
Signed-off-by: Kevin ORourke <kevin.orourke@ferroamp.se>
Fabio Baltieri