We still have some issues with the allocation of continous memory for
the VPU support. Enabled some additional drivers/frameworks in the
kernel to perform further tests.

The 5.15.32 kernel is the first official kernel from NXP for Kirkstone.
Forked the kernel from NXP and applied our changes on top of it.

The logo selection is based on disabling the fngsystem or seco
logo in the defconfig.
Fixed the defconfig to re-enable the selection mechanism.

The names of the fngsystem and guf (now seco) logo have changed.

We don't use the audit messages and they spam the log constantly.
Disabled them in the defconfig.

BCS 746-000835

Since we may need a different driver for touch tuning purposes, it is
advantageous to integrate  the driver as a module.

BCS 746-000889

(cherry picked from commit f88db235)

We don't want to use the machine overrides from the meta-freescale
layer. Therefore, we disabled the filter mechanism and re-added
the old SoC names.
To reflect this change, the files have been moved to the correct folders.

The overlays should be at the end, and the normal devicetrees from the
second on should be sorted alphabetically, but the first entry should be
kept as default used during installation when no dtb is given as
parameter.

The freescale layer would require this change, but we don't use the
freescale layer together with the imx6 machines.

NXP removed the old MACHINEOVERRIDES (mx6, mx8m, ...) and filters
them out during the Yocto build.
We rely on them quite often in our recipes and therefore disabled
the filter for now.

NXP suggests using the dma-heap allocator instead of the ION memory
manager from kernel 5.15.5 onwards.

Activated/Enabled modules/drivers that might be related to the
Hantro VPU and DRM.

Set the preferred gstreamer version for the i.MX8M devices to
1.18.5.

The mx8mm had a duplicate definition of the preferred kernel provider
and version.
Also the preferred version in the include for the i.MX8 devices
has been changed to the correct name (linux-imx).

The defconfig for the 5.15.5 kernel is used by the mx8mm and mx8mp.
The location "imx8mguf" is only accessible by the mx8mm. To make
the config available to the mx8mp, the config folder was renamed.

Note: imx8mguf is the machine name of the mx8mm. This is a known bug
and will be fixed in the future.

For the i.MX8 devices, we use the 5.15.5 Yocto kernel provided by NXP.

In Yocto Kirkstone, we use the 5.15.5 kernel from NXP for the i.MX8
devices. In the kernel repository we moved all G&F and K&K devicetrees
to a new folder called seconorth.
Edit the machine configurations to reflect this change and build the
correct devicetrees.

Clemens Terasa authored 2 years ago and Jonas Höppner committed 2 years ago

Add support for GPIO and PWM beepers. This enables the on-board beeper
on the SECO Northern Europe NALLLINO platform.

BCS 746-000992

(cherry picked from commit ad7371e0)

Felix Gerking authored 2 years ago and Jonas Höppner committed 2 years ago

* imx6:mxt-touch: Add kernel support for atmel mxt touch
  BCS 746-000886
  (cherry picked from commit 82cbcf67)

* maxTouch:udev: Add udev rule to skip maxTouch fwr loading fallback

  The current version of the atmel_mxt_ts driver tries to load a controller
  configuration on each driver probe. However, if no config is provided or
  can't be provided because the driver is built-in, the driver probing process
  is delayed by 60 seconds because of a sysfs firmware load fallback.
  Added a udev rule that automatically cancels the sysfs firmware fallback.

  BCS 746-000892
  (cherry picked from commit 55a34692)

* atmel-mxt: convert recipe to new syntax

Tobias Kahlki authored 2 years ago and Jonas Höppner committed 2 years ago

Added an description file with the default devicetree for i.MX8
devices.
The file is parsed/used by the post-install scripts to generate
the boot configuration.

BCS 746-000877

(cherry picked from commit 283c6dfb)

Tobias Kahlki authored 2 years ago and Jonas Höppner committed 2 years ago

Changed the copyright and URL in the bootscript recipes.
Also did a clean-up/reformat of the recipes.

(cherry picked from commit ba9e87ec)

Tobias Kahlki authored 2 years ago and Jonas Höppner committed 2 years ago

In the future, the TANARO will be produced with two possible
RTC variants. Both variants are present in the main devicetree
but are disabled by default. During the installation, one of
the RTCs will be activated via one of the two devicetree overlays.

BCS 746-000877

(cherry picked from commit df176aae)

Tobias Kahlki authored 2 years ago and Jonas Höppner committed 2 years ago

Also small changes to the Kernel include file.

(cherry picked from commit 49cec441)

Clemens Terasa authored 4 years ago and Jonas Höppner committed 2 years ago

Sometimes we get no touchup signal in Qt.
This was seen with the QML drag-and-drop example.

Looking at the output of evtest of the sis input device, you see
different behavior for a working and a missing touch-up.

