Age | Commit message (Collapse) | Author |
|
variant is essentially the same in regards to sdmmc as the i.MX6SX
variant, which is why the device tree specifies that version. The
i.MX6SX has a few quirks. One of these is related to tuning, which
we don't do, the other one to the CAP1 register, which we don't use,
and the third is for high speed support, where the "support bit" is
missing for HS200. Of all these, only the one where the CAP1 register
spills into the CAP register seems relevant to us. With this I can
mount and newfs on the SD card.
ok kettenis@
|
|
device tree uses completely differently numbered indices compared to
the i.MX6QDL variant. This means we have to add another clock list
and use the right one depending on the compatible. Also, on the UL
variant there is another mux in front of the perclk divider, so we
have to cope with that as well.
With feedback from and "looks reasonable" kettenis@
|
|
|
|
It doesn't compile und hasn't been working during the last decade.
ok kettenis@, deraadt@
|
|
|
|
this means packets are consistently counted in one place, unlike the
many and various ways that drivers thought they should do it.
ok mpi@ deraadt@
|
|
struct proc to struct process.
ok deraadt@ kettenis@
|
|
|
|
ok jsg@, patrick@
|
|
|
|
This can lead to tsleep in an interrupt context, which resulted in the
following panic:
kernel diagnostic assertion "p->p_wchan == NULL" failed: file
"/usr/src/sys/kern/kern_sched.c", line 333
TID PPID PGRP UID S FLAGS WAIT COMMAND
86009 0 0 0 2 0x40014200 miiaut idle0
Reported by matthieu@ with sabre lite, analysis by guenther@
ok kettenis@
|
|
longer needed, including the imx board IDs.
ok patrick@, jsg@
|
|
controller. This register controls whether the controller is in device or
host mode on many dual role controllers and gets reset during a reset of
the controller, placing the controller in (non-functional) idle mode. By
saving and restoring it, we keep the controller in host mode. Since this is
a non-standard register, add a new EHCIF_USBMODE flag and only do the save and
restore if it has been set.
Makes the upper "OTG" port of the Cubox-i work.
ok mpi@, jsg@
|
|
before imxocotp(4), delay reading the temperature sensor calibration
information until after imxocotp(4) attaches.
|
|
mii(4). Should fix the link negotiation issues that people have been seeing.
ok jsg@, mikeb@, guenther@
|
|
ok patrick@, tom@, mikeb@
|
|
locator to attach them before other drivers that might need their services.
ok patrick@, jsg@
|
|
Noticed when looking into a regression on sabre lite with fec(4)
bisected by matthieu@. This fixes the sabre lite problems with fec and
also recent problems with the i2c rtc on cubox.
ok kettenis@
|
|
|
|
|
|
ok kettenis
|
|
|
|
Theo's Cubox-i comes up without working Ethernet after a warm boot.
ok deraadt@
|
|
by patrick@.
ok deraadt@
|
|
|
|
and see the BCM4330 wireless (for which we don't have a driver yet).
ok jsg@
|
|
driver. This allows us to use to hook up the Ethernet interrupt
on the Nitrogen6x, SabreLite and WandBoard like it's described
in the device tree.
ok kettenis@
|
|
ok patrick@
|
|
|
|
controller. Switch all i.MX6 devices over to the new FDT-aware interrupt
establish API and enable imxgpc(4).
This may break other platforms that use ampintc(4) as their interrupt
controller. We will fix this as soon as possible by switching them over
to the new interrupt establish API as well.
This also removes the hack in fec(4) to avoid the gpio-based interrupt
workaround. This commit is an essential step on the road to fix that
issue properly.
ok patrick@, jsg@
|
|
acts as a "transparent" interrupt controller. This driver just hands
interrupt handlers to its parent (the Cortex-A9 GIC). It doesn't implement
any powermanagement features yet.
ok patrick@
|
|
to fix autonegotiation at 100BaseTX. Drop the bit of code that powers up
the PHY as the reset should already take care of that.
ok patrick@
|
|
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@
|
|
used in the fdt attach args and the device tree.
ok kettenis@
|
|
is always the serial console. With device tree enumeration, this order
is not given anymore. The serial console might now attach with a
different minor and has to be updated, otherwise there will be no
further output on the serial. Thus, re-create the i.MX6 console with
the correct minor number on attach.
ok jsg@, kettenis@
|
|
the device tree says. As a result many device trees encode it as active-high
when active-low is needed. For now just override the device tree.
ok jsg@, patrick@
|
|
with i.mx6 quad but with more memory bandwidth and some graphics tweaks.
ok kettenis@
|
|
interrupts-extended property is missing or not the size we expect.
Some dtbs implement a workaround for "ERR006687 ENET: Only the ENET
wake-up interrupt request can wake the system from Wait mode" suggested
by the IMX6DQCE errata document to set an undocumented gpio mux mode and
handle the interrupt via gpio.
We don't support gpio interrupts yet, hopefully this change is enough
to make interrupts work on wandboard and sabre lite again till we do.
Discussed with kettenis and patrick, tested on sabre lite by patrick.
|
|
ok patrick@
|
|
PHYs based on device tree properties instead of the board ID. Untested as
I don't have the hardware.
ok jsg@, patrick@
|
|
bus. For this only supports "fixed" regulators that are controlled through a
gpio. But this covers all the case we currently handle with board ID specific
code. Note that the old code did explicitly remove power first on some boards,
which would reset bus-powered devices/hubs on the bus. The new code doesn't do
this. If that causes problems we can revisit the issue. The boards that would
be affected are sabrelight/nitrogen6x and utilite.
The plan is to evolve this into a generic regulator framework that supports
more complex regulator types as well.
ok jsg@, patrick@
|
|
such that we can don't end up with conflicting attachments of other
SoC-specific glue code.
|
|
such that we can don't end up with conflicting attachments of other
SoC-specific glue code.
ok jsg@, patrick@
|
|
hardcoding particular gpios based on board IDs.
ok visa@, jsg@
|
|
gpios based on board IDs.
ok visa@, jsg@
|
|
ok visa@, jsg@
|
|
In that case, soft fail and return instead of allocating buffer with
a bogus size.
ok kettenis@
|
|
|
|
|
|
These are used to do board-specific setup of mux settings and pad
configuration.
ok jsg@, patrick@
|