Fix backported kria device tree changes

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

Bug Description

[ Impact ]

* Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch.
* Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms.

[ Test Plan ]

 * QA will run certification testing on the KD240 platform
 * Normal certification testing will be run on all other certified platforms

[ Where problems could occur ]

* This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change.

[ Fixes ]
* 6.1 compatible string and interrupt-name for gpu: gpu@fd4b0000 incorrectly backported
* 6.1 compatible string for ethernet@ff0b0000 incorrectly backported
* dwc3_[01] quirks incorrectly updated for 6.1
* xilinx_ams <reg> field incorrectly updated.

[ Other info ]
* Private launchpad bugs that contain detail on the KD240 regressions:
https://bugs.launchpad.net/limerick/+bug/2051228
https://bugs.launchpad.net/limerick/+bug/2051224
https://bugs.launchpad.net/limerick/+bug/2051201

Changed in linux-xilinx-zynqmp (Ubuntu):
assignee: nobody → Portia Stephens (portias)
importance: Undecided → Critical
importance: Critical → High
description: updated
Changed in linux-xilinx-zynqmp (Ubuntu):
status: New → In Progress
description: updated
Changed in linux-xilinx-zynqmp (Ubuntu Jammy):
status: New → 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-1027.31 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
Changed in linux-xilinx-zynqmp (Ubuntu Jammy):
assignee: nobody → Portia Stephens (portias)
importance: Undecided → High
tags: added: verification-done-jammy-linux-xilinx-zynqmp
removed: verification-needed-jammy-linux-xilinx-zynqmp
Revision history for this message
Portia Stephens (portias) wrote :

I have tested this on KD240 and verified all 3 regressions listed the bug are fixed.

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (63.5 KiB)

This bug was fixed in the package linux-xilinx-zynqmp - 5.15.0-1027.31

---------------
linux-xilinx-zynqmp (5.15.0-1027.31) jammy; urgency=medium

  * jammy/linux-xilinx-zynqmp: 5.15.0-1027.31 -proposed tracker (LP: #2054500)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/d2024.02.07)

  * Fix backported kria device tree changes (LP: #2054366)
    - SAUCE: zynqmp.dtsi fix incorrectly backported changes

  [ Ubuntu: 5.15.0-94.104 ]

  * jammy/linux: 5.15.0-94.104 -proposed tracker (LP: #2048777)
  * [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
    (LP: #2028158)
    - device-dax: Fix duplicate 'hmem' device registration
  * Add ODM driver f81604 usb-can (LP: #2045387)
    - can: usb: f81604: add Fintek F81604 support
    - [Config] updateconfigs for ODM drivers CONFIG_CAN_F81604
  * Add ODM driver gpio-m058ssan (LP: #2045386)
    - SAUCE: ODM: gpio: add M058SSAN gpio driver
    - [Config] updateconfigs for ODM drivers CONFIG_GPIO_M058SSAN
  * Add ODM driver rtc-pcf85263 (LP: #2045385)
    - SAUCE: ODM: rtc: add PCF85263 RTC driver
    - [Config] updateconfigs for ODM drivers CONFIG_RTC_DRV_PCF85263
  * AppArmor patch for mq-posix interface is missing in jammy (LP: #2045384)
    - SAUCE: (no-up) apparmor: reserve mediation classes
    - SAUCE: (no-up) apparmor: Add fine grained mediation of posix mqueues
  * Packaging resync (LP: #1786013)
    - [Packaging] update annotations scripts

  [ Ubuntu: 5.15.0-93.103 ]

  * jammy/linux: 5.15.0-93.103 -proposed tracker (LP: #2048330)
  * Packaging resync (LP: #1786013)
    - [Packaging] resync git-ubuntu-log
    - [Packaging] resync update-dkms-versions helper
    - [Packaging] remove helper scripts
    - [Packaging] update annotations scripts
    - debian/dkms-versions -- update from kernel-versions (main/2024.01.08)
  * Hotplugging SCSI disk in QEMU VM fails (LP: #2047382)
    - Revert "PCI: acpiphp: Reassign resources on bridge if necessary"
  * CVE-2023-6622
    - netfilter: nf_tables: bail out on mismatching dynset and set expressions
  * CVE-2024-0193
    - netfilter: nf_tables: skip set commit for deleted/destroyed sets
  * CVE-2023-6040
    - netfilter: nf_tables: Reject tables of unsupported family
  * Patches needed for AmpereOne (arm64) (LP: #2044192)
    - clocksource/arm_arch_timer: Add build-time guards for unhandled register
      accesses
    - clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read accessors
    - clocksource/drivers/arm_arch_timer: Extend write side of timer register
      accessors to u64
    - clocksource/drivers/arm_arch_timer: Move system register timer programming
      over to CVAL
    - clocksource/drivers/arm_arch_timer: Move drop _tval from erratum function
      names
    - clocksource/drivers/arm_arch_timer: Fix MMIO base address vs callback
      ordering issue
    - clocksource/drivers/arm_arch_timer: Move MMIO timer programming over to CVAL
    - clocksource/drivers/arm_arch_timer: Advertise 56bit timer to the core code
    - clocksource/drivers/arm_arch_timer: Work around broken CVAL implementations
    - clocksource/drivers/arm_arch_timer: Remove any trace of the TVAL progra...

Changed in linux-xilinx-zynqmp (Ubuntu Jammy):
status: Fix Committed → Fix Released
Changed in linux-xilinx-zynqmp (Ubuntu):
status: In Progress → Fix Released
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.