> Date: Tue, 4 Oct 2022 07:56:22 +0200 > From: Matthias Schmidt <[email protected]> > > Hi Mark, > > * Mark Kettenis wrote: > > The diff below adds the hooks to disable and enable GPIO interrupts > > for amdgpio(4), aplgpio(4), bytgpio(4), chvgpio(4), glkgpio(4) and > > pchgpio(4). This is similar to what I did for qcgpio(4) a few weeks > > ago. This should fix potential interrupt storms related to > > level-triggered interrupts. > > > > I can't really test this myself. But if you have a machine with a > > line like this: > > > > ihidev0 at iic7 addr 0x2c gpio 18, vendor 0x6cb product 0x8253, SYNA2B43 > > I have a Tuxedo Infinitbook with the following: > > ihidev0 at iic1 addr 0x2c gpio 327, vendor 0x93a product 0x255, UNIW0001 > > > that contains the string "gpio", please give this a shot and check > > whether your keyboard and touchpad still work with it and report back > > with a fullk dmesg. > > I can confirm that both devices still work as expected. However, the > spdmem device is "gone". Here's a diff between dmesg before and after
That is strange; I don't really see how this would happen. > ichiic0 at pci0 dev 31 function 4 "Intel 500 Series SMBus" rev 0x20: apic 2 > int 16 > iic2 at ichiic0 > ... > -spdmem0 at iic2 addr 0x52: 32GB DDR4 SDRAM PC4-25600 SO-DIMM > +"eeprom" at iic2 addr 0x52 not configured So an EEPROM of some sort is still detected; it just isn't detected as an SPD EEPROM anymore. Have you seen this happening before? Is there a difference between a cold and a warm boot?
