| Message ID | 20230315183729.2376178-1-sboyd@kernel.org (mailing list archive) |
|---|---|
| Headers | show |
| Series | clk: Add kunit tests for fixed rate and parent data | expand |
On Thu, 16 Mar 2023 at 02:37, Stephen Boyd <sboyd@kernel.org> wrote: > > This patch series adds unit tests for the clk fixed rate basic type and > the clk registration functions that use struct clk_parent_data. To get > there, we add support for loading device tree overlays onto the live DTB > along with probing platform drivers to bind to device nodes in the > overlays. With this series, we're able to exercise some of the code in > the common clk framework that uses devicetree lookups to find parents > and the fixed rate clk code that scans device tree directly and creates > clks. Please review. > > I Cced everyone to all the patches so they get the full context. I'm > hoping I can take the whole pile through the clk tree as they almost all > depend on each other. > > Changes from v1 (https://lore.kernel.org/r/20230302013822.1808711-1-sboyd@kernel.org): > * Don't depend on UML, use unittest data approach to attach nodes > * Introduce overlay loading API for KUnit > * Move platform_device KUnit code to drivers/base/test > * Use #define macros for constants shared between unit tests and > overlays > * Settle on "test" as a vendor prefix > * Make KUnit wrappers have "_kunit" postfix > Thanks! I like this much better, and it is working fine here under UML and x86_64. There are some issues with other architectures (mostly endianness problems, but I got a refcount underflow in kunit_remove_resource after platform_device_alloc_kunit_test on sparc64 as well), but otherwise it's working on most of the things I've tried. I'll play around with it some more next week and dig into the code in more detail, but I've not seen anything I dislike about the overall design so far. Thanks! -- David > Stephen Boyd (11): > of: Load KUnit DTB from of_core_init() > of: Add test managed wrappers for of_overlay_apply()/of_node_put() > dt-bindings: vendor-prefixes: Add "test" vendor for KUnit and friends > dt-bindings: test: Add KUnit empty node binding > of: Add a KUnit test for overlays and test managed APIs > platform: Add test managed platform_device/driver APIs > dt-bindings: kunit: Add fixed rate clk consumer test > clk: Add test managed clk provider/consumer APIs > clk: Add KUnit tests for clk fixed rate basic type > dt-bindings: clk: Add KUnit clk_parent_data test > clk: Add KUnit tests for clks registered with struct clk_parent_data > > .../clock/test,clk-kunit-parent-data.yaml | 47 ++ > .../kunit/test,clk-kunit-fixed-rate.yaml | 35 ++ > .../bindings/test/test,kunit-empty.yaml | 30 ++ > .../devicetree/bindings/vendor-prefixes.yaml | 2 + > drivers/base/test/Makefile | 3 + > drivers/base/test/platform_kunit-test.c | 108 +++++ > drivers/base/test/platform_kunit.c | 186 +++++++ > drivers/clk/.kunitconfig | 3 + > drivers/clk/Kconfig | 7 + > drivers/clk/Makefile | 9 +- > drivers/clk/clk-fixed-rate_test.c | 299 ++++++++++++ > drivers/clk/clk-fixed-rate_test.h | 8 + > drivers/clk/clk_kunit.c | 219 +++++++++ > drivers/clk/clk_parent_data_test.h | 10 + > drivers/clk/clk_test.c | 459 +++++++++++++++++- > drivers/clk/kunit_clk_fixed_rate_test.dtso | 19 + > drivers/clk/kunit_clk_parent_data_test.dtso | 28 ++ > drivers/of/.kunitconfig | 5 + > drivers/of/Kconfig | 23 + > drivers/of/Makefile | 7 + > drivers/of/base.c | 182 +++++++ > drivers/of/kunit.dtso | 10 + > drivers/of/kunit_overlay_test.dtso | 9 + > drivers/of/of_kunit.c | 123 +++++ > drivers/of/of_private.h | 6 + > drivers/of/of_test.c | 43 ++ > drivers/of/overlay_test.c | 107 ++++ > drivers/of/unittest.c | 101 +--- > include/kunit/clk.h | 28 ++ > include/kunit/of.h | 90 ++++ > include/kunit/platform_device.h | 15 + > 31 files changed, 2119 insertions(+), 102 deletions(-) > create mode 100644 Documentation/devicetree/bindings/clock/test,clk-kunit-parent-data.yaml > create mode 100644 Documentation/devicetree/bindings/kunit/test,clk-kunit-fixed-rate.yaml > create mode 100644 Documentation/devicetree/bindings/test/test,kunit-empty.yaml > create mode 100644 drivers/base/test/platform_kunit-test.c > create mode 100644 drivers/base/test/platform_kunit.c > create mode 100644 drivers/clk/clk-fixed-rate_test.c > create mode 100644 drivers/clk/clk-fixed-rate_test.h > create mode 100644 drivers/clk/clk_kunit.c > create mode 100644 drivers/clk/clk_parent_data_test.h > create mode 100644 drivers/clk/kunit_clk_fixed_rate_test.dtso > create mode 100644 drivers/clk/kunit_clk_parent_data_test.dtso > create mode 100644 drivers/of/.kunitconfig > create mode 100644 drivers/of/kunit.dtso > create mode 100644 drivers/of/kunit_overlay_test.dtso > create mode 100644 drivers/of/of_kunit.c > create mode 100644 drivers/of/of_test.c > create mode 100644 drivers/of/overlay_test.c > create mode 100644 include/kunit/clk.h > create mode 100644 include/kunit/of.h > create mode 100644 include/kunit/platform_device.h > > > base-commit: fe15c26ee26efa11741a7b632e9f23b01aca4cc6 > -- > https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git/ > https://git.kernel.org/pub/scm/linux/kernel/git/sboyd/spmi.git >
Hi, On Wed, Mar 15, 2023 at 11:37:17AM -0700, Stephen Boyd wrote: > This patch series adds unit tests for the clk fixed rate basic type and > the clk registration functions that use struct clk_parent_data. To get > there, we add support for loading device tree overlays onto the live DTB > along with probing platform drivers to bind to device nodes in the > overlays. With this series, we're able to exercise some of the code in > the common clk framework that uses devicetree lookups to find parents > and the fixed rate clk code that scans device tree directly and creates > clks. Please review. > > I Cced everyone to all the patches so they get the full context. I'm > hoping I can take the whole pile through the clk tree as they almost all > depend on each other. > > Changes from v1 (https://lore.kernel.org/r/20230302013822.1808711-1-sboyd@kernel.org): > * Don't depend on UML, use unittest data approach to attach nodes > * Introduce overlay loading API for KUnit > * Move platform_device KUnit code to drivers/base/test > * Use #define macros for constants shared between unit tests and > overlays > * Settle on "test" as a vendor prefix > * Make KUnit wrappers have "_kunit" postfix Maybe I'm overthinking this, but wouldn't it make more sense to have a kunit *prefix* to those functions? Any other function in the kernel taking a kunit test pointer as a parameter starts with kunit (like kunit_kzalloc), so it would make more sense to me that kunit-related clk functions follow the same pattern. Maxime