summaryrefslogtreecommitdiff
path: root/net/Kconfig
diff options
context:
space:
mode:
authorAaron Sierra <asierra@xes-inc.com>2018-01-25 03:19:23 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-01-25 14:44:50 +0300
commitc7e1b4059075c9e8eed101d7cc5da43e95eb5e18 (patch)
treeada41aa888bae48f5ceb147dfb9f816d01c2fca9 /net/Kconfig
parentb027e2298bd588d6fa36ed2eda97447fb3eac078 (diff)
downloadlinux-c7e1b4059075c9e8eed101d7cc5da43e95eb5e18.tar.xz
tty: serial: exar: Relocate sleep wake-up handling
Exar sleep wake-up handling has been done on a per-channel basis by virtue of INT0 being accessible from each channel's address space. I believe this was initially done out of necessity, but now that Exar devices have their own driver, we can do things more efficiently by registering a dedicated INT0 handler at the PCI device level. I see this change providing the following benefits: 1. If more than one port is active, eliminates the redundant bus cycles for reading INT0 on every interrupt. 2. This note associated with hooking in the per-channel handler in 8250_port.c is resolved: /* Fixme: probably not the best place for this */ Cc: Matt Schulte <matts@commtech-fastcom.com> Signed-off-by: Aaron Sierra <asierra@xes-inc.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/Kconfig')
0 files changed, 0 insertions, 0 deletions