Dietmar Muscholik authored 1 year ago and Jonas Höppner committed 1 year ago

Added additional compatible entry to enable support for eDP displays.

The ectrl_stm32 drive isn't yet ported. Disable the support in the DTS
for now.

BCS 746-001345

Gianfranco Mariotti authored 1 year ago and Tobias Kahlki committed 1 year ago

* enabled at u-boot: seco_config tool CSI0, CSI1 peripherals
* on carrier B79: CSD18REVB + CSC47REVA + CSC19REVB (CSI CN39)
* Test details:
  root@seco-imx8mp-d18:~# dmesg | grep -i ov5640
  ...
  mx8-img-md: Registered sensor subdevice: ov5640 2-003c (1)
  mx8-img-md: Registered sensor subdevice: ov5640 1-003c (2)
  mx8-img-md: created link [ov5640 2-003c] => [mxc-mipi-csi2.0]
  mx8-img-md: created link [ov5640 1-003c] => [mxc-mipi-csi2.1]
  root@seco-imx8mp-d18:~# v4l2-ctl --list-devices
  ...
  mxc-isi-cap (platform:32e00000.isi:cap_devic):
    /dev/video2
  ...
  mxc-isi-cap (platform:32e02000.isi:cap_devic):
    /dev/video3
  ...
  root@seco-imx8mp-d18:~# gst-launch-1.0 -v v4l2src device=/dev/video2 ! waylandsink
  root@seco-imx8mp-d18:~# gst-launch-1.0 -v v4l2src device=/dev/video3 ! waylandsink

Gianfranco Mariotti authored 1 year ago and Tobias Kahlki committed 1 year ago

* enabled at u-boot: seco_config tool

Gianfranco Mariotti authored 1 year ago and Tobias Kahlki committed 1 year ago

* enabled at u-boot: seco_config tool

Gianfranco Mariotti authored 1 year ago and Tobias Kahlki committed 1 year ago

* enabled at u-boot: seco_config tool

Gianfranco Mariotti authored 1 year ago and Tobias Kahlki committed 1 year ago

* enabled at u-boot: seco_config tool
* on CSB79REVB: panel BOE EV156FHM (eDP0 CN60: switch SW6 2-4 position ON,
  jumper CN18 and CN19 position 1-2)

Gianfranco Mariotti authored 1 year ago and Tobias Kahlki committed 1 year ago

* enabled at u-boot: seco_config tool
* connected on LVDS channel 1
* on CSB79REVB: panel URT UMSH-8596MD-20T + CV1338/400REVB
  (LVDS CN14+LCD CN17: switch SW6 1-3 position OFF, jumper CN20
  position 1-2 and CN21 position 1-2)

Gianfranco Mariotti authored 1 year ago and Tobias Kahlki committed 1 year ago

* enabled at u-boot: seco_config tool
* on CSB79REVB: panel AUO P215HVN01.0 + CV1235/750REVB
  (LVDS CN14: switch SW6 1-3 and 2-4 position OFF, jumper CN18
  position 2-3 and CN19 position 1-2)

Gianfranco Mariotti authored 1 year ago and Tobias Kahlki committed 1 year ago

* enabled at u-boot: seco_config tool

Gianfranco Mariotti authored 1 year ago and Tobias Kahlki committed 1 year ago

* enabled at u-boot: seco_config tool
* audio over SAI3 interface
  * SAI3 --> carrier board or onboard bluetooth (I2S2 SMARC | AUDIO BT)
* Filesystem support --> pulseaudio + bluez5
  * Yocto packages:
    pulseaudio-server pulseaudio-module-cli pulseaudio-misc
    pulseaudio-module-device-manager bluez5-noinst-tools bluez5-obex
    bluez5-testtools pulseaudio-module-bluetooth-discover
    pulseaudio-module-bluetooth-policy pulseaudio-module-bluez5-discover
    pulseaudio-module-bluez5-device pulseaudio-module-switch-on-connect
    pulseaudio-module-loopback
* Test details:
  root@seco-imx8mp-d18:~# pulseaudio -D
  root@seco-imx8mp-d18:~# bluetoothctl
  [bluetooth]# default-agent
  [bluetooth]# power on
  [bluetooth]# scan on
  ...
  Device 74:45:CE:40:2B:DD WH-CH510
  ...
  [bluetooth]# scan off
  [bluetooth]# trust 74:45:CE:40:2B:DD
  [bluetooth]# pair 74:45:CE:40:2B:DD
  [bluetooth]# connect 74:45:CE:40:2B:DD
  [WH-CH510]# info
  Device 74:45:CE:40:2B:DD (public)
    Name: WH-CH510
    Alias: WH-CH510
    Class: 0x00240404
    ...
  [WH-CH510]# exit
  root@seco-imx8mp-d18:~# pactl list sinks short | awk '{print $2}'
  root@seco-imx8mp-d18:~# paplay -d bluez_sink.74_45_CE_40_2B_DD.a2dp_sink test.wav

Gianfranco Mariotti authored 1 year ago and Tobias Kahlki committed 1 year ago

* audio over SAI2 interface
* output needs to be enabled: /usr/bin/amixer sset -q 'LO Driver Gain' 100%
* sound works only at 48000Hz: this derives from SAI2 assigned clock rate.
  * Filesystem support for pulseaudio:
    /etc/pulse/daemon.conf --> default-sample-rate = 48000
                               alternate-sample-rate = 48000
* on CSB79REVB: I2S0 to audio jack CN41 (switch SW16 2-4 position OFF,
  jumper CN82 position 2-3)

Gianfranco Mariotti authored 1 year ago and Tobias Kahlki committed 1 year ago

Workaround for NXP chip errata ERR007805 "I2C: When the I2C clock speed is
configured for 400 kHz, the SCL low period violates the I2C spec of 1.3 uS min"
This errata is found on the following SoCs:
* MX8M{M,N,P,Q}
* MX7{S,D}
* MX6{UL{,L,Z},S{,LL,X},S,D,DL,Q,DP,QP}

Gianfranco Mariotti authored 1 year ago and Tobias Kahlki committed 1 year ago

* on CSB79REVB: card PCIe-Intel-I210-x4 (PCIe x4 slot CN33: switch SW17 2-4 position OFF)
* Test details:
  root@seco-imx8mp-d18:~# lspci
  00:00.0 PCI bridge: Synopsys, Inc. DWC_usb3 / PCIe bridge (rev 01)
  01:00.0 PCI bridge: Pericom Semiconductor PI7C9X2G608GP PCIe2 6-Port/8-Lane Packet Switch
  ...
  06:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

Gianfranco Mariotti authored 1 year ago and Tobias Kahlki committed 1 year ago

* the module is based on Marvell 88W8997 chipset
* CSD18REVB has a pull-down on WIFI_PWRDWN#, set P1_2_WiFi_EN to allow probing

Gianfranco Mariotti authored 1 year ago and Tobias Kahlki committed 1 year ago

* DP83867 Gigabit Ethernet PHY transceiver

Gianfranco Mariotti authored 1 year ago and Tobias Kahlki committed 1 year ago

* internal eMMC --> device 0
* external SD   --> device 1

Original Commit 90ac559b5dc95a52dd15b6d11568acbde6c5fd76

BCS 746-001345

BCS 746-001345

BCS 746-001345

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

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/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/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

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

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/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