wireguard-openbsd/sys/arch/arm/simplebus, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/arm/simplebus?h=jd%2Fqueueboosts 2020-04-29T15:25:07Z Let the armv7 bus_dma layer and simplebus(4) implementation deal with 2020-04-29T15:25:07Z kettenis kettenis@openbsd.org 2020-04-29T15:25:07Z urn:sha1:37084e1e34e6eafe959b14d27c905d6c5ddf0888 DMA remapping in the same way as arm64. This relies on the dma-ranges property in the device tree and allows us to get rid of the hack for the Raspberry Pi in the dwctwo(4) driver. Note that this does not include the hack in simplebus(4) that we have on arm64 since firmware that has the dma-ranges is in widespread use now. ok patrick@ Prevent attaching drivers to devices for which we attached a driver early. 2019-04-16T13:16:06Z kettenis kettenis@openbsd.org 2019-04-16T13:16:06Z urn:sha1:2a1245a1658648a18e7cc6071aef722b4898055c ok patrick@, dlg@, visa@ match arm64 and print unconfigured simplebus devices on armv7 2019-01-05T03:42:19Z jsg jsg@openbsd.org 2019-01-05T03:42:19Z urn:sha1:ad434fd9e6cb47723d3e5ed46887978b88f72dd7 ok dlg@ kettenis@ Bring over the changes to mainbus(4) and simplebus(4) from arm64. 2017-04-27T22:41:46Z kettenis kettenis@openbsd.org 2017-04-27T22:41:46Z urn:sha1:88a615dbeb839372707b48a527d25530dadf0d81 No need to explicitly use config_activate_children in the cfattach struct. 2017-01-23T06:13:34Z kettenis kettenis@openbsd.org 2017-01-23T06:13:34Z urn:sha1:fc955b36c7dac13ebe51e9f80b3a42a83418e549 Outsource simplebus softc definition so that it can be used by 2016-10-21T20:09:49Z patrick patrick@openbsd.org 2016-10-21T20:09:49Z urn:sha1:619bab233d94abf92c07566db3cbf5b5b44f0a81 simplebus compatible bus drivers. ok kettenis@ Some device trees use 64-bit intermediate virtual addresses. This 2016-10-05T07:44:24Z patrick patrick@openbsd.org 2016-10-05T07:44:24Z urn:sha1:ed541e3a3388d9d16c92bacf4e996fbd317100a0 means that even though the hardware in the end never leaves the 32-bit address space, some addresses used solely in the device tree can be bigger than 32-bit. As bus_space_map(9) takes addresses of size bus_addr_t, which is 32-bit on ARMv7, we cannot pass those virtual addresses to the parent bus, even though it will be mapped back into a 32-bit address in the end. To work around this, make bus_space_map(9) take a 64-bit address. Since this is implemented as a macro and function pointer we can safely do that without harming any other architecture. ok kettenis@ deraadt@ Use a locator (named "early") to let designated drivers attach before others. 2016-09-18T17:50:25Z kettenis kettenis@openbsd.org 2016-09-18T17:50:25Z urn:sha1:abc4f2a0e3d3628005c2e9aa0046e1e2202e4372 ok patrick@, jsg@ Instead of passing the raw reg property to simplebus nodes, 2016-07-27T11:45:02Z patrick patrick@openbsd.org 2016-07-27T11:45:02Z urn:sha1:ac7c670e22cf9895ac879f0332e94ba5d46d5a76 pass a pre-processed array of fdt_reg structs. This means that the drivers don't have to understand the cell properties themselves but can rely on the 64-bit addr/size pairs. ok kettenis@ Some SoCs have a ranges property set in their device trees. This can 2016-07-18T11:53:32Z patrick patrick@openbsd.org 2016-07-18T11:53:32Z urn:sha1:39d0e1dc2812464507bc6e3ad94a104ea5452f4e be used to translate one memory address to another. Currently we just pass the child's memory address to bus space map. If one of the parent busses implements a ranges property, the child's address property is not the real address. This change hooks up a bus space map function that is aware of the ranges property and translates the addresses if needed. ok kettenis@ looks fine jsg@