Skip to content
Snippets Groups Projects
Select Git revision
0 results
Search by author
  • Any Author
0 authors
  1. Oct 11, 2023
  3. Oct 09, 2023
  5. Oct 06, 2023
  7. Oct 04, 2023
  9. Sep 29, 2023
  11. Sep 28, 2023
  13. Sep 25, 2023
  15. Sep 22, 2023
    • Jonas Höppner's avatar
      imx6: Fixed touch performance issues · dec026ea
      Jonas Höppner authored 
      The i2c driver had a performance issue that lead to problems with some
eeti and ilitik touch drivers. This issue was fixed with a kernel
commit.
This updates the related lines in the feature list.

Change-Id: I688be6a7f33251a69782f7bc834f87142c3ef370
      2 tags
      dec026ea
    • GitBot's avatar
      Integrate meta-seconorth-machine/kirkstone-stabilize-ip-for-edgehog · 58aa1cc8
      GitBot authored 
      --

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



systemd-conf:wired.network: do not send DHCP release on service stop

Fix the problem with floating IP addresses after first reboot in Edgehog
image.

Even when a stable MAC is assigned to device via device-tree, an IP address
may change after the first reboot.
This is due to default implementation of built-in DHCP client provided by
systemd-network daemon - DHCP RELEASE packet is sent to the DHCP server
during reboot by this daemon. So, next time a new IP address is allocated
to the same DHCP client (device).

To change this behavior of the DHCP client, a
"KeepConfiguration=dhcp-on-stop" option is enabled in configuration file
for systemd-networkd.

Signed-off-by: default avatarMikhail Vanyulin <mikhail.vanyulin@rtsoft.de>
      58aa1cc8
  17. Sep 21, 2023
  19. Sep 20, 2023
  21. Sep 19, 2023
  23. Sep 18, 2023
    • GitBot's avatar
      Integrate uboot-imx-kuk/mx6-enable-fastboot · 893ae50e
      GitBot authored 
      --

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
      893ae50e
    • GitBot's avatar
      Integrate linux-imx-kuk/i2c_imx_isr_read_fsl · 0d2d5788
      GitBot authored 
      --

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
      0d2d5788
    • GitBot's avatar
      Integrate linux-guf/i2c_imx_isr_read · 7c4c771f
      GitBot authored 
      --

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
      7c4c771f
    • GitBot's avatar
      Integrate gitlab-ci/hide-stages-if-variables-not-set and 4 more · dfde16e9
      GitBot authored 
      --

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
      dfde16e9
  25. Sep 15, 2023
  27. Sep 14, 2023
  29. Sep 13, 2023
  31. Sep 12, 2023
    • GitBot's avatar
      Integrate linux-imx-kuk/fix_wm9705_dig2 · 1ee67229
      GitBot authored 
      --

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
      1ee67229