GitLab

The Acer Chromebook R13 needs some alsa configuration ucm2 files to make
the audio work, as these are not provided by any debian package yet,
install it manually.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

The VPU firmware for MT8173 Chromebooks devices is not present on
any debian package, so install manually.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

Add support for the Lenovo IdeaPad Duet Chromebook, a board based on the
MT8183 SoC.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

Use the latest stable toolchain.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

The reason to have it as a separate fragment is because there are some
options that doesn't work as a module, we should fix those before
upstream the configuration options to support better the Mediatek
devices.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

Add the profile for the HP Chromebook 11A G6 EE (grunt)
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

This package contains the setuid chromium sandbox.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

The MT8173 boards Elm and Hana are now upstream, so add their devicetree
to create properly a FIT image to support these boards.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

Add the profile for the Lenovo Chromebook (hana), which is using mt8173
as SoC.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

This will add basic support for the Lenovo IdeaPad Duet Chromebook.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

This fragment enables tracing and dynamic debugging kernel options.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

This is required, for example, for Acer Chromebook R13.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

This is required, for example, for Acer Chromebook R11.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

The SOF firmware for Bytrail and Cherrytrail devices is not present on
any debian package, so install manually.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

This driver is required, for example, on Acer Chromebook R11 (Cyan).
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

There is Intel support in place for Baytrail, Cherrytrail, Broadwell,
Apollolake, Cannonlake, and Braswell DSP hardware. So enable SOF for the
sound system.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

Enable TPM security chip that is compliant with the TCG TIS 1.2 TPM
specification. All Chromebooks come with a TPM chip.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

The CONFIG_SND_HDA_INTEL is redefined by fragment so we can remove it.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

On some devices, like Cherrytrail devices, we will need to pass extra
parameter to the kernel in order to fix some issues. For that purpose
add and extra kernel parameter option to be able to pass these
parameters.

Pixel and others devices has known bug with its TPM where it doesn't
initialize correctly. To get around this, the tpm_tis module must be
force-loaded at boot. If this is not done, the Chromebook performs a
hard reboot when attempting to resume from suspend. While here,
force-loaded at boot for AMD64 based devices.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

Now that kernel 5.5 was released, update the status report accordingly.

  - Display works with CONFIG_DRM_PANEL_KINGDISPLAY_KD097D04 and
   CONFIG_DRM_PANEL_INNOLUX_P079ZCA.
  - Touchscreen works thanks to CONFIG_TOUCHSCREEN_ELAN
  - Wifi works and have been tested using gnome preferences.
  - GPU drivers is loaded successfully and used by other modules.
  - Headphone does not work.
  - Bluetooth does not work. The first issue was a missing firmware.
    Then we still cannot see any devices.
Signed-off-by: Fabien Lahoudere <fabien.lahoudere@collabora.com>
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

Scarlet uses ELAN touchscreen, so enable its driver.
Signed-off-by: Fabien Lahoudere <fabien.lahoudere@collabora.com>
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

Now that we 5.5 was released update the status report accordingly. Not a
lot of changes regarding on what is supported and what not.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

Scarlet LCD config is missing. We have to add 2 panels for the two
models described in the two device tree.
Signed-off-by: Fabien Lahoudere <fabien.lahoudere@collabora.com>

Sometimes we just want to update the kernel fit image,
e.g. change the device tree or the kernel boot comand.
In this case we don't need to copy again the whole kernel modules
which takes a lot of time. Option deploy_kernel_only just
builds a fit image and writes it to the storage medium.
Signed-off-by: Matthias Brugger <mbrugger@suse.com>

Signed-off-by: Fabien Lahoudere <fabien.lahoudere@collabora.com>

Mainline status update.
Also add a note about how to use camera
Signed-off-by: Fabien Lahoudere <fabien.lahoudere@collabora.com>

x86 based chromeboook need bluetooth config in the kernel.
Signed-off-by: Fabien Lahoudere <fabien.lahoudere@collabora.com>

Nocturne uses one IPU, 2 sensors and 1 lens for the camera.
This patch enable all requested drivers to get data from cameras.
Signed-off-by: Fabien Lahoudere <fabien.lahoudere@collabora.com>

Nocturne uses 2 i2c eeprom managed by at24 drivers.
Signed-off-by: Fabien Lahoudere <fabien.lahoudere@collabora.com>

The cros-ec tests have been renamed to crostests, switch the test
template to use the new project.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

Enable the drivers needed for the Mediatek Video Decoder, WiFi and
Bluetooth for ELM devices.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

The purpose of this {{kernel_tree}} variable is be able to point any
kernel tree built in KernelCI. By default it points to 'mainline/master'
but you can use a template variable to use any other tree (i.e.
'chrome-platform/for-kernelci')
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

The GNOME3 desktop rootfs is used now for all the boards and is not
specific to Rockchip anymore, so update the documentation according to
that.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

We not use lxde image anymore in favor of Gnome3 based image, so remove
this paragraph.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

Nocturne comes with a Intel WiFi chipset so add the driver in the
chromebooks fragment.
Signed-off-by: Fabien Lahoudere <fabien.lahoudere@collabora.com>
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

Nocturne needs Intel sound drivers to work. Moreover it does not work if
built-in so we force CONFIG_SND_HDA_INTEL to module to make it work.
Signed-off-by: Fabien Lahoudere <fabien.lahoudere@collabora.com>
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

Now that the cros-ec test suite has its own repository [1], switch to use
that repository and remove the test suite frome here to avoid code
duplication.

[1] https://gitlab.collabora.com/chromiumos/crostests.gitSigned-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

This test is actually integrated in the test-cros-ec.py suite, so we
don't need to run the test-cros-ec-pwm-backlight.sh script. Remove from
the run steps.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

The scripts checks the embedded controller and other MCU ABI to ensure
that all required files are present.
Signed-off-by: Fabien Lahoudere <fabien.lahoudere@collabora.com>
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

lqa is able to replace the YAML template variables like {{variable}}
with the values specified using -t options from the command line. Use
those variables allows us to make the YAML file generic for all the
supported boards in the LAVA Lab. Add a profiles file and the variables
needed in order to be able to use the same YAML file to launch a LAVA
job for a specific board or all boards. I.e: You should be able to see the
jobs running issuing a:

  lqa submit -g chromebooks-profiles.yaml --all-profiles -t kernel_version:<kernel version> chromebooks-tpl.yaml

Or instead of using --all-profiles use -p <device_type> to launch a LAVA
job for a specific device.
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>