FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F13.2.0 2023-01-20T03:21:16Z 2023-01-20T03:21:16Z Konstantin Belousov kib@FreeBSD.org 2022-12-02T01:26:13Z urn:sha1:1610f04c9daceb5b4f2849e48d0021ecc975bb60 Tested by: pho (cherry picked from commit 6403a140243d4f5377f589f93aeb44fe75ea8d59) 2022-12-29T17:02:37Z Rene Ladan rene@FreeBSD.org 2022-12-21T21:24:11Z urn:sha1:534470090d987118b9728deda1b28f96ae5d1cec The pin-mode (ft, pd, pu for floating, pull-down, pull-up) is specified after the intr-config (no, eb, ef, er) for each pin. Tested on my Raspberry Pi 1B. PR: 268504 Approved by: manu MFC after: 1 week (cherry picked from commit 453db42291a3179a51b9bf41ca7dbc0a5298bffa) gpioevents: fix some white-space errors Fixes: 453db42291a3 - gpioevents: add support for pull-down and floating input pins. Approved by: manu (implicit) MFC after: 1 week (cherry picked from commit e2f3742ab8b10ba5ec4dc190c5b64e9151bb0d57) 2022-09-18T06:26:39Z Kyle Evans kevans@FreeBSD.org 2022-01-11T23:41:10Z urn:sha1:540ecebdd01b1a094cdcdef30e4b6cbd87aa3403 Record error condition when iconv_open() fails rather than leaving a bogus iconv_t that iconv_close() can later choke on; this is one failure mode. If we opened MAX_LIMIT files with success, we need to rewind one so that we don't iconv_close() one past the end of cd; this is the second failure mode. Sponsored by: Klara, Inc. (cherry picked from commit 814bd1ed438f7dfc5bedcb1f3e772a46fe7026bb) 2021-10-07T21:41:47Z Alan Somers asomers@FreeBSD.org 2021-09-14T20:50:01Z urn:sha1:ce10852cb3a03a1233cff0a54b2d1c67d16d1ee6 Sponsored by: Axcient (cherry picked from commit 5dc5f849be9047309d32c4df8e7ee617c27ec43f) 2021-09-19T11:18:12Z Konstantin Belousov kib@FreeBSD.org 2021-09-16T17:23:11Z urn:sha1:9eb77afb4df14160426319582e101c5b9c1f8dfb (cherry picked from commit 9a8eb5db55964c2fc7aca0db5939d8300badc9ab) 2020-12-12T18:34:15Z Ian Lepore ian@FreeBSD.org 2020-12-12T18:34:15Z urn:sha1:ff3468ac94597efdcbc56f372528dfc98b114dac This is an import of the Google Summer of Code 2018 project completed by Christian Kramer (and, sadly, ignored by us for two years now). The goals stated for that project were: FreeBSD already has support for interrupts implemented in the GPIO controller drivers of several SoCs, but there are no interfaces to take advantage of them out of user space yet. The goal of this work is to implement such an interface by providing descriptors which integrate with the common I/O system calls and multiplexing mechanisms. The initial imported code supports the following functionality: - A kernel driver that provides an interface to the user space; the existing gpioc(4) driver was enhanced with this functionality. - Implement support for the most common I/O system calls / multiplexing mechanisms: - read() Places the pin number on which the interrupt occurred in the buffer. Blocking and non-blocking behaviour supported. - poll()/select() - kqueue() - signal driven I/O. Posting SIGIO when the O_ASYNC was set. - Many-to-many relationship between pins and file descriptors. - A file descriptor can monitor several GPIO pins. - A GPIO pin can be monitored by multiple file descriptors. - Integration with gpioctl and libgpio. I added some fixes (mostly to locking) and feature enhancements on top of the original gsoc code. The feature ehancements allow the user to choose between detailed and summary event reporting. Detailed reporting provides a record describing each pin change event. Summary reporting provides the time of the first and last change of each pin, and a count of how many times it changed state since the last read(2) call. Another enhancement allows the recording of multiple state change events on multiple pins between each call to read(2) (the original code would track only a single event at a time). The phabricator review for these changes timed out without approval, but I cite it below anyway, because the review contains a series of diffs that show how I evolved the code from its original state in Christian's github repo for the gsoc project to what is being commited here. (In effect, the phab review extends the VC history back to the original code.) Submitted by: Christian Kramer Obtained from: https://github.com/ckraemer/freebsd/tree/gsoc2018 Differential Revision: https://reviews.freebsd.org/D27398 2020-10-01T01:10:51Z Kyle Evans kevans@FreeBSD.org 2020-10-01T01:10:51Z urn:sha1:7cc42f6d25ef2e19059d088fa7d4853fe9afefb5 Repeating the default WARNS here makes it slightly more difficult to experiment with default WARNS changes, e.g. if we did something absolutely bananas and introduced a WARNS=7 and wanted to try lifting the default to that. Drop most of them; there is one in the blake2 kernel module, but I suspect it should be dropped -- the default WARNS in the rest of the build doesn't currently apply to kernel modules, and I haven't put too much thought into whether it makes sense to make it so. 2020-04-01T15:39:02Z Hartmut Brandt harti@FreeBSD.org 2020-04-01T15:39:02Z urn:sha1:a82d25d731de24e53839cf4eec084023b70b54b8 This is not automatically built or run but must explicitly be built with 'make' and run with 'make run'. 2020-02-27T04:44:58Z Warner Losh imp@FreeBSD.org 2020-02-27T04:44:58Z urn:sha1:f33b14f02ef7c5aff623734b1a24abe0567ff51d Submitted by: kib@ (libthr) 2019-07-03T19:22:44Z Eric van Gyzen vangyzen@FreeBSD.org 2019-07-03T19:22:44Z urn:sha1:8c5a9161d16094d9db474fe78ddead1325246d05 Save the last callout function pointer (and its argument) executed on each CPU for inspection by a debugger. Add a ddb `show callout_last` command to show these pointers. Add a kernel module that I used for testing that command. Relocate `ce_migration_cpu` to reduce padding and therefore preserve the size of `struct callout_cpu` (320 bytes on amd64) despite the added members. This should help diagnose reference-after-free bugs where the callout's mutex has already been freed when `softclock_call_cc` tries to unlock it. You might hope that the pointer would still be available, but it isn't. The argument to that function is on the stack (because `softclock_call_cc` uses it later), and that might be enough in some cases, but even then, it's very laborious. A pointer to the callout is saved right before these newly added fields, but that callout might have been freed. We still have the pointer to its associated mutex, and the name within might be enough, but it might also have been freed. Reviewed by: markj jhb MFC after: 2 weeks Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D20794