Failed:
<pre>
...
Event: time 1587646331.383580, type 3 (EV_ABS), code 0 (ABS_X), value 2365
Event: time 1587646331.383580, type 3 (EV_ABS), code 1 (ABS_Y), value 2894
Event: time 1587646331.383580, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2365
Event: time 1587646331.383580, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 2894
Event: time 1587646331.383580, -------------- SYN_REPORT ------------
Event: time 1587646331.402073, type 3 (EV_ABS), code 0 (ABS_X), value 2367
Event: time 1587646331.402073, type 3 (EV_ABS), code 1 (ABS_Y), value 2887
Event: time 1587646331.402073, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 0
Event: time 1587646331.402073, type 3 (EV_ABS), code 58 (ABS_MT_PRESSURE), value 0
Event: time 1587646331.402073, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 2367
Event: time 1587646331.402073, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 2887
Event: time 1587646331.402073, -------------- SYN_REPORT ------------
</pre>

Good
<pre>
Event: time 1587646407.907930, -------------- SYN_REPORT ------------
Event: time 1587646407.922769, type 3 (EV_ABS), code 0 (ABS_X), value 790
Event: time 1587646407.922769, type 3 (EV_ABS), code 1 (ABS_Y), value 1747
Event: time 1587646407.922769, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 790
Event: time 1587646407.922769, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 1747
Event: time 1587646407.922769, -------------- SYN_REPORT ------------
Event: time 1587646407.945577, type 3 (EV_ABS), code 0 (ABS_X), value 840
Event: time 1587646407.945577, type 3 (EV_ABS), code 1 (ABS_Y), value 1918
Event: time 1587646407.945577, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 840
Event: time 1587646407.945577, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 1918
Event: time 1587646407.945577, -------------- SYN_REPORT ------------
Event: time 1587646407.968810, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 0
Event: time 1587646407.968810, type 3 (EV_ABS), code 58 (ABS_MT_PRESSURE), value 0
Event: time 1587646407.968810, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1587646407.968810, -------------- SYN_REPORT ------------
</pre>

It seems that the @ABS_MT_TRACKING_ID value -1@ is missing somehow.

This might be the case when the driver sends a valid coodinate but also
states that the pressure is 0.

Fix this by sending a touch-up (all ABS_PRESSUE, ABS_MT_PRESSURE, and
ABS_BUTTON 0 and ABS_MT_TRACKING_ID -1) when pressure is 0.

BCS 746-000871

(cherry picked from commit 0326de4b)

Felix Gerking authored 2 years ago and Jonas Höppner committed 2 years ago

BCS 746-000857

(cherry picked from commit 4bf6746d)

Clemens Terasa authored 2 years ago and Jonas Höppner committed 2 years ago

Add the iMX Medium Quality Sound driver and the simple amplifier driver
to the defconfig. Together with the latest kernel changes for NALLINO
this adds sound support for the NALLINO board.

BCS 746-000796

(cherry picked from commit 69fb720b)

Clemens Terasa authored 2 years ago and Jonas Höppner committed 2 years ago

According to our company licensing policy for software the Yocto layers
should be licensed under the Apache 2.0 license.
Adapt the LICENSE-2.0.txt file from https://www.apache.org/licenses/LICENSE-2.0.txt
as described in the APPENDIX.

Add the license as LICENSE.txt file to the layer repository.

BCS 746-000657

(cherry picked from commit 66d98abb)

GitBot authored 2 years ago and Tim Jaacks committed 2 years ago

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@075aeccb

Refactoring: share build and test job basics for ci-test and Yocto

This shares YAML code for the following procedures:
- Build environment
- Source code checkout via repo
- SSH key and known hosts setup
- LAVA test submission
- Docker check if build folder is empty

GitBot authored 2 years ago and Tim Jaacks committed 2 years ago

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@6508e800

CI: Add hardcoded artifact's path generation also for fng system

GitBot authored 2 years ago and Tim Jaacks committed 2 years ago

--

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

CI: pipeline yocto: Change scope of CI_PARAM_IMAGE, ... to fix fngsystem build

The variables CI_PARAM_IMAGE, CI_PARAM_DISTRO, CI_MACHINE have been
defined outside the job in the '.gitlab-ci.yml' file. This has a lower
precedence then variables defined inside the job, but it seems that
these variables are used in the scope of 'Trigger variables' when
available in the trigger job. These override the value set in the
template. As main results this made FNGSystem jobs build the normal
yocto.

GitBot authored 2 years ago and Tim Jaacks committed 2 years ago

--

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

CI: Readd allow_failure:true to fix not finished pipelines

According to the docs a manual job always has allow_failure set to
true, but we see a lot of jobs staying in an unfinished state since
the removal of the allow_failure: true keyword for the sdk and test
jobs. This should fix the broken behaviour.

GitBot authored 2 years ago and Tim Jaacks committed 2 years ago

--

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

CI: Hardcode the artifacts path in the generated job description

Some gitlab update(?) seem to have changed the behaviour in
variable passing. In the scripts the variables are available
but in the artifacts path does not resolve them any more.
May be it has something to do with the introduction of the
trigger:forward keyword.