** Summary changed:

- Add non-sof soundwire support to AMD platforms
+ Add soundwire support for AMD platforms

** Description changed:

  Add non-sof soundwire support to AMD platforms
  
  [ Impact ]
  
  This patch series introduce non-sof soundwire support for AMD platform,
  as well as code reorganization in preparation for that.
  
  [ Test ]
  
  1. Install the test kernel
  2. Install proper alsa-ucm-confs
  3. Confirm the audio function normally on the DUT with 1) AMD soundwire and 
2) existing Intel platforms using soundwire. Might include:
-         * Checkbox audio test plan
-       * Built-in speaker and built-in mic
-       * Audio function when headphone is connected to the DUT.
+ 
+         * Checkbox audio test plan
+         * Built-in speaker and built-in mic
+         * Audio function when headphone is connected to the DUT.
  
  [ Where problems could occur ]
  
  Patches needed, other than 3 SAUCE patches that planned to upstream in
  6.13 cycle, are listed in [1] to [8] below.
  
  Soundwire used to appear mostly on Intel platforms and is almost always
  in combination with sof. To support AMD, it has to be refactored into a
  more generic framework (or at least that's what AMD people did).  This
  happens in patch series [1][2] and [3], extracting soundwire code from
  the sound/soc/intel directory to a more generic location, as well as
  rename/refactor things to better fit the ASoC context. This will impact
  all other soundwire platforms and if not done correctly, regression risk
  may be high.
  
  The all other patch sets other than [5] are AMD specific, so
  theoretically the impact is limited to AMD platforms with soundwire,
  which are rather uncommon.
  
  [1] 
https://lore.kernel.org/all/20240801091446.10457-1-vijendar.muku...@amd.com/
  [2] 
https://lore.kernel.org/lkml/20240913090631.1834543-1-vijendar.muku...@amd.com/
  [3] 
https://lore.kernel.org/all/20241101020802.1103181-1-vijendar.muku...@amd.com/
  [4] 
https://lore.kernel.org/all/20240924081846.1834612-1-vijendar.muku...@amd.com/
  [5] https://lore.kernel.org/all/20241105100557.1987917-1-shumi...@realtek.com/
  [6] 
https://lore.kernel.org/all/20241113115223.3274868-1-vijendar.muku...@amd.com/
  [7] 
https://lore.kernel.org/all/20241112185138.3235375-1-vijendar.muku...@amd.com/
  [8] 
https://lore.kernel.org/all/20241112161142.28974-1-mario.limoncie...@amd.com/

** Description changed:

  Add non-sof soundwire support to AMD platforms
  
  [ Impact ]
  
- This patch series introduce non-sof soundwire support for AMD platform,
- as well as code reorganization in preparation for that.
+ This patch series introduce soundwire support for AMD platform, as well
+ as code reorganization in preparation for that.
  
  [ Test ]
  
  1. Install the test kernel
  2. Install proper alsa-ucm-confs
  3. Confirm the audio function normally on the DUT with 1) AMD soundwire and 
2) existing Intel platforms using soundwire. Might include:
  
          * Checkbox audio test plan
-         * Built-in speaker and built-in mic
-         * Audio function when headphone is connected to the DUT.
+         * Built-in speaker and built-in mic
+         * Audio function when headphone is connected to the DUT.
  
  [ Where problems could occur ]
  
  Patches needed, other than 3 SAUCE patches that planned to upstream in
  6.13 cycle, are listed in [1] to [8] below.
  
  Soundwire used to appear mostly on Intel platforms and is almost always
  in combination with sof. To support AMD, it has to be refactored into a
  more generic framework (or at least that's what AMD people did).  This
  happens in patch series [1][2] and [3], extracting soundwire code from
  the sound/soc/intel directory to a more generic location, as well as
  rename/refactor things to better fit the ASoC context. This will impact
  all other soundwire platforms and if not done correctly, regression risk
  may be high.
  
  The all other patch sets other than [5] are AMD specific, so
  theoretically the impact is limited to AMD platforms with soundwire,
  which are rather uncommon.
  
  [1] 
https://lore.kernel.org/all/20240801091446.10457-1-vijendar.muku...@amd.com/
  [2] 
https://lore.kernel.org/lkml/20240913090631.1834543-1-vijendar.muku...@amd.com/
  [3] 
https://lore.kernel.org/all/20241101020802.1103181-1-vijendar.muku...@amd.com/
  [4] 
https://lore.kernel.org/all/20240924081846.1834612-1-vijendar.muku...@amd.com/
  [5] https://lore.kernel.org/all/20241105100557.1987917-1-shumi...@realtek.com/
  [6] 
https://lore.kernel.org/all/20241113115223.3274868-1-vijendar.muku...@amd.com/
  [7] 
https://lore.kernel.org/all/20241112185138.3235375-1-vijendar.muku...@amd.com/
  [8] 
https://lore.kernel.org/all/20241112161142.28974-1-mario.limoncie...@amd.com/

** Tags added: jira-delta-14 oem-priority

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launchpad.net/bugs/2089273

Title:
  Add soundwire support for AMD platforms

Status in OEM Priority Project:
  New
Status in linux-oem-6.11 package in Ubuntu:
  New
Status in linux-oem-6.11 source package in Noble:
  New

Bug description:
  Add non-sof soundwire support to AMD platforms

  [ Impact ]

  This patch series introduce soundwire support for AMD platform, as
  well as code reorganization in preparation for that.

  [ Test ]

  1. Install the test kernel
  2. Install proper alsa-ucm-confs
  3. Confirm the audio function normally on the DUT with 1) AMD soundwire and 
2) existing Intel platforms using soundwire. Might include:

          * Checkbox audio test plan
          * Built-in speaker and built-in mic
          * Audio function when headphone is connected to the DUT.

  [ Where problems could occur ]

  Patches needed, other than 3 SAUCE patches that planned to upstream in
  6.13 cycle, are listed in [1] to [8] below.

  Soundwire used to appear mostly on Intel platforms and is almost
  always in combination with sof. To support AMD, it has to be
  refactored into a more generic framework (or at least that's what AMD
  people did).  This happens in patch series [1][2] and [3], extracting
  soundwire code from the sound/soc/intel directory to a more generic
  location, as well as rename/refactor things to better fit the ASoC
  context. This will impact all other soundwire platforms and if not
  done correctly, regression risk may be high.

  The all other patch sets other than [5] are AMD specific, so
  theoretically the impact is limited to AMD platforms with soundwire,
  which are rather uncommon.

  [1] 
https://lore.kernel.org/all/20240801091446.10457-1-vijendar.muku...@amd.com/
  [2] 
https://lore.kernel.org/lkml/20240913090631.1834543-1-vijendar.muku...@amd.com/
  [3] 
https://lore.kernel.org/all/20241101020802.1103181-1-vijendar.muku...@amd.com/
  [4] 
https://lore.kernel.org/all/20240924081846.1834612-1-vijendar.muku...@amd.com/
  [5] https://lore.kernel.org/all/20241105100557.1987917-1-shumi...@realtek.com/
  [6] 
https://lore.kernel.org/all/20241113115223.3274868-1-vijendar.muku...@amd.com/
  [7] 
https://lore.kernel.org/all/20241112185138.3235375-1-vijendar.muku...@amd.com/
  [8] 
https://lore.kernel.org/all/20241112161142.28974-1-mario.limoncie...@amd.com/

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2089273/+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

Reply via email to