wireguard-openbsd/sys/dev, branch master

Clean up nonexistent/unused properties handling

2021-04-01T12:06:00Z

Never used since import and probably just ported over from NetBSD as-is; "design-capacity" does not exist in the device tree binding. "monitor-interval-ms" defaults to 250ms as per binding and could be used in the sensor_task_register() call, but our framework only supports whole seconds and there's no advantage over our current fixed poll interval of 5s. OK patrick

Hardcode meaningful alert level, track apm's battery state better

2021-04-01T10:34:21Z

The current code looks for the nonexistent "cellwise,alert-level" property and falls back to zero as threshold (like the original NetBSD code). It also updates the CONFIG register with that very threshold to let the hardware set a bit and thus alert us when it has been reached. Since our sensor framework is designed to poll every N seconds and this driver does not actually look at whether the hardware alerted, neither using a default threshold of zero nor updating the hardware with it makes sense. Remove the alert level code and simply map >50%, >25% and <=25% of remaining battery life to apm(4)'s "high", "low" and "critical" battery state respectively; this matches exactly what acpibat(4) does and provides more meaningful sensor readings without relying on nonexistent device tree bindings. Feedback OK patrick

Push kernel lock down to umb_rtrequest().

2021-04-01T08:39:52Z

We are going to unlock PF_ROUTE sockets. This means `if_rtrequest' handler will be performed without kernel lock. umb_rtrequest() calls umb_send_inet_proposal() which touches kernel lock protected `ipv{4,6}dns' array. Also umb_rtrequest() is the only handler which requires kernel lock to be held. So push the lock down to umb_rtrequest() instead of grab it around `if_rtrequest' call. This hunk was commited separately for decreases PF_ROUTE sockets unlocking diff. ok gerhard@ deraadt@

sync

2021-03-31T09:59:32Z

Remove redundant "HUAWEI Mobile" in usbdevs strings, mention radio

2021-03-31T09:59:21Z

technology where known. ok deraadt

fix typos in comments

2021-03-30T20:58:19Z

Handle systems, such as the Dell Precision 3640, that access

2021-03-30T16:49:58Z

GenericSerialBus operating regions witout checking whether they're really available. This needs to work on RAMDISK kernels as well. Since we don't want to pull in the i2c subsystem on those, provide a separate and much simpler dummy implementation of the GenericSerialBus access code when SMALL_KERNEL is defined. ok tb@

Register the PCI variant of dwiic(4) with acpi(4).

2021-03-30T16:46:36Z

ok tb@

Some cards announce support for the NTB16 format, but that support does not

2021-03-30T15:59:04Z

work. Hence, add support for NTB32 in the transmit path. We already have support for NTB32 in the receive path. We detect the supported format on boot and can then decide on transmit which format to use. From ehrhardt@ with gerhard@ Tested by jan@ ok sthen@

Some umb(4) devices require the NDP pointer behind the NDP datagram.

2021-03-30T15:48:36Z

From gerhard@ "broadly OK" sthen@