Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>

Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>

Signed-off-by: Sjoerd Simons <sjoerd@collabora.com>

Frederic Danis authored Oct 21, 2022 and Sjoerd Simons committed Nov 10, 2022

This is automatically started on user login.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Frederic Danis authored Oct 21, 2022 and Sjoerd Simons committed Nov 10, 2022

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Frederic Danis authored Oct 21, 2022 and Sjoerd Simons committed Nov 10, 2022

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Frederic Danis authored Oct 13, 2022 and Sjoerd Simons committed Nov 10, 2022

Enable DBus experimental interfaces
Enable BlueZ Experimental ISO socket support in kernel

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Frederic Danis authored Oct 21, 2022 and Sjoerd Simons committed Nov 10, 2022

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Splitting system partition(s) and storage makes a lot of sense for
product type images, but for a demonstrator it just means things are
less flexible. Switch to a single big partition instead

Signed-off-by: Sjoerd Simons <sjoerd@collabora.com>

Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>

Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>

Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

Install weston/GL stack and systemd services to automatically launch a
user session with weston running as well as a weston-terminal instance
as an example of running some program on boot.

Currently weston gets launched with the standard shell rather then the
kiosk shell as it's a bit nicer for initial development; But once the
demo app is running weston should be switched over to kiosk shell

Having apertis is confusing as i've got lots of machines with that
hostname ;) Make the hostname a bit more specific to the purpose

Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>

This reverts commit e6ae8cc3.

Now that we are shipping the driver for the DC/DC converter in
Apertis kernel package with https://gitlab.apertis.org/pkg/linux/-/merge_requests/198

,
we no longer need to carry a downstream patch to workaround
the driver not being present.

Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>

This reverts commit f6d98e05.

With https://gitlab.apertis.org/pkg/initramfs-tools/-/merge_requests/13

,
we no longer need to ship our own modified configuration file
for initramfs-tools to copy the Rockchip io-domain module into
the initramfs.

Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>

Currently the kernel (mainline & Apertis) devicetree for this
board is broken: it doesn't hangs when attempting to bringup
the usb-typec PHY:

    [    1.586285] OF: graph: no port node found in /i2c@ff3d0000/usb-typec@22

Unfortunately the dc_12v boost regulator node, which powers
the system, has some issues:

1) Apertis does not build the Kernel driver for the regulator
   (i.e. CONFIG_REGULATOR_MP8859).

2) The Device tree does not contain the port node for fusb0,
   which is the input for the dc_12v regulator. This results
   in the kernel not knowing where the input power for the
   regulator comes from and hanging.

3) When powering from 12v header, the Boost converter is not
   powered and is not found by the Kernel driver during boot.
   Since this regulator powers the whole system, the other
   regulators end up not deferring until the dc_12v regulator
   has been enabled, which never happens, resulting in a broken
   system.

So while these are fixed in the kernel, revert the patch and
rebuild the devicetree.

Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fc61ed04d309b0b8b3562acf701ab988eee12de


Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>

Without the Rockchip io-domain driver inside the initramfs,
the kernel cannot determine when the mmc IO voltage level
has switched from 3v0 to 1v8. This results in the mmc not
being detected during boot:

    [    6.948043] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
    [    7.046302] mmc_host mmc0: Bus speed (slot 0) = 148500000Hz (slot req 150000000Hz, actual 148500000HZ div = 0)
    [    7.050458] dwmmc_rockchip fe320000.mmc: All phases bad!
    [    7.050470] mmc0: tuning execution failed: -5
    [    7.050878] mmc0: error -5 whilst initialising SD card

Add the io-domain module into the initramfs to prevent the
error.

Link: https://patchwork.kernel.org/project/linux-arm-kernel/patch/20180308213540.4309-1-enric.balletbo@collabora.com/
Link: https://salsa.debian.org/kernel-team/initramfs-tools/-/commit/db7aec447eac0e5e88d114fccae1bea964924051


Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>

Signed-off-by: Christopher Obbard <chris.obbard@collabora.com>