summaryrefslogtreecommitdiff
path: root/arch/arm/mach-tegra/board-colibri_t30-pinmux.c
AgeCommit message (Collapse)Author
2013-03-12colibri_t20/30: can: integrate mcp251x and sja1000 supportMarcel Ziswiler
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.
2013-02-21colibri_t30: fix gpio-key pull-upsMarcel Ziswiler
Due to missing pull-ups on the gpio-key pins Android unintentionally entered safe-mode.
2013-01-21colibri_t30: set DD pins to push/pullMax Krummenacher
set DD pins to push/pull if not used for I2C in open drain mode
2012-12-21colibri_t30: pin-mux: validate for latest hardwareMarcel Ziswiler
Validate pin-muxing for latest Colibri T30 v1.1a and v1.1b module hardware.
2012-12-05colibri_t30: MMC: fix SDMMC4B pinmuxMarcel Ziswiler
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.
2012-12-05colibri_t30: fix pinmuxing for NC ballsMarcel Ziswiler
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.
2012-11-02colibri_t30: no input driver required on ext clk2 camera master clockMarcel Ziswiler
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.
2012-10-03tegra: colibri_t30: initial Toradex Colibri T30 L4T R16 supportMarcel Ziswiler
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