~mreed8855/ubuntu/+source/linux/+git/mantic:fnic_update_2036777

Last commit made on 2023-12-07
Get this branch:
git clone -b fnic_update_2036777 https://git.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic
Only Michael Reed can upload to this branch. If you are Michael Reed please log in for upload directions.

Branch merges

Branch information

Name:
fnic_update_2036777
Repository:
lp:~mreed8855/ubuntu/+source/linux/+git/mantic

Recent commits

5c87840... by Karan Tilak Kumar

scsi: fnic: Fix sg_reset success path

BugLink: https://bugs.launchpad.net/bugs/2036777

sg_reset performs a target or LUN reset. Since the command is issued by the
user, it does not come into the driver with a tag or a queue id. Fix the
fnic driver to create an io_req and use a SCSI command tag. Fix the ITMF
path to special case the sg_reset response.

Reviewed-by: Sesidhar Baddela <email address hidden>
Reviewed-by: Arulprabhu Ponnusamy <email address hidden>
Tested-by: Karan Tilak Kumar <email address hidden>
Signed-off-by: Karan Tilak Kumar <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Martin K. Petersen <email address hidden>
(cherry picked from commit 514f0c400bde6b62405467daaf2a0a86bcf7794b)
Signed-off-by: Michael Reed <email address hidden>

608cf11... by Karan Tilak Kumar

scsi: fnic: Replace sgreset tag with max_tag_id

BugLink: https://bugs.launchpad.net/bugs/2036777

sgreset is issued with a SCSI command pointer. The device reset code
assumes that it was issued on a hardware queue, and calls block multiqueue
layer. However, the assumption is broken, and there is no hardware queue
associated with the sgreset, and this leads to a crash due to a null
pointer exception.

Fix the code to use the max_tag_id as a tag which does not overlap with the
other tags issued by mid layer.

Tested by running FC traffic for a few minutes, and by issuing sgreset on
the device in parallel. Without the fix, the crash is observed right away.
With this fix, no crash is observed.

Reviewed-by: Sesidhar Baddela <email address hidden>
Tested-by: Karan Tilak Kumar <email address hidden>
Signed-off-by: Karan Tilak Kumar <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Martin K. Petersen <email address hidden>
(backported from commit 15924b0503630016dee4dbb945a8df4df659070b)
Signed-off-by: Michael Reed <email address hidden>
[Michael Reed - corrected misaligned patch for DRV_VERSION]

92068b6... by Mac Chiang

ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic config

BugLink: https://bugs.launchpad.net/bugs/2042090

This is additional HW board: rt713+rt1316 without rt713-dmic configuration:

SDW0: rt713 audio jack
SDW1: rt1316 spk_amp_l
SDW2: rt1316 spk_amp_r

Signed-off-by: Mac Chiang <email address hidden>
Reviewed-by: Bard Liao <email address hidden>
Reviewed-by: Pierre-Louis Bossart <email address hidden>
Signed-off-by: Peter Ujfalusi <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Mark Brown <email address hidden>

(cherry picked from commit 817178e7674bd8ca35344b2212a3105ed75559e5 linux-next)
Signed-off-by: You-Sheng Yang <email address hidden>
Acked-by: Manuel Diewald <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

50b2348... by Bard Liao <email address hidden>

ASoC: Intel: sof_sdw_rt712_sdca: construct cards->components by name_prefix

BugLink: https://bugs.launchpad.net/bugs/2042090

sof_sdw_rt712_sdca is used by rt712 and rt713. Using different
cards->components string allow UCM distinguish the two codecs.

Reviewed-by: Rander Wang <email address hidden>
Signed-off-by: Bard Liao <email address hidden>
Signed-off-by: Pierre-Louis Bossart <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Mark Brown <email address hidden>

(backported from commit 5124d08d0ea49c7f4dda989827d0959e58a22150)
[vicamo: fix use of snd_soc_rtd_to_codec]
Signed-off-by: You-Sheng Yang <email address hidden>
Acked-by: Manuel Diewald <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

8675815... by Bard Liao <email address hidden>

ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713 support

BugLink: https://bugs.launchpad.net/bugs/2042090

Adding rt713 support to sof_sdw_rt_sdca_jack_common.c.

Fixes: fbaaf80d8cf6 ("ASoC: Intel: sof_sdw: add rt713 support")
Signed-off-by: Bard Liao <email address hidden>
Signed-off-by: Pierre-Louis Bossart <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Mark Brown <email address hidden>

(cherry picked from commit b6d6e5abf64562985fdbbdbdfe8088cde634d834)
Signed-off-by: You-Sheng Yang <email address hidden>
Acked-by: Manuel Diewald <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

f9e6e74... by Bard Liao <email address hidden>

ASoC: Intel: soc-acpi-intel-mtl-match: add rt713 rt1316 config

BugLink: https://bugs.launchpad.net/bugs/2042090

Adding rt713 jack + rt1316 amp + rt1713 dmic configuration support.

Reviewed-by: Rander Wang <email address hidden>
Signed-off-by: Bard Liao <email address hidden>
Signed-off-by: Pierre-Louis Bossart <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Mark Brown <email address hidden>

(cherry picked from commit e70ca580e9c8d59bc8cf70cb15546da5aecff3a0)
Signed-off-by: You-Sheng Yang <email address hidden>
Acked-by: Manuel Diewald <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

c825fec... by Juerg Haefliger

UBUNTU: [Packaging] Fix kernel module compression failures

BugLink: https://bugs.launchpad.net/bugs/2044512

The kernel module compression step is run for every binary package,
not just the modules packages. This results in a build failure when
run in a console for packages that don't contain any .ko files:

\# Compress kernel modules
find debian/linux-unstable-tools-6.6.0-12 -name '*.ko' -print0 | xargs -0 -n1 -P 8 zstd -19 --quiet --rm
stdout is a console, aborting
make: *** [debian/rules.d/2-binary-arch.mk:769: binary-perarch] Error 123

Basically, if find returns nothing, zstd tries to read from stdin:
$ echo | xargs zstd
stdout is a console, aborting
$ echo $?
123

To fix that, tell xargs not to run the command if stdin is empty:
$ echo | xargs -r zstd
$ echo $?
0

Signed-off-by: Juerg Haefliger <email address hidden>
Acked-by: Manuel Diewald <email address hidden>
Acked-by: Thibault Ferrante <email address hidden>
Acked-by: Dimitri John Ledkov <email address hidden>
Acked-by: Agathe Porte <email address hidden>
[smb: Updated to apply with ajustable(on/off) module compression]
Signed-off-by: Stefan Bader <email address hidden>

fec8193... by Dimitri John Ledkov

UBUNTU: [Packaging] make ZSTD module compression conditional

BugLink: https://bugs.launchpad.net/bugs/2045412

Make ZSTD module compression conditional. Only enable it when building
on recent series, such that backports of v6.5 kernels to jammy keep
uncompressed modules, with zstd compressed .deb.

Fixes: b2638e9702 ("UBUNTU: [Packaging] ZSTD compress modules")
Ignore: yes
Signed-off-by: Dimitri John Ledkov <email address hidden>
Acked-by: Andrea Righi <email address hidden>
Acked-by: Roxana Nicolescu <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

0c7fd02... by Stefan Binding <email address hidden>

ASoC: cs35l41: Detect CSPL errors when sending CSPL commands

BugLink: https://bugs.launchpad.net/bugs/2042060

The existing code checks for the correct state transition after sending
a command. However, it is possible for the message box to return -1,
which indicates an error, if an error has occurred in the firmware.
We can detect if the error has occurred, and return a different error.
In addition, there is no recovering from a CSPL error, so the retry
mechanism is not needed in this case, and we can return immediately.

Signed-off-by: Stefan Binding <email address hidden>
Acked-by: Mark Brown <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Takashi Iwai <email address hidden>

(cherry picked from commit 76c121821a3128eb9d0183a525cf334beb9ccc47)
Signed-off-by: Chris Chiu <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

d5c9468... by Stefan Binding <email address hidden>

ALSA: hda: cs35l41: Check CSPL state after loading firmware

BugLink: https://bugs.launchpad.net/bugs/2042060

CSPL firmware should be in RUNNING or PAUSED state after loading.
If not, the firmware has not been loaded correctly, and we can unload
it and pass the error up.

Signed-off-by: Stefan Binding <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Takashi Iwai <email address hidden>

(cherry picked from commit a51d8ba03a4fc92940d5e349f0325f36e85a89cb)
Signed-off-by: Chris Chiu <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>