Monorepo for Aesthetic.Computer
aesthetic.computer
native: dump all ACPI INT* HIDs to find G7's pinctrl device name
+30
+30
fedac/native/initramfs/init
+30
fedac/native/initramfs/init
···
208
208
;;
209
209
esac
210
210
done
211
+
# All INT* HIDs — need to know what pinctrl device (INT34C8 for JSL, INT34C5
212
+
# for ICL, INT3450-INT3456 for other Intel platforms) is actually declared
213
+
# on this firmware. Absence of any of these is the reason the Jasper Lake
214
+
# pinctrl driver sits idle: the driver is linked and module_init ran, but
215
+
# acpi_driver_match never fires without a matching device on the ACPI bus.
216
+
echo "ACPI Intel HIDs (INT*):" >> $LOG
217
+
for d in /sys/bus/acpi/devices/*; do
218
+
[ -d "$d" ] || continue
219
+
hid=$(cat "$d/hid" 2>/dev/null)
220
+
case "$hid" in
221
+
INT*)
222
+
drv=$(basename "$(readlink "$d/physical_node/driver" 2>/dev/null)" 2>/dev/null)
223
+
echo " $hid drv=${drv:-NONE}" >> $LOG
224
+
;;
225
+
esac
226
+
done
227
+
# PNP + ACPI devices with the names coreboot uses for pinctrl on various
228
+
# Intel platforms. Helps us find whether the board's DSDT simply uses a
229
+
# different HID than upstream Linux expects.
230
+
echo "ACPI pinctrl candidates:" >> $LOG
231
+
for d in /sys/bus/acpi/devices/*; do
232
+
[ -d "$d" ] || continue
233
+
hid=$(cat "$d/hid" 2>/dev/null)
234
+
name=$(basename "$d")
235
+
case "$hid:$name" in
236
+
INT34*|*GPI*|*GPIO*|PNP0C*)
237
+
echo " $hid $name" >> $LOG
238
+
;;
239
+
esac
240
+
done
211
241
echo "SOF platform devices:" >> $LOG
212
242
ls /sys/bus/platform/devices/ 2>/dev/null | grep -iE "sof|jsl_rt5682|cs42l42|hda" >> $LOG
213
243
echo "Platform drivers (audio-related):" >> $LOG