| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Add helper routines to deal with attach and detach of gpiobus and gpioc
devices that are common to all drivers.
|
|
|
|
|
|
| |
drivers.
This paves the way for upcoming work.
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
Allocate all four, we will use them soon.
Simplificate the allocation of memory and interrupt resources with a single
bus_alloc_resources() call instead of doing them separately.
Destroy the mutex in case of errors.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With this change, it is now possible to verify the pin function and level
of reserved pins (but not set them).
The use of reserved pins on Raspberry pi can lead to short circuits and
real damage to the SoC.
While here, remove duplicated code, make use of OF_getencprop_alloc()
instead of using fixed sized variables and reduce the dmesg spam by
printing reserved pin ranges (when possible) instead of printing each pin
in the range.
|
|
|
|
|
|
|
|
|
|
| |
string.
With this change it is not necessary redeclare the driver relations with
gpiobus and gpioc.
This also prevents redundant declarations when gpiobusvar.h is included
(which is going to happen soon).
|
|
|
|
|
|
| |
Minimum LCDC is 2 so clock freq shouild be 2*max_pixel_clock. Maximum pixel
clock for HDMI is 148500 (1920x1080). But AM335x can not run in this mode
due to bandwidth and clock limitations
|
|
|
|
|
|
| |
Differential Revision: https://reviews.freebsd.org/D1687
Reviewed by: rpaulo
Sponsored by: DARPA, AFRL
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
lock around the mapping and uiomove(). Before r277643, it was
partially protected by Giant (but potential sleeping in fault from
uiomove() would still allow other thread to reuse the mapping).
Noted by: ian
Reviewed by: alc, ian
Sponsored by: The FreeBSD Foundation
MFC after: 3 weeks
|
|
|
|
|
|
|
| |
1 second is not enugh for TDA19988 HDMI framer (e.g. on Beaglebone Black)
- Add per-device i2c_timout sysctl (dev.iichb.X.i2c_timeout) to control
I2C bus timeout manually
- Pass softc instead of device_t to all sysctl handlers
|
| |
|
|
|
|
|
|
|
|
|
|
| |
o Digital Audio Multiplexer (AUDMUX)
o Smart Direct Memory Access Controller (SDMA)
o Synchronous Serial Interface (SSI)
Disable by default as it depends on SDMA firmware.
Sponsored by: Machdep, Inc.
|
|
|
|
|
|
|
|
|
| |
for i386, and from the code inspection, nothing in the
arm/mips/sparc64 implementations depends on it.
Discussed with: imp, nwhitehorn
Sponsored by: The FreeBSD Foundation
MFC after: 3 weeks
|
|
|
|
|
|
| |
should fix "Spurious inteerupt" message
Suggested by ian@
|
|
|
|
|
| |
that the linux guys made up on the fly (but didn't document) last August.
This type of encoded config now appears in the imx6 fdt data.
|
|
|
|
|
|
| |
any given board will be using.
Yes, changing source is an unusually primitive power control implementation.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
the data the inline functions access together at the start of the bus_space
struct. The start-of part isn't so important, it's the grouping-together
that's the point: now all the most-accessed data should be in one cache line.
Suggested by: cognet
|
| |
|
|
|
|
| |
arm/bus_space_base.c).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
duplicates of the standard arm base bus_space, so just use it.
|
|
|
|
|
| |
and now some v5 Marvell systems are using it. Only define fdt_bus_tag
if option FDT is defined.
|
| |
|
| |
|
|
|
|
| |
so just use it.
|
|
|
|
|
| |
values have armv4 in the name. There's nothing armv4-special about them,
so just use the same sort of names as all the other functions.
|
|
|
|
| |
files for lpc and xilinx aren't needed. Also, fix a couple paste-os.
|
|
|
|
|
|
| |
Fill in some formerly NULL members where the implementation function
exists. Add a dummy function that panics and use it as a placeholder
for thigns that are still unimplemented. Remove a few unused includes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
every operation to retrieve the bs_cookie value almost nothing actually uses.
The bus_space struct contains a private data pointer (poorly named bs_cookie,
now renamed to bs_privdata) which is used only by a few old armv4 xscale
implementations. The bus_space functions were all defined to take this
value as the first parameter instead of the bus_space_tag_t, requiring all
the inline macro and function expansions to dereference the tag to pass it
to another function, which never uses it. Now all the functions take the tag
as the first parameter and retrieve the privdata if they need it.
Also fix a couple bus_space_unmap() implementations that were calling
kva_free() instead of pmap_unmapdev().
Discussed with: cognet
|
|
|
|
| |
Reviewed by: cognet
|
|
|
|
|
|
| |
there is no multi-core hardware prior to ARMv6.
Sponsored by: The FreeBSD Foundation
|
|
|
|
| |
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
|
|
| |
driver on Rockchip boards. It currently supports PIO mode
and dma mode needs external dma controller to be used.
Submitted by: jmcneill
Approved by: stas (mentor)
|
|
|
|
| |
This register is not documented in TRM but that's what linux driver does
|
|
|
|
|
|
| |
This doesn't actually change any behavior, because it just allows a 16-bit
read of the command register to return the correct value, and nothing
actually does a 16-bit read of that register.
|
|
|
|
|
|
| |
HSW, VSW
is register's programmed value + 1.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sdhci controllers, such as the one on a Raspberry Pi, mishandle the signal
timing in high speed signaling mode, but run just fine in standard mode
with the bus running at frequencies between 25-50MHz (which shouldn't work).
This is the solution adopted by U-Boot and other OSes (linux and *BSD)
for the timeouts on Raspberry Pi boards with certain SD cards. Some
research shows that this quirk is also used on a few other boards, so the
fix is a generic quirk instead of being in the RPi-specific driver code.
This change is based on information discovered by Michal Meloun.
|
|
|
|
|
|
| |
the stack for secondary cores, the other two values are only used for zeroing
bss on the primary core. No need to store the size of the stack at the
top of the stack (seems to be a leftover instruction from some cut-n-paste).
|
|
|
|
|
|
| |
the bootloader to have done so.
Submitted by: Thomas Skibo <thomasskibo@sbcglobal.net>
|