[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <007001ce55c4$139f96e0$3adec4a0$@lge.com>
Date: Tue, 21 May 2013 10:39:46 +0900
From: "Jongsung Kim" <neidhard.kim@....com>
To: "'Stephen Warren'" <swarren@...dotorg.org>
Cc: "'Russell King'" <linux@....linux.org.uk>,
"'Greg Kroah-Hartman'" <gregkh@...uxfoundation.org>,
<jslaby@...e.cz>, <linux-serial@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
<linux-rpi-kernel@...ts.infradead.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: RE: [PATCH] ARM: PL011: add support for extended FIFO-size of PL011-r1p5
Jongsung Kim <neidhard.kim@....com> :
> Stephen Warren <swarren@...dotorg.org> :
>>> All r1p5 have 32-byte FIFO depth and it's not configurable. From the
>>> PL011
>>> TRM:
>>>
>>> r1p4-r1p5 Contains the following differences in functionality:
>>> * The receive and transmit FIFOs are increased to a depth of
32.
>>> * The Revision field in the UARTPeriphID2 Register on page
3-24
>>> bits [7:4] now reads back as 0x3.
>>
>> Well, that certainly isn't true in practice. I think we should revert
>> this commit until we can determine what the problem is.
>
> I asked to the ARM support about this. Waiting for reply..
ARM support said they doesn't have information about BCM2835 UART. Does
anyone have a communication channel to Broadcom? It takes time for me to
get contact point to Broadcom.. (I'm trying)
However, ARM support also said:
"If the Broadcom part definitely has 16-deep FIFOs, it cannot be based
on a PL011 r1p5, so I might guess that Broadcom have just referenced
the latest version of the documentation on our website, but have actually
implemented an earlier version."
--
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