On a notebook I ran into an issue with the touchpad "hanging" and eating loads
of
resources:

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
  909 root     -51   0       0      0      0 D 14.89 0.000   1:15.58
irq/51-SYNA2B29
  631 root      20   0   12056   5120   1572 S 2.128 0.031   0:07.23 haveged
  841 root     -51   0       0      0      0 D 0.709 0.000   3:43.81
irq/87-ITE8396:
 1939 gp        20   0  709120 147156 120792 S 0.709 0.901   3:36.15 X
 2642 gp        20   0  639044  46020  31036 S 0.709 0.282   0:45.56
gnome-terminal-

This report is NOT about that per se, but rather the fact that i2c issues error 
messages into the log at a crazy rate:

08:29:32 ghazala kernel: i2c_hid i2c-ITE8396:00: failed to set a report to
device. 
08:29:32 ghazala kernel: i2c_designware i2c_designware.0: timeout waiting for
bus ready 
08:29:32 ghazala kernel: i2c_designware i2c_designware.0: timeout waiting for
bus ready 
08:29:32 ghazala kernel: i2c_hid i2c-ITE8396:00: failed to set a report to
device. 
08:29:32 ghazala kernel: i2c_designware i2c_designware.0: timeout waiting for
bus ready 
08:29:32 ghazala kernel: i2c_designware i2c_designware.0: timeout waiting for
bus ready 
08:29:32 ghazala kernel: i2c_hid i2c-ITE8396:00: failed to retrieve report from
device. 
08:29:32 ghazala kernel: i2c_designware i2c_designware.0: t^C

# journalctl --since today | grep 'i2c.*timeout' | wc -l
333455
# journalctl --since today | grep 'i2c.*timeout' | uniq | wc -l
8232

That is, 40 identical errors are logged.  Per second.  "Forever" (until I shut
down the system).

At a minimum, can this be rate limited (to no more than one per second, or
better every 5-10 seconds)?