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

(cherry picked from commit 518566e856ed0aa8e127a1eda48c6392a39e4e86)

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

(cherry picked from commit 492a65c2b6fbf47ebe26b851d0adf1beca2ba2e9)

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

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>
(cherry picked from commit e30bc118a5d2b4fd003c71006980c5b2c06429ca)

--

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.

For level interrupts, the latching of the inputs is rather unwanted. The
latching might lead to false interrupt states which occur if the input changes
again before the interrupt is completely processed. This can either be
resolved by reading the input status register twice or by disabling the
latching for level interrupt pins. Without the latching, very short level
interrupt changes are ignored. Since we don't want them anyway, we opt for
the second solution.

This adds level interrupt support to the pca953x driver. In the IRQ routine,
the input status register is compared to the irq_trig_level_high and
irq_trig_level_low parameters. If the value from the input status register
aligns with one of the parameters, a level interrupt is issued.
After processing all nested interrupts, the pending function is called again,
to determine if the level interrupt condition is still active. If this is the
case, the nested interrupts are processed again.

Reading the input status register resets the interrupt status register.
If an interrupt from the GPIO-Expander to the SoC is issued and an additional
GPIO read occurs at the same time, the GPIO read might reset the interrupt
status register (by reading the input status register). The IRQ routine of
the GPIO-Expander is then unable to determine on which input an interrupt
occurred. To prevent this from happening, the interrupt status register is
read before each read of the input status register and the result is saved
for later processing. In the IRQ routine, the current interrupt status
register value is then combined with the stored value.

--

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

The line-names have to be assigned to the GPIO-Expander and not the
I2C-Bus.

--

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 patch adds the necessary device-tree settings for the ModularVision
carrier board to support the TAS2505 audio-codec.

Note: Also requires CONFIG_SND_SOC_TLV320AIC32X4_I2C to be enabled in
kernel defconfig (the tlva320aic32x4 driver also provides support for
the TAS2505 codec).

Mikhail Vanyulin authored 1 year ago and Jonas Höppner committed 1 year ago

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>

Mikhail Vanyulin authored 1 year ago and Jonas Höppner committed 1 year ago

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

Since commit 91a7cda1 ("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: 91a7cda1 ("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>

This provides support for the 10-inch display variant for Modular Vision
on the i.MX8MP SMARC module.

This adds the combined devicetree for the Modular Vision 7-inch HMI.

This adds a devicetree include for specific functionality of the Modular
Vision SMARC module carrier.
The audio interface and GPIO expander are not working yet.

The display and backlight enable pins are configured in the respective
display DTs. Remove them from the imx8mp-d18 base DT.

The deletion of the B79 nodes didn't work as expected. Rewrote all
deletions to fix this.

This partly reverts commit 8fa40ae3. In the original commit, the
devicetree was split into two. With the splitting, cherry-picks from the
upstream repo doesn't work anymore. As a workaround, we revert the
seco-imx8mp-d18.dts to its original state, include it in a new
devicetree include and remove the B79 nodes there.

 imported from branch kuk_lf-5.10.y_android
 currently only ConXM baseboards with HDMI are supported

 On some modules the interrupt of the bd718x7 is not connected to anything,
 but the PMIC functionality is needed anyway. For such modules it would be
 helpfull if the probe function succeeds without an interrupt configured.

The boot strapping in U-Boot isn't integrated correctly yet. Because of
this, we have a collision between the ethphys. Since we don't use the
second phy right now, we disable it.

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.

--

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

There is no such property in device tree. Previously it was set by kernel
in runtime (see function "set_video_mode_from_xml" in guf_xml_to_dt.c).

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