Adding support for clock nexus had some prerequisites requested by
Stephen, such as adding new selftests, the initial discussions come from:

Link: https://lore.kernel.org/linux-clk/20260129201003.288605-1-miquel.raynal@bootlin.com/

Then there has been a bigger series (including patches for other
subsystems) to show the big picture, but let's split again and focus on
one subsystem at a time:

Changes in v2:
- Collected tags.
- Rebased on top of v7.2-rc1
- Exported (test) clock symbols using the _IF_KUNIT() variant, and
  imported the NS in the test file.
- Fixed a leaking node reported by Brian in the tests. Also used
  existing helpers to simplify the test implementation as he wisely
  suggested.
- Reworded the nexus node binding description as suggested by Stephen.
- Dropped redundant and non restraining properties from the Nexus
  node as suggested by Rob.
- Assigned clock/clock-rate properties now traverse Nexus nodes.
- Rename helpers following Stephen proposals.
- Rework tests following Stephen hints.
- Link to v1: https://lore.kernel.org/r/20260327-schneider-v7-0-rc1-crypto-v1-0-5e6ff7853994@bootlin.com

Signed-off-by: Miquel Raynal (Schneider Electric) <miquel.raynal@bootlin.com>
---
Miquel Raynal (Schneider Electric) (7):
      dt-bindings: clock: Introduce nexus nodes
      clk: tests: Add clk_parse_clkspec() Kunit testing
      clk: tests: Add Kunit testing for of_clk_get_parent_name()
      clk: Improve a couple of comments
      clk: Use the generic OF phandle parsing in only one place
      clk: Add support for clock nexus dt bindings
      clk: tests: Add Kunit testing for nexus nodes

 .../bindings/clock/clock-nexus-node.yaml           |  30 +++++
 drivers/clk/Makefile                               |   1 +
 drivers/clk/clk-conf.c                             |  12 +-
 drivers/clk/clk.c                                  |  13 +-
 drivers/clk/clk_kunit_helpers.c                    |  31 +++++
 drivers/clk/clk_test.c                             | 146 +++++++++++++++++++++
 drivers/clk/kunit_clk_parse_clkspec.dtso           |  31 +++++
 include/kunit/clk.h                                |   2 +
 8 files changed, 254 insertions(+), 12 deletions(-)
---
base-commit: 7f26e010764df304602f33912a0550dcf46e72c2
change-id: 20260710-schneider-v7-2-rc1-eip201-upstream-a470e5eab92d

Best regards,
-- 
Miquel Raynal (Schneider Electric) <miquel.raynal@bootlin.com>

Hi Miquel,

> Then there has been a bigger series (including patches for other
> subsystems) to show the big picture, but let's split again and focus on
> one subsystem at a time:

This is a good idea IMO. Sadly, for this series, I won't have time for
review. If you have a branch available for testing, I could provide
test-tags, though.

Happy hacking,

   Wolfram

Hello Wolfram,

On 12/07/2026 at 10:18:46 +02, Wolfram Sang <wsa+renesas@sang-engineering.com> wrote:

> Hi Miquel,
>
>> Then there has been a bigger series (including patches for other
>> subsystems) to show the big picture, but let's split again and focus on
>> one subsystem at a time:
>
> This is a good idea IMO. Sadly, for this series, I won't have time for
> review. If you have a branch available for testing, I could provide
> test-tags, though.

We are working on adding the two other crypto algorithms in. I believe
the crypto stuff is worth testing for you as it is the one showing proof
that all the drivers work on RZN1 hardware. When we send this out we
will include a link in the cover letter with a branch to test,
connecting the clock, irqchip an crypto changes together. Don't hesitate
to remind us for that testing branch if we forget to include it!

Thanks,
Miquèl

Hi Miquel,

> that all the drivers work on RZN1 hardware. When we send this out we
> will include a link in the cover letter with a branch to test,
> connecting the clock, irqchip an crypto changes together. Don't hesitate
> to remind us for that testing branch if we forget to include it!

Will surely do. Sounds awesome, thank you! Bonus points if you could
also shorty summarize how you tested all the stuff then.

Looking forward to it,

   Wolfram

On 15/07/2026 at 15:59:01 +02, Wolfram Sang <wsa+renesas@sang-engineering.com> wrote:

> Hi Miquel,
>
>> that all the drivers work on RZN1 hardware. When we send this out we
>> will include a link in the cover letter with a branch to test,
>> connecting the clock, irqchip an crypto changes together. Don't hesitate
>> to remind us for that testing branch if we forget to include it!
>
> Will surely do. Sounds awesome, thank you! Bonus points if you could
> also shorty summarize how you tested all the stuff then.

So far I just enabled all the crypto selftests (CONFIG_CRYPTO_SELFTESTS,
CONFIG_CRYPTO_SELFTESTS_FULL). Given the amount of errors I got during
my first iterations, it seemed pretty complete :-)

Thanks,
Miquèl