1. 27 3月, 2015 3 次提交
  2. 07 3月, 2015 5 次提交
  3. 03 2月, 2015 1 次提交
  4. 10 1月, 2015 1 次提交
  5. 26 11月, 2014 1 次提交
  6. 07 11月, 2014 3 次提交
    • S
      parport: Add support for the WCH382 2S/1P multi-IO card · 2fdd8c8c
      Sergej Pupykin 提交于
      WCH382 is a PCI-E card with 1 LPT and 2 DB9 COM ports detected as
      Serial controller: Device 1c00:3250 (rev 10) (prog-if 05 [16850])
      Signed-off-by: NSergej Pupykin <ml@sergej.pp.ru>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      2fdd8c8c
    • A
      serial: 8250_pci: Check mapping in pci_ni8430_init · 5d14bba9
      Aaron Sierra 提交于
      Check the return value of ioremap_nocache to make sure we got a
      valid mapping.
      Signed-off-by: NAaron Sierra <asierra@xes-inc.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      5d14bba9
    • A
      serial: 8250_pci: Handle devices mapped above 4 GiB · 398a9db6
      Aaron Sierra 提交于
      Several init/setup functions passed the PCI BAR resource start address
      to ioremap_nocache() via an unsigned long. This caused address truncation
      for a 32-bit device mapped above 4 GiB (i.e. the CPU interacts with the
      device via a translated address), which resulted in a kernel panic.
      
      This patch replaces all of the instances of intermediate variable use
      with pci_ioremap_bar() to ensure the full resource_size_t start address
      is used and that ioremap_nocache() is still called.
      
      The kernel panic (Exar XR17V358 PCIe device on a Freescale P2020 SBC):
      
      Machine check in kernel mode.
      Caused by (from MCSR=10008): Bus - Read Data Bus Error
      Oops: Machine check, sig: 7 [#1]
      SMP NR_CPUS=2 X-ES P2020
      Modules linked in:
      CPU: 1 PID: 1 Comm: swapper/0 Not tainted 3.14.15-xes_r2-00002-g560e401 #978
      task: bf850000 ti: bffee000 task.ti: bf84c000
      NIP: 80318e10 LR: 80319ecc CTR: 80318dfc
      REGS: bffeff10 TRAP: 0204   Not tainted  (3.14.15-xes_r2-00002-g560e401)
      MSR: 00021000 <CE,ME>  CR: 20adbe42  XER: 00000000
      DEAR: c1058001 ESR: 00000000
      GPR00: 00000000 bf84db30 bf850000 80cb4af8 00000001 00000000 80000007 80000000
      GPR08: bf837c9c c1058001 00000001 00000000 80000007 00000000 80002a10 00000000
      GPR16: 00000000 00000000 00000000 00000000 00000000 00000000 80cb0000 80c72dc4
      GPR24: 80cb4900 fffffffe 00029000 00000001 bf8c11e8 ffffffea 80c72ce4 80cb4af8
      NIP [80318e10] mem_serial_in+0x14/0x28
      LR [80319ecc] serial8250_config_port+0x160/0xe38
      Call Trace:
      [bf84db30] [80319d94] serial8250_config_port+0x28/0xe38 (unreliable)
      [bf84db60] [80315e3c] uart_add_one_port+0x148/0x3a4
      [bf84dbf0] [8031bf40] serial8250_register_8250_port+0x2dc/0x3c8
      [bf84dc20] [8032111c] pciserial_init_ports+0xd4/0x1c0
      [bf84dd50] [803212f8] pciserial_init_one+0xf0/0x224
      [bf84dd90] [802d8ff4] local_pci_probe+0x34/0x8c
      [bf84dda0] [802d92c8] pci_device_probe+0x84/0xa0
      [bf84ddc0] [80329ee0] driver_probe_device+0xac/0x26c
      [bf84dde0] [8032a15c] __driver_attach+0xbc/0xc0
      [bf84de00] [80328388] bus_for_each_dev+0x90/0xcc
      [bf84de30] [80329cd0] driver_attach+0x24/0x34
      [bf84de40] [80328e28] bus_add_driver+0x104/0x1fc
      [bf84de60] [8032a8c8] driver_register+0x70/0x138
      [bf84de70] [802d93c0] __pci_register_driver+0x48/0x58
      [bf84de80] [8077e0e4] serial_pci_driver_init+0x24/0x34
      [bf84de90] [80002228] do_one_initcall+0x34/0x1b0
      [bf84df00] [80764294] kernel_init_freeable+0x138/0x1e8
      [bf84df30] [80002a24] kernel_init+0x14/0x108
      [bf84df40] [8000ef94] ret_from_kernel_thread+0x5c/0x64
      Instruction dump:
      800800c4 7d290214 39290001 7c0004ac 7ca049ae 7c0004ac 4e800020 88030035
      81230008 7c840030 7d292214 7c0004ac <88690000> 0c030000 4c00012c 5463063e
      ---[ end trace e3c16443b5d573c6 ]---
      Signed-off-by: NAaron Sierra <asierra@xes-inc.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      398a9db6
  7. 06 11月, 2014 1 次提交
  8. 29 9月, 2014 2 次提交
  9. 11 9月, 2014 2 次提交
  10. 18 7月, 2014 1 次提交
  11. 29 5月, 2014 2 次提交
  12. 09 3月, 2014 2 次提交
  13. 14 2月, 2014 1 次提交
    • D
      serial: 8250_pci: unbreak last serial ports on NetMos 9865 cards · 333c085e
      Dmitry Eremin-Solenikov 提交于
      Aparently 9865 uses standard BAR encoding scheme (unlike 99xx cards).
      Current pci_netmos_9900_setup() uses wrong BAR indices for the 9865 PCI
      device, function 2. Using standard BAR indices makes all 6 ports work
      for me. Thus disable the NetMos 9900 quirk for NetMos 9865 pci device.
      
      For the reference, here is the relevant part of lspci for my device:
      
      02:07.0 Serial controller: MosChip Semiconductor Technology Ltd. PCI
      9865 Multi-I/O Controller (prog-if 02 [16550])
      	Subsystem: Device a000:1000
      	Flags: bus master, medium devsel, latency 32, IRQ 17
      	I/O ports at ac00 [size=8]
      	Memory at fcfff000 (32-bit, non-prefetchable) [size=4K]
      	Memory at fcffe000 (32-bit, non-prefetchable) [size=4K]
      	Capabilities: [48] Power Management version 2
      	Kernel driver in use: serial
      
      02:07.1 Serial controller: MosChip Semiconductor Technology Ltd. PCI
      9865 Multi-I/O Controller (prog-if 02 [16550])
      	Subsystem: Device a000:1000
      	Flags: bus master, medium devsel, latency 32, IRQ 18
      	I/O ports at a800 [size=8]
      	Memory at fcffd000 (32-bit, non-prefetchable) [size=4K]
      	Memory at fcffc000 (32-bit, non-prefetchable) [size=4K]
      	Capabilities: [48] Power Management version 2
      	Kernel driver in use: serial
      
      02:07.2 Communication controller: MosChip Semiconductor Technology Ltd.
      PCI 9865 Multi-I/O Controller
      	Subsystem: Device a000:3004
      	Flags: bus master, medium devsel, latency 32, IRQ 19
      	I/O ports at a400 [size=8]
      	I/O ports at a000 [size=8]
      	I/O ports at 9c00 [size=8]
      	I/O ports at 9800 [size=8]
      	Memory at fcffb000 (32-bit, non-prefetchable) [size=4K]
      	Capabilities: [48] Power Management version 2
      	Kernel driver in use: serial
      Signed-off-by: NDmitry Eremin-Solenikov <dbaryshkov@gmail.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      333c085e
  14. 08 1月, 2014 1 次提交
  15. 20 12月, 2013 2 次提交
  16. 09 12月, 2013 1 次提交
  17. 20 10月, 2013 1 次提交
  18. 18 10月, 2013 1 次提交
  19. 01 10月, 2013 1 次提交
  20. 28 9月, 2013 1 次提交
  21. 27 9月, 2013 1 次提交
  22. 27 7月, 2013 3 次提交
  23. 01 7月, 2013 1 次提交
  24. 16 3月, 2013 1 次提交
    • W
      serial: 8250_pci: Add WCH CH352 quirk to avoid Xscale detection · 8b5c913f
      Wang YanQing 提交于
      The code in 8250.c for detecting ARM/XScale UARTs says:
      
        * Try writing and reading the UART_IER_UUE bit (b6).
        * If it works, this is probably one of the Xscale platform's
        * internal UARTs.
      
      If the above passes, it then goes on to:
      
           * It's an Xscale.
           * We'll leave the UART_IER_UUE bit set to 1 (enabled).
      
      However, the CH352 uses the UART_IER_UUE as the LOWPOWER function,
      so it is readable and writable.  According to the datasheet:
      
          "LOWPOWER:When the bit is 1, close the internal benchmark
           clock of serial port to set into low-power status.
      
      So it essentially gets mis-detected as Xscale, and gets
      powered down in the process.  The device in question where
      this was seen is listed by lspci as:
      
       Serial controller: Device 4348:3253 (rev 10) (prog-if 02 [16550])
      
      Re-using the 353 quirk which just sets flags to fixed and type
      to 16550 is suitable for fixing the 352 as well.
      Signed-off-by: NWang YanQing <udknight@gmail.com>
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      8b5c913f
  25. 12 3月, 2013 1 次提交