This reverts commit feaf4122.

--

Commit: seco-ne/3rd-party/u-boot/u-boot-mtk@c88d9631

Add gitlab-ci

--

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@0ca48bfa

seco-mx6: enable fastboot

--

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@abf30977

seco-mx6: update config via savedefconfig

--

Commit: seco-ne/kernel/linux-imx-kuk@a6646c02

arm:dts:imx6qdl-san: Enable i2c msg read within ISR for bus 3

Some connected touches lead to a large traffic on the bus.
If this traffic is handled too slowly, some ugly effects show up,
such as input delays or a high CPU load due to the touch driver.
Set the enable-isr-read flag to speed up the message read process.

Cherry-picked from 52d249fcd8ff14c01bce0b4049613b11c779426e
https://git.seco.com/seco-ne/kernel/linux-guf

BCS 746-001477 746-001000

--

Commit: seco-ne/kernel/linux-imx-kuk@8ab02e4d

drivers:i2c-imx: Add option for i2c read processing within ISR

By default the read msg process is handled by the follwing queue
mechanism:
1. Client driver read request
2. The i2c driver triggers a read and waits for a byte to be ready to read
3. ISR sends a wake_up call to the queue when the byte is ready to read
5. The i2c driver becomes scheduled again and reads the byte
6. The i2c driver waits for the next byte and so on

For some reason, it often takes a long time to reschedule the i2c
driver after the ISR reports ready status. This causes problems with
i2c devices that cause a lot of bus traffic, such as touch devices.
To resolve this, the devicetree flag "enable-i2c-isr" enables the
following read routine:
1. Client driver read request
2. The i2c driver triggers a read and waits for the ISR
3. The ISR reads the bytes itself and wakes up the queue when
   all bytes are processed

This way the wake_up calls are reduced by the number of bytes in a message
and processing becomes much faster. However the ISR does more, but adding
something that controls the scheduling of the i2c driver also seems to be
very complicated.

Cherry-picked from 850be496c49aeca59bf9caa295a939d39fb4dbec
https://git.seco.com/seco-ne/kernel/linux-guf

BCS 746-001477 746-001000

--

Commit: seco-ne/kernel/linux-guf@1ec2a30d

arm:dts:imx6qdl-san: Enable i2c msg read within ISR for bus 3

Some connected touches lead to a large traffic on the bus.
If this traffic is handled too slowly, some ugly effects show up,
such as input delays or a high CPU load due to the touch driver.
Set the enable-isr-read flag to speed up the message read process.

BCS 746-001477 746-001000

--

Commit: seco-ne/kernel/linux-guf@8037dbaa

drivers:i2c-imx: Add option for i2c read processing within ISR

By default the read msg process is handled by the follwing queue
mechanism:
1. Client driver read request
2. The i2c driver triggers a read and waits for a byte to be ready to read
3. ISR sends a wake_up call to the queue when the byte is ready to read
5. The i2c driver becomes scheduled again and reads the byte
6. The i2c driver waits for the next byte and so on

For some reason, it often takes a long time to reschedule the i2c
driver after the ISR reports ready status. This causes problems with
i2c devices that cause a lot of bus traffic, such as touch devices.
To resolve this, the devicetree flag "enable-i2c-isr" enables the
following read routine:
1. Client driver read request
2. The i2c driver triggers a read and waits for the ISR
3. The ISR reads the bytes itself and wakes up the queue when
   all bytes are processed

This way the wake_up calls are reduced by the number of bytes in a message
and processing becomes much faster. However the ISR does more, but adding
something that controls the scheduling of the i2c driver also seems to be
very complicated.

BCS 746-001477 746-001000

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@64dc51d3

Use regex operator to check for multiple variables

The "&&" operator does not work as expected when checking if multiple
variables are set.

See for reference:
https://gitlab.com/gitlab-org/gitlab/-/issues/321371

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@89fbce24

Hide Confluence stage if confluence variables not set

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@db50e93b

Hide deploy stage if DEPLOY_RELEASE_TARGET not set

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@f4aa0048

Hide FTP stage if DEPLOY_FTP_TARGET not set

