Age | Commit message (Collapse) | Author |
|
Previously the device tree only described one but now it describes both.
Do not attempt to set the global variable that points to a softc or
register a watchdog if this has already been done.
Fixes rebooting on the OMAP4 based PandaBoard-ES with a device tree from
linux 4.15-rc1.
|
|
Rework the code to store the relevant information in the softc. As a bonus,
this reduces the stack space that is used such that this file compiles with
clang.
ok ians@
|
|
ok ians@
|
|
a -Wtautological-pointer-compare warning.
ok ians@
|
|
|
|
thanks Artturi Alm, ok patrick@
|
|
|
|
|
|
|
|
|
|
ok kettenis@ patrick@
|
|
Using a name with the 'db_' prefix makes it invisible from the dynamic
profiler.
ok deraadt@, kettenis@, visa@
|
|
|
|
|
|
From Ian Sutton.
|
|
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 kettenis@ patrick@
|
|
The consensus is that this was done before the bugs in the cache
flushing code were fixed. The pl310 has been enabled on imx for some
time now and it works fine here on pandaboard as well.
ok patrick@ kettenis@ bmercer@
|
|
|
|
by the controller. Needed as the bus_clock callback is called with
SDMMC_TIMING_HIGHSPEED even if the controller capability is not set.
Required to raise the bus width on pandaboard which doesn't have the
highspeed capability.
As anything other than 1 bit mode results in the emmc on the bbb
timing out waiting for command completion, limit higher bus
modes to the first hsmmc controller. This at least lets 4 bit
modes work with sd cards on bbb and pandaboard.
|
|
configuration that attaches with the fdt and writes values to registers
based on the pinctrl data in the fdt. Handles 16 bit values
(OMAP3/OMAP4) and 32 bit values (AM335x/AM57xx).
Feedback from and ok kettenis@ tom@ on an earlier version.
|
|
"ifconfig: SIOCSETVLAN: No buffer space available" when creating vlan
interfaces without first lowering the mtu. Reported by Steven Chamberlain,
diagnosed by mikeb@, patch from Brad. ok bmercer@
|
|
and routes interrupts to the GIC/ampintc(4).
The code is derived from imxgpc(4) which has the same role on imx.
In the pandaboard device tree wugen is the default interrupt parent
and is used for the hsmmc nodes. Adding this driver makes ommmc(4)
interrupts work again on pandaboard.
ok kettenis@
|
|
|
|
rename it to fit the typical scheme of such an attachment driver.
ok kettenis@ jsg@
|
|
ok kettenis@
|
|
am335x has a compatible string of "ti,omap4-gpio" and has the same
offsets as omap4, so combine the omap4 and am335x cases when setting up
function pointers.
|
|
ok kettenis@ patrick@
|
|
Requested by and ok kettenis@
|
|
drivers that use the FDT over to the FDT interrupt establish API.
ok kettenis@
|
|
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@
|
|
didn't attach previously on OMAP4 with the static device configuration
and now do with the fdt. Like most of the other OMAP4 prcm cases
these don't do anything, hopefully we'll properly configure clocks with
data from the fdt at some point in the future.
Tested by abieber@ on PandaBoard-ES.
|
|
pinctrl-single,pins to handle mux settings and pad configuration.
The fdt data has offsets from the start of the pinmux address range so
the am335x specific pinmux offset from the scm base is added to the
offsets. This as not a new driver as sitaracm does manual table
driven pad configuration for gpio. If all the offsets in the
ti_padconf_devmap table were reduced by the am335x pinmux offset (0x800)
it may make sense to map only the pinmux memory region and not the
scm superset.
looks good kettenis@
|
|
|
|
ok kettenis@ on an earlier version
|
|
ok kettenis@
|
|
clkbase to be set to 0 (if it wasn't all commented out anyway).
ok patrick@
|
|
and match based on the compatible property of the root node in the fdt.
Each of am33xx, omap3, and omap4 have their own list of devices to
attach.
|
|
use the fdt.
|
|
port as well, though we still only handle a single port for now.
ok kettenis@
|
|
|
|
Only match on omap4 compatible controllers such as the one in the
am335x on bbb. omap3 has different register offsets and a different
compatible string.
This reuses kettenis' fdt i2c scan function from imxiic(4).
|
|
|
|
|
|
|
|
|
|
|
|
Writing to the bbb emmc (but not reading) gives errors otherwise.
This does not occur with an sd card on bbb but apparently does on panda.
|