--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@6e6f124b

package_release: Add a way to copy the whole directory

Item should end with "/" to be treated as a directory

--

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

CI: collect_release_information: jump to next pipeline if no deploy jobs found

See for error:
https://git.seco.com/seco-ne/yocto/infrastructure/ci-test/minimal-manifest/-/jobs/828261

--

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

CI: Confluence page: Fix not created mx6 section

The function that merges the variables of the different jobs, i.e:

`MACHINE="mx6"`

`MACHINE="mx6ull"`

used python `in` to check if a value already exists.
But `"mx6" in "mx6ull"` is true, so mx6 was dropped.
This rewrites it, storing the variables in a set (which is unique
automatically) instead of space seperated strings.
Space seperation is added before printing the variables to be used on
on the shell.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@094983ae

git_config: Add "*" as safedir to omnit 'dubious ownership' error

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@44000de1

Check bitbake recipes with linter

The job checks bitbake recipes added/updated in MR using the
oelint-adv tool (https://github.com/priv-kweihmann/oelint-adv).

.oelint.json is a rulefile, created with the command
"oelint-adv --print-rulefile". It can be used during development.
It contains default rules for now, but will probably be customized later.

To get the list of changed files in MR, we adjusted the GIT_DEPTH variable.
The new value is 50, which should be fine for getting MR changes,
and still small enough to keep checkout fast for large projects.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@9d9574d1

convert_md2html: fix text duplication

Fix the problem introduced by commit 4f06516 "convert_md2html: fix id
fields for headings".

The text converted from markdown was written twice to the HTML document.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@4f06516a



convert_md2html: fix id fields for headings

Converter adds "user-content-" to "id" fields for headings.
As a result links from TOC do not work.
Fix this for now by removing "user-content-" from the resulting html.

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

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@97898e9e



convert_md2html: use gitlab api

Update convert_md2html.py to use gitlab api with gitlab flavor.

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

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@4595835d

build:machines: Add Genio510 to the build job template

--

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

scripts:firmware: Fix check for U-Boot file types

On i.MX6 devices, the U-Boot file types are not set at all. Extent check for
the existance of the uboot_file_types var.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@3146ed1e

CI: increase timeout of package-documentation to 5m

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@4d5bca8f

CI: remove 'setup_ssh' as ssh access is disabled

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@8353d920

CI: lava testing: replace ssh with https url and CI_JOB_TOKEN

--

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

gitlab-ci: Disable sourcery

The sourcery plugin fails again due to a missing login. Disable it for
now.

--

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

manifest:integration: Fix issue in trigger/include

--

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

pipelines:build: Add check to JSON generation

Without the check, we have a race condition when building from sources
outside of the Yocto group.

This is a cherry-pick of b148230b7470ec6a4b6946a619174deeaac380ef commit
from 4.1.15 kernel.

Author: Carsten Behling <carsten.behling@garz-fricke.com>
Date:   Wed Aug 17 09:27:12 2016 +0000

PMIC: refs #18401
* port deep sleep mode reboot fix linux-kernel:r2608 to kernel 4.1.15

git-svn-id: http://srv80.hamburg.garz-fricke.de/svn/sw/som/linux-kernel/trunk/linux-4.1.15-guf@2955

 9c94d2d2-9c12-c147-a17b-948b59ea09cc

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

Backported from linux-6.7.0,  commit a0e026e7b37e997f4fa3fcaa714e5484f3ce9e75
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/phy/phy.c?id=a0e026e7b37e997f4fa3fcaa714e5484f3ce9e75

Since commit 91a7cda1f4b8 ("net: phy: Fix race condition on link status
change") all the phy_error() method invocations have been causing the
nested-mutex-lock deadlock because it's normally done in the PHY-driver
threaded IRQ handlers which since that change have been called with the
phydev->lock mutex held. Here is the calls thread:

IRQ: phy_interrupt()
     +-> mutex_lock(&phydev->lock); <--------------------+
         drv->handle_interrupt()                         | Deadlock due
         +-> ERROR: phy_error()                          + to the nested
                    +-> phy_process_error()              | mutex lock
                        +-> mutex_lock(&phydev->lock); <-+
                            phydev->state = PHY_ERROR;
                            mutex_unlock(&phydev->lock);
         mutex_unlock(&phydev->lock);

The problem can be easily reproduced just by calling phy_error() from any
PHY-device threaded interrupt handler. Fix it by dropping the phydev->lock
mutex lock from the phy_process_error() method and printing a nasty error
message to the system log if the mutex isn't held in the caller execution
context.

Note for the fix to work correctly in the PHY-subsystem itself the
phydev->lock mutex locking must be added to the phy_error_precise()
function.

Link: https://lore.kernel.org/netdev/20230816180944.19262-1-fancer.lancer@gmail.com


Fixes: 91a7cda1f4b8 ("net: phy: Fix race condition on link status change")
Suggested-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: Serge Semin <fancer.lancer@gmail.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>

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

To reduce boot time, we have disabled CONFIG_EXPERT and CONFIG_DEBUG_KERNEL
in seco-mx6 defconfig.

However, for backward compatibility, we need to leave CONFIG_GPIO_SYSFS
enabled. For this, the config should be visible even when expert mode is
disabled.

The following errors can be observed in dmesg on some boards (e.g.
SANTINO/SANTINO-LT):
[    3.102655] /disp0: could not find display-timings node
[    3.108037] /disp0: no timings specified

It looks like panel_dt_get_non_edid_modes() was made from
panel_simple_get_non_edid_modes() of drivers/gpu/drm/panel/panel-simple.c
but increasing number of found modes was omited.

panel-simple.c has this code:
283-            if (mode) {
284-                    drm_mode_probed_add(connector, mode);
285:                    num = 1;
286-            } else {

So add the same assignment in panel-dt.c too.

Guiling Deng authored 2 years ago and Mikhail Vanyulin committed 1 year ago

Image.dx gets wrong value because of missing '()'.

If xres == logo->width and n == 1, image.dx = -16.

Signed-off-by: Guiling Deng <greens9@163.com>
Fixes: 3d8b1933 ("fbdev: fbmem: add config option to center the bootup logo")
Cc: stable@vger.kernel.org # v5.0+
Signed-off-by: Helge Deller <deller@gmx.de>

Dmitry Petrov authored 1 year ago and Mikhail Vanyulin committed 1 year ago

The 'reserved-memory' node must exist in device tree, so that we can apply
the DT overlay to reserve memory for a custom logo.

Dmitry Petrov authored 1 year ago and Mikhail Vanyulin committed 1 year ago

The 'reserved-memory' node must exist in device tree, so that we can apply
the DT overlay to reserve memory for a custom logo.

This is a fix for issue [746-000092] logo: Implement logo driver to show
logo from RAM

If CONFIG_LOGO_SECO_MEMLOGO is set, logo driver will get logo memory address
and size from dtb. And if this points to a correct data, logo, loaded into
memory will be displayed.
If some part of dtb node is missing or data in the memory is incorrect,
a logo, which was selected by the driver before will be used.

It is also necessary to reserve memory to which logo is loaded.

Exampled dtb nodes:
       seco-memlogo {
               compatible = "seco,memlogo";
               address = <0x14000000>;
               size = <74501>;
       };

       reserved-memory {
               #address-cells = <1>;
               #size-cells = <1>;
               ranges;

               logo_reserved: logo@14000000 {
                       reusable;
                       reg = <0x14000000 74501>;
               };
       };

Example script, which will generate logo from logo.png:
    WIDTH=492
    HEIGHT=150
    pngtopam logo.png > logo.ppm
    pnmpad -width $WIDTH -height $HEIGHT logo.ppm > logo_pad.ppm
    pnmcolormap 224 logo_pad.ppm > colormap
    pnmremap -floyd -plain -mapfile=colormap logo_pad.ppm > logo_plain.ppm
    seco-pnmtologo -t clut224 -o logo.dat -f bin logo_plain.ppm

Example command to load logo into memory from U-Boot:
    load mmc 1:3 0x14000000 logo.dat

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

Dmitry Petrov authored 1 year ago and Jonas Höppner committed 1 year ago

Instead of using always-on regulator, configure it as supply for
the port, so it gets enabled when the port is opened.

Dmitry Petrov authored 1 year ago and Jonas Höppner committed 1 year ago

Add the fixed regulator for the CAN/RS485 output of SANTINO, that may be
optionally galvanic isolated.

Add rts-gpios for RS485.

On some hw the rs485 needs an additional regulator to be switched on.
With this patch it is possible to configure the regulator as supply for
the port, so it gets enabled when the port is opened.

BCS 746-001117

Dmitry Petrov authored 1 year ago and Jonas Höppner committed 1 year ago

The wrong compatible string is used for the EEPROM.
STMicroelectronics M24C32/TSSOP8 is installed on i.MX6 SAN boards.

Dmitry Petrov authored 1 year ago and Jonas Höppner committed 1 year ago

Use interpolated brightness table for i.MX6 SAN boards.
The "brightness-levels" values are taken from XML configurations.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@42bfe4f0

build:prepare: Add setup script for Git Credentials

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@24653ff8

build:machines: Add i.MX93 to the build job template

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@7aae72ea

Re-enable sourcery

With the free open source plan, sourcery works only when called from the
repository's root directory. Re-enable it by calling it from there.

Also apply sourcery's suggestions to file generate_firmware_package.py,
which did not exist before disabling sourcery.

Dmitry Petrov authored 1 year ago and Felix Gerking committed 1 year ago

Modified platform initialization to check for (a) @lcd@-node in device-tree
to identify systems with parallel LCD-interface and (b) presence of enabled
spread-spectrum settings in device-tree to change the IPU-DI PLL from
PLL5 to PLL2 in this case to allow spread-spectrum clocking of parallel
LCD-displays

Dmitry Petrov authored 1 year ago and Felix Gerking committed 1 year ago

The helper function checks if spread spectrum clocking is enabled in
device tree.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@51e0cf67

build:stages: Add Firmware Package JSON stage

The old Alphaplan stage is deprecated and was removed in a prior commit.
Add new stage to generate the Firmware Package JSON files that do replace
the old Alphaplan articles.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@1830cb02

And another improvement for the build-up-to-date job

--

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

Improve the output message in the build-up-to-date job a bit more

Use explicit line breaks to make the message look better.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@68aaab94

Improve the output message in the build-up-to-date job

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@26b9eb1d

Rename "check" job to "build-up-to-date"

This is a more meaningful name and might give a hint what the job does.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@07f0c898

Make build runner tag configurable

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@0d70d719

Disable sourcery check

Sourcery changed its license model to only be available for open source
projects with the free plan. According to the documentation, sourcery
should detect automatically whether it is running on an open source
repo. This does not work in our case, though. Disable it until we find a
way to correctly make it work.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@9be2c52b

pipeline:build: Fix indentation of here-doc

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@245e6537

pipeline:build: Make generation of install script optional

The Genio 700 platform doesn't have an fng_install.sh. Currently, the
pipeline fails because of the exit code in the script check.
Make the generation of the install command optional and only show a
warning if the script is missing.

--

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

pipeline:build: Add MediaTek Genio 700 SoC

Dmitry Petrov authored 1 year ago and Tobias Kahlki committed 1 year ago

The LDB is enabled via device tree overlay generated by gfxml2dto tool,
depending on "display" settings in the XML configuration file.

There is a problem with HDMI output when "display" settings are missing
in the XML configuration file.

The following errors can be observed in dmesg:
[    2.081476] /ldb/lvds-channel@0: could not find display-timings node
[    2.088014] /ldb/lvds-channel@0: no timings specified

It happens because gfxml2dto does not completely disable the "ldb" node,
but disables only the "panel". After this, the DRM driver does not bind
any device.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@6f773de5

Remove Alphaplan stage

We do not use Alphaplan anymore. Remove everything Alphaplan related
stuff from the pipeline.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@56bd1900

Confluence: add helper script to get page content

This can be helpful if something is configurable in the GUI editor and
we can't figure out to do the same thing via the API.

--

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

Confluence: enforce fixed page width on creation

On page creation via the API, the page always seems to be created with
full width, even if "full_width=False" is set. Update the page right
after creating it in order to correctly set it to fixed width.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@82053a2f

Confluence: set width for download table columns

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@96f5745c

Confluence: group download files by type

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@3697b4ea

cancel_pipelines: reverse order of cancellation

Cancel parent pipeline first before cancelling its children in order not
to have failed parent pipelines (trigger jobs are failed if their
downstream pipeline is cancelled).

--

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

cancel_pipelines: list actually cancelled (child-)pipelines

--

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

Cancel all pipelines on newer commit

We already canceled running pipelines before. Gitlab, however, might
have already canceled previous pipelines automatically, but without
canceling their child pipelines.
Remove the "running" status filter when cancelling pipelines, so that
also already cancelled pipelines will be included.

--

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

Revert "Cancel all pipelines on newer commit"

This reverts commit f7582b74e7c565d55bb8a0315fe75c4ab4385fa2.

--

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

Cancel all pipelines on newer commit

We already canceled running pipelines before. Gitlab, however, might
have already canceled previous pipelines automatically, but without
canceling their child pipelines.
Extend the mechanism now to cancel all pipelines up to and including
"running" as well as "canceled" states.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@0ec55c07

Fix list() call in update_submodule

Here we don't just iterate over the results, so we have to use
"all=True" instead of "as_list=False". See previous commit for
explaination.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@4b3a517e

Make sure to get all items on Gitlab list() calls

The list() call on Gitlab classes uses pagination per default. If the
number of items exceeds a certain limit, we only get a part of the
results. We can pass "all=True" to the calls in order to disable
pagination and get all results.
If we're looping over the items, though, the recommended way of getting
them is to use a generator object, which works calling list() with
"as_list=False". See documentation for reference:

https://python-gitlab.readthedocs.io/en/v2.10.1/api-usage.html#pagination

Note: the "as_list" argument is deprecated in newer versions of the
python-gitlab library, in favor of the newer "iterator=True":
https://python-gitlab.readthedocs.io/en/v3.6.0/changelog.html#feature
We are using v2.10.1 of the library, though, so this commit also updates
calls using the new way, which is not working with our version.

--

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

Confluence: combine data from parallel child pipelines

We deploy Yocto image and SDK in different pipelines, which both have
their Confluence jobs with the same Confluence target. Previously these
pipelines have been independent, so that running the Confluence job in
one of them would overwrite the Confluence page if it has been run in
the other pipeline before. Hence we could either have the image files or
the SDK files in the Confluence page.
Combine these now by checking for other parallel child pipelines with
the same Confluence configuration, so that running the Confluence jobs
in the Yocto pipeline also includes the information from the SDK build
and vice versa.

--

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

Fix ci-test SDK version

--

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

Fix ci-test SDK download

Since the implementation of multiple child pipelines we cannot use the
previous artifacts download links anymore specifying tag and job name,
because the jobs for image build and SDK build are equal. Use direct
download links instead via job number.

--

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

Build documentation in Yocto

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@0a3b1406

Confluence: get only those build jobs with a corresponding successful deploy job

We cannot handle build jobs and deploy jobs similarly, because all build
jobs are successful usually, while not all deploy jobs necessarily have
run. Get build.env only from those build job which have a corresponding
successful deploy job, otherwise MACHINE and SUPPORTED_HARDWARE fields
always contain the full list of built platforms, even if they might have
not been deployed.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@97228cdb

Move MACHINE variable from deploy.env to build.env

The Confluence stage is the only stage that needs the MACHINE variable.
Since the collect_release_information script already loads the build.env
from the build jobs, there is no need to store this variable in
deploy.env.

--

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

Confluence: check if variables are defined

--

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

Confluence: improve variable passing to template

Use a general mechanism of storing all job variables for each build job
separately, so that we have all documentation files in the
FILES_documentation variable. This makes the dedicated HTML_FILES
variable obsolete.
The merged variables are still kept, though, so that we have all
machines in the MACHINE variable to loop over.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@41f8a49f

Confluence: add error handling if artifact not found

--

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

Make documentation files configurable

This disables the documentation jobs for SDK and FNGSystem.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@303e24eb

Build documentation in dedicated job

Previously the documentation files were rendered as part of the package
jobs. Each package job converted the same set of static markdown files
to HTML files, which was redundant.

Add dedicated jobs to build, package and deploy the documentation files.

Modify convert_md2html.py to support file globs as arguments.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@838da585

Refactoring: move Alphaplan stage code to the end

This reflects the stage order in the code.

--

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

Refactoring: use multiple MACHINE loops for better structure

This is a preparation for adding dedicated documentation jobs. In order
to have these grouped by stage along with their corresponding machine
jobs, we have to get rid of the giant outer loop and add loops for each
stage instead.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@69973c95

Deploy: save deployed files in dotenv variable instead of dedicated file

Previously the deployed files were stored in a dedicated text file
called files.txt. Move this information to a dotenv variable called
FILES, so that we don't need special handling for it in the Confluence
stage.

--

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

Remove disabling sourcery low-code-quality in package_release

This check is not failing anymore since the latest refactorings.

--

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

Define manifest file to build from

--

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

Confluence: add supported hardware information

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@0ef32ce7

Update simulated build to kirkstone-14.0

Remove temporary workarounds that were necessary due to changes after
the previously used release kirkstone-7.0.

Felix Gerking authored 1 year ago and Jonas Höppner committed 1 year ago

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

Felix Gerking authored 1 year ago and Jonas Höppner committed 1 year ago

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