This makes the variable HIDE_FTP_UPLOAD_STAGE obsolete, because we can
hide the FTP stage now by setting DEPLOY_FTP_TARGET to an empty string.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@409c4f27

Do not run CI test sub-pipeline on master

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@a731b156

Remove DISTRO_IMAGES

This variable has been removed in Yocto. Its contents have been merged
into DISTRO_RELEASE_ARTEFACTS.

See for reference:
seco-ne/yocto/layers/meta-seconorth-distro@a316e95e

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@a316e95e

Refactoring: remove DISTRO_IMAGES variable

DISTRO_IMAGES was passed to the CI package stage only to add the
corresponding manifest and testdata.json files as well. Add these
directly to DISTRO_RELEASE_ARTEFACTS and remove DISTRO_IMAGES variable.

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@ba99e05b

Refactoring: remove DISTRO_INSTALL_SCRIPTS

This variable is not needed anywhere else, so we can use its value
directly.

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@1846382a

Refactoring: append to DISTRO_IMAGES for FNGSystem instead of redefining it

${IMAGE_LINK_NAME}.cpio.gz is part of DISTRO_IMAGES automatically due to
its original definition in seconorth-distro.inc. Append
${IMAGE_LINK_NAME}.tgz to make clear that this is an addition compared
to the Yocto build.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@45f2aca7

Refactoring: remove parsing of testdata.json in package stage

Extract and save these variables in the build stage instead and
explicitly pass them as arguments to the package script.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@8ca2487d

Move .simulate_build below .build_yocto

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@2808f067

Fix build.env contents for simulated build

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@73d00715

Pretty print release metadata JSON file

--

Commit: seco-ne/kernel/linux-imx-kuk@b5e752d6

driver:ucb1400: Add retry to read routine

If an invalid value was returned, retry the read operation without a
delay.

--

Commit: seco-ne/tools/seco-sharedconf@ebbb85c2

config:networkd: Adapted networkd generation function

Added check for invalid netmask.
Added validation to MAC.

BCS 746-001437

--

Commit: seco-ne/tools/seco-sharedconf@ffccbdd7

config:network:nm: Adapted nm generation function

Added check for an invalid netmask.
Added validation checks to MAC and fallback IP.

BCS 746-001437

--

Commit: seco-ne/tools/seco-sharedconf@1c03a33d

config:network: Add check for invalid settings

Check the static interface settings and exit if they are invalid.
Also check if we have a valid MAC before expanding the string.

BCS 746-001437

--

Commit: seco-ne/kernel/linux-imx-kuk@b5006e3e

driver:wm9705: Check and re-set dig2 config register

Due to an unknown reason, the dig2 config register resets randomly. This
disables the generation of pen-down interrupts. Without the interrupt, doesn't
sample further touches.
As a first workaround, we check the dig2 config register before exiting the
sample function and re-set the config value, if it was reset.

BCS 746-001452
BCS 746-001447

--

Commit: seco-ne/tools/yocto-install@6c54f459



fngsystem: add script to run postinstallation on installed yocto

This is a fix for issue with ID 746-001246: "FNG-System: Add way to manually
update the configuration"

To solve the problem (to be able to update the settings in Yoto after xconfig
import), we added a fngsystem-rootfs-postinstall.sh script to the FNG System.
It is a simplified version of the existing fng-install.sh script and right now
it supports only an "--AB-target" argument from the original script.

This script can be run like this:
yocto-postinstallation.sh

Note: due to lack of iMX8 boards for which AB partition layout may be used,
this functionality in the script has not been tested yet (but already exists).

Signed-off-by: Mikhail Vanyulin <mikhail.vanyulin@rtsoft.de>

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@e4880f69

qt-multi-screen-compositor:mx6: Enable linux-dmabuf-unstable-v1

Enabling linux-dmabuf-unstable-v1 fixes the distorted visualization
on imx6 devices.

See https://codereview.qt-project.org/c/qt/qtwayland/+/214050

BCS 746-000838

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@f2a29f53

Refactoring: remove RELEASE_NAME from deploy targets

Append it to the configured target at the deploy class level instead.
This removes the need for eval'ing the variables before usage.
RELEASE_NAME can be used directly at the class level because it is known
from build-version.env.

This makes the deploy behavior identical to the Azure stage.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@e136e5e2

