Age | Commit message (Collapse) | Author |
|
Written by Alastair Poole.
|
|
|
|
ok kettenis@
|
|
which is used on the Pinebook Pro.
Driver written by Jared McNeill at NetBSD
ok kettenis@
|
|
RK3399.
Driver written by Jared McNeill at NetBSD
ok kettenis@
|
|
is one of the aux devices for simpleaudio(4). Its only job is
to turn the amplifier's regulator and GPIO on/off when needed.
ok kettenis@
|
|
just a wrapper that connects the I2S controller, the codec and
some aux devices, and provides the information needed to set all
those devices up to use the same settings.
With help from ratchov@
ok kettenis@
|
|
populate a list of 256 levels as fallback. This makes the Pinebook
Pro display work with the dtb that's part of Linux 5.7.
"Fine with me" Krystian Lewandowski
ok kettenis@
|
|
reading the current battery voltage, capacity and remaining minutes on
the Pinebook Pro. Integration into the APM framework stays as exercise
for the reader.
Driver written by Jared McNeill at NetBSD
ok kettenis@
|
|
adds kernel support for
amdgpu: vega20, raven2, renoir, navi10, navi14
inteldrm: icelake, tigerlake
Thanks to the OpenBSD Foundation for sponsoring this work, kettenis@ for
helping, patrick@ for helping adapt rockchip drm and many developers for
testing.
|
|
tested by benno@
|
|
conversion steps). it only contains kernel prototypes for 4 interfaces,
all of which legitimately belong in sys/systm.h, which are already included
by all enqueue_randomness() users.
|
|
OK kettenis@
|
|
miod explained it was initially a long as it was thought drivers may
need to allocate storage but in practice they don't need more than
32 bits for an attribute.
suggested and reviewed by miod@
|
|
Suggested by John Carmack. miod agrees a rename would make sense and
explained it was initially thought drivers may need to allocate storage
but in practice they don't need more than 32 bits for an attribute.
ok mpi@
|
|
Hold the reset GPIO for 100ms instead of 20ms, and also directly
continue setting up the link instead of waiting for another 20ms.
This brings us in line with what Linux is doing and removes the 10%
risk of em(4) not showing up on my HummingBoard Pulse.
ok kettenis@
|
|
ok patrick@
|
|
which is supposed to be PERST. Before issuing PERST, we must disable link
training. This makes my PCIe device come up reliably after warm reboots.
Promped by, with feedback from and ok kettenis@
|
|
Inspired by a proposed fix for Linux mainline.
|
|
3700 and 8040 SoCs and allows me to use an SD card as storage on the
Turris Mox. It also should make eMMC/SD show up on the MACCHIATObin.
ok kettenis@
|
|
mvclock(4) cannot attach to the NB's xtal clock anymore. Instead, have
mvpinctrl(4) attach the xtal clock. With this we can use the SD card
detect pins on the Turris Mox.
ok kettenis@
|
|
leads to unsorted interface lists in ifconfig and the installer,
depending on hardware configuration.
ok kettenis@
|
|
up diffs before committing.
|
|
commit.
|
|
If those properties exist, use those to detect a card.
ok kettenis@
|
|
the Armada 3700 SoC. So far only MSI is supported, since it was
easier to implement. Both MSI and INTx share a single interrupt
pin, so there's nothing to gain anyway, apart from legacy device
support.
With this I can push traffic through a bwfm(4) in my Turris Mox.
ok kettenis@
|
|
Armada 3700. This makes my second ethernet controller/port
work on the Turris Mox.
ok kettenis@
|
|
|
|
|
|
|
|
|
|
Amlogic SoCs.
|
|
|
|
clock on the G12A variant.
|
|
/dev/fdt.
ok patrick@, visa@
|
|
fixed values for the divisors, but the imxesdhc(4) nodes for
SD Cards usually have an assigned clock rate of 200 MHz instead of
400 MHz. So instead of just clearing the divisor, we should set it
according to what is asked. This also allows us to add the clock
for the second imxesdhc(4) node to the list, which I have previously
skipped, since otherwise the controller would have been clocked too
high.
ok kettenis@
|
|
those are already on, since on those machines we mostly boot from SD/MMC
and U-Boot prepares them for us. On machines with a WiFi on imxesdhc(4),
U-Boot isn't necessarily configured to do so. Enabling the clocks is the
right thing to do anyway.
ok kettenis@
|
|
imxesdhc(4) device tree nodes.
|
|
A Type-C controller has multiple tasks. Even though the orientation
of the plug doesn't matter for the user, it matters for the hardware.
To be able to know how to route the SuperSpeed pins you need to know
which way the plug is connected. Also you need to know if you're a
sink/source or device/host. To get the first connection, you toggle
between the modes until you find a connection. In case you see that
a sink is connected, you can turn on USB Vbus to power the sink.
This driver explicitly does not implement USB's Type-C state machine,
but if we get more and more of these controllers it might be worth
doing. Also there's no support for Power Delivery messages yet.
"go for it" kettenis@
|
|
to i.MX27, they actually need different bits to be set than the i.MX27.
The i.MX8MM's node instead rightfully only claims to be compatible to
i.MX7D, since it's the same implementation. Thus change imxehci(4) to
also match the i.MX7D compatible.
ok kettenis@
|
|
instead of hardcoding the values.
Tested on a Cubox-i by kettenis@
ok kettenis@
|
|
controller and its nop-PHYs. This is needed on the i.MX8MM.
ok kettenis@
|
|
not USB_CORE_REF.
|
|
come up. This apparently happens when there's no card in the PCIe slot.
Thus improve the error handling in all cases where we wait for a link to
come up, return and don't proceed any further.
ok kettenis@
|
|
that aren't claimed by kernel drivers can be used from userland.
ok sthen@
|
|
ok kettenis@
|
|
ok kettenis@
|
|
for i.MX8MQ support, but adds some PHY initialization via the
imxpciephy(4) regmap and needs a few other bit-settings in the
IOMUXC GPR for selecting the ref clock.
ok kettenis@
|
|
is also implemented on the i.MX8MM. So far this driver is a
glorified regmap provider, which will be used by dwpcie(4).
ok kettenis@
|
|
the i.MX8MQ variant and sit in the same places, but there seems to
be only one ROOT clock. Since the device tree bindings don't seem
to use assigned-clock-rates, there's no need to implement the get/
set frequency for the USB clocks. Essentially this means: fewer
code to copy.
|