Age | Commit message (Collapse) | Author |
|
When hotpluging hdmi the read of edid often fails.
Add up to 4 retries with a 500ms delay before giving up.
|
|
Reworked driver in order to properly support default watchdog api
such as triggering by writing a character and disable by sending
a magic character. Renamed ENABLE_ON_PROBE to ENABLE_HEARTBEAT
which triggers the watchdog using the interrupt service routine.
|
|
Initialisation of the framebuffer console on DVI-D aka HDMI always
failed on monitors which report the vertical front porch to be 1
in their EDID.
The fix now changes also the modedb and not only the list of
videomodes with a compatible timing.
This was particularly bad on Apalis T30 where this is activated
by default. On Colibri T30 this was observed when enabling it using the
fbcon=map:1 boot argument.
|
|
|
|
I211 with a blank iNVM uses a different PCI ID. Hack the driver to load
despite i211 data sheet claiming tools only, not for driver.
Please note that the existing driver hacks concerning NVM validation
skipping and Ethernet MAC address assignment equally apply.
Tested on initial samples of Apalis T30 1GB V1.0A.
|
|
Re-work input selection to apply to a live camera stream.
While at it default to automatic input selection and make this option
available via IOCTL as input value 2 as well.
|
|
Re-work input selection to apply to a live camera stream.
While at it disable the automatic I2C module loading for now as due to
our currently redundant soc-camera-pdrv registration via board specific
platform data the adv7180 driver is always automatically loaded upon
modprobe tegra_v4l2_camera invocation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
export access to the 'Local Shared OS and T_Crit Limit'
register.
|
|
Hack to avoid 24 Hz mode in X resulting in no display at all. This has
been encountered using e.g. a Samsung SyncMaster F2380 if connected by
HDMI.
root@apalis-t30:~# xrandr
Screen 0: minimum 256 x 128, current 1920 x 1080, maximum 2048 x 2048
LVDS-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1920x1080 58.6*+
HDMI-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 160mm x 90mm
1920x1080 60.0 + 24.0*
1680x1050 59.9
1280x1024 75.0 60.0
1440x900 75.0 59.9
1280x960 60.0
1280x800 59.9
1152x864 75.0
1280x720 60.0 50.0
1024x768 75.0 70.1 60.0
832x624 74.6
800x600 72.2 75.0 60.3 56.2
720x576 50.0
720x480 59.9
640x480 75.0 72.8 66.7 59.9
720x400 70.1
|
|
Previously only 64-lead and 40-lead models were identified. This patch
adds 48-lead and 32-lead device identification as well.
Please note that due to missing parameter negotiation functions one
might get the following message with a subsequent crash:
WARNING: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Could
not get parameters on device '/dev/video0'
This can be avoided by explicitly specifying the format as follows:
gst-launch v4l2src ! deinterlace tff=1 method=4 ! 'video/x-raw-yuv,
width=(int)720, height=(int)576, format=(fourcc)I420' !
nv_omx_videomixer ! nv_gl_eglimagesink
|
|
|
|
|
|
Powering on, improved interlacing.
|
|
|
|
Move paddr to correct ifdef to enable CONFIG_NVMAP_PAGE_POOLS=n
compilation.
|
|
Use right buffer flag NVMAP_HANDLE_WRITE_COMBINE to allocate buffer,
which can be shared by VI/CSI and CPU. Don't use NVMAP_HEAP_SYSMEM.
It is validated to old T20 silicon and can't support big buffers. By
default, our nvmap_alloc() will use IOVMM to allocate buffers.
nvmap_pin() gives us IOVA for hardware engines like VI/CSI module
with IOMMU enabled in kernel. nvmap_mmap() gives us VA for CPU
read/write operations. So we need to convert VA address to physical
address of the buffer and map that buffer to user space processor's
memory space "page by page".
Change-Id: I543d9d95fc14395200647e09480f25d9bc001e00
Signed-off-by: Bryan Wu <pengw@nvidia.com>
|
|
This reverts commit 080c3135b58aa700851991fb672e6c33cf16d9d9.
|
|
|
|
Fix issue with nvhost_client_device_init being issued more than once.
|
|
|
|
Revise Ethernet MAC address assignment: should now handle up to two
instances of custom user MACs (2nd one with a 0x100000 offset). This
way customer does not have to worry about NVM on a secondary Ethernet
on the carrier board and still gets a valid official MAC address from
us (e.g. analogous to how we did it on our Protea carrier board).
|
|
bug report courtesy of Mikhail Shevchuk
|
|
Fix the following build issue introduced by commit
5cfcbc23d116927a7ae8d5b67baeacf2905b21f9 if neither
CONFIG_MACH_APALIS_T30 nor CONFIG_MACH_COLIBRI_T30 is defined as in
case of e.g. the Colibri T20:
drivers/mmc/host/sdhci-tegra.c:951:2:
error: expected expression before '.' token
|
|
The Dell 5800 appears to be a simple rebrand of the Novatel E362.
Signed-off-by: Dan Williams <dcbw@redhat.com>
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
|
This device is also known as the Verizon USB551L.
Signed-off-by: Forest Bond <forest.bond@rapidrollout.com>
Acked-by: Dan Williams <dcbw@redhat.com>
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
|
SDR12, SDR25, SDR50, SDR104 and DDR50 all require 1.8V signalling which
our current T30 designs can't do. Newer cards will fail as follows:
Kingston 32GB microSDHC class 10
[ 69.000280] mmc1: error -84 whilst initialising SD card
SanDisk Mobile Ultra 8GB microSDHC I
[ 28.289174] mmc1: error -110 whilst initialising SD card
This patch activates a quirk which signals our lack of 1.8V support.
|
|
The OLPC XO-1.75 laptop includes a SDHCI controller which is 1.8v
capable, and it truthfully reports so in its capabilities. This
alternate voltage is used for driving new "UHS-I" SD cards at their
full speed.
However, what the controller doesn't know is that the motherboard
physically doesn't have a 1.8v supply available.
Add a quirk so that systems such as this one can override disable
1.8v support, adding support for UHS-I cards (by running them at
3.3v).
This avoids a problem where the system would first try to run the
card at 1.8v, fail, and then not be able to fully reset the card
to retry at the normal 3.3v voltage.
This is more appropriate than using the MISSING_CAPS quirk, which
is intended for cases where the SDHCI controller is actually lying
about its capabilities, and would force us to somehow override both
caps words from another source.
Signed-off-by: Daniel Drake <dsd@laptop.org>
Reviewed-by: Philip Rakity <prakity@nvidia.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
|
|
Turns out after suspend an unbind and bind operation is executed upon
which we subsequently gave out the 2nd custom user MAC address followed
by the default ASIX MAC address.
This patch fixes it by checking for the custom user MAC address upon
unbinding and in this case properly releasing it for subsequent reuse.
|
|
resolution for PAL/NTSC.
|
|
|
|
|
|
|
|
For Android use ICS variant of Fusion 7 and 10 multi-touch driver (See
Fusion 7 and 10 drivers for Linux.pdf and Linux Drivers Fusion 10.zip).
Tested to be working both with Android 4.0.4 for Colibri T20 as well as
Android 4.2.1 for Colibri T30.
|
|
This involved adding some callback methods, and pretending that this is a
YUV sensor.
Signed-off-by: Andrew Chew <achew@nvidia.com>
|
|
The Android idc parser seems to have an issue with spaces in names:
D/EventHub( 159): No input device configuration file found for device
'wm97xx touchscreen'.
Rename the driver in order for the idc parser to recognise idc file
/system/usr/idc/wm97xx-ts.idc being a simple copy of the qwerty.idc
one.
|
|
Rotate touch for now due to missing resistive touch calibration
integration. This makes our 5.7 inch EDT ET057090DHU panel usable.
|
|
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.
|
|
|
|
The VI client within drivers/video/tegra is mutually exclusive with the
Tegra V4L2 framework, since they both want to own the camera hardware.
Signed-off-by: Andrew Chew <achew@nvidia.com>
|
|
set some platform_data.
Signed-off-by: Andrew Chew <achew@nvidia.com>
|
|
arch/arm/mach-tegra/common.c
drivers/ata/ahci-tegra.c
|
|
Rotate touch for now due to missing resistive touch calibration
integration. This makes our 7 inch EDT ET070080DH6 panel usable.
|