Remove top-level "release" folder from package

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@1d5e479f

Define MACHINE variable on job level

Instead of passing MACHINE from stage to stage or loading it from
testdata.json, use the original value from the Jinja2 loop and set it
directly for each job where it is used.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@cdd47023

Introduce separate variables to set RELEASE_NAME and RELEASE_VERSION

The expressions to calculate RELEASE_NAME and RELEASE_VERSION cannot be
stored within these variables themseselves. If set on the trigger level,
they would override the calculated values in build-version.env then,
as trigger variables always have the highest precedence.

Use separate variables RELEASE_VERSION_EXPRESSION and
RELEASE_NAME_EXPRESSION to define how RELEASE_VERSION and RELEASE_NAME
are calculated instead.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@372d192b

Use RELEASE_VERSION and RELEASE_NAME from build-version job

Instead of passing these variables from stage to stage or regenerating
their values in later stages, use the ones set in the build-version job
at all places.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@cad30c20

Remove RELEASE_SUFFIX variable

The RELEASE_NAME variable can be set directly now, so there's no need to
have a dedicated RELEASE_SUFFIX anymore. A previous configuration like

  RELEASE_SUFFIX: "-custom"

can now be achieved using:

  RELEASE_NAME: "Yocto-${RELEASE_VERSION}-custom"

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@922f49f8

Add yocto version job

This adds a machine-independent job "build-version" which populates the
RELEASE_VERSION and RELEASE_NAME variables, so that following jobs can
use these without depending on the various build jobs.
The variables can be set from the trigger job in a project's
`.gitlab-ci.yml` file. They are eval'ed before saving them to
version.env, so we can use deferred variable expansion or even command
execution to construct their values. This mechanism is already used for
the Flash-N-Go System variables.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@073ae81e

LAVA: rename MACHINE to LAVA_MACHINE

Rename variable in order to avoid confusion with the original MACHINE
variable used everywhere else. Also rename the local Jinja2 variable to
include an underscore to make naming consistent.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@a91baa55

Clean build.env before writing

This had been accidentally removed in
5e36715ef6cf98df4c1b98fedddc0c3c50ed4040.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@1860ca8e

Remove LOG_PREFIX variable

This was used in times when the same code was executed from different
places. We don't do that anymore, so the variable is obsolete.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@3d2dbe4d

Documentation: update job generation chapter

--

Commit: seco-ne/yocto/layers/meta-seconorth-machine@aeb1509b

conf:seco-mx6-fsl: Add mx6dl to MACHINEOVERRIDES

The VPU firmware binary for the imx6dl SoCs was not present in the
image. Adding the mx6dl override adds the firmware-imx-vpu-imx6d package
to the image.

--

Commit: seco-ne/yocto/layers/meta-seconorth-machine@5afddac3

kernel:firmware: Fix install task for seco-mx6-fsl sdk build

Perform the do_install task only for the seco-mx6 machines, otherwise the
firmware binaries conflict with the files from the firmware-imx recipe
of the Freescale layer.

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@1146c5fb

packages:iot: Added Edgehog packages and dependencies

BCS 746-001531

--

Commit: config@edf6b42d

config:setup: Add check to fngsystem NoGPLv3 feature

Some custom projects already include the NoGPLv3 or GPLv2 layer. If these
layers are already present, the Bitbake parsing fails. As a precaution,
check if the layers are already present and only add them if not.

--

Commit: seco-ne/yocto/layers/meta-seconorth-machine@ae0d8e91

bootscript:alt: Check for custom script and run it if found

The Flash-N-Go System bootscript should also check for an additional
custom bootscript and run it if one was found.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@17b87f84

Refactoring: remove CI_PARAM_ prefix from variables

There is no need to add a prefix to the variables. Basically every
variable can be set or overridden at the trigger level, so we just use
plain variable names for everything.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@825f3686

Refactoring: do not rename *_PATH variables in build.env

We were using different variable names for the same variable in build
and package stages. Unify these names in order to reduce potential
confusion.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@2346bb98

Refactoring: make build variable naming consistent

Use underscore to separate words within variable name.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@581541b9

Refactoring: improve FNG_INSTALL_URL definition

FNG_INSTALL_URL was defined in build.env only, and in order to use it
during the build we sourced build.env after writing it.
Remove this workaround and define the variable cleanly in the first
place. This removes the intermediate variable FNG_INSTALL_PATH.
Also move the "/artifact" path from JOB_URL to FNG_INSTALL_URL in order
to make the JOB_URL variable name match better.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@35784f29

Refactoring: improve IMAGEPATH et al. definition

On every usage of IMAGEPATH, SDKPATH and LICENSESPATH we prepended
BUILDPATH to it. Prepend it directly on definition to prevent
repetition.
Also remove redundant variable IMAGEBASEPATH.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e36715e

Remove needless variables from build.env

There were three variables set in build.env of which the values are
already known in the environment for all jobs, because they are passed
from the parent pipeline. Use the original variables instead of defining
new ones.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@84aa6afb

Fix LAVA job name

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@8160c7d5

Sourcery: enable "low-code-quality" check globally

Disable it locally instead, so that
 1. new code additions are always checked, and
 2. we can refactor one function at a time to make the check pass.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@ef60c378

Sourcery: keep "for-append-to-extend" check disabled

This is another check that suggests changes an average developer without
profound Python experience would find hard to understand. Disable it.

See for reference:
https://docs.sourcery.ai/Reference/Python/Default-Rules/for-append-to-extend/

--

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@901ec1fb

boards:trizeps8plus: Better module detection

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@fe3b93c4

utils:mxt-app: Improve config parser

Config files generated with maXTouchStudio contain a FILE_INFO_HEADER
section that was not handled correctly by the mxt-app parser.
Add this section to the skipped sections.

--

Commit: config@03461917

Enable the no-gplv3 layers for fngsystem distros.

Actually fixes the lates commit.

--

Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@121c130b

Move the relevant no-gplv3 config to include file to reuse it

--

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@e2700f67

trizeps8mini: Adjust mx8mm modules in Kconfig

--

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@fb842ad0

trizeps8mini: Adjust SDRAM size and offset

To be compatible with arch/arm/mach-imx/imx8m/soc.c pathch for Trizeps 8 Plus

--

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@f85ee8cc

trizeps8plus: Adjust timings for 2GB and 4GB RAM

--

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@7792d620

trizeps8plus: Support for full 4GB RAM

--

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@1be1a838

trizeps8plus: Support for 4GB DRAM added, but cut to 3GB.

Using the full 4GB would break compatibility to modules with less than 4GB. (Maybe somewhere in time someone will have a better idea.)

--

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@37a6cc0b

trizeps8plus: clocks for 4G rams added

--

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@a335ca78

trizeps8plus: RAM-timings for 4GB-modules added

--

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@aa430125

trizeps8plus: Support for different ram sizes started

--

Commit: config@1c116388

setup-environment: add gpl2 layers for fngsystem-image

Append "meta-seconorth-nogplv3" and "meta-gplv2" layers to bblayers.conf
only for "fngsystem-image" to avoid possible side effects for normal
builds.

--

Commit: seco-ne/tools/seco-sharedconf@86315479

udev:rules: Fix force_ro and disable it

The action to disable the force_ro switch must be called after the blkid
action (because it requires the ID_FS_LABEL).
Moved the action to the right position.
However, since we don't want /etc/shared to be writable anyways, we
disable the action for now.

BCS 746-001439

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@1bb49495

openssh: Remount /etc/shared before generating SSH keys

If /etc/shared is located on mmcblk0boot1, the partition is read-only
per default. This prevents the SSH key generation service from working
properly.

BCS 746-001439

--

Commit: seco-ne/kernel/linux-imx-kuk@e2f09b85



regulator: Lower priority of logging when setting supply

We lowered all the other constraint related log messages to debug level so
lower the logging of what supplies we're configuring to debug level too.

Signed-off-by: Mark Brown <broonie@kernel.org>
Link: https://lore.kernel.org/r/20210929140717.3769-1-broonie@kernel.org


Signed-off-by: Mark Brown <broonie@kernel.org>

--

Commit: seco-ne/kernel/linux-guf@c8ccfb27



regulator: Lower priority of logging when setting supply

