| 2024-02-28 04:32:13 |
Portia Stephens |
bug |
|
|
added bug |
| 2024-02-28 04:32:25 |
Portia Stephens |
nominated for series |
|
Ubuntu Jammy |
|
| 2024-02-28 04:32:25 |
Portia Stephens |
bug task added |
|
linux-xilinx-zynqmp (Ubuntu Jammy) |
|
| 2024-02-28 04:32:32 |
Portia Stephens |
linux-xilinx-zynqmp (Ubuntu Jammy): assignee |
|
Portia Stephens (portias) |
|
| 2024-02-28 04:32:37 |
Portia Stephens |
linux-xilinx-zynqmp (Ubuntu Jammy): status |
New |
In Progress |
|
| 2024-02-28 04:32:40 |
Portia Stephens |
linux-xilinx-zynqmp (Ubuntu Jammy): importance |
Undecided |
High |
|
| 2024-02-28 04:33:22 |
Portia Stephens |
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 ]
* 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 ]
https://github.com/Xilinx/linux-xlnx/commit/bd1a7261325afa7526ed12fbaeb8f2e939bd02f8
https://github.com/Xilinx/linux-xlnx/commit/d9d492b32494611dbcc422d9f365a59df20c69b1
https://github.com/Xilinx/linux-xlnx/commit/a0fe3083d290f8507922a68daa60cb92d76d56b2 |
[ 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 ]
https://github.com/Xilinx/linux-xlnx/commit/bd1a7261325afa7526ed12fbaeb8f2e939bd02f8
https://github.com/Xilinx/linux-xlnx/commit/d9d492b32494611dbcc422d9f365a59df20c69b1
https://github.com/Xilinx/linux-xlnx/commit/a0fe3083d290f8507922a68daa60cb92d76d56b2 |
|
| 2024-02-28 04:33:40 |
Portia Stephens |
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 ]
https://github.com/Xilinx/linux-xlnx/commit/bd1a7261325afa7526ed12fbaeb8f2e939bd02f8
https://github.com/Xilinx/linux-xlnx/commit/d9d492b32494611dbcc422d9f365a59df20c69b1
https://github.com/Xilinx/linux-xlnx/commit/a0fe3083d290f8507922a68daa60cb92d76d56b2 |
[ 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 |
|
| 2024-03-26 23:50:45 |
Portia Stephens |
linux-xilinx-zynqmp (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2024-04-26 06:52:06 |
Ubuntu Kernel Bot |
tags |
|
kernel-spammed-jammy-linux-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp |
|
| 2024-05-02 00:10:33 |
Portia Stephens |
tags |
kernel-spammed-jammy-linux-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp |
kernel-spammed-jammy-linux-xilinx-zynqmp-v2 verification-done-jammy-linux-xilinx-zynqmp |
|
