[Kernel-packages] [Bug 2055241] Re: Update on-chip oscillator clock nodes for Kria
@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'." -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2055241 Title: Update on-chip oscillator clock nodes for Kria Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2055241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055241] Re: Update on-chip oscillator clock nodes for Kria
** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2055241 Title: Update on-chip oscillator clock nodes for Kria Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2055241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055241] Re: Update on-chip oscillator clock nodes for Kria
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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2055241 Title: Update on-chip oscillator clock nodes for Kria Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2055241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055241] Re: Update on-chip oscillator clock nodes for Kria
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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2055241 Title: Update on-chip oscillator clock nodes for Kria Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2055241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055241] Re: Update on-chip oscillator clock nodes for Kria
** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2055241 Title: Update on-chip oscillator clock nodes for Kria Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2055241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