We lowered all the other constraint related log messages to debug level so
lower the logging of what supplies we're configuring to debug level too.

Signed-off-by: Mark Brown <broonie@kernel.org>
Link: https://lore.kernel.org/r/20210929140717.3769-1-broonie@kernel.org


Signed-off-by: Mark Brown <broonie@kernel.org>

--

Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@d7f4a6cc

README: remove parted from list

--

Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@0c342bea

core-base-utils: remove parted from override

--

Commit: seco-ne/yocto/layers/meta-seconorth-nogplv3@7a5a15ca

parted: add gplv2 version

The license was changed in 2007 from gplv2 to v3.
There is no recipe for the old parted in the meta-gplv2 layer.

By contrast with the latest parted recipe, this recipe does not
contains ptest part.

--

Commit: seco-ne/3rd-party/kuk/uboot-imx-kuk@fbf116e3

gitlab: Set new recipe name

The recipe name for U-Boot was changed to u-boot-seco-imx

The name was changed to reflect the name used in Italy.

--

Commit: seco-ne/tools/yocto-install@09bc9c41



fnginstall-common: handle gpt partition table

This is a fix for issue with ID 746-001412 : "fng-install: Handle existing
GPT partition layout."

Edgehog is distributed via WIC files which use a GPT partition table. But
fngsystem-self-update scripts, which are used with SECO NE boards, do not
work correctly with GPT partition table, so the installation of FNG System
fails on boards, where Edgehog WIC is installed.

Added the handling of GPT partition table to fngsystem-self-update:
 - if "--fdisk|--force-repartition" argument is not specified, installation
   will stop immediately with error message;
 - if "--fdisk|--force-repartition" argument is specified, an existing
   partition table on storage device on SECO NE board will be erased, and
   the installation process will continue as if this storage device was
   unformatted.

Signed-off-by: Mikhail Vanyulin <mikhail.vanyulin@rtsoft.de>

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@cf371aca

alphaplan_fwr: Remove obsolete pkg.py artifact

The pkg.py file is no longer deployed by the build process.

See commit
seco-ne/yocto/layers/meta-seconorth-distro@e79e8579

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@b2b43f71

Sourcery: keep "use-named-expression" check disabled

This suggestion aims to reduce code size, but IMO for the expense of
readability for non-python-experts, so we disable it.

See for reference:
https://docs.sourcery.ai/Reference/Python/Default-Rules/use-named-expression/

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@ae8c5423

Sourcery: keep "use-next" check disabled

I don't see any benefit in accepting the refactoring suggestions based
on this rule. IMO it makes the code harder to read, especially for non-
experienced Python developers.

See for reference:
https://docs.sourcery.ai/Reference/Python/Default-Rules/use-next/

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@9462f826

Refactoring: raise specific errors

See for reference:
https://docs.sourcery.ai/Reference/Python/Default-Rules/raise-specific-error/

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@61eb3e11

Switch all strings to formatted string literals (f-strings)

The old printf-style string formatting syntax using '%' is not
recommended anymore. See for reference:
https://docs.python.org/3/library/stdtypes.html#printf-style-string-formatting
https://docs.sourcery.ai/Reference/Python/Default-Rules/replace-interpolation-with-fstring/

Python 3.6 introduced f-strings as a better alternative:
https://docs.python.org/3/reference/lexical_analysis.html#f-strings

Consequently switch to this new syntax for all strings.

--

Commit: seco-ne/yocto/layers/meta-seconorth-distro@69302a36

uuu: fix shellcheck warning

SC2046: Quote this to prevent word splitting.

https://www.shellcheck.net/wiki/SC2046

--

Commit: seco-ne/yocto/layers/meta-seconorth-machine@956a0653

yocto-install: Workarround for seco-mx6-fsl build

As the u-boot for seco-mx6-fsl does not work yet, the install script
should only be generated for seco-mx6 instead for all mx6q machines.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@b2fb3e93

Combine build-yocto.yml and and build-common.yml to build-pipeline.yml

--

Commit: seco-ne/kernel/modules/touchgpio@9b880984

Add gitlab-ci configuration for automatic manifest integration

--

Commit: seco-ne/kernel/modules/ilitek@25cde723

Add gitlab-ci configuration for automatic manifest integration