| Age | Commit message (Collapse) | Author |
|---|
|
In order to avoid any floating SD card detect pins as may e.g. happen on
Ixora V1.1A pull them all up.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Acked-by: Dominik Sliwa <dominik.sliwa@toradex.com>
|
|
While SODIMM pin 45 is pulled down with 100 K on the Colibri Evaluation
board it is currently left floating on the Iris carrier board. This can
cause an unintended high interrupt load on the default power-key with
wake-up capabilities which can cause a lower CPU performance.
Signed-off-by: Bhuvanchandra DV <bhuvanchandra.dv@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Floating pins towards the camera input level-shifter cause it to
consume at least 100mW of power even in idle. This patch fixes this by
configuring pull-downs on all multiplexed camera input pins.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Acked-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Add a comment about DAP FS pin mux requiring INPUT when operating as I2S slave.
Add a comment about DAP SCLK requiring INPUT even when operating as I2S master.
Add a comment about is_i2s_master in the platform data meaning T30 SoC is I2S
master.
|
|
Add SPI controller platform data required for use of hardware chip
selects.
While at it pull-up SPI chip select pin due to NVIDIA's designers
taking the term chip select a little too personal: they indeed only
select a chip otherwise all the chip select pins are just left
floating!
|
|
Integrate CAN support for the Colibri Evaluation Board V3.1a with built-in
MCP2515 SPI CAN controller resp. the Colibri Evaluation Board V2.1c with its
built-in SJA1000 CAN controller connected to the GMI bus.
The following kernel configuration needs to be enabled as well:
CONFIG_CAN
CONFIG_CAN_RAW
CONFIG_CAN_BCM
CONFIG_CAN_DEV
Plus depending on the Evaluation Board revision:
CONFIG_CAN_MCP251X
or
CONFIG_CAN_SJA1000
CONFIG_CAN_SJA1000_PLATFORM
Optional support for 32-bit GMI as well as xPOD CAN on MECS Tellurium for
Colibri T20 is provided via commented defines in
arch/arm/mach-tegra/board-colibri_t20.h.
|
|
Due to missing pull-ups on the gpio-key pins Android unintentionally
entered safe-mode.
|
|
set DD pins to push/pull if not used for I2C in open drain mode
|
|
Validate pin-muxing for latest Colibri T30 v1.1a and v1.1b module
hardware.
|
|
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.
|
|
As the camera master clock is an output no input driver is required on
the external clk2 out pin we use for that purpose.
Note: We do not use the regular camera MCLK due to this pin being 1.8V
only.
|
|
Tested on early prototype Colibri T30 V1.0a eMMC module.
Known issues:
- spurious boot hang after following kernel message
[ 5.595219] Timed out waiting for lock bit on pll pll_a
- no audio (SGTL5000) support integrated yet
- NAND detection/support disabled for now due to boot hang
- USB OTG support disabled for now due to boot hang
- trying to spawn L4T R16 X driver seems to hang
Note: requires uImage with adjusted entry point/load address as follows
mkimage -A arm -C none -O linux -T kernel -a 0x82008000 -e 0x82008000 -n 'Linux-3.1.10-colibri_t30' -d zImage uImage
|
