10 Jul, 2019
1 commit
06 May, 2016
1 commit
21 Apr, 2016
1 commit
20 Apr, 2016
1 commit
14 Dec, 2015
1 commit
01 Nov, 2015
1 commit
31 Oct, 2015
1 commit
-
…i_dev->irq before actually allocating IRQ number for the PCI device
26 Oct, 2015
2 commits
26 Aug, 2015
1 commit
25 Aug, 2015
1 commit
04 Aug, 2015
1 commit
24 Jul, 2015
2 commits
26 Jun, 2015
1 commit
-
…pt mapping for an imx6 pcie host connected to a P2P bridge when using legacy interrupts
25 Jun, 2015
1 commit
23 Jun, 2015
1 commit
11 Jun, 2015
3 commits
-
…lel RGB driven strength; 4. Other minor bug fixed
28 May, 2015
1 commit
07 May, 2015
2 commits
20 Mar, 2015
1 commit
-
System will be no response after resume back under low busfreq mode. The
root cause of this issue is that when the system is under ultra_low_bus_freq
mode on i.MX6SL, resume process has a low bus mode deamon in background,
cause system enter low bus mode twice, busfreq driver will notify thermal
driver to turn off PLL3 twice, and cause PLL3 usecount incorrect and UART
no message out.Signed-off-by: Bai Ping
19 Mar, 2015
1 commit
-
Do not switch the mem view when the imx pcie ep/rc
validation system is enabled.
Otherwise, the RC wouldn't access the mem of the ep
device in the imx pcie ep/rc validation system.Signed-off-by: Richard Zhu
(cherry picked from commit aeab51838317e0843a021b2e8426f942b97b01a8)
16 Mar, 2015
1 commit
-
System will hang if csi unit test mx6s_v4l2_capture.out process
been killed.In csi capture driver function mx6s_csi_enable/disable is called
by vidioc_streamon/streamoff function.
But when csi unit test process is killed, vidioc_streamon/streamoff
will not been called, and csi function still working even the csi
clock is gated.Move mx6s_csi_enable/disable function from
mx6s_vidioc_streamon/streamoff function to
mx6s_start_streaming/ mx6s_stop_streaming function to resolve the
issue.Signed-off-by: Sandor Yu
(cherry picked from commit fe3700b2dc97952ef5a055a48e1d5ba89e11b7dd)
06 Mar, 2015
3 commits
-
…uninstalling ath6kl_sdio after iperf test.
When handing the command "ifconfig wlan0 down", the driver handler did
not notify the disconnected event to the upper layer stack cfg80211,
which would cause the relating resources unable to be released. A
notification of disconnet event to cfg80211 was added when the driver
was changed to the disconnect state.Signed-off-by: Shenwei Wang <shenwei.wang@freescale.com>
(cherry picked from commit 0b7b203a563ac98f5f0c5695a5149ec80d2114b4) -
We can observe the following error during system resume.
dpm_run_callback(): platform_pm_resume+0x0/0x4c returns -110
PM: Device 2090000.can failed to resume: error -110It is caused by the flexcan is in disable state and the clock is disabled
by default while the CAN is not up. During resume, the calling of
flexcan_chip_enable will obviously fail due to no clock.The issue only happened when CAN device is not up. If CAN is up, clock is there
and no issue will happen.Because the CAN is always in disabled state by default if it's not up.
We don't have to disable it again during suspend and enable it after resume.
This patch simply the suspend/resume to only enter/exit disabled mode if CAN
is up.Signed-off-by: Dong Aisheng
(cherry picked from commit 1a8a68cb11ce2de085efb05aa0262a7eca07aba6) -
Enable CONFIG_NETFILTER as requested by Yocto community.
Signed-off-by: Nitin Garg
05 Mar, 2015
2 commits
-
In imx6sl/sx dts, the lcdif display bpp is setting to 16,
and sii902x hdmi driver bpp is 32.
The sii902x driver will overwrite the display bpp when it loading,
but some module such as v4l2 output driver is misses bpp change event.
So align sii902x hdmi driver bpp with lcdif display bpp.Signed-off-by: Sandor Yu
(cherry picked from commit 0fd274cc93a71c8636551c17d7d4157e97fe5cf2) -
There are two ov5640 driver in kernel, one is subdev ov5640 driver,
the other is int-device ov5640 driver.
Rename int-device ov5640 driver to ov564x.Signed-off-by: Sandor Yu
(cherry picked from commit a084ad80684a5b2800d3610e22b4352da88cb749)
04 Mar, 2015
3 commits
-
for i.MX6SX, according to the latest datasheet, added a 198MHz setpoint in cpufreq driver.
The 198MHz setpoint is NOT enough to support playing mp3,the system will stay at a higher
setpoint and high_bus_mode. So when having a setpoint lower than 396MHz, make sure when
the cpufreq is at 396MHz or lower, the busfreq is always in low_bus_mode to save more power.Signed-off-by: Bai Ping
-
Set enet pll rate to 125Mhz for RGMII tx refrence clock to
support i.MX6q sabreauto cpu2 board.changed the enet_ref clock name for 3.14 kernel.
Signed-off-by: Fugang Duan
(cherry picked from commit 6ee3d49271b1f13e359c1acde189dbb6dc4cb13e) -
SDb WP pin is not connected by default on MX6Q CPU2 board, so we removed it
in DTS file. BTW, SDb slot is designed for WiFi slot, it is ok to disable WP
for old CPU board also.Signed-off-by: Dong Aisheng
(cherry picked from commit 2efa09eb28d7404933725bc25b528641a9dc10f9)
(cherry picked from commit dd6e28f2932284494c89bb4897ad84c01db969d8)
02 Mar, 2015
1 commit
-
Fix the clock index for cfg clock and use MACRO instead of hard-codes.
This patch fixes the following issue.
-----------------------------------------------------------
root@imx6qdlsolo:~# /unit_tests/mxc_v4l2_capture.out -d /dev/video1 1.yuv
in_width = 176, in_height = 144
out_width = 176, out_height = 144
top = 0, left = 0
mipi csi2 can not receive sensor clk!
...ERROR: v4l2 capture: mxc_v4l_dqueue timeout enc_counter 0
VIDIOC_DQBUF failed.ERROR: v4l2 capture: VIDIOC_QBUF: buffer already queued
-----------------------------------------------------------Signed-off-by: Robby Cai
(cherry picked from commit 6e4ee449de591d3cfb93575ca639ca32944832bc)
27 Feb, 2015
2 commits
-
We should only do charger detection if both we have enabled
usb charger at kernel configuration and set usb charger enable
at dts. Otherwise, we will do useless things, like toggle dp.Signed-off-by: Peter Chen
(cherry picked from commit 6b677c09dbda0274c6b2e1d61ea0d7f1cc73f621) -
We should signal connect (pull up dp) after we have already
at peripheral mode, otherwise, the dp may be toggled due to
we reset controller or do disconnect during the initialization
for peripheral, then, the host may be confused during the
enumeration, eg, it finds the reset can't succeed, but the
device is still there, see below error message.hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: cannot reset port 1 (err = -32)
hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
hub 1-0:1.0: unable to enumerate USB device on port 1Signed-off-by: Peter Chen
(cherry picked from commit b4b5728425454c1713d152855f09af9c9c12d78d)
26 Feb, 2015
2 commits
-
Sync imx_v7_defconfig with imx_3.10. ARCH_MULTI_V6 is
not required.Signed-off-by: Nitin Garg
(cherry picked from commit ea673b70908b301fc9901d804f141974491dcb3d) -
The PL310 integrated on i.MX6 series and VF610 are revision r3p1 and
later. Per ARM PL310 errata document, 588369 is fixed in r2p0 and
727915 is fixed in r3p1. Neither is needed for i.MX6 or VF610. So
let's drop them.Signed-off-by: Shawn Guo
(cherry picked from commit 8629a0f43b832573b06c27a214100c9b6398f59a)
(cherry picked from commit 09d9f7dcfb59b6c65c9b1f4e37b72da480262133)
15 Feb, 2015
1 commit
-
The kernel boot stops at "Starting kernel ..." if assign cmdline
"video=mxcfb0:dev=lcd,if=RGB565".The cause is that there's no 'mode_str' property for mxcfb0 in DTS file,
so of_property_read_string() does not touch it and 'mode_str' could be used
uninitialized in mxcfb_get_of_property(), where it's assigned to
plat_data->mode_str and then used uninitialized in fb_find_mode().
This may cause buffer overflow. This patch initializes 'mode_str' to NULL
to fix it.Signed-off-by: Robby Cai
(cherry picked from commit 115d11804b7b56d058ee6be8496b13f57869be93)