Age | Commit message (Collapse) | Author |
|
GPIO keys configured as active-low either require pull-ups on the
carrier board or via pin-muxing. We enable the later for now.
|
|
Use GPIO inputs for function tri-stating rather than pin group
tri-stating to avoid influencing neighbouring pins.
While at it get rid of most pull-up/downs and a lot of commented out
stuff.
|
|
Rename CAMERA_INTERFACE to COLIBRI_T20_VI which stands for video input
to be more in-line with Colibri T30.
|
|
Get rid of optional CAM/GEN3_I2C on SODIMM pin 127/133.
|
|
Verify standard GPIO usage for latest v1.2a modules.
|
|
The Iris carrier board by default uses SODIMM pin 73 as DAC power save.
Note: This conflicts with the CAN interrupt on the new EvalBoard v3.1a.
|
|
VESA VGA mode defines hsync/vsync to be of polarity low rather than
high.
|
|
The HDMI power rail configuration used to be done within the LVDS aka
TFTLCD panel enable function. Now moving it to the platform power
initialisation where it really belongs. This avoids any
duplicate/spurious regulator configuration.
|
|
As the deep-sleep LP0 suspend mode is currently anyway not supported
default to the LP1 suspend mode for now.
|
|
The full PMIC power off decreases power consumption but doing a
subsequent reset won't force a re-boot any more.
|
|
Clean-up the following unused regulator supplies in the platform power
stuff:
p_cam_avdd, avdd_lvds, vddio_sys (panjit_touch), vmmc (sdhci-tegra.3)
and avdd_2v85.
While at it add some more comments concerning specific consumers/rails.
|
|
Instead of copying the boot loader frame buffer which currently neither
displays anything worth preserving nor even what it has in the right
resolution make sure both LVDS as well as HDMI frame buffers get
cleared during initialisation to avoid displaying random garbled stuff.
|
|
The boot logo and framebuffer console where displayed with a wrong
stride caused by a colour depth mismatch. Fix this by initially
configuring the display controllers to 16 bpp.
|
|
There are some classes of devices that are controlled entirely from
user space. Userspace consumer driver provides ability to control power
supplies for such devices. Enable this configuration option to be more
in line with the T30.
|
|
If the console is locked while the system is rebooted, the messages in
the temporary log buffer would not have propagated to all the console
drivers. This option forces the console lock to be released if it
failed to be acquired, which will cause all the pending messages to be
flushed. Enable this configuration option to be more in line with the
T30.
|
|
Get rid of the 2G/2G user/kernel memory split configuration in order to
use the default 3G/1G user/kernel memory split. This is more in line
with the T30 and avoids issues trying to run Android.
|
|
Fix two issues concerning SDMMC4B pinmux (e.g. using a regular SD card
as the boot device instead of the on-module eMMC). First according to
the TRM it is illegal to mux a certain function to two sets of balls
(e.g. the regular SDMMC4 as well as the SDMMC4B muxing). Second make
absolutely sure all unused balls are not only tri-stating their outputs
but also disable their inputs to prevent any illegal internal states.
|
|
Make sure NC balls are not only tri-stating their outputs but also do
not drive their inputs but rather have them pulled down in order to
prevent any unstable internal values.
While at it fix alphabetical order of the pinmuxes.
|
|
This fixes the following build issue:
arch/arm/mach-tegra/board-colibri_t30.c:276:41: error:
'colibri_t30_emmc_platform_data' defined but not used
[-Werror=unused-variable]
cc1: all warnings being treated as errors
|
|
Verify standard GPIO usage for latest v1.1a samples.
While at it get rid of some commented out obsolete stuff.
|
|
Integrate proper Ethernet initialisation analogous to how it is done
for the Colibri T20.
|
|
Add a commented out define for v1.0a modules with optional NAND
variants which are auto detected.
|
|
As we don't want to exclusively reserve the detection GPIO temporarily
enabling it is still required.
|
|
Hack to force WIRELESS_EXT required to build Redpine Signals LiteFi driver.
|
|
Enable kernel configuration for USB audio.
|
|
As Colibris are usually self powered default drawn VBUS to 2 mA rather
than demanding 500 mA. This should fix it running from not self powered
USB hubs as well.
|
|
Activate Android rather than mass storage gadget driver to support
multiple USB functions. The functions can be configured via a board
file and may be enabled and disabled dynamically. E.g. the following
enables regular Ethernet aka RNDIS functionality once booted:
echo rndis > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
|
|
Activate Colibri rather than Tegra USB OTG driver as used on
Colibri T20 as well.
|
|
Integrate USB OTG functionality similar to Colibri T20.
|
|
Clean up various comments, indentation and white space issues.
|
|
Get rid of duplicate USB EHCI ULPI VIEWPORT stuff in Kconfig.
|
|
Several file names and paths showed copy/paste or otherwise issues.
|
|
Add default kernel configuration in order to run oe-core on any of the
Colibri PXA series modules. So far no further platform data additions
have been committed meaning only older PXA270 v1.x, PXA300/310 v1.x or
PXA320 v1.x modules as anyway supported in mainline will work.
|
|
So far only Income's board advertised PWM availability but of course
any Colibri is potentially PWM capable.
|
|
Due to a missing else if always the GPIO number as on colibri_pxa320
was being used which of course failed card detection.
|
|
The definition of __exception_irq_entry for
CONFIG_FUNCTION_GRAPH_TRACER=y needs linux/ftrace.h, but this creates a
circular dependency with it's current home in asm/system.h. Create
asm/exception.h and update all current users.
v4: - rebase to rmk/for-next
v3: - remove redundant includes of linux/ftrace.h
v2: - document the usage restricitions of __exception*
Cc: Zoltan Devai <zdevai@gmail.com>
Signed-off-by: Jamie Iles <jamie@jamieiles.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
|
|
As pageattr.c gets built unconditionally it fails linking on none v7
arms (e.g. PXA) with the following error message:
arch/arm/mm/pageattr.c:38:
undefined reference to `v7_flush_kern_cache_all'
|
|
Looks like this DPD stuff whatever it is fails eMMC detection on our
current Colibri T30 prototypes.
See f4cd0d4448d65a42b65c338f85a3ab8064923c61.
|
|
As Colibris are usually self powered default drawn VBUS to 2 mA rather
than demanding 500 mA. This should fix it running from not self powered
USB hubs as well.
|
|
Activate Android rather than Ethernet gadget driver to support multiple
USB functions. The functions can be configured via a board file and may
be enabled and disabled dynamically. E.g. the following enables regular
Ethernet aka RNDIS functionality once booted:
echo rndis > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
|
|
Android R14 userspace seems to have issues with timestamp support:
[ 14.764337] host1x host1x: SurfaceFlinger: syncpoint id 8 (disp0_a) stuck waiting 3, timeout=2147483447
[ 14.773845] host1x host1x: id 8 (disp0_a) min 2 max 4
[ 14.779163] host1x host1x: id 9 (disp1_a) min 2 max 4
[ 14.784316] host1x host1x: id 18 (2d_0) min 21 max 25
[ 14.789586] host1x host1x: id 20 (disp0_b) min 2 max 4
[ 14.794889] host1x host1x: id 21 (disp1_b) min 2 max 4
[ 14.800241] host1x host1x: id 22 (3d) min 77 max 95
[ 14.805217] host1x host1x: id 24 (disp0_c) min 2 max 4
[ 14.810573] host1x host1x: id 25 (disp1_c) min 2 max 4
[ 14.815873] host1x host1x: id 26 (vblank0) min 800 max 0
[ 14.821264] host1x host1x: id 27 (vblank1) min 684 max 0
[ 14.826810] host1x host1x: waitbase id 3 val 77
Therefore conditionally revert it in that case for now.
See e4e2e776a3d4bf1adf37fc061cfdfb92281f3ace.
|
|
Use the existing boardfile for everything, just match using DT.
See df80522dd557e2759552b6c6b0f1f1c8ad1c5614.
|
|
Add configurability support for i2s parameters.
See 907bac80691c7df5b5b57cbf27f91e8bb1dcf434.
|
|
This is a WAR solution that allows for the turning on SD DPD feature.
The original issue is that enabling SD DPD immediately after device
comes out of LP0 causes ULPI disconnect. The root cause of that is not
known.
The WAR is to delay the enabling of SD DPD for 100ms after
device comes out of LP0.
While at it remove commented out tegra_reserve stuff.
See 5e07056dc8b922b8b43a01b60a949c1dda75d9a9.
|
|
Enable device tree support for Colibri T20 by adding board compatible
table.
See 293b009a282e1508a4947d84463fdfe820445a50.
|
|
Since there is no PMC available in tegra2 we will not be able to get
any remote wakeup events. Hence do not power of the phy during usb
suspend.
See c4a5c51e493a8d4154c15c95d2bd93b348090892.
|
|
SODIMM pin 135 is really GPIO K6 multiplexed with ACC1_DETECT. Unfortunately the later can't be tri-stated but since it is anyway always an input it should not interfere. Please note however that this SODIMM pin is rather low resistance.
|
|
Conflicts:
arch/arm/mach-tegra/tegra3_usb_phy.c
arch/arm/mach-tegra/usb_phy.c
drivers/usb/gadget/tegra_udc.c
drivers/usb/otg/Makefile
drivers/video/tegra/fb.c
sound/soc/tegra/tegra_pcm.c
|
|
Add emc table for 256 MB module version. Assume less than 256 MB of
kernel memory (e.g. physical memory minus carveout and framebuffers)
means we are running on a 256 MB module.
|
|
Hack to force WIRELESS_EXT required to build Redpine Signals LiteFi driver.
|