summaryrefslogtreecommitdiffstats
path: root/drivers/usb/serial/safe_serial.c
diff options
context:
space:
mode:
authorAlexander Shishkin <alexander.shishkin@linux.intel.com>2012-05-04 16:47:16 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-05-08 09:27:57 -0700
commitf9df8395c7f9b1b8d0ea9221595a97f2f4720359 (patch)
treed8fea00b1dd8194e091380537b99e92bbbf59486 /drivers/usb/serial/safe_serial.c
parentd36ade60e3cc212992f001d2046815b068073c0c (diff)
downloadlinux-f9df8395c7f9b1b8d0ea9221595a97f2f4720359.tar.gz
linux-f9df8395c7f9b1b8d0ea9221595a97f2f4720359.tar.bz2
linux-f9df8395c7f9b1b8d0ea9221595a97f2f4720359.zip
usb: gadget: ci13xxx: rename register layouts
Currently, the register prefixes in the driver seem to be mixed: the capability registers are the ones that contain capability information, such as number of hardware endpoints, while the registers that are used to program the controller are called operational registers. Normally, capability registers start at 0x100 offset of the register window and are followed by operational registers. In some versions, however, capability registers start at 0x0 offset. This patch renames the register and adjusts their offsets appropriately, leaving the possibility of having a non-standard capability offset. I couldn't find any mentions of the TESTMODE register anywhere, so I suspect it might only be enabled in chipidea internal versions of the controller and I'm really inclined to remove it from the driver or at least hiding it behind a config option. Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/usb/serial/safe_serial.c')
0 files changed, 0 insertions, 0 deletions