Update on-chip oscillator clock nodes for Kria

Bug #2055241 reported by Portia Stephens
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-xilinx-zynqmp (Ubuntu)
New
Undecided
Unassigned
Jammy
Fix Committed
High
Portia Stephens

Bug Description

[ Impact ]

* This models on-chip oscillator clock nodes in KV/KR/KD board device trees built for Xilinx products to be in sync with the corresponding board schematic
* Currently a few clocks were not modelled which are planned to be included now.
* Most clocks in board device trees are currently included so this should have minimal size impact.
* The correct and cleanest approach is to model clock sources in Xilinx's application dtsi's in order to reference these clock nodes from the board device tree rather than having duplicated nodes in application overlay dtbo's

[ Test Plan ]

* Normal certification will test that the device tree changes did not introduce a regression on any certified platform.
* Xilinx will verify they can load the dtbo's for the FPGA during runtime

[ Where problems could occur ]

* There could be an unexpected impact since there are discrepancies between some revA vs revB board device trees, all clock nodes not being modelled to be in sync with board schematics

[ Other Info ]

* Changes are pulled from Xilinx' 6.6 tree
https://github.com/Xilinx/linux-xlnx/commit/bd1a7261325afa7526ed12fbaeb8f2e939bd02f8
https://github.com/Xilinx/linux-xlnx/commit/d9d492b32494611dbcc422d9f365a59df20c69b1
https://github.com/Xilinx/linux-xlnx/commit/a0fe3083d290f8507922a68daa60cb92d76d56b2

Changed in linux-xilinx-zynqmp (Ubuntu Jammy):
assignee: nobody → Portia Stephens (portias)
status: New → In Progress
importance: Undecided → High
description: updated
description: updated
Changed in linux-xilinx-zynqmp (Ubuntu Jammy):
status: In Progress → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-xilinx-zynqmp/5.15.0-1029.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp
Revision history for this message
Sagar Karmarkar (sagark2408) wrote :

Hi @Portia

I verified the update of on chip oscillators clock nodes for Kria, with the above 1029.33 kernel. Everything working as expected and all good there.

Thanks

-Sagar

tags: added: verification-done-jammy-linux-xilinx-zynqmp
removed: verification-needed-jammy-linux-xilinx-zynqmp
Revision history for this message
Portia Stephens (portias) wrote :

@Sagar - thanks, I've updated the tags. In the future, "If the problem is solved, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'."

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.