Unknown Tuples from SDIO mmc device

From: Christian Hewitt
Date: Fri Feb 10 2023 - 05:13:00 EST


Hello folks, I see this in dmesg from the SDIO mmc device on an Amlogic S905D
based set-top box (running Linux 6.1.11):

SML5442TW:~ # dmesg | grep mmc
[ 0.367575] meson-gx-mmc d0072000.mmc: Got CD GPIO
[ 0.367728] meson-gx-mmc d0074000.mmc: allocated mmc-pwrseq
[ 0.438107] mmc0: new high speed SDHC card at address aaaa
[ 0.439663] mmcblk0: mmc0:aaaa SL16G 14.8 GiB
[ 0.445720] mmcblk0: p1 p2
[ 0.463812] mmc1: new HS200 MMC card at address 0001
[ 0.465304] mmcblk1: mmc1:0001 8GME4R 7.28 GiB
[ 0.470109] mmcblk1boot0: mmc1:0001 8GME4R 4.00 MiB
[ 0.473747] mmcblk1boot1: mmc1:0001 8GME4R 4.00 MiB
[ 0.477168] mmcblk1rpmb: mmc1:0001 8GME4R 512 KiB, chardev (242:0)
[ 1.253756] meson-gx-mmc d0070000.mmc: allocated mmc-pwrseq
[ 1.331767] mmc2: queuing unknown CIS tuple 0x01 [d9 01 ff] (3 bytes)
[ 1.341857] mmc2: queuing unknown CIS tuple 0x1a [01 01 00 02 07] (5 bytes)
[ 1.346197] mmc2: queuing unknown CIS tuple 0x1b [c1 41 30 30 ff ff 32 00] (8 bytes)
[ 1.347097] mmc2: queuing unknown CIS tuple 0x14 [] (0 bytes)
[ 1.351373] mmc2: new ultra high speed SDR104 SDIO card at address 0001
[ 2.170379] fsck: /dev/mmcblk0p1: 174 files, 16383/65501 clusters
[ 3.042438] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: disabled.
[ 11.897414] ath10k_sdio mmc2:0001:1: qca9377 hw1.1 sdio target 0x05020001 chip_id 0x00000000 sub 0000:0000
[ 11.897451] ath10k_sdio mmc2:0001:1: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
[ 11.897992] ath10k_sdio mmc2:0001:1: firmware ver WLAN.TF.1.1.1-00061-QCATFSWPZ-1 api 5 features ignore-otp crc32 7746e551
[ 12.115387] ath10k_sdio mmc2:0001:1: failed to fetch board data for bus=sdio,vendor=0271,device=0701,subsystem-vendor=0000,subsystem-device=0000 from ath10k/QCA9377/hw1.0/board-2.bin
[ 12.125611] ath10k_sdio mmc2:0001:1: board_file api 1 bmi_id N/A crc32 544289f7
[ 13.399691] meson-gx-mmc d0070000.mmc: unaligned sg offset 1100, disabling descriptor DMA for transfer
[ 13.449279] ath10k_sdio mmc2:0001:1: htt-ver 3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 13.533081] mmc2: queuing unknown CIS tuple 0x01 [d9 01 ff] (3 bytes)
[ 13.543521] mmc2: queuing unknown CIS tuple 0x1a [01 01 00 02 07] (5 bytes)
[ 13.548428] mmc2: queuing unknown CIS tuple 0x1b [c1 41 30 30 ff ff 32 00] (8 bytes)
[ 13.549378] mmc2: queuing unknown CIS tuple 0x14 [] (0 bytes)

I’m not a coding developer (only light device-tree hacking) so I can’t quite
follow the code in drivers/mmc/core/sdio_cis.c

What’s needed to make the unknown tuple(s) known?

Christian