For some reason the define TLA2518_PIN_ALL_ADC was set to 0xFF what
means gpio mode is selected. This somehow was not noted, as the ADC
generally still did work. But it drains too much current, leading to wrong
measurements.
This sets the config to the correct value of 0.

PBB-47

The long irq latencies measured on the RS485 ports could be tracked
down to the time it takes the cpu to wake up from idle.
With the pm_qos framework it is possible to request low latencies from
the powermanagement, so it would select another idle state with shorter
wakeup latency (on i.MX8MP cpu-pd-wait (slow) vs WFI (fast)).
With this the interrupts are executed much faster and the measured
latency on the RS485 port, between last stop bit and the release of
TX_EN was reduced from up to 300us to 8-30us.

The industrial variant is the only one used in production, so we could
omnit the overlay.

When the led brightness is changed from 0->1 the pwm needs to be enabled.
This clock-enabling introduces a delay from about 1ms. With the new devicetree
property the pwm is left enabled also in the 0 brightness state of the led/pwm.
This removes the delay.

PBB-36

The customer prefers a complete devicetree, as this can be handled by
his secureboot mechanism.

The reset out is already used by the gpio expander on the baseboard
and has no functional meaning for PCIe in this setup.

When switching from the tr8mmini to the tr8mplus the gpio mapping was
already changed automatically by macros, but not all labels have been
adapted. This fixes the two leftover wrong labels.

The changes didn't got integrated automatically.

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

automotive: 115C alert, 125C critical
industrial: 95C alert, 105C critical

BCS 746-001385

(cherry picked from commit 8e5eb5ab)

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

The mx8mp SoC has an additional thermal zone compared to the mx8mm.
Therefore, different overlays are required.

automotive: 115C alert, 125C critical
industrial: 95C alert, 105C critical

BCS 746-001385

(cherry picked from commit 5ea29585)

BCS 746-001467

The new variant has a controlable powersupply for the AVDD input of the
tla2518 adc. This patch configures this in the devicetree so it gets
enabled during probe.

BCS 746-001459

The smbus fails to answer a short period after the reset is released.
Increase the hardcoded reset time by 1ms to adapt to this.

The vdd and the lvds outputs ( not the signal) have been enabled
at the same time, but the panels controller is not ready and has the
termination not enabled, leading to an overshot in the lvds signals.

These delays should now make sure that the specified power sequence
is execute when blanking and unblanking the panel.

Allow to specify for delays in the devicetree:
prepare: sleep after enable of the panels power supply
enable: delay between signal enable and backlight enable
disable: delay between backlight off and signal off
unprepare: delay between signal off and panel's power supply off

As their are currently not enough serial ports available, bluetooth is
only supported on a special hardware variant.
This now can be used with the 'ble' version of the devicetree.

BCS 746-001283

BCS 746-00127

The trizeps modules may be equipped with an MCU that exposes different
features like gpio and touch.
This driver is based on kuk_tr8mcu_touch.c but splits up into an mfd
part and implements the gpio part. Further features are not yet
available.

BCS 746-00127

By default, the cma size is set to 920MiB, which cannot be initialized
on some of our some of our machines because the memory is too small.
Previously, the cma value was bypassed by setting a suitable value
in the kernel command line.
To make the devicetree config usable, the cma size is set to 320 MiB.
The value seems to be suitable for EGL surfaces and video playback.
By default libimxdmabuffer (required for vpu video playback) expects
the cma heap node to be available at /dev/dma_heap/linux,cma-uncached.
This node is only created when the devicetree cma declaration is used.
However, it seems to be possible to create a soft-link if the node is
named differently.

BCS 746-001058 746-001291

(cherry picked from commit d425df6e)

BCS 746-001281

BCS 746-001274

BCS 746-001288