<feed xmlns='http://www.w3.org/2005/Atom'>
<title>litmus-rt-imx6.git/drivers, branch master</title>
<subtitle>LITMUS^RT and MC^2 V1 support for the i.MX6 processor family.</subtitle>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/litmus-rt-imx6.git/'/>
<entry>
<title>seems working</title>
<updated>2015-02-26T15:10:13+00:00</updated>
<author>
<name>Namhoon Kim</name>
<email>namhoonk@cs.unc.edu</email>
</author>
<published>2015-02-26T15:10:13+00:00</published>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/litmus-rt-imx6.git/commit/?id=f34d9982907644ade66b8689460cf0f414e88ce7'/>
<id>f34d9982907644ade66b8689460cf0f414e88ce7</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>ENGR00326135 pcie: pcie ep test fail on imx6q sd</title>
<updated>2014-08-07T03:28:36+00:00</updated>
<author>
<name>Richard Zhu</name>
<email>r65037@freescale.com</email>
</author>
<published>2014-08-07T02:00:25+00:00</published>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/litmus-rt-imx6.git/commit/?id=94a7e472c47b800c001c0a5d17bb2f14a13e1980'/>
<id>94a7e472c47b800c001c0a5d17bb2f14a13e1980</id>
<content type='text'>
Rootcause: doesn't get the correct mem ranges
from DT on imx6q after added imx6sx sdb pcie ep/rc
validation system support.
solution: Remove the imx6sx specification when get
the mem ranges from DT.

Signed-off-by: Richard Zhu &lt;r65037@freescale.com&gt;
(cherry picked from commit b42f60a06c77448a8a00b961fb8035c58a5ed8a1)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Rootcause: doesn't get the correct mem ranges
from DT on imx6q after added imx6sx sdb pcie ep/rc
validation system support.
solution: Remove the imx6sx specification when get
the mem ranges from DT.

Signed-off-by: Richard Zhu &lt;r65037@freescale.com&gt;
(cherry picked from commit b42f60a06c77448a8a00b961fb8035c58a5ed8a1)
</pre>
</div>
</content>
</entry>
<entry>
<title>ENGR00324668 mmc: core: add delay for SD3.0 UHS mode switch</title>
<updated>2014-08-06T08:56:33+00:00</updated>
<author>
<name>Dong Aisheng</name>
<email>b29396@freescale.com</email>
</author>
<published>2014-08-06T05:04:09+00:00</published>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/litmus-rt-imx6.git/commit/?id=ef3bce5feb2ed36c9f4483287454d35ae330dbe3'/>
<id>ef3bce5feb2ed36c9f4483287454d35ae330dbe3</id>
<content type='text'>
We may meet the following errors with a SD3.0 DDR50 cards during reboot test.
mmc0: new ultra high speed DDR50 SDHC card at address aaaa
mmcblk0: mmc0:aaaa SU08G 7.40 GiB
mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
end_request: I/O error, dev mmcblk0, sector 0
.....
Buffer I/O error on device mmcblk0, logical block 0
 mmcblk0: unable to read partition table

The root cause is still unknown.
Since there's an errata of Sandisk eMMC card before that it requires delay for CMD6
for eMMC DDR mode to work stable, we also suspect the SD3.0 DDR requires similar delay.
(Still not confirmed by Sandisk)
By adding the delay, the overnight reboot test(run 2000+ times) did not
show the issue anymore. Originally it can easy show the error after about 20 times of
reboot test.

So this patch would be the temporary workaround for Sandisk SD3.0 DDR50 mode
unstable issue.

Signed-off-by: Dong Aisheng &lt;b29396@freescale.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We may meet the following errors with a SD3.0 DDR50 cards during reboot test.
mmc0: new ultra high speed DDR50 SDHC card at address aaaa
mmcblk0: mmc0:aaaa SU08G 7.40 GiB
mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
end_request: I/O error, dev mmcblk0, sector 0
.....
Buffer I/O error on device mmcblk0, logical block 0
 mmcblk0: unable to read partition table

The root cause is still unknown.
Since there's an errata of Sandisk eMMC card before that it requires delay for CMD6
for eMMC DDR mode to work stable, we also suspect the SD3.0 DDR requires similar delay.
(Still not confirmed by Sandisk)
By adding the delay, the overnight reboot test(run 2000+ times) did not
show the issue anymore. Originally it can easy show the error after about 20 times of
reboot test.

So this patch would be the temporary workaround for Sandisk SD3.0 DDR50 mode
unstable issue.

Signed-off-by: Dong Aisheng &lt;b29396@freescale.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ENGR00325794 [#1087] fix video memory mutex sharing issue</title>
<updated>2014-08-06T06:52:06+00:00</updated>
<author>
<name>Xianzhong</name>
<email>b07117@freescale.com</email>
</author>
<published>2014-08-01T10:44:20+00:00</published>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/litmus-rt-imx6.git/commit/?id=789d6703b1372ec59ddf65a7bc87bf28f9186acd'/>
<id>789d6703b1372ec59ddf65a7bc87bf28f9186acd</id>
<content type='text'>
the root cause is video memory mutex is not global variable,
it will cause video memory managment problem with mixed 2D/3D/VG.

kernel panic with multiple instances stress test running glesx_viv.sh.

Date: Jul 31, 2014
Signed-off-by: Xianzhong &lt;b07117@freescale.com&gt;
Acked-by: Jason Liu
(cherry picked from commit 9cec1cbd7ca2378e5c429f57d088d23d73d9c2f3)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
the root cause is video memory mutex is not global variable,
it will cause video memory managment problem with mixed 2D/3D/VG.

kernel panic with multiple instances stress test running glesx_viv.sh.

Date: Jul 31, 2014
Signed-off-by: Xianzhong &lt;b07117@freescale.com&gt;
Acked-by: Jason Liu
(cherry picked from commit 9cec1cbd7ca2378e5c429f57d088d23d73d9c2f3)
</pre>
</div>
</content>
</entry>
<entry>
<title>ENGR00325494 pcie:delay is requried after clks_en</title>
<updated>2014-08-06T02:51:56+00:00</updated>
<author>
<name>Richard Zhu</name>
<email>r65037@freescale.com</email>
</author>
<published>2014-08-01T11:40:03+00:00</published>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/litmus-rt-imx6.git/commit/?id=c8a6b97fa238d4cd79ae90c721c9e77eec05f71c'/>
<id>c8a6b97fa238d4cd79ae90c721c9e77eec05f71c</id>
<content type='text'>
- the async reset input need ref clock to sync internally,
when the ref clock comes after reset, internal synced reset
time is too short , cannot meet the requirement
so, ssp_en should be asserted at least 4us after ref clock stable.
- align to the community imx pcie driver, add the about
200us delay to make sure that it can allow the pcie clks
stabilize, when pcie clks are enabled on imx6q/dl/solo.

Signed-off-by: Richard Zhu &lt;r65037@freescale.com&gt;
(cherry picked from commit 5d9635c8d92b21bc12753517fa3e9884417b19be)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
- the async reset input need ref clock to sync internally,
when the ref clock comes after reset, internal synced reset
time is too short , cannot meet the requirement
so, ssp_en should be asserted at least 4us after ref clock stable.
- align to the community imx pcie driver, add the about
200us delay to make sure that it can allow the pcie clks
stabilize, when pcie clks are enabled on imx6q/dl/solo.

Signed-off-by: Richard Zhu &lt;r65037@freescale.com&gt;
(cherry picked from commit 5d9635c8d92b21bc12753517fa3e9884417b19be)
</pre>
</div>
</content>
</entry>
<entry>
<title>ENGR00325572 v4l2 capture: fix build issue for built-in modules</title>
<updated>2014-08-01T19:00:14+00:00</updated>
<author>
<name>Oliver Brown</name>
<email>oliver.brown@freescale.com</email>
</author>
<published>2014-08-01T18:46:36+00:00</published>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/litmus-rt-imx6.git/commit/?id=ebc42698e2beb03012af152474129dacd215ef98'/>
<id>ebc42698e2beb03012af152474129dacd215ef98</id>
<content type='text'>
Fix a build error for built-int modules do to missing inline declaration

Signed-off-by: Oliver Brown &lt;oliver.brown@freescale.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fix a build error for built-int modules do to missing inline declaration

Signed-off-by: Oliver Brown &lt;oliver.brown@freescale.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ENGR00325203 usb: chipidea: host: check if ci-&gt;hcd initialized before access it</title>
<updated>2014-08-01T08:13:30+00:00</updated>
<author>
<name>Li Jun</name>
<email>B47624@freescale.com</email>
</author>
<published>2014-07-31T06:01:40+00:00</published>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/litmus-rt-imx6.git/commit/?id=24f2a0187a52bfad75212a7b6a2cd107bde0d183'/>
<id>24f2a0187a52bfad75212a7b6a2cd107bde0d183</id>
<content type='text'>
When ci core driver enable runtime pm in probe, it's possible runtime suspend
will be started before otg fsm queue work get to run, in this case, host has not
been started yet so ci-&gt;hcd is NULL, but suspend routine will access it for save
ehci registers, which result in kernle panic, this patch adds pointer valid check.

Signed-off-by: Li Jun &lt;b47624@freescale.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When ci core driver enable runtime pm in probe, it's possible runtime suspend
will be started before otg fsm queue work get to run, in this case, host has not
been started yet so ci-&gt;hcd is NULL, but suspend routine will access it for save
ehci registers, which result in kernle panic, this patch adds pointer valid check.

Signed-off-by: Li Jun &lt;b47624@freescale.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ENGR00323682 MMC: Fixed boot_config overwritten by switch partition</title>
<updated>2014-07-21T14:24:53+00:00</updated>
<author>
<name>Ye.Li</name>
<email>B37916@freescale.com</email>
</author>
<published>2014-07-21T13:53:50+00:00</published>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/litmus-rt-imx6.git/commit/?id=50ef3db3e4c83bc7b0da05c1dac1af88328d73f4'/>
<id>50ef3db3e4c83bc7b0da05c1dac1af88328d73f4</id>
<content type='text'>
In MMC driver, two variables: boot_config and part_config  are used to
keep eCSD(179) PARTITION_CONFIG. The part_config is not updated when
set new boot_config, which causes the eCSD(179) is overwritten by
any following partition switching, so the new boot_config is lost.

Signed-off-by: Ye.Li &lt;B37916@freescale.com&gt;
(cherry picked from commit ed6ae43d513d211aba3ab6218feebbccbc33bdbd)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In MMC driver, two variables: boot_config and part_config  are used to
keep eCSD(179) PARTITION_CONFIG. The part_config is not updated when
set new boot_config, which causes the eCSD(179) is overwritten by
any following partition switching, so the new boot_config is lost.

Signed-off-by: Ye.Li &lt;B37916@freescale.com&gt;
(cherry picked from commit ed6ae43d513d211aba3ab6218feebbccbc33bdbd)
</pre>
</div>
</content>
</entry>
<entry>
<title>ENGR00323241 usb: chipidea: otg: delay 2s to decrease power.usage_count</title>
<updated>2014-07-18T08:28:31+00:00</updated>
<author>
<name>Li Jun</name>
<email>B47624@freescale.com</email>
</author>
<published>2014-07-18T08:16:09+00:00</published>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/litmus-rt-imx6.git/commit/?id=8532e80d479ef7ea61e288b321c10d1b14933196'/>
<id>8532e80d479ef7ea61e288b321c10d1b14933196</id>
<content type='text'>
There is 2s delay for controller resume from usb wakeup case already,
in OTG fsm mode, A-dev can start a new session via sys input file(means
not via usb wakeup), in this case, A-dev still need the 2s delay for
host root hub access registers, otherwise system will hang due to access
register at low power mode.

Signed-off-by: Li Jun &lt;b47624@freescale.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
There is 2s delay for controller resume from usb wakeup case already,
in OTG fsm mode, A-dev can start a new session via sys input file(means
not via usb wakeup), in this case, A-dev still need the 2s delay for
host root hub access registers, otherwise system will hang due to access
register at low power mode.

Signed-off-by: Li Jun &lt;b47624@freescale.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ENGR00322215 EPDC: kernel dump when do EPDC framebuffer unit test</title>
<updated>2014-07-18T01:14:31+00:00</updated>
<author>
<name>Fancy Fang</name>
<email>chen.fang@freescale.com</email>
</author>
<published>2014-07-17T07:22:39+00:00</published>
<link rel='alternate' type='text/html' href='http://rtsrv.cs.unc.edu/cgit/cgit.cgi/litmus-rt-imx6.git/commit/?id=ad0a08722750b31b594fec65e12439d911fa0a01'/>
<id>ad0a08722750b31b594fec65e12439d911fa0a01</id>
<content type='text'>
[&lt;80013b00&gt;] (unwind_backtrace+0x0/0xf4) from [&lt;80011524&gt;] (show_stack+0x10/0x14)
[&lt;80011524&gt;] (show_stack+0x10/0x14) from [&lt;8026bc4c&gt;] (Ldiv0+0x8/0x10)
[&lt;8026bc4c&gt;] (Ldiv0+0x8/0x10) from [&lt;802c1144&gt;] (pxp_dispatch_thread+0xd74/0x11f8)
[&lt;802c1144&gt;] (pxp_dispatch_thread+0xd74/0x11f8) from [&lt;80046a90&gt;] (kthread+0xb4/0xb8)
[&lt;80046a90&gt;] (kthread+0xb4/0xb8) from [&lt;8000e118&gt;] (ret_from_fork+0x14/0x3c)

This is caused by div by 0 in some corner cases. So add the
check before doing the division.

Signed-off-by: Fancy Fang &lt;chen.fang@freescale.com&gt;
(cherry picked from commit 2a5dfad5ff763d4eb8b33628ea96291ad4b95d5e)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
[&lt;80013b00&gt;] (unwind_backtrace+0x0/0xf4) from [&lt;80011524&gt;] (show_stack+0x10/0x14)
[&lt;80011524&gt;] (show_stack+0x10/0x14) from [&lt;8026bc4c&gt;] (Ldiv0+0x8/0x10)
[&lt;8026bc4c&gt;] (Ldiv0+0x8/0x10) from [&lt;802c1144&gt;] (pxp_dispatch_thread+0xd74/0x11f8)
[&lt;802c1144&gt;] (pxp_dispatch_thread+0xd74/0x11f8) from [&lt;80046a90&gt;] (kthread+0xb4/0xb8)
[&lt;80046a90&gt;] (kthread+0xb4/0xb8) from [&lt;8000e118&gt;] (ret_from_fork+0x14/0x3c)

This is caused by div by 0 in some corner cases. So add the
check before doing the division.

Signed-off-by: Fancy Fang &lt;chen.fang@freescale.com&gt;
(cherry picked from commit 2a5dfad5ff763d4eb8b33628ea96291ad4b95d5e)
</pre>
</div>
</content>
</entry>
</feed>
