bcm27xx: add support for linux v5.15

Build system: x86_64
Build-tested: bcm2708, bcm2709, bcm2710, bcm2711
Run-tested: bcm2708/RPiB+, bcm2709/RPi3B, bcm2710/RPi3B, bcm2711/RPi4B

Signed-off-by: Marty Jones <mj8263788@gmail.com>
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>

1 files changed, 92 insertions, 0 deletions

diff --git a/target/linux/bcm27xx/patches-5.15/950-0838-clk-tests-Add-test-suites-description.patch b/target/linux/bcm27xx/patches-5.15/950-0838-clk-tests-Add-test-suites-description.patch
new file mode 100644
index 0000000000..c5e1256143
--- /dev/null
+++ b/target/linux/bcm27xx/patches-5.15/950-0838-clk-tests-Add-test-suites-description.patch
@@ -0,0 +1,92 @@
+From 3f935fd9776cace286d40ab37726f80c8d2ed8b1 Mon Sep 17 00:00:00 2001
+From: Maxime Ripard <maxime@cerno.tech>
+Date: Fri, 1 Apr 2022 17:08:26 +0200
+Subject: [PATCH] clk: tests: Add test suites description
+
+We start to have a few test suites, and we'll add more, so it will get
+pretty confusing to figure out what is supposed to be tested in what
+suite.
+
+Let's add some comments to explain what setup they create, and what we
+should be testing in every suite.
+
+Tested-by: Alexander Stein <alexander.stein@ew.tq-group.com> # imx8mp
+Tested-by: Marek Szyprowski <m.szyprowski@samsung.com> # exynos4210, meson g12b
+Signed-off-by: Maxime Ripard <maxime@cerno.tech>
+---
+ drivers/clk/clk_test.c | 36 ++++++++++++++++++++++++++++++++++++
+ 1 file changed, 36 insertions(+)
+
+--- a/drivers/clk/clk_test.c
++++ b/drivers/clk/clk_test.c
+@@ -250,6 +250,11 @@ static struct kunit_case clk_test_cases[
+ 	{}
+ };
+ 
++/*
++ * Test suite for a basic rate clock, without any parent.
++ *
++ * These tests are supposed to exercise the rate API with simple scenarios
++ */
+ static struct kunit_suite clk_test_suite = {
+ 	.name = "clk-test",
+ 	.init = clk_test_init,
+@@ -336,6 +341,14 @@ static struct kunit_case clk_orphan_tran
+ 	{}
+ };
+ 
++/*
++ * Test suite for a basic mux clock with one parent. The parent is
++ * registered after its child. The clock will thus be orphan when
++ * registered, but will no longer be when the tests run.
++ *
++ * These tests are supposed to make sure a clock that used to be orphan
++ * has a sane, consistent, behaviour.
++ */
+ static struct kunit_suite clk_orphan_transparent_single_parent_test_suite = {
+ 	.name = "clk-orphan-transparent-single-parent-test",
+ 	.init = clk_orphan_transparent_single_parent_mux_test_init,
+@@ -645,6 +658,13 @@ static struct kunit_case clk_range_test_
+ 	{}
+ };
+ 
++/*
++ * Test suite for a basic rate clock, without any parent.
++ *
++ * These tests are supposed to exercise the rate range API
++ * (clk_set_rate_range, clk_set_min_rate, clk_set_max_rate,
++ * clk_drop_range).
++ */
+ static struct kunit_suite clk_range_test_suite = {
+ 	.name = "clk-range-test",
+ 	.init = clk_test_init,
+@@ -822,6 +842,14 @@ static struct kunit_case clk_range_maxim
+ 	{}
+ };
+ 
++/*
++ * Test suite for a basic rate clock, without any parent.
++ *
++ * These tests are supposed to exercise the rate range API
++ * (clk_set_rate_range, clk_set_min_rate, clk_set_max_rate,
++ * clk_drop_range), with a driver that will always try to run at the
++ * highest possible rate.
++ */
+ static struct kunit_suite clk_range_maximize_test_suite = {
+ 	.name = "clk-range-maximize-test",
+ 	.init = clk_maximize_test_init,
+@@ -991,6 +1019,14 @@ static struct kunit_case clk_range_minim
+ 	{}
+ };
+ 
++/*
++ * Test suite for a basic rate clock, without any parent.
++ *
++ * These tests are supposed to exercise the rate range API
++ * (clk_set_rate_range, clk_set_min_rate, clk_set_max_rate,
++ * clk_drop_range), with a driver that will always try to run at the
++ * lowest possible rate.
++ */
+ static struct kunit_suite clk_range_minimize_test_suite = {
+ 	.name = "clk-range-minimize-test",
+ 	.init = clk_minimize_test_init,