| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
The lzo available to this build is the lzo from busybox, which doesn't
support the high-compression mode that Linux requires.
We can work around this, by changing the kernel from being lzo compressed
to gzip compressed.
|
|
|
|
| |
This is needed by newer systemd.
|
|\ \ \ \ \ \ |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This is based off kernel release 3.12
|
| | | | | |\ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Tested by me, by building and deploying to wandboards.
Reviewed-by: Jonathan Maw
Reviewed-by: Richard Maw
|
| | | | | |/ / |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
It appears that the default code copied from Freescale routes parallel CSI
to IPU1, which is the IPU that we are using for MIPI-CSI. Change the route
from parallel to MIPI
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(cherry picked from commit f77f22601e4f4bcbf3e14a48266a4fe3fa56e6e0)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Fix error included when checkpatch errors were fixed
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Running scripts/checkpatch.pl -f on baseboard-wand.c results in many
formatting errors that are not critical but would cause some problems
if we were to upstream this code.
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Fix a small bug when excluding MIPI from the build configuration. There
was a '2' missing at the end of the CONFIG_IMX_HAVE_PLATFORM_IMX_MIPI_CSI2
var.
Also, reorganized the code so that all of the IPU capture, MIPI, and sensor
init is called using wand_init_mipi_csi(), which is a stub now when MIPI
is deslected.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(cherry picked from commit 11a509c6d0958741af52fd85661c08975d1e271d)
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(cherry picked from commit 1c1fd4c1721b3c778a583c41daaf6eaef86fc2f4)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(cherry picked from commit 65bdd402ba6967518794f3379339fb0a469a976c)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(cherry picked from commit 26c6d7b49f9d59d43ec166a97eb2cb8d519d1441)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Commits 13c1310c and 7361e1f0 attempt to read undocumented memory
bits (as of TRM released 2013-05-30) to determine CPU speed rating.
This calculation appears to disable 1GHz mode for (some?) iMX6 Solo
and DualLite CPUs sold by Freescale as 1GHz parts.
This patch reverts the changes and hard-hacks the maximum speed to
1GHz for all iMX6 parts until more information is available.
(cherry picked from commit 177c82740df1a817ccbe978ca687246e77a0718b)
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(cherry picked from commit 81a8ff3743ae3dd21b5a0225f1ecf6bc798cbad4)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The IOMUXC_GPR13 control register has different functionality on iMX6S/iMX6DL
(cherry picked from commit 2a118bb2c07da80ad8906387d75c0b083ec9e619)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Some video application require the "usb/video.h" header.
So here the patch to add it during the kernel header installation :
(cherry picked from commit c97d13e34c4f3d466cb3404e83a782ca11d3cf41)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This commit breaks Bluetooth UART connection on the WandBoard.
This reverts commit e21b0b06f4b99a22f9cf5d63641c00a6d83d433a.
(cherry picked from commit 7cdaeabf2df37efc5bc7d84319c58af8df6345a6)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
In case of inband interrupts, if we handle the interrupt in dpc thread,
two level of thread switching takes place to process wifi interrupts.
One in SDHCI driver and the other in Wifi driver. This may cause the system
instability.
Because the SDHCI calls sdio_irq_thread() to handle the irq, this thread locks
mmc host and calls wifi handler. It expects WiFi handler to be quick and
enables sdio interrupt from card at end. If wifi handler defers this work for
a different thread, sdio_irq_thread() will be stuck on next wifi interrupt
since mmc lock is not freed.
Handling the interrupt in ISR directly will prevent thread context switching in
wifi driver. It can fix the instability problems.
Signed-off-by: Wei Ni <wni@nvidia.com>
(cherry picked from commit c782ec69711573ee082fa78b80dae3897269266e)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
In the event that a I2C bus is disturbed, for instance by a slave missing
a clock pulse, it is desirable to have a way to get the bus back working
other than by power-cycling the whole system. This patch makes it possible to
to have a special function in board support code issue an I2C reset, since
the IMX peripheral is not capable of doing this, and it needs to be done
by bit-banging the corresponding pins in GPIO mode.
The reset function needs to check if the bus is hung by checking the state
of SDA and issue a reset by pulsing SCL a few times as long as SDA is low.
Signed-off-by: David Jander <david@xxxxxxxxxxx>
Conflicts:
drivers/i2c/busses/i2c-imx.c
(cherry picked from commit c1c409c8e9f96e1bd16717733c7456497b42d558)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
without CPU_FREQ
Conflicts:
arch/arm/plat-mxc/dvfs_core.c
(cherry picked from commit 1195fac5d0324c267660b706f5e347e003728d13)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(cherry picked from commit 59d6b4294f5f43c75a9cf4b3cc12bca9bf122e24)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Previously the SGTL5000 was selectable only when certain machines were
being built. Remove this option and make it manually selectable.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
compiled into the same module
and both contain a module_init().
The fix is cleaning up sound/soc/imx/Makefile.
A result is that HDMI config is not assumed always enabled.
(cherry picked from commit 96b71a9a30690f3e4f8fed7e7b92dcbf7fc10a08)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This patch reverts a change introduced by commit eec23c400e5c39ae338b9112031a302230220294
Conflicts:
sound/soc/imx/imx-sgtl5000.c
(cherry picked from commit 39405bfab671b5dbfc3ff7b41b77a0fc954b7824)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This reverts commit d6612bf5c36d7f93552921fcf09e29ad2b323413.
(cherry picked from commit 1af57a1e6d9473a4de0c3708cfa50d9741d3d9b7)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
With the current default configuration, this commit is no longer needed.
Avoid patching specialized driver files such as the GPU.
This reverts commit c0fceed3315ed3167cd024a6b5a27b7c711a0d22.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Update the wandboard defconfig file to reflect a closer alignment to
the default configurations of the Freescale reference boards. Here
is a high-level summary of changes:
- Disable SWAP, as we do not have a swap partition
- Enable/disable certain ARM errata workarounds
- Enable audio and SGTL5000
- Build all cpufreq modes
- Touchscreen and keyboard input support
- DRM support converted from built-in to modules
- Added some USB gadget support
- Added default crypto options and hardware crypto support (FSL CAAM)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The sound subsystem Kconfig file uses MACH_<board> to select whether
the SGTL5000 is selectable as a sound device. Add Wandboard to the
list of boards that are used.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Adds MIPI-CSI support for Wandboard
Upstream-Status: Inappropriate
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(cherry picked from commit 076ad8b1528a6439e9bb629951d8fea6878d1dfc)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(cherry picked from commit 48df1ff3c9969b00f097b8030ce4c16d5aaeeb66)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(cherry picked from commit 70a61be9a499b24484b4da3e1ea7f69f3c0c72dd)
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The previous behavior of the driver did not work properly with Qt5
QtQuick multi touch-point gestures, due to how touch-points are
reported when removing a touch-point. My interpretation of the
available documentation [1] was that the driver should report all
touch-points between SYN_REPORTs, but it is not explicitly stated so.
I've found another mail-thread [2] where the creator of the protocol
states:
"The protocol defines a generic way of sending a variable amount of
contacts. The contact count is obtained by counting the number of
non-empty finger packets between SYN_REPORT events."-Henrik Rydberg
I think this verifies my assumption that all touch-points should be
reported between SYN_REPORTs, otherwise it can not be used to obtain
the count.
[1] https://www.kernel.org/doc/Documentation/input/multi-touch-protocol.txt
[2] http://lists.x.org/archives/xorg-devel/2010-March/006466.html
Signed-off-by: Erik Boto <erik.boto@pelagicore.com>
Signed-off-by: Mahesh Mahadevan <Mahesh.Mahadevan@freescale.com>
(cherry picked from commit 7cba001c5a502680f6dbf902821726779a9c9287)
|