> echo icn8528 0x48 > /sys/bus/i2c/devices/i2c-4/newdevice
> After this kernel automatically loads myicn_ts_acpi.ko module.
>
> ...
>
> gsl_ts_probe: got a device named icn8528 at address 0x48, IRQ 0, flags
> 0x0
> Mar 02 12:07:31 archiso kernel: icn8528 4-0048: gsl_ts_probe: missing
> IRQ configuration
> Mar 02 12:07:31 archiso kernel: icn8528: probe of 4-0048 rejects match -19
>
> So, based on main line output: archiso kernel: CHPN0001 4-0048: probe
> info: gsl_ts_probe: got a device named CHPN0001 at address 0x48, IRQ
> 0, flags 0x0
>
> It looks that via ACPI no info is provided? No IRQ, no flags?
Umm... Ok, this seems a bit weird. Normally, you wouldn't create devices from
user space, as the kernel should automatically instantiate them when parsing
the DSDT or DT.
However, you got an ACPI name (CHPN0001), which leads me to conclude that some
interaction was going on.
Ok, now about the interrupt. The DSDT you posted previously contained this:
Interrupt (ResourceConsumer, Level, ActiveHigh, Exclusive, ,, )
{
0x00000044,
}
So the irq field should have been set. I don't really understand why this
wasn't the case, sorry.
I recommend you try to load the module without creating a device from user
space first. Either install the module and reboot or load the module manually.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
