src/sys/dev/uart/uart_core.c, branch release/12.3.0FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=release%2F12.3.02020-09-08T22:50:24ZMFC 359900: Export a sysctl count of RX FIFO overrun events.2020-09-08T22:50:24ZJohn Baldwinjhb@FreeBSD.org2020-09-08T22:50:24Zurn:sha1:13ccf661f6633628bf977612b86b6b638f0b5273
uart(4) backends currently detect RX FIFO overrun errors and report
them to the uart(4) core layer. They are then reported to the generic
TTY layer which promptly ignores them. As a result, there is
currently no good way to determine if a uart is experiencing RX FIFO
overruns. One could add a generic per-tty counter, but there did not
appear to be a good way to export those. Instead, add a sysctl under
the uart(4) sysctl tree to export the count of overruns.
add snps IP uart support / genaralize UART2018-08-19T21:10:21ZMatt Macymmacy@FreeBSD.org2018-08-19T21:10:21Zurn:sha1:381388b9c48b07b08199b07b7657d46e8fcb59b0
This is an amalgam of a patch by Doug Ambrisko to
generalize uart_acpi_find_device, imp moving the
ACPI table to uart_dev_ns8250.c and advice by jhb
to work around a bug in the EPYC 3151 BIOS
(the BIOS incorrectly marks the serial ports as
disabled)
Reviewed by: imp
MFC after: 8 weeks
Differential Revision: https://reviews.freebsd.org/D16432
sys/dev: further adoption of SPDX licensing ID tags.2017-11-27T14:52:40ZPedro F. Giffunipfg@FreeBSD.org2017-11-27T14:52:40Zurn:sha1:718cf2ccb9956613756ab15d7a0e28f2c8e91cab
Mainly focus on files that use BSD 2-Clause license, however the tool I
was using misidentified many licenses so this was mostly a manual - error
prone - task.
The Software Package Data Exchange (SPDX) group provides a specification
to make it easier for automated tools to detect and summarize well known
opensource licenses. We are gradually adopting the specification, noting
that the tags are considered only advisory and do not, in any way,
superceed or replace the license texts.
Allow setting access-width for UART registers.2017-02-27T20:08:42ZRuslan Bukinbr@FreeBSD.org2017-02-27T20:08:42Zurn:sha1:c214a270f501ce3711165c0d18f55733bcc0ca93
This is required for FDT's standard "reg-io-width" property
(similar to "reg-shift" property) found in many DTS files.
This fixes operation on Altera Arria 10 SOC Development Kit,
where standard ns8250 uart allows 4-byte access only.
Reviewed by: kan, marcel
Sponsored by: DARPA, AFRL
Differential Revision: https://reviews.freebsd.org/D9785
Allow uart(4) to use MSI interrupts on single-port PCI instances.2017-01-12T16:30:27ZBruce M Simpsonbms@FreeBSD.org2017-01-12T16:30:27Zurn:sha1:fb1d9b7f4113d7aeb72a7313f05a629ad691c627
Do this here as puc(4) disallows single-port instances; at least
one multi-port PCIe UART chip (in this case, the ASIX MCS9922)
present separate PCI configuration space (functions) for each UART.
Tested using lrzsz and a null-modem cable. The ExpressCard/34
variants containing the MCS9922 should also use MSI with this change.
Reviewed by: jhb, imp, rpokala
MFC after: 2 weeks
Differential Revision: https://reviews.freebsd.org/D9123
Do not reallocate driver softc for uart unnecessarily.2016-11-17T16:06:53ZRuslan Bukinbr@FreeBSD.org2016-11-17T16:06:53Zurn:sha1:5515b0cb39fae7d2951b779b64a7e56823ac44c2
Do not assume that all uart drivers use uart_softc structure as is.
Some do a sensible thing and do declare their uart class and driver
properly and arrive into uart_bus_attach with suitably sized softc.
Submitted by: kan
Sponsored by: DARPA, AFRL
Fix UART PPS capture mode printing2016-08-28T04:40:27ZJustin Hibbitsjhibbits@FreeBSD.org2016-08-28T04:40:27Zurn:sha1:7bd8311dec8365f15c103e17aa236f7ccffb6161
* Add breaks to prevent fallthrough and printing of multiple modes.
* Only check the mode, mask out all other bits.
Restore uart PPS signal capture polarity to its historical norm, and add an2016-01-12T18:42:00ZIan Leporeian@FreeBSD.org2016-01-12T18:42:00Zurn:sha1:fdfbb3f5b1b6199051e3421609c783b216cef6e5
option to invert the polarity in software. Also add an option to capture
very narrow pulses by using the hardware's MSR delta-bit capability of
latching line state changes.
This effectively reverts the mistake I made in r286595 which was based on
empirical measurements made on hardware using TTL-level signaling, in which
the logic levels are inverted from RS-232. Thus, this re-syncs the polarity
with the requirements of RFC 2783, which is writen in terms of RS-232
signaling.
Narrow-pulse mode uses the ability of most ns8250 and similar chips to
provide a delta indication in the modem status register. The hardware is
able to notice and latch the change when the pulse width is shorter than
interrupt latency, which results in the signal no longer being asserted by
time the interrupt service code runs. When running in this mode we get
notified only that "a pulse happened" so the driver synthesizes both an
ASSERT and a CLEAR event (with the same timestamp for each). When the pulse
width is about equal to the interrupt latency the driver may intermittantly
see both edges of the pulse. To prevent generating spurious events, the
driver implements a half-second lockout period after generating an event
before it will generate another.
Differential Revision: https://reviews.freebsd.org/D4477
Use bus_alloc_resource_any(), rather than bus_alloc_resource()2015-08-12T04:03:04ZMarcel Moolenaarmarcel@FreeBSD.org2015-08-12T04:03:04Zurn:sha1:9def69ec5fdce709902ea961222af87b4934533c
with start 0 and end ~0. This avoids confusion WRT to what the
value of length can or should be.
Style fix, no functional changes -- do the braces for switches correctly.2015-08-11T02:30:54ZIan Leporeian@FreeBSD.org2015-08-11T02:30:54Zurn:sha1:dc4aaf6dd1d30f0c77bbca468827a4f54ec1a238