Message-ID: <aa4c40ff1003082115x3e9e1492je90e5afb826b3408@mail.gmail.com>
Date:	Mon, 8 Mar 2010 21:15:26 -0800
From:	James Lamanna <jlamanna@...il.com>
To:	Robert Hancock <hancockrwd@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: SIIG DP CyberSerial 4S PCIe Support

On Mon, Mar 8, 2010 at 6:19 PM, Robert Hancock <hancockrwd@...il.com> wrote:
> On 03/08/2010 03:13 PM, James Lamanna wrote:
>>
>> On Mon, Mar 8, 2010 at 11:07 AM, James Lamanna<jlamanna@...il.com>  wrote:
>>>
>>> Hi,
>>> I recently purchased a SIIG DP CyberSerial 4S PCIe card, however the
>>> kernel doesn't seem to recognize it.
>>> There are no messages in dmesg or anything about it.
>>> Currently I'm at 2.6.24, but looking at drivers/serial/8250_pci.c
>>> between 2.6.24 and 2.6.32 there doesn't
>>> seem to be real changes with SIIG cards.
>>> Seems like other SIIG cards are supported, so are we just missing the
>>> PCI IDs for this card?
>>>
>>> Here's the lspci -nnvvvvvv output:
>>>
>>> 01:00.0 Serial controller [0700]: Oxford Semiconductor Ltd Unknown
>>> device [1415:c208] (prog-if 06 [16950])
>>>        Subsystem: Siig Inc Unknown device [131f:2250]
>>>        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
>>> ParErr- Stepping- SERR- FastB2B-
>>>        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast>TAbort-
>>> <TAbort-<MAbort->SERR-<PERR-
>>>        Interrupt: pin A routed to IRQ 16
>>>        Region 0: Memory at fe8fc000 (32-bit, non-prefetchable) [size=16K]
>>>        Region 1: Memory at fe600000 (32-bit, non-prefetchable) [size=2M]
>>>        Region 2: Memory at fe400000 (32-bit, non-prefetchable) [size=2M]
>>>        Capabilities: [40] Power Management version 3
>>>                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=55mA
>>> PME(D0-,D1+,D2+,D3hot+,D3cold+)
>>>                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>>>        Capabilities: [70] Express Endpoint IRQ 0
>>>                Device: Supported: MaxPayload 128 bytes, PhantFunc 0,
>>> ExtTag-
>>>                Device: Latency L0s<128ns, L1<2us
>>>                Device: AtnBtn- AtnInd- PwrInd-
>>>                Device: Errors: Correctable- Non-Fatal+ Fatal+
>>> Unsupported-
>>>                Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
>>>                Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
>>>                Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port
>>> 0
>>>                Link: Latency L0s<512ns, L1<64us
>>>                Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
>>>                Link: Speed 2.5Gb/s, Width x1
>>>        Capabilities: [b0] MSI-X: Enable- Mask- TabSize=16
>>>                Vector table: BAR=1 offset=001b3000
>>>                PBA: BAR=1 offset=001b2000
>>
>> After some more digging I found these messages in dmesg which doesn't
>> exactly sound good:
>>
>> [   52.104180] ACPI: PCI Interrupt 0000:01:00.0[A] ->  GSI 16 (level,
>> low) ->  IRQ 16
>> [   52.104189] ACPI: PCI interrupt for device 0000:01:00.0 disabled
>>
>> 01:00.0 is the device ID of the SIIG card.
>> Any reason ACPI would disable interrupts for this card?
>
> Probably just means some driver temporarily decided to enable the interrupt,
> then disabled it (maybe because it decided it couldn't run the device?)

That's probably the case.
It looks like 8250 doesn't know about this PCIe device at all.
The Oxford PCI ID is not in pci_ids.h nor is the SIIG subsystem ID.
I'll see if I can maybe work up a patch to support this device, since I've found
the datasheet for the Oxford 4 port UART controller, but I may need some help.
Or if anyone else (who has more experience with this) wants to formulate one,
it would be greatly appreciated.

-- James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists