wireguard-openbsd - WireGuard implementation for the OpenBSD kernel

	Commit message (Collapse)	Author	Age	Files	Lines
*	Even when polling is requested, install ihidev's interrupt handler	jcs	2019-07-22	1	-1/+2
\| \| \| \| \| \| \| \|	If an interrupt is received, turn off polling and rely on interrupts. This may happen after S3 resume. Also properly shut down polling during suspend and start it up again on resume only after dwiic is back in action.
*	Print a meaningful interrupt string for i2c devices.	kettenis	2016-04-23	1	-1/+4
\|
*	Fix layer violation in the ihidev(4) code by implementing a generic mechanism	kettenis	2016-04-10	1	-4/+9
\| \| \| \| \| \| \| \| \| \|	that allows the i2c controller implementation to establish interrupts on behalf of i2c slave device drivers. Use this mechanism in dwiic(4) to let it configure the right acpi interrupt (global or gpio). Change the level to IPL_TTY as this is the appropriate level to use for keyboards and other input devices. ok jsg@
*	Add support for I2C HID devices with GPIO signalled interrupts.	jsg	2016-04-02	1	-1/+2
\| \| \| \| \| \|	Required for the keyboard and touchpad on the ideapad 100s. ok kettenis@
*	rename new i2c_attach_args fields to avoid conflict with cpp magic in	deraadt	2016-01-12	1	-3/+3
\| \| \| \| \|	isavar.h (a few parts of the tree include both) ok jcs
*	Add dwiic, a driver for the Synopsys DesignWare i2c controller found	jcs	2016-01-12	1	-1/+3
\| \| \| \| \| \| \| \| \| \| \| \| \|	on the Samsung ATIV Book 9 laptop. This initial version only supports ACPI config/attachment. Add ihidev, a HID-over-i2c driver largely based on uhidev. dwiic handles attaching ihidev devices found in ACPI. Add ims, a HID-over-i2c mouse/trackpad driver to get basic cursor and button functionality from HID-compliant i2c trackpads. ok kettenis deraadt
*	Provide a forward declaration of struct device.	kettenis	2013-07-05	1	-1/+3
\| \| \| \|	ok deraadt@
*	add a member to the i2c_attach args so that a controller can pass a	dlg	2006-02-08	1	-1/+2
\| \| \| \| \| \| \| \|	cookie down to the device. the most obvious use of this is to pass a device its ofw node on sparc64 and macppc so it can configure itself more appropriately. ok kettenis@ henning@ deraadt@
*	switch from macppc-specific maciic(4) driver to the generic iic(4),	deraadt	2006-01-01	1	-2/+4
\| \| \| \| \|	after teaching it to use a function pointer to get back to the OFW scan.. this will also help the sparc64 later; ok kettenis
*	spacing	deraadt	2005-12-31	1	-2/+2
\|
*	some chips (especially those crazy i2c/lpc/isa gross things) expose their	deraadt	2005-12-28	1	-1/+3
\| \| \| \| \| \| \|	banks at other addresses, but there are issues with accessing these other devices. so allow a driver to "knock" these out from future probing. tested by kettenis -- unfortunate enough to have one of these winbond pieces of poo
*	no longer use ia_compat; tested by a few	deraadt	2005-12-27	1	-2/+1
\|
*	permit outsider to call iic_print	deraadt	2005-12-22	1	-1/+2
\|
*	Do bus scanning only if underlying controller asked for it.	grange	2005-12-20	1	-1/+2
\|
*	First attempt to have a table of known I2C slave devices that we	grange	2005-12-19	1	-1/+3
\| \| \| \| \| \| \| \|	have drivers for. iic(4) will scan the bus for them and try to attach an appropriate driver. For now iic(4) scans for all possible addresses for debugging purposes. ok deraadt@
*	instead of passing OF nodes down to the drivers, pass name/compat string	deraadt	2005-11-15	1	-1/+3
\| \| \| \| \| \|	pointers. This lets their match() functions actually make real decisions. OF-capable machines will pass name/compat pointers, but other machines will not. grudging ok kettenis
*	I2C framework originally written by Steve C. Woodford and Jason R. Thorpe	grange	2004-05-23	1	-0/+144
	for NetBSD (r). This framework supports various i2c master controllers: - dumb bit-bang controllers - a few styles of automated controllers that give you control over sending start/stop conditions on the i2c bus - automated controllers that are too smart for its own good, giving software no control over start/stop conditions - smbus controllers by emulating smbus protocol with i2c commands i2c slave devices need their addresses to be specified in the kernel config file, no device discovery presented. ok deraadt@