I don't know if changing the device after a kernel suspend/resume could be a kernel bug. Basically, I don't think the kernel guarantees much more than that device names should be unique(?)
The proper solution to handle situation is to install a udev rule which sets up a stable device name for the device. This should certainly work also after suspend resume.
Anyway, this is not a lirc bug and this issue should IMHO be closed (or possibly re-assigned to the kernel if there is some guarantee that device names should be stable during suspend/resume).
I don't know if changing the device after a kernel suspend/resume could be a kernel bug. Basically, I don't think the kernel guarantees much more than that device names should be unique(?)
The proper solution to handle situation is to install a udev rule which sets up a stable device name for the device. This should certainly work also after suspend resume.
Anyway, this is not a lirc bug and this issue should IMHO be closed (or possibly re-assigned to the kernel if there is some guarantee that device names should be stable during suspend/resume).