wireguard-openbsd/sys/dev/i2c, branch masterWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sys/dev/i2c?h=master2021-01-22T17:35:00Zims: an actual i2c-connected mouse is unlikely2021-01-22T17:35:00Zjcsjcs@openbsd.org2021-01-22T17:35:00Zurn:sha1:f1440c79fafea7a835e6898614feeebeded4a9b9
Claim to be a touchpad instead, which sets up ims devices in X11 to
be more like touchpads.
ok mglocker
Add support for the HYM8563 RTC, which is a PCF8563 clone.2021-01-13T11:01:19Zketteniskettenis@openbsd.org2021-01-13T11:01:19Zurn:sha1:48c44e63ed4ef2dc2c40dfccc9f1e07f2606dec9
ok kurt@
Extend pcamux(4) with ACPI support. So far pcamux(4) has assumed it's2020-11-14T21:50:51Zpatrickpatrick@openbsd.org2020-11-14T21:50:51Zurn:sha1:2a7dffccb5a013f770e774651d3abb9cc0af2906
always matched on an FDT-capable device, but the HoneyComb LX2K seems
to have a PCA9547 and provides it as NXP0002 HID. This means we know
if it's ACPI or FDT based on the name passed. This is required to be
able to make two acpitz(4) nodes work, since the thermel sensors are
behind the mux.
ok kettenis@
Add support for the PCA9547 I2C mux to pcamux(4). In comparison to2020-11-13T10:14:52Zpatrickpatrick@openbsd.org2020-11-13T10:14:52Zurn:sha1:b7461f4bb2004ebed4660ebc3bf78b00583e21f9
the PCA954[68], this is a mux instead of a switch and can only have
one active channel at a time. On the bright side, we treat switches
like a mux, so only the bits have to be set a little bit differently.
ok kettenis@
Add support for the Micro Crystal RV4162. This variant holds the2020-10-23T20:55:15Zpatrickpatrick@openbsd.org2020-10-23T20:55:15Zurn:sha1:35cccaaef0891f4e60849b1b78f8a0612497db4e
square wave frequency control bits in the Day Of Week register.
To make sure we don't fudge with those bits, only reset those that
hold the day and keep the rest as is.
ok kettenis@
Move mfokclock(4) from loongson to sys/dev/i2c so that it be used by more2020-09-30T22:23:40Zpatrickpatrick@openbsd.org2020-09-30T22:23:40Zurn:sha1:d714ed3db694a238d1e0a5018a7fb156af9527f3
platforms than just loongson. Rename it to mfokrtc(4) for consistency with
other RTC drivers. Make it match on st,m41t83, since that was the chip for
which the driver was written for. More compatible strings can be added for
each chip of the series verified to behave the same.
Discussed with kettenis@
Compile tested on loongson by kn@
Tested on loongson by and ok visa@
Add support for the PCA9546 I2C switch to pcamux(4). In comparison to2020-09-29T13:59:22Zpatrickpatrick@openbsd.org2020-09-29T13:59:22Zurn:sha1:49361fec501967f67bfb75c4623ac7e57b9705db
PCA9548, this variant supports only 4 instead of 8 channels.
ok kettenis@
The pcamux(4) device tree node's children are the individual channels,2020-09-29T13:50:54Zpatrickpatrick@openbsd.org2020-09-29T13:50:54Zurn:sha1:332805e1f24acc346bc7dede8f639333595c087c
which we each treat as an I2C bus. While scanning these, we need to
use each channel's node as starting point instead of the pcamux(4) node.
This fixes finding and attaching devices connected to these channels.
ok kettenis@
Declare hw_{prod,serial,uuid,vendor,ver} in <sys/systm.h>.2020-08-26T03:29:05Zvisavisa@openbsd.org2020-08-26T03:29:05Zurn:sha1:85fcfc35df4a58ba20bf8a539339bc9ad114950e
OK deraadt@, mpi@
On some laptops that have a Windows Precision Touchpad (imt) and2020-07-09T21:01:55Zjcsjcs@openbsd.org2020-07-09T21:01:55Zurn:sha1:8fabbf99b406209dfff93615e906d9d6117e312a
also a trackstick or separate physical buttons, imt was claiming all
report ids of the ihidev device preventing the trackstick/buttons
from attaching as a separate ims device on other report ids.
Just claim the report ids that imt needs and let ims attach to
others it may find.
Fixes two Dell Latitude laptops and tested in snaps for a bit.