| Message ID | 1447337532-18258-1-git-send-email-geert+renesas@glider.be (mailing list archive) |
|---|---|
| State | Accepted |
| Delegated to: | Geert Uytterhoeven |
| Headers | show |
On Thu, Nov 12, 2015 at 3:12 PM, Geert Uytterhoeven <geert+renesas@glider.be> wrote: > Cfr. Manual Errata for Rev 0.50 of the R-Car Gen3 datasheet. > > This has no user-visible impact. > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> Acked-by: Linus Walleij <linus.walleij@linaro.org> I count on you to continue to accumulate SH-PFC patches and send me pull requests for the v4.5 cycle, OK? Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Linus, On Tue, Nov 17, 2015 at 2:44 PM, Linus Walleij <linus.walleij@linaro.org> wrote: > On Thu, Nov 12, 2015 at 3:12 PM, Geert Uytterhoeven > <geert+renesas@glider.be> wrote: > >> Cfr. Manual Errata for Rev 0.50 of the R-Car Gen3 datasheet. >> >> This has no user-visible impact. >> >> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> > > Acked-by: Linus Walleij <linus.walleij@linaro.org> Thanks! > I count on you to continue to accumulate SH-PFC patches and send > me pull requests for the v4.5 cycle, OK? Sure! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Laurent-san Thanks for your kindness support! I don't mean to bother you! But as you know, we have reported to you before, have some problems related to DU driver. We couldn't show a image on the display. We found the messages as showed below: ----- Boot logs on Rcar-H2: rcar-du feb00000.display: failed to initialize encoder /i2c@e6520000/hdmi@39 (-38), skipping rcar-du feb00000.display: fb0: frame buffer device ----- Boot logs on Rcar-M2: rcar-du feb00000.display: failed to initialize encoder /i2c@e6530000/hdmi@39 (-g rcar-du feb00000.display: error: no encoder could be initialized rcar-du feb00000.display: failed to initialize DRM/KMS (-22) rcar-du: probe of feb00000.display failed with error -22 ----- This is tested on linux stable v4.3. Please have a look when you have time. Best Regards, Jinso/Cao Minh Hiep. -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello, and sorry for the late reply. On Friday 20 November 2015 16:39:28 Cao Minh Hiep wrote: > Hi Laurent-san > > Thanks for your kindness support! > I don't mean to bother you! You're not bothering me at all :-) > But as you know, we have reported to you before, have some problems > related to DU driver. > We couldn't show a image on the display. We found the messages as showed > below: > ----- > Boot logs on Rcar-H2: > rcar-du feb00000.display: failed to initialize encoder > /i2c@e6520000/hdmi@39 (-38), skipping > rcar-du feb00000.display: fb0: frame buffer device > ----- > Boot logs on Rcar-M2: > rcar-du feb00000.display: failed to initialize encoder > /i2c@e6530000/hdmi@39 (-g > rcar-du feb00000.display: error: no encoder could be initialized > rcar-du feb00000.display: failed to initialize DRM/KMS (-22) > rcar-du: probe of feb00000.display failed with error -22 > ----- > > This is tested on linux stable v4.3. > Please have a look when you have time. Have you enabled CONFIG_DRM_RCAR_HDMI ?
Hi Laurent-san Thanks for your reply! On 2015?11?25? 10:08, Laurent Pinchart wrote: > Hello, and sorry for the late reply. No, problems! > On Friday 20 November 2015 16:39:28 Cao Minh Hiep wrote: >> Hi Laurent-san >> >> Thanks for your kindness support! >> I don't mean to bother you! > You're not bothering me at all :-) > >> But as you know, we have reported to you before, have some problems >> related to DU driver. >> We couldn't show a image on the display. We found the messages as showed >> below: >> ----- >> Boot logs on Rcar-H2: >> rcar-du feb00000.display: failed to initialize encoder >> /i2c@e6520000/hdmi@39 (-38), skipping >> rcar-du feb00000.display: fb0: frame buffer device >> ----- >> Boot logs on Rcar-M2: >> rcar-du feb00000.display: failed to initialize encoder >> /i2c@e6530000/hdmi@39 (-g >> rcar-du feb00000.display: error: no encoder could be initialized >> rcar-du feb00000.display: failed to initialize DRM/KMS (-22) >> rcar-du: probe of feb00000.display failed with error -22 >> ----- >> >> This is tested on linux stable v4.3. >> Please have a look when you have time. > Have you enabled CONFIG_DRM_RCAR_HDMI ? > Yes, These initialize logs are taken with default config that CONFIG_DRM_RCAR_HDMI disabled at v4.3. But when we enabled CONFIG_DRM_RCAR_HDMI, then we still could not show any images on HDMI or RGB Screen. I found that, CONFIG_DRM_RCAR_HDMI have already enabled in default config at v4.4-rc2. But have a error message as below and DU is still not improved(still can not show images on screen). On Rcar-H2(Lager): [drm] Initialized drm 1.1.0 20060810 [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] No driver support for vblank timestamp query. rcar-du feb00000.display: failed to initialize DRM/KMS (-517) rcar-du feb00000.display: fb0: frame buffer device [drm] Initialized rcar-du 1.0.0 20130110 on minor 0 On Rcar-M2(Koelsch): [drm] Initialized drm 1.1.0 20060810 [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] No driver support for vblank timestamp query. rcar-du feb00000.display: failed to initialize DRM/KMS (-517) rcar-du feb00000.display: fb0: frame buffer device [drm] Initialized rcar-du 1.0.0 20130110 on minor 0 Thank you! Jinso/Hiep -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello, On Thursday 26 November 2015 11:48:22 Cao Minh Hiep wrote: > On 2015?11?25? 10:08, Laurent Pinchart wrote: > > On Friday 20 November 2015 16:39:28 Cao Minh Hiep wrote: > >> Hi Laurent-san > >> > >> Thanks for your kindness support! > >> I don't mean to bother you! > > > > You're not bothering me at all :-) > > > >> But as you know, we have reported to you before, have some problems > >> related to DU driver. > >> We couldn't show a image on the display. We found the messages as showed > >> below: > >> ----- > >> Boot logs on Rcar-H2: > >> rcar-du feb00000.display: failed to initialize encoder > >> /i2c@e6520000/hdmi@39 (-38), skipping > >> rcar-du feb00000.display: fb0: frame buffer device > >> ----- > >> Boot logs on Rcar-M2: > >> rcar-du feb00000.display: failed to initialize encoder > >> /i2c@e6530000/hdmi@39 (-g > >> rcar-du feb00000.display: error: no encoder could be initialized > >> rcar-du feb00000.display: failed to initialize DRM/KMS (-22) > >> rcar-du: probe of feb00000.display failed with error -22 > >> ----- > >> > >> This is tested on linux stable v4.3. > >> Please have a look when you have time. > > > > Have you enabled CONFIG_DRM_RCAR_HDMI ? > > Yes, These initialize logs are taken with default config that > CONFIG_DRM_RCAR_HDMI disabled at v4.3. > But when we enabled CONFIG_DRM_RCAR_HDMI, then we still could not show > any images on HDMI or RGB Screen. > > I found that, CONFIG_DRM_RCAR_HDMI have already enabled in default > config at v4.4-rc2. > But have a error message as below and DU is still not improved(still can > not show images on screen). > > > On Rcar-H2(Lager): > > [drm] Initialized drm 1.1.0 20060810 > [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [drm] No driver support for vblank timestamp query. > rcar-du feb00000.display: failed to initialize DRM/KMS (-517) > rcar-du feb00000.display: fb0: frame buffer device > [drm] Initialized rcar-du 1.0.0 20130110 on minor 0 > > On Rcar-M2(Koelsch): > > [drm] Initialized drm 1.1.0 20060810 > [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [drm] No driver support for vblank timestamp query. > rcar-du feb00000.display: failed to initialize DRM/KMS (-517) > rcar-du feb00000.display: fb0: frame buffer device > [drm] Initialized rcar-du 1.0.0 20130110 on minor 0 -517 (-EPROBE_DEFER) means that probe deferral is requested because a required dependency is not present. Have you compiled and loaded the adv7511 driver (CONFIG_DRM_I2C_ADV7511) ?
Hello Laurent-san, >>>> But as you know, we have reported to you before, have some problems >>>> related to DU driver. >>>> We couldn't show a image on the display. We found the messages as showed >>>> below: >>>> ----- >>>> Boot logs on Rcar-H2: >>>> rcar-du feb00000.display: failed to initialize encoder >>>> /i2c@e6520000/hdmi@39 (-38), skipping >>>> rcar-du feb00000.display: fb0: frame buffer device >>>> ----- >>>> Boot logs on Rcar-M2: >>>> rcar-du feb00000.display: failed to initialize encoder >>>> /i2c@e6530000/hdmi@39 (-g >>>> rcar-du feb00000.display: error: no encoder could be initialized >>>> rcar-du feb00000.display: failed to initialize DRM/KMS (-22) >>>> rcar-du: probe of feb00000.display failed with error -22 >>>> ----- >>>> >>>> This is tested on linux stable v4.3. >>>> Please have a look when you have time. >>> Have you enabled CONFIG_DRM_RCAR_HDMI ? >> Yes, These initialize logs are taken with default config that >> CONFIG_DRM_RCAR_HDMI disabled at v4.3. >> But when we enabled CONFIG_DRM_RCAR_HDMI, then we still could not show >> any images on HDMI or RGB Screen. >> >> I found that, CONFIG_DRM_RCAR_HDMI have already enabled in default >> config at v4.4-rc2. >> But have a error message as below and DU is still not improved(still can >> not show images on screen). >> >> >> On Rcar-H2(Lager): >> >> [drm] Initialized drm 1.1.0 20060810 >> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). >> [drm] No driver support for vblank timestamp query. >> rcar-du feb00000.display: failed to initialize DRM/KMS (-517) >> rcar-du feb00000.display: fb0: frame buffer device >> [drm] Initialized rcar-du 1.0.0 20130110 on minor 0 >> >> On Rcar-M2(Koelsch): >> >> [drm] Initialized drm 1.1.0 20060810 >> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). >> [drm] No driver support for vblank timestamp query. >> rcar-du feb00000.display: failed to initialize DRM/KMS (-517) >> rcar-du feb00000.display: fb0: frame buffer device >> [drm] Initialized rcar-du 1.0.0 20130110 on minor 0 > -517 (-EPROBE_DEFER) means that probe deferral is requested because a required > dependency is not present. Have you compiled and loaded the adv7511 driver > (CONFIG_DRM_I2C_ADV7511) ? > Yes, CONFIG_DRM_I2C_ADV7511=y has already enabled in default config at v4.4-rc2. I also have enabled CONFIG_DRM_SHMOBILE and CONFIG_FB_SH_MOBILE_HDMI then test. But It has nothing change. Is there other configuration or reason could we think? we usually use Morimoto-san's the bmap tool to show a image as below: ./bmap /dev/fb0 ./hdmi.bmp It is good for showing a image in bsp version ltsi-v3.10.31-rcar/gen2-1.9.5. Thank you! Jinso/Hiep -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Laurent-san Sorry to bother you again! On 2015?11?27? 15:13, Cao Minh Hiep wrote: > Hello Laurent-san, > > >>>>> But as you know, we have reported to you before, have some problems >>>>> related to DU driver. >>>>> We couldn't show a image on the display. We found the messages as >>>>> showed >>>>> below: >>>>> ----- >>>>> Boot logs on Rcar-H2: >>>>> rcar-du feb00000.display: failed to initialize encoder >>>>> /i2c@e6520000/hdmi@39 (-38), skipping >>>>> rcar-du feb00000.display: fb0: frame buffer device >>>>> ----- >>>>> Boot logs on Rcar-M2: >>>>> rcar-du feb00000.display: failed to initialize encoder >>>>> /i2c@e6530000/hdmi@39 (-g >>>>> rcar-du feb00000.display: error: no encoder could be initialized >>>>> rcar-du feb00000.display: failed to initialize DRM/KMS (-22) >>>>> rcar-du: probe of feb00000.display failed with error -22 >>>>> ----- >>>>> >>>>> This is tested on linux stable v4.3. >>>>> Please have a look when you have time. >>>> Have you enabled CONFIG_DRM_RCAR_HDMI ? >>> Yes, These initialize logs are taken with default config that >>> CONFIG_DRM_RCAR_HDMI disabled at v4.3. >>> But when we enabled CONFIG_DRM_RCAR_HDMI, then we still could not show >>> any images on HDMI or RGB Screen. >>> >>> I found that, CONFIG_DRM_RCAR_HDMI have already enabled in default >>> config at v4.4-rc2. >>> But have a error message as below and DU is still not improved(still >>> can >>> not show images on screen). >>> >>> >>> On Rcar-H2(Lager): >>> >>> [drm] Initialized drm 1.1.0 20060810 >>> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). >>> [drm] No driver support for vblank timestamp query. >>> rcar-du feb00000.display: failed to initialize DRM/KMS (-517) >>> rcar-du feb00000.display: fb0: frame buffer device >>> [drm] Initialized rcar-du 1.0.0 20130110 on minor 0 >>> >>> On Rcar-M2(Koelsch): >>> >>> [drm] Initialized drm 1.1.0 20060810 >>> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). >>> [drm] No driver support for vblank timestamp query. >>> rcar-du feb00000.display: failed to initialize DRM/KMS (-517) >>> rcar-du feb00000.display: fb0: frame buffer device >>> [drm] Initialized rcar-du 1.0.0 20130110 on minor 0 >> -517 (-EPROBE_DEFER) means that probe deferral is requested because a >> required >> dependency is not present. Have you compiled and loaded the adv7511 >> driver >> (CONFIG_DRM_I2C_ADV7511) ? >> > Yes, CONFIG_DRM_I2C_ADV7511=y has already enabled in default config at > v4.4-rc2. > I also have enabled CONFIG_DRM_SHMOBILE and CONFIG_FB_SH_MOBILE_HDMI > then test. > But It has nothing change. > Is there other configuration or reason could we think? > Does this problem happen on your board? If not, Could you please send me your config file?. Thank you! Jinso/Hiep -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello Laurent-san
We have tested the DMAC driver on Lager, Koelsch at Upstream-v4.4-rc2
and LTSI-v4.1.13-rc1.
In test case of unbind/rebind dmac device, we found the warning
messages as below:
"WARNING: CPU: 1 PID: 2171 at drivers/dma/dmaengine.c:971
dma_async_device_unregister+0x8c/0xf)
dma_async_device_unregister called while 1 clients hold a reference
CPU: 1 PID: 2171 Comm: bash Not tainted 4.1.13-ltsi-00392-g5308b95 #1
Hardware name: Generic R8A7790 (Flattened Device Tree)
Backtrace:
[<c0012f88>] (dump_backtrace) from [<c0013130>] (show_stack+0x18/0x1c)
r7:c06e2408 r6:ed0eb080 r5:00000009 r4:00000000
[<c0013118>] (show_stack) from [<c059a4d8>] (dump_stack+0x78/0x94)
[<c059a460>] (dump_stack) from [<c0026274>] (warn_slowpath_common+0x88/0xb4)
...."
I attach the test log files of Lager and Koelsch board at LTSI
version.(Upstream is also the same)
Lager_unbind-rebind-DMA_error-log.txt
KOELSCH_unbind-rebind-DMA_error-log.txt
We found that, On Upstream version, This bug happened since the DMAC
supported.
Please have a look at this when you have time!
Best regards,
Jinso/Hiep
--------------------------------------------ec700000.dma-controll ------------------------------------
root@linaro-nano:~# uname -a
Linux linaro-nano 4.1.13-ltsi-00392-gbffcbe0 #14 SMP Thu Dec 3 11:08:10 JST 2015 armv7l armv7l armv7lx
root@linaro-nano:~# cd /sys/bus/platform/drivers/rcar-dmac
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
er > unbind-nano:/sys/bus/platform/drivers/rcar-dmac# echo ec700000.dma-controll
------------[ cut here ]------------
WARNING: CPU: 1 PID: 1706 at drivers/dma/dmaengine.c:971 dma_async_device_unregister+0x8c/0xf0()
dma_async_device_unregister called while 1 clients hold a reference
Modules linked in:
CPU: 1 PID: 1706 Comm: bash Not tainted 4.1.13-ltsi-00392-gbffcbe0 #14
Hardware name: Generic R8A7791 (Flattened Device Tree)
Backtrace:
[<c0013148>] (dump_backtrace) from [<c0013368>] (show_stack+0x18/0x1c)
r7:c0674f2d r6:ee0bc640 r5:00000009 r4:00000000
[<c0013350>] (show_stack) from [<c05005c0>] (dump_stack+0x78/0x94)
[<c0500548>] (dump_stack) from [<c00272a0>] (warn_slowpath_common+0x8c/0xb8)
r5:00000009 r4:ede31dd0
[<c0027214>] (warn_slowpath_common) from [<c0027304>] (warn_slowpath_fmt+0x38/0x40)
r9:000be408 r8:ede31f80 r7:c074ae50 r6:c075dd25 r5:ee221b10 r4:ee02b810
[<c00272d0>] (warn_slowpath_fmt) from [<c02727fc>] (dma_async_device_unregister+0x8c/0xf0)
r3:c0565eb4 r2:c067f050
[<c0272770>] (dma_async_device_unregister) from [<c02761a8>] (rcar_dmac_remove+0x24/0x38)
r6:c0742610 r5:ee221b10 r4:ee995e00
[<c0276184>] (rcar_dmac_remove) from [<c02dc6ec>] (platform_drv_remove+0x20/0x38)
r5:c0742610 r4:ee995e10
[<c02dc6cc>] (platform_drv_remove) from [<c02daa68>] (__device_release_driver+0x84/0xe8)
r5:c0742610 r4:ee995e10
[<c02da9e4>] (__device_release_driver) from [<c02daaf0>] (device_release_driver+0x24/0x30)
r5:ee995e10 r4:ee995e44
[<c02daacc>] (device_release_driver) from [<c02d9b3c>] (unbind_store+0x60/0x94)
r5:ee995e10 r4:00000018
[<c02d9adc>] (unbind_store) from [<c02d9278>] (drv_attr_store+0x2c/0x38)
r7:edc8b98c r6:edc8b980 r5:eeba93c0 r4:00000018
[<c02d924c>] (drv_attr_store) from [<c0125534>] (sysfs_kf_write+0x40/0x4c)
[<c01254f4>] (sysfs_kf_write) from [<c0124aac>] (kernfs_fop_write+0x120/0x180)
[<c012498c>] (kernfs_fop_write) from [<c00cd06c>] (__vfs_write+0x34/0xdc)
r9:ede30000 r8:c000ff44 r7:00000018 r6:ede31f80 r5:c012498c r4:ee9fec40
[<c00cd038>] (__vfs_write) from [<c00cd794>] (vfs_write+0xb4/0x13c)
r7:ede31f80 r6:000be408 r5:ee9fec40 r4:00000018
[<c00cd6e0>] (vfs_write) from [<c00cdeb8>] (SyS_write+0x50/0x90)
r9:ede30000 r8:c000ff44 r7:00000018 r6:000be408 r5:ee9fec40 r4:ee9fec40
[<c00cde68>] (SyS_write) from [<c000fda0>] (ret_fast_syscall+0x0/0x3c)
r7:00000004 r6:b6ec4b58 r5:000be408 r4:00000018
---[ end trace b8804040772e70dd ]---
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
lert@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# ls -d ec700000.dma-control
ls: cannot access ec700000.dma-controller: No such file or directory
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
er > bindro-nano:/sys/bus/platform/drivers/rcar-dmac# echo ec700000.dma-controll
rcar-dmac ec700000.dma-controller: DMAOR initialization failed.
rcar-dmac ec700000.dma-controller: failed to reset device
rcar-dmac: probe of ec700000.dma-controller failed with error -5
-bash: echo: write error: No such device
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
lert@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# ls -d ec700000.dma-control
ls: cannot access ec700000.dma-controller: No such file or directory
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# cd
root@linaro-nano:~# ls
UnixBench5.1.3.tgz board-koelsch data lmbench-3.0-a9.tgz unbind
bind board-lager hdmi.bmp test-char
root@linaro-nano:~#
--------------------------------------------e6700000.dma-controll------------------------------------
root@linaro-nano:~# uname -a
Linux linaro-nano 4.1.13-ltsi-00392-gbffcbe0 #14 SMP Thu Dec 3 11:08:10 JST 2015 armv7l armv7l armv7lx
root@linaro-nano:~#
root@linaro-nano:~#
root@linaro-nano:~# cd /sys/bus/platform/drivers/rcar-dmac
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
er > unbind-nano:/sys/bus/platform/drivers/rcar-dmac# echo e6700000.dma-controll
------------[ cut here ]------------
WARNING: CPU: 0 PID: 1705 at drivers/dma/dmaengine.c:971 dma_async_device_unregister+0x8c/0xf0()
dma_async_device_unregister called while 1 clients hold a reference
Modules linked in:
CPU: 0 PID: 1705 Comm: bash Not tainted 4.1.13-ltsi-00392-gbffcbe0 #14
Hardware name: Generic R8A7791 (Flattened Device Tree)
Backtrace:
[<c0013148>] (dump_backtrace) from [<c0013368>] (show_stack+0x18/0x1c)
r7:c0674f2d r6:eebbd540 r5:00000009 r4:00000000
[<c0013350>] (show_stack) from [<c05005c0>] (dump_stack+0x78/0x94)
[<c0500548>] (dump_stack) from [<c00272a0>] (warn_slowpath_common+0x8c/0xb8)
r5:00000009 r4:eebd1dd0
[<c0027214>] (warn_slowpath_common) from [<c0027304>] (warn_slowpath_fmt+0x38/0x40)
r9:000be408 r8:eebd1f80 r7:c074ae50 r6:c075dd25 r5:ee050810 r4:eea83010
[<c00272d0>] (warn_slowpath_fmt) from [<c02727fc>] (dma_async_device_unregister+0x8c/0xf0)
r3:c0565eb4 r2:c067f050
[<c0272770>] (dma_async_device_unregister) from [<c02761a8>] (rcar_dmac_remove+0x24/0x38)
r6:c0742610 r5:ee050810 r4:ee92e600
[<c0276184>] (rcar_dmac_remove) from [<c02dc6ec>] (platform_drv_remove+0x20/0x38)
r5:c0742610 r4:ee92e610
[<c02dc6cc>] (platform_drv_remove) from [<c02daa68>] (__device_release_driver+0x84/0xe8)
r5:c0742610 r4:ee92e610
[<c02da9e4>] (__device_release_driver) from [<c02daaf0>] (device_release_driver+0x24/0x30)
r5:ee92e610 r4:ee92e644
[<c02daacc>] (device_release_driver) from [<c02d9b3c>] (unbind_store+0x60/0x94)
r5:ee92e610 r4:00000018
[<c02d9adc>] (unbind_store) from [<c02d9278>] (drv_attr_store+0x2c/0x38)
r7:ee2fd48c r6:ee2fd480 r5:ee313e80 r4:00000018
[<c02d924c>] (drv_attr_store) from [<c0125534>] (sysfs_kf_write+0x40/0x4c)
[<c01254f4>] (sysfs_kf_write) from [<c0124aac>] (kernfs_fop_write+0x120/0x180)
[<c012498c>] (kernfs_fop_write) from [<c00cd06c>] (__vfs_write+0x34/0xdc)
r9:eebd0000 r8:c000ff44 r7:00000018 r6:eebd1f80 r5:c012498c r4:edcd6040
[<c00cd038>] (__vfs_write) from [<c00cd794>] (vfs_write+0xb4/0x13c)
r7:eebd1f80 r6:000be408 r5:edcd6040 r4:00000018
[<c00cd6e0>] (vfs_write) from [<c00cdeb8>] (SyS_write+0x50/0x90)
r9:eebd0000 r8:c000ff44 r7:00000018 r6:000be408 r5:edcd6040 r4:edcd6040
[<c00cde68>] (SyS_write) from [<c000fda0>] (ret_fast_syscall+0x0/0x3c)
r7:00000004 r6:b6ee1b58 r5:000be408 r4:00000018
---[ end trace cb78c9678d128192 ]---
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
lert@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# ls -d e6700000.dma-control
ls: cannot access e6700000.dma-controller: No such file or directory
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
er > bindro-nano:/sys/bus/platform/drivers/rcar-dmac# echo e6700000.dma-controll
rcar-dmac e6700000.dma-controller: DMAOR initialization failed.
rcar-dmac e6700000.dma-controller: failed to reset device
rcar-dmac: probe of e6700000.dma-controller failed with error -5
-bash: echo: write error: No such device
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
lert@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# ls -d e6700000.dma-control
ls: cannot access e6700000.dma-controller: No such file or directory
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# ls
bind ec700000.dma-controller uevent
e6720000.dma-controller ec720000.dma-controller unbind
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# cd
root@linaro-nano:~# ls
UnixBench5.1.3.tgz board-koelsch data lmbench-3.0-a9.tgz unbind
bind board-lager hdmi.bmp test-char
root@linaro-nano:~#
--------------------------------------------e6720000.dma-controll------------------------------------
root@linaro-nano:~# uname -a
Linux linaro-nano 4.1.13-ltsi-00392-gbffcbe0 #14 SMP Thu Dec 3 11:08:10 JST 2015 armv7l armv7l armv7lx
root@linaro-nano:~#
root@linaro-nano:~# cd /sys/bus/platform/drivers/rcar-dmac
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# ls
bind ec700000.dma-controller unbind
e6700000.dma-controller ec720000.dma-controller
e6720000.dma-controller uevent
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
er > unbind-nano:/sys/bus/platform/drivers/rcar-dmac# echo e6720000.dma-controll
------------[ cut here ]------------
WARNING: CPU: 1 PID: 1705 at drivers/dma/dmaengine.c:971 dma_async_device_unregister+0x8c/0xf0()
dma_async_device_unregister called while 1 clients hold a reference
Modules linked in:
CPU: 1 PID: 1705 Comm: bash Not tainted 4.1.13-ltsi-00392-gbffcbe0 #14
Hardware name: Generic R8A7791 (Flattened Device Tree)
Backtrace:
[<c0013148>] (dump_backtrace) from [<c0013368>] (show_stack+0x18/0x1c)
r7:c0674f2d r6:eebb8040 r5:00000009 r4:00000000
[<c0013350>] (show_stack) from [<c05005c0>] (dump_stack+0x78/0x94)
[<c0500548>] (dump_stack) from [<c00272a0>] (warn_slowpath_common+0x8c/0xb8)
r5:00000009 r4:ee3dddd0
[<c0027214>] (warn_slowpath_common) from [<c0027304>] (warn_slowpath_fmt+0x38/0x40)
r9:000be408 r8:ee3ddf80 r7:c074ae50 r6:c075dd25 r5:ee1a1a10 r4:ee91a010
[<c00272d0>] (warn_slowpath_fmt) from [<c02727fc>] (dma_async_device_unregister+0x8c/0xf0)
r3:c0565eb4 r2:c067f050
[<c0272770>] (dma_async_device_unregister) from [<c02761a8>] (rcar_dmac_remove+0x24/0x38)
r6:c0742610 r5:ee1a1a10 r4:ee92e200
[<c0276184>] (rcar_dmac_remove) from [<c02dc6ec>] (platform_drv_remove+0x20/0x38)
r5:c0742610 r4:ee92e210
[<c02dc6cc>] (platform_drv_remove) from [<c02daa68>] (__device_release_driver+0x84/0xe8)
r5:c0742610 r4:ee92e210
[<c02da9e4>] (__device_release_driver) from [<c02daaf0>] (device_release_driver+0x24/0x30)
r5:ee92e210 r4:ee92e244
[<c02daacc>] (device_release_driver) from [<c02d9b3c>] (unbind_store+0x60/0x94)
r5:ee92e210 r4:00000018
[<c02d9adc>] (unbind_store) from [<c02d9278>] (drv_attr_store+0x2c/0x38)
r7:ee3a44cc r6:ee3a44c0 r5:edc9d9c0 r4:00000018
[<c02d924c>] (drv_attr_store) from [<c0125534>] (sysfs_kf_write+0x40/0x4c)
[<c01254f4>] (sysfs_kf_write) from [<c0124aac>] (kernfs_fop_write+0x120/0x180)
[<c012498c>] (kernfs_fop_write) from [<c00cd06c>] (__vfs_write+0x34/0xdc)
r9:ee3dc000 r8:c000ff44 r7:00000018 r6:ee3ddf80 r5:c012498c r4:edc5b4c0
[<c00cd038>] (__vfs_write) from [<c00cd794>] (vfs_write+0xb4/0x13c)
r7:ee3ddf80 r6:000be408 r5:edc5b4c0 r4:00000018
[<c00cd6e0>] (vfs_write) from [<c00cdeb8>] (SyS_write+0x50/0x90)
r9:ee3dc000 r8:c000ff44 r7:00000018 r6:000be408 r5:edc5b4c0 r4:edc5b4c0
[<c00cde68>] (SyS_write) from [<c000fda0>] (ret_fast_syscall+0x0/0x3c)
r7:00000004 r6:b6ed2b58 r5:000be408 r4:00000018
---[ end trace 1cde6e25404aa85e ]---
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
lert@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# ls -d e6720000.dma-control
ls: cannot access e6720000.dma-controller: No such file or directory
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
er > bindro-nano:/sys/bus/platform/drivers/rcar-dmac# echo e6720000.dma-controll
rcar-dmac e6720000.dma-controller: DMAOR initialization failed.
rcar-dmac e6720000.dma-controller: failed to reset device
rcar-dmac: probe of e6720000.dma-controller failed with error -5
-bash: echo: write error: No such device
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
lert@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# ls -d e6720000.dma-control
ls: cannot access e6720000.dma-controller: No such file or directory
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# ls
bind ec700000.dma-controller uevent
e6700000.dma-controller ec720000.dma-controller unbind
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# cd
root@linaro-nano:~# ls
UnixBench5.1.3.tgz board-koelsch data lmbench-3.0-a9.tgz unbind
bind board-lager hdmi.bmp test-char
root@linaro-nano:~#
--------------------------------------------ec700000.dma-controll ------------------------------------
LAGER SPI_LOADER V0.28 2014.09.29
DEVICE S25FL512
U-Boot 2013.01.01-g46367b1 (Feb 02 2015 - 11:09:08)
CPU: Renesas Electronics R8A7790 rev 2.0
Board: Lager Board
DRAM: 2 GiB
MMC: sh_mmcif: 0, sh-sdhi: 1, sh-sdhi: 2
SF: Detected S25FL512S with page size 256 KiB, total 64 MiB
In: serial
Out: serial
Err: serial
Net: sh_eth
=>
=> bootp;bootm
sh_eth Waiting for PHY auto negotiation to complete.. done
sh_eth: 100Base/Full
BOOTP broadcast 1
DHCP client bound to address 172.16.1.81
Using sh_eth device
TFTP from server 172.16.1.85; our IP address is 172.16.1.81
Filename 'lager/uImage.dtb'.
Load address: 0x40007fc0
Loading: #################################################################
#################################################################
#################################################################
#################################################################
########
1.7 MiB/s
done
Bytes transferred = 3927922 (3bef72 hex)
## Booting kernel from Legacy Image at 40007fc0 ...
Image Name: Linux-4.1.13-ltsi-00392-g5308b95
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3927858 Bytes = 3.7 MiB
Load Address: 40008000
Entry Point: 40008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
Booting Linux on physical CPU 0x0
Linux version 4.1.13-ltsi-00392-g5308b95 (nguyen@ky) (gcc version 4.9.2 20140904 (prerelease)5
CPU: ARMv7 Processor [413fc0f2] revision 2 (ARMv7), cr=10c5307d
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
Machine model: Lager
Ignoring memory block 0x140000000 - 0x200000000
debug: ignoring loglevel setting.
Memory policy: Data cache writealloc
On node 0 totalpages: 262144
free_area_init_node: node 0, pgdat c07ac480, node_mem_map eeff9000
Normal zone: 1520 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 194560 pages, LIFO batch:31
HighMem zone: 67584 pages, LIFO batch:15
PERCPU: Embedded 9 pages/cpu @eef8c000 s15872 r0 d20992 u36864
pcpu-alloc: s15872 r0 d20992 u36864 alloc=9*4096
pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260624
Kernel command line: console=ttySC0,38400 ignore_loglevel rw root=/dev/nfs ip=dhcp
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1031044K/1048576K available (5728K kernel code, 223K rwdata, 1584K rodata, 288K init,)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xf0000000 - 0xff000000 ( 240 MB)
lowmem : 0xc0000000 - 0xef800000 ( 760 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
.text : 0xc0008000 - 0xc072d03c (7317 kB)
.init : 0xc072e000 - 0xc0776000 ( 288 kB)
.data : 0xc0776000 - 0xc07ade00 ( 224 kB)
.bss : 0xc07b0000 - 0xc07e1744 ( 198 kB)
Hierarchical RCU implementation.
Additional per-CPU info printed with stalls.
NR_IRQS:16 nr_irqs:16 16
Architected cp15 timer(s) running at 10.00MHz (virt).
clocksource arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x24e6a1710, max_idle_ns: 44s
sched_clock: 56 bits at 10MHz, resolution 100ns, wraps every 4398046511100ns
Switching to timer-based delay loop, resolution 100ns
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 20.00 BogoMIPS (lp)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
CPU: Testing write buffer coherency: ok
CPU0: update cpu_capacity 1535
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x40009000 - 0x40009058
CPU1: update cpu_capacity 1535
CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
CPU2: update cpu_capacity 1535
CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
CPU3: update cpu_capacity 1535
CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
CPU4: failed to boot: -22
CPU5: failed to boot: -22
CPU6: failed to boot: -22
CPU7: failed to boot: -22
Brought up 4 CPUs
SMP: Total of 4 processors activated (80.00 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 s
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
renesas_irqc e61c0000.interrupt-controller: driving 4 irqs
sh-pfc e6060000.pfc: r8a77900_pfc support registered
No ATAGs?
hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 8 bytes.
IRQ2 is asserted, installing da9063/da9210 regulator quirk
gpio-regulator regulator@2: Could not obtain regulator setting GPIOs: -517
gpio-regulator regulator@4: Could not obtain regulator setting GPIOs: -517
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c-sh_mobile e6500000.i2c: I2C adapter 4, bus speed 100000 Hz
i2c-sh_mobile e6510000.i2c: I2C adapter 5, bus speed 100000 Hz
i2c-sh_mobile e6520000.i2c: I2C adapter 6, bus speed 100000 Hz
i2c 7-0058: Masking da9063 interrupt sources
i2c 7-0068: Masking da9210 interrupt sources
i2c 7-0068: IRQ2 is not asserted, removing quirk
i2c-sh_mobile e60b0000.i2c: I2C adapter 7, bus speed 100000 Hz
media: Linux media interface: v0.10
Linux video capture interface: v2.00
sh_cmt ffca0000.timer: ch0: used for clock events
sh_cmt ffca0000.timer: ch1: used as clock source
clocksource ffca0000.timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462s
Advanced Linux Sound Architecture Driver Initialized.
cfg80211: Calling CRDA to update world regulatory domain
Switched to clocksource arch_sys_counter
NET: Registered protocol family 2
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
futex hash table entries: 2048 (order: 5, 131072 bytes)
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
nfs4filelayout_init: NFSv4 File Layout Driver Registering...
nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
bounce: pool size: 64 pages
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
gpio_rcar e6050000.gpio: driving 32 GPIOs
gpio_rcar e6051000.gpio: driving 32 GPIOs
gpio_rcar e6052000.gpio: driving 32 GPIOs
gpio_rcar e6053000.gpio: driving 32 GPIOs
gpio_rcar e6054000.gpio: driving 32 GPIOs
gpio_rcar e6055000.gpio: driving 32 GPIOs
pci-rcar-gen2 ee090000.pci: PCI: bus0 revision 11
pci-rcar-gen2 ee090000.pci: PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0xee080000-0xee0810ff]
pci_bus 0000:00: root bus resource [mem 0xee080000-0xee0810ff]
pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
pci 0000:00:00.0: [1033:0000] type 00 class 0x060000
pci 0000:00:00.0: reg 0x10: [mem 0xee090800-0xee090bff]
pci 0000:00:00.0: reg 0x14: [mem 0x40000000-0x7fffffff pref]
pci 0000:00:01.0: [1033:0035] type 00 class 0x0c0310
pci 0000:00:01.0: reg 0x10: [mem 0x00000000-0x00000fff]
pci 0000:00:01.0: supports D1 D2
pci 0000:00:01.0: PME# supported from D0 D1 D2 D3hot
pci 0000:00:02.0: [1033:00e0] type 00 class 0x0c0320
pci 0000:00:02.0: reg 0x10: [mem 0x00000000-0x000000ff]
pci 0000:00:02.0: supports D1 D2
pci 0000:00:02.0: PME# supported from D0 D1 D2 D3hot
PCI: bus0: Fast back to back transfers disabled
pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
pci 0000:00:01.0: BAR 0: assigned [mem 0xee080000-0xee080fff]
pci 0000:00:02.0: BAR 0: assigned [mem 0xee081000-0xee0810ff]
pci 0000:00:01.0: enabling device (0140 -> 0142)
pci 0000:00:02.0: enabling device (0140 -> 0142)
pci-rcar-gen2 ee0b0000.pci: PCI: bus0 revision 11
pci-rcar-gen2 ee0b0000.pci: PCI host bridge to bus 0001:01
pci_bus 0001:01: root bus resource [io 0xee0a0000-0xee0a10ff]
pci_bus 0001:01: root bus resource [mem 0xee0a0000-0xee0a10ff]
pci_bus 0001:01: No busn resource found for root bus, will use [bus 01-ff]
pci 0001:01:00.0: [1033:0000] type 00 class 0x060000
pci 0001:01:00.0: reg 0x10: [mem 0xee0b0800-0xee0b0bff]
pci 0001:01:00.0: reg 0x14: [mem 0x40000000-0x7fffffff pref]
pci 0001:01:01.0: [1033:0035] type 00 class 0x0c0310
pci 0001:01:01.0: reg 0x10: [mem 0x00000000-0x00000fff]
pci 0001:01:01.0: supports D1 D2
pci 0001:01:01.0: PME# supported from D0 D1 D2 D3hot
pci 0001:01:02.0: [1033:00e0] type 00 class 0x0c0320
pci 0001:01:02.0: reg 0x10: [mem 0x00000000-0x000000ff]
pci 0001:01:02.0: supports D1 D2
pci 0001:01:02.0: PME# supported from D0 D1 D2 D3hot
PCI: bus1: Fast back to back transfers disabled
pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 01
pci 0001:01:01.0: BAR 0: assigned [mem 0xee0a0000-0xee0a0fff]
pci 0001:01:02.0: BAR 0: assigned [mem 0xee0a1000-0xee0a10ff]
pci 0001:01:01.0: enabling device (0140 -> 0142)
pci 0001:01:02.0: enabling device (0140 -> 0142)
pci-rcar-gen2 ee0d0000.pci: PCI: bus0 revision 11
pci-rcar-gen2 ee0d0000.pci: PCI host bridge to bus 0002:02
pci_bus 0002:02: root bus resource [io 0xee0c0000-0xee0c10ff]
pci_bus 0002:02: root bus resource [mem 0xee0c0000-0xee0c10ff]
pci_bus 0002:02: No busn resource found for root bus, will use [bus 02-ff]
pci 0002:02:00.0: [1033:0000] type 00 class 0x060000
pci 0002:02:00.0: reg 0x10: [mem 0xee0d0800-0xee0d0bff]
pci 0002:02:00.0: reg 0x14: [mem 0x40000000-0x7fffffff pref]
pci 0002:02:01.0: [1033:0035] type 00 class 0x0c0310
pci 0002:02:01.0: reg 0x10: [mem 0x00000000-0x00000fff]
pci 0002:02:01.0: supports D1 D2
pci 0002:02:01.0: PME# supported from D0 D1 D2 D3hot
pci 0002:02:02.0: [1033:00e0] type 00 class 0x0c0320
pci 0002:02:02.0: reg 0x10: [mem 0x00000000-0x000000ff]
pci 0002:02:02.0: supports D1 D2
pci 0002:02:02.0: PME# supported from D0 D1 D2 D3hot
PCI: bus2: Fast back to back transfers disabled
pci_bus 0002:02: busn_res: [bus 02-ff] end is updated to 02
pci 0002:02:01.0: BAR 0: assigned [mem 0xee0c0000-0xee0c0fff]
pci 0002:02:02.0: BAR 0: assigned [mem 0xee0c1000-0xee0c10ff]
pci 0002:02:01.0: enabling device (0140 -> 0142)
pci 0002:02:02.0: enabling device (0140 -> 0142)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
SuperH (H)SCI(F) driver initialized
e6c40000.serial: ttySC0 at MMIO 0xe6c40000 (irq = 103, base_baud = 0) is a scifa
console [ttySC0] enabled
e6c50000.serial: ttySC1 at MMIO 0xe6c50000 (irq = 104, base_baud = 0) is a scifa
[drm] Initialized drm 1.1.0 20060810
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] No driver support for vblank timestamp query.
rcar-du feb00000.display: failed to initialize encoder /i2c@e6520000/hdmi@39 (-38), skipping
rcar-du feb00000.display: fb0: frame buffer device
rcar-du feb00000.display: registered panic notifier
[drm] Initialized rcar-du 1.0.0 20130110 on minor 0
da9063 7-0058: Device detected (chip-ID: 0x61, var-ID: 0x50)
scsi host0: sata_rcar
ata1: SATA max UDMA/133 irq 106
renesas_spi e6b10000.spi: DMA available
m25p80 spi0.0: s25fl512s (65536 Kbytes)
3 ofpart partitions found on MTD device spi0.0
Creating 3 MTD partitions on "spi0.0":
0x000000000000-0x000000040000 : "loader"
0x000000040000-0x000000440000 : "user"
0x000000440000-0x000004000000 : "flash"
renesas_spi e6b10000.spi: probed
spi_sh_msiof e6e10000.spi: DMA available
libphy: sh_mii: probed
sh-eth ee700000.ethernet eth0: Base address at 0xee700000, 2e:09:0a:00:7c:ff, IRQ 105.
usbcore: registered new interface driver rt2800usb
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-pci 0000:00:02.0: EHCI Host Controller
ehci-pci 0000:00:02.0: new USB bus registered, assigned bus number 1
ehci-pci 0000:00:02.0: irq 120, io mem 0xee081000
cfg80211: Calling CRDA to update world regulatory domain
ehci-pci 0000:00:02.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ehci-pci 0001:01:02.0: EHCI Host Controller
ehci-pci 0001:01:02.0: new USB bus registered, assigned bus number 2
ehci-pci 0001:01:02.0: irq 121, io mem 0xee0a1000
ehci-pci 0001:01:02.0: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
ehci-pci 0002:02:02.0: EHCI Host Controller
ehci-pci 0002:02:02.0: new USB bus registered, assigned bus number 3
ehci-pci 0002:02:02.0: irq 122, io mem 0xee0c1000
ehci-pci 0002:02:02.0: USB 2.0 started, EHCI 1.00
hub 3-0:1.0: USB hub found
ata1: link resume succeeded after 1 retries
hub 3-0:1.0: 1 port detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
ohci-pci 0000:00:01.0: OHCI PCI host controller
ohci-pci 0000:00:01.0: new USB bus registered, assigned bus number 4
ohci-pci 0000:00:01.0: irq 120, io mem 0xee080000
ata1: SATA link down (SStatus 0 SControl 300)
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 1 port detected
ohci-pci 0001:01:01.0: OHCI PCI host controller
ohci-pci 0001:01:01.0: new USB bus registered, assigned bus number 5
ohci-pci 0001:01:01.0: irq 121, io mem 0xee0a0000
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 1 port detected
ohci-pci 0002:02:01.0: OHCI PCI host controller
ohci-pci 0002:02:01.0: new USB bus registered, assigned bus number 6
ohci-pci 0002:02:01.0: irq 122, io mem 0xee0c0000
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 1 port detected
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver pl2303
usbserial: USB Serial support registered for pl2303
sh-pfc e6060000.pfc: pin GP_5_19 already requested by ee090000.pci; cannot claim for e6590000b
sh-pfc e6060000.pfc: pin-179 (e6590000.usb) status -22
sh-pfc e6060000.pfc: could not request pin 179 (GP_5_19) from group usb0_ovc_vbus on device c
renesas_usbhs e6590000.usb: Error applying setting, reverse things back
renesas_usbhs e6590000.usb: transceiver found
renesas_usbhs e6590000.usb: gadget probed
renesas_usbhs e6590000.usb: USB function not selected (GPIO 850)
renesas_usbhs e6590000.usb: probe failed
renesas_usbhs: probe of e6590000.usb failed with error -524
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
adv7180 6-0020: chip found @ 0x20 (e6520000.i2c)
soc-camera-pdrv soc-camera-pdrv.0: Probing soc-camera-pdrv.0
rcar_vin e6ef1000.video: group probe failed: -6
usb 2-1: new high-speed USB device number 2 using ehci-pci
rcar_thermal e61f0000.thermal: 1 sensor probed
sh_mobile_sdhi ee100000.sd: Got CD GPIO
sh_mobile_sdhi ee140000.sd: Got CD GPIO
sh_mmcif ee220000.mmc: No vqmmc regulator found
sh_mmcif ee220000.mmc: Chip version 0x0003, clock rate 12MHz
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
usb-storage 2-1:1.0: USB Mass Storage device detected
rcar_sound ec500000.sound: probed
NET: Registered protocol family 10
scsi host1: usb-storage 2-1:1.0
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
Key type dns_resolver registered
Registering SWP/SWPB emulation handler
sh_mobile_sdhi ee100000.sd: Got CD GPIO
mmc0: MAN_BKOPS_EN bit is not set
mmc0: new high speed MMC card at address 0001
mmcblk0: mmc0:0001 MMC08G 7.32 GiB
usb 3-1: new high-speed USB device number 2 using ehci-pci
mmcblk0boot0: mmc0:0001 MMC08G partition 1 2.00 MiB
mmcblk0boot1: mmc0:0001 MMC08G partition 2 2.00 MiB
sh_mobile_sdhi ee100000.sd: mmc1 base at 0xee100000 clock rate 97 MHz
sh_mobile_sdhi ee140000.sd: Got CD GPIO
mmcblk0: p1
sh_mobile_sdhi ee140000.sd: mmc2 base at 0xee140000 clock rate 97 MHz
usb-storage 3-1:1.0: USB Mass Storage device detected
scsi host2: usb-storage 3-1:1.0
asoc-simple-card sound: ak4642-hifi <-> ec500000.sound mapping ok
input: keyboard as /devices/platform/keyboard/input/input0
hctosys: unable to open rtc device (rtc0)
sh-eth ee700000.ethernet eth0: attached PHY 1 (IRQ 344) to driver Micrel KSZ8041RNLI
Sending DHCP requests .
scsi 1:0:0:0: Direct-Access K390 USB-CVIDE5 0.00 PQ: 0 ANSI: 0
sd 1:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 1:0:0:0: [sda] Test WP failed, assume Write Enabled
sd 1:0:0:0: [sda] Asking for cache data failed
sd 1:0:0:0: [sda] Assuming drive cache: write through
sda: sda1 sda2
sd 1:0:0:0: [sda] Attached SCSI disk
scsi 2:0:0:0: Direct-Access JetFlash Transcend 16GB 1.00 PQ: 0 ANSI: 6
sd 2:0:0:0: [sdb] 30867456 512-byte logical blocks: (15.8 GB/14.7 GiB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
sd 2:0:0:0: [sdb] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA
sdb: sdb1
sd 2:0:0:0: [sdb] Attached SCSI removable disk
cfg80211: Calling CRDA to update world regulatory domain
.
sh-eth ee700000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
cfg80211: Calling CRDA to update world regulatory domain
., OK
IP-Config: Got DHCP answer from 172.16.1.85, my address is 172.16.1.81
IP-Config: Complete:
device=eth0, hwaddr=2e:09:0a:00:7c:ff, ipaddr=172.16.1.81, mask=255.255.255.0, gw=172.165
host=172.16.1.81, domain=, nis-domain=(none)
bootserver=172.16.1.85, rootserver=172.16.1.85, rootpath=
nameserver0=169.254.192.1, nameserver1=169.254.192.70, nameserver2=8.8.8.8
SDHI2 VccQ: disabling
SDHI0 VccQ: disabling
SDHI2 Vcc: disabling
SDHI0 Vcc: disabling
ALSA device list:
#0: rsnd-dai.0-ak4642-hifi
VFS: Mounted root (nfs filesystem) on device 0:14.
devtmpfs: mounted
Freeing unused kernel memory: 288K (c072e000 - c0776000)
cfg80211: Calling CRDA to update world regulatory domain
Mount failed for selinuxfs on /sys/fs/selinux: No such file or directory
random: init urandom read with 70 bits of entropy available
init: plymouth-upstart-bridge main process (1001) terminated with status 1
init: plymouth-upstart-bridge main process ended, respawning
init: plymouth-upstart-bridge main process (1011) terminated with status 1
init: plymouth-upstart-bridge main process ended, respawning
init: plymouth-upstart-bridge main process (1015) terminated with status 1
init: plymouth-upstart-bridge main process ended, respawning
random: nonblocking pool is initialized
systemd-udevd[1106]: starting version 204
init: systemd-logind pre-start process (1632) terminated with status 32
systemd-udevd[1630]: could not open moddep file '/lib/modules/4.1.13-ltsi-00392-g5308b95/modu'
CPU4: failed to boot: -22
CPU5: failed to boot: -22
CPU6: failed to boot: -22
CPU7: failed to boot: -22
init: udev-fallback-graphics main process (1794) terminated with status 1
cfg80211: Calling CRDA to update world regulatory domain
* Stopping Send an event to indicate plymouth is up[ OK ]
* Starting Mount filesystems on boot[ OK ]
* Starting Signal sysvinit that the rootfs is mounted[ OK ]
* Starting Clean /tmp directory[ OK ]
* Starting Populate and link to /run filesystem[ OK ]
* Stopping Clean /tmp directory[ OK ]
* Stopping Populate and link to /run filesystem[ OK ]
* Stopping Track if upstart is running in a container[ OK ]
* Starting set console keymap[ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted[ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted[ OK ]
* Starting Bridge udev events into upstart[ OK ]
* Starting Signal sysvinit that local filesystems are mounted[ OK ]
* Starting Signal sysvinit that remote filesystems are mounted[ OK ]
* Starting device node and kernel event manager[ OK ]
* Stopping Mount filesystems on boot[ OK ]
* Stopping set console keymap[ OK ]
* Starting Enabling additional executable binary formats[ OK ]
* Starting flush early job output to logs[ OK ]
* Starting load modules from /etc/modules[ OK ]
* Starting cold plug devices[ OK ]
* Starting log initial device creation[ OK ]
* Starting D-Bus system message bus[ OK ]
* Stopping flush early job output to logs[ OK ]
* Stopping load modules from /etc/modules[ OK ]
* Starting SystemD login management service[fail]
* Stopping SystemD login management service[ OK ]
* Starting system logging daemon[ OK ]
* Starting configure network device security[ OK ]
* Stopping cold plug devices[ OK ]
* Stopping log initial device creation[ OK ]
* Starting configure network device[ OK ]
* Starting load fallback graphics devices[ OK ]
* Starting configure network device security[ OK ]
* Starting load fallback graphics devices[fail]
* Starting save udev log and update rules[ OK ]
* Stopping save udev log and update rules[ OK ]
* Starting set console font[ OK ]
* Stopping set console font[ OK ]
* Starting userspace bootsplash[ OK ]
* Stopping userspace bootsplash[ OK ]
* Starting Send an event to indicate plymouth is up[ OK ]
* Stopping Send an event to indicate plymouth is up[ OK ]
* Starting System V initialisation compatibility[ OK ]
* Starting configure virtual network devices[ OK ]
* Starting configure network device security[ OK ]
* Starting configure network device security[ OK ]
* Starting configure network device[ OK ]
* Starting configure network device[ OK ]
* Starting Mount network filesystems[ OK ]
* Starting Failsafe Boot Delay[ OK ]
* Stopping Mount network filesystems[ OK ]
* Starting Bridge socket events into upstart[ OK ]
* Starting Bridge file events into upstart[ OK ]
[ OK ]ting sensors limits
[ OK ]ting up X socket directories...
* Stopping System V initialisation compatibility[ OK ]
* Starting System V runlevel compatibility[ OK ]
* Starting Restore Sound Card State[ OK ]
* Starting reinit: alsa-restore main process (2003) terminated with status 99
gular background program processing daemon[ OK ]
* Starting save kernel messages[ OK ]
* Starting Restore Sound Card State[fail]
* Stopping Restore Sound Card State[ OK ]
* Starting OpenSSH server[ OK ]
* Stopping System V runlevel compatibility[ OK ]
* Stopping save kernel messages[ OK ]
init: plymouth-upstart-bridge main process ended, respawning
Last login: Thu Jan 1 00:00:18 UTC 1970 on tty1
Welcome to Linaro 14.04 (GNU/Linux 4.1.13-ltsi-00392-g5308b95 armv7l)
* Documentation: https://wiki.linaro.org/
init: tty1 main process (2053) killed by TERM signal
root@linaro-nano:~# cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: Exceeded CRDA call max attempts. Not calling CRDA
root@linaro-nano:~#
root@linaro-nano:~# cd /sys/bus/platform/drivers/rcar-dmac
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# ls
bind ec700000.dma-controller unbind
e6700000.dma-controller ec720000.dma-controller
e6720000.dma-controller uevent
er > unbindnano:/sys/bus/platform/drivers/rcar-dmac# echo ec700000.dma-controll
------------[ cut here ]------------
WARNING: CPU: 1 PID: 2171 at drivers/dma/dmaengine.c:971 dma_async_device_unregister+0x8c/0xf)
dma_async_device_unregister called while 1 clients hold a reference
CPU: 1 PID: 2171 Comm: bash Not tainted 4.1.13-ltsi-00392-g5308b95 #1
Hardware name: Generic R8A7790 (Flattened Device Tree)
Backtrace:
[<c0012f88>] (dump_backtrace) from [<c0013130>] (show_stack+0x18/0x1c)
r7:c06e2408 r6:ed0eb080 r5:00000009 r4:00000000
[<c0013118>] (show_stack) from [<c059a4d8>] (dump_stack+0x78/0x94)
[<c059a460>] (dump_stack) from [<c0026274>] (warn_slowpath_common+0x88/0xb4)
r5:00000009 r4:edb61dd0
[<c00261ec>] (warn_slowpath_common) from [<c002630c>] (warn_slowpath_fmt+0x38/0x40)
r9:000be408 r8:edb61f80 r7:c0791790 r6:c07adce8 r5:eea68a10 r4:ee32b810
[<c00262d8>] (warn_slowpath_fmt) from [<c02660cc>] (dma_async_device_unregister+0x8c/0xf0)
r3:c060023a r2:c06ec62f
[<c0266040>] (dma_async_device_unregister) from [<c0268d10>] (rcar_dmac_remove+0x24/0x38)
r6:c0788f50 r5:eea68a10 r4:eea74800
[<c0268cec>] (rcar_dmac_remove) from [<c02ceacc>] (platform_drv_remove+0x20/0x38)
r5:c0788f50 r4:eea74810
[<c02ceaac>] (platform_drv_remove) from [<c02cd260>] (__device_release_driver+0x84/0xe8)
r5:c0788f50 r4:eea74810
[<c02cd1dc>] (__device_release_driver) from [<c02cd9b8>] (device_release_driver+0x24/0x30)
r5:eea74810 r4:eea74844
[<c02cd994>] (device_release_driver) from [<c02cc19c>] (unbind_store+0x60/0x94)
r5:eea74810 r4:00000018
[<c02cc13c>] (unbind_store) from [<c02cbb30>] (drv_attr_store+0x2c/0x38)
r7:ee204f8c r6:ee204f80 r5:ed80a440 r4:00000018
[<c02cbb04>] (drv_attr_store) from [<c011fb7c>] (sysfs_kf_write+0x40/0x4c)
[<c011fb3c>] (sysfs_kf_write) from [<c011f21c>] (kernfs_fop_write+0x120/0x180)
[<c011f0fc>] (kernfs_fop_write) from [<c00c8598>] (__vfs_write+0x34/0xdc)
r9:edb60000 r8:c000fd84 r7:00000018 r6:edb61f80 r5:c011f0fc r4:edaef640
[<c00c8564>] (__vfs_write) from [<c00c87bc>] (vfs_write+0xb4/0x13c)
r7:edb61f80 r6:000be408 r5:edaef640 r4:00000018
[<c00c8708>] (vfs_write) from [<c00c8924>] (SyS_write+0x50/0x90)
r9:edb60000 r8:c000fd84 r7:00000018 r6:000be408 r5:edaef640 r4:edaef640
[<c00c88d4>] (SyS_write) from [<c000fbe0>] (ret_fast_syscall+0x0/0x3c)
r7:00000004 r6:b6f7ab58 r5:000be408 r4:00000018
---[ end trace 4ac573ae0bf47e6f ]---
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
er > bindo-nano:/sys/bus/platform/drivers/rcar-dmac# echo ec700000.dma-controll
rcar-dmac ec700000.dma-controller: DMAOR initialization failed.
rcar-dmac ec700000.dma-controller: failed to reset device
rcar-dmac: probe of ec700000.dma-controller failed with error -5
-bash: echo: write error: No such device
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# cd
--------------------------------------------e6700000.dma-controll------------------------------------
root@linaro-nano:~#
root@linaro-nano:~#
root@linaro-nano:~# cd /sys/bus/platform/drivers/rcar-dmac
er > unbindnano:/sys/bus/platform/drivers/rcar-dmac# echo e6700000.dma-controll
------------[ cut here ]------------
WARNING: CPU: 2 PID: 2172 at drivers/dma/dmaengine.c:971 dma_async_device_unregister+0x8c/0xf)
dma_async_device_unregister called while 1 clients hold a reference
CPU: 2 PID: 2172 Comm: bash Not tainted 4.1.13-ltsi-00392-g5308b95 #1
Hardware name: Generic R8A7790 (Flattened Device Tree)
Backtrace:
[<c0012f88>] (dump_backtrace) from [<c0013130>] (show_stack+0x18/0x1c)
r7:c06e2408 r6:ee0da080 r5:00000009 r4:00000000
[<c0013118>] (show_stack) from [<c059a4d8>] (dump_stack+0x78/0x94)
[<c059a460>] (dump_stack) from [<c0026274>] (warn_slowpath_common+0x88/0xb4)
r5:00000009 r4:ed9d3dd0
[<c00261ec>] (warn_slowpath_common) from [<c002630c>] (warn_slowpath_fmt+0x38/0x40)
r9:000be408 r8:ed9d3f80 r7:c0791790 r6:c07adce8 r5:eea54e10 r4:ee1a8010
[<c00262d8>] (warn_slowpath_fmt) from [<c02660cc>] (dma_async_device_unregister+0x8c/0xf0)
r3:c060023a r2:c06ec62f
[<c0266040>] (dma_async_device_unregister) from [<c0268d10>] (rcar_dmac_remove+0x24/0x38)
r6:c0788f50 r5:eea54e10 r4:ee9dc000
[<c0268cec>] (rcar_dmac_remove) from [<c02ceacc>] (platform_drv_remove+0x20/0x38)
r5:c0788f50 r4:ee9dc010
[<c02ceaac>] (platform_drv_remove) from [<c02cd260>] (__device_release_driver+0x84/0xe8)
r5:c0788f50 r4:ee9dc010
[<c02cd1dc>] (__device_release_driver) from [<c02cd9b8>] (device_release_driver+0x24/0x30)
r5:ee9dc010 r4:ee9dc044
[<c02cd994>] (device_release_driver) from [<c02cc19c>] (unbind_store+0x60/0x94)
r5:ee9dc010 r4:00000018
[<c02cc13c>] (unbind_store) from [<c02cbb30>] (drv_attr_store+0x2c/0x38)
r7:edf7decc r6:edf7dec0 r5:ed87c800 r4:00000018
[<c02cbb04>] (drv_attr_store) from [<c011fb7c>] (sysfs_kf_write+0x40/0x4c)
[<c011fb3c>] (sysfs_kf_write) from [<c011f21c>] (kernfs_fop_write+0x120/0x180)
[<c011f0fc>] (kernfs_fop_write) from [<c00c8598>] (__vfs_write+0x34/0xdc)
r9:ed9d2000 r8:c000fd84 r7:00000018 r6:ed9d3f80 r5:c011f0fc r4:edf12340
[<c00c8564>] (__vfs_write) from [<c00c87bc>] (vfs_write+0xb4/0x13c)
r7:ed9d3f80 r6:000be408 r5:edf12340 r4:00000018
[<c00c8708>] (vfs_write) from [<c00c8924>] (SyS_write+0x50/0x90)
r9:ed9d2000 r8:c000fd84 r7:00000018 r6:000be408 r5:edf12340 r4:edf12340
[<c00c88d4>] (SyS_write) from [<c000fbe0>] (ret_fast_syscall+0x0/0x3c)
r7:00000004 r6:b6ed0b58 r5:000be408 r4:00000018
---[ end trace 0f084e0d223d6299 ]---
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
er > bindro-nano:/sys/bus/platform/drivers/rcar-dmac# echo e6700000.dma-controll
rcar-dmac e6700000.dma-controller: DMAOR initialization failed.
rcar-dmac e6700000.dma-controller: failed to reset device
rcar-dmac: probe of e6700000.dma-controller failed with error -5
-bash: echo: write error: No such device
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# cd
root@linaro-nano:~#
root@linaro-nano:~#
--------------------------------------------e6720000.dma-controll------------------------------------
root@linaro-nano:~# cd /sys/bus/platform/drivers/rcar-dmac
er > unbindnano:/sys/bus/platform/drivers/rcar-dmac# echo e6720000.dma-controll
------------[ cut here ]------------
WARNING: CPU: 2 PID: 2170 at drivers/dma/dmaengine.c:971 dma_async_device_unregister+0x8c/0xf)
dma_async_device_unregister called while 1 clients hold a reference
CPU: 2 PID: 2170 Comm: bash Not tainted 4.1.13-ltsi-00392-g5308b95 #1
Hardware name: Generic R8A7790 (Flattened Device Tree)
Backtrace:
[<c0012f88>] (dump_backtrace) from [<c0013130>] (show_stack+0x18/0x1c)
r7:c06e2408 r6:eea5c140 r5:00000009 r4:00000000
[<c0013118>] (show_stack) from [<c059a4d8>] (dump_stack+0x78/0x94)
[<c059a460>] (dump_stack) from [<c0026274>] (warn_slowpath_common+0x88/0xb4)
r5:00000009 r4:ed07fdd0
[<c00261ec>] (warn_slowpath_common) from [<c002630c>] (warn_slowpath_fmt+0x38/0x40)
r9:000be408 r8:ed07ff80 r7:c0791790 r6:c07adce8 r5:ee991810 r4:ee9c6010
[<c00262d8>] (warn_slowpath_fmt) from [<c02660cc>] (dma_async_device_unregister+0x8c/0xf0)
r3:c060023a r2:c06ec62f
[<c0266040>] (dma_async_device_unregister) from [<c0268d10>] (rcar_dmac_remove+0x24/0x38)
r6:c0788f50 r5:ee991810 r4:eea74c00
[<c0268cec>] (rcar_dmac_remove) from [<c02ceacc>] (platform_drv_remove+0x20/0x38)
r5:c0788f50 r4:eea74c10
[<c02ceaac>] (platform_drv_remove) from [<c02cd260>] (__device_release_driver+0x84/0xe8)
r5:c0788f50 r4:eea74c10
[<c02cd1dc>] (__device_release_driver) from [<c02cd9b8>] (device_release_driver+0x24/0x30)
r5:eea74c10 r4:eea74c44
[<c02cd994>] (device_release_driver) from [<c02cc19c>] (unbind_store+0x60/0x94)
r5:eea74c10 r4:00000018
[<c02cc13c>] (unbind_store) from [<c02cbb30>] (drv_attr_store+0x2c/0x38)
r7:ee19ad4c r6:ee19ad40 r5:ed954b80 r4:00000018
[<c02cbb04>] (drv_attr_store) from [<c011fb7c>] (sysfs_kf_write+0x40/0x4c)
[<c011fb3c>] (sysfs_kf_write) from [<c011f21c>] (kernfs_fop_write+0x120/0x180)
[<c011f0fc>] (kernfs_fop_write) from [<c00c8598>] (__vfs_write+0x34/0xdc)
r9:ed07e000 r8:c000fd84 r7:00000018 r6:ed07ff80 r5:c011f0fc r4:ed9a4b80
[<c00c8564>] (__vfs_write) from [<c00c87bc>] (vfs_write+0xb4/0x13c)
r7:ed07ff80 r6:000be408 r5:ed9a4b80 r4:00000018
[<c00c8708>] (vfs_write) from [<c00c8924>] (SyS_write+0x50/0x90)
r9:ed07e000 r8:c000fd84 r7:00000018 r6:000be408 r5:ed9a4b80 r4:ed9a4b80
[<c00c88d4>] (SyS_write) from [<c000fbe0>] (ret_fast_syscall+0x0/0x3c)
r7:00000004 r6:b6f80b58 r5:000be408 r4:00000018
---[ end trace 327b02d192054087 ]---
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
er > bindo-nano:/sys/bus/platform/drivers/rcar-dmac# echo e6720000.dma-controll
rcar-dmac e6720000.dma-controller: DMAOR initialization failed.
rcar-dmac e6720000.dma-controller: failed to reset device
rcar-dmac: probe of e6720000.dma-controller failed with error -5
-bash: echo: write error: No such device
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac#
root@linaro-nano:/sys/bus/platform/drivers/rcar-dmac# cd
root@linaro-nano:~#
Hello Cao Minh-san, (this is a bit of a stupid question, and I apologize for that, but what is the proper way to address you, Cao-san, Cao Minh-san, Hiep-san, or something else ?) On Thursday 10 December 2015 10:43:18 Cao Minh Hiep wrote: > > >>> Yes, CONFIG_DRM_I2C_ADV7511=y has already enabled in default config at > >>> v4.4-rc2. > >>> I also have enabled CONFIG_DRM_SHMOBILE and CONFIG_FB_SH_MOBILE_HDMI > >>> then test. > >>> But It has nothing change. > >>> Is there other configuration or reason could we think? > >> > >> Does this problem happen on your board? > >> If not, Could you please send me your config file?. > > > > Sorry for the delay, I wanted to retry on my Koelsch board before > > replying. > > > > The probe deferral error (-517) you're seeing is normal, it comes from the > > DU being probed before its dependencies. Probe is deferred and retried, > > and finally succeeds as shown by > > > > [drm] Initialized rcar-du 1.0.0 20130110 on minor 0 > > > > With a stock v4.4-rc2 kernel I get the same result, and I can then use the > > HDMI output without any issue with the modetest application. > > > > I've attached the kernel configuration I used for testing, just in case. > > Thanks, I have changed our HDMI display device(Old one -> other newer one), > and then I could show a image on the display successfully. This test is > on Koelsch board. > But I found that, before showing the image on HDMI display, > I have to enable CONFIG_FRAMEBUFFER_CONSOLE =y or > run a command something like "fbset -xres 640 -yres 480 -laced 0", in > order to clear the first screen. > > On Lager, with the same test method, I could show a image on RGB display > very well, > but when I showed image on HDMI display, The image showed on display > looks bad as attached picture. > The attached picture: HDMI-Display-image-showed-from-Lager.jpg > > Please have a look and show me what i have to do! I'll try to reproduce that. Could you please send me the image file and the exact test procedure ?
Hello Hiep-san, On Tuesday 28 Jun 2016 10:19:20 Hiep Cao Minh wrote: > Hi Laurent-san > > Sorry to bother you again! > I would like to confirm the fixed patch for this issue on Lager. > I have retested it on Lager(Rcar-H2), The issue still happens at the > Linux upstream version v4.7-rc2 > Have you released the fixed patch? > Please tell me the version and test method if you have already released it. > I resent the damage image when displaying it on the HDMI screen. I'm currently traveling and have only taken my H3 board with me, so I don't have access to Lager. I'll be back home on the 5th of July and then test this. Sorry for the delay. > On 12/17/2015 03:37 PM, Cao Minh Hiep wrote: > > Hello Laurent-san > > > > On 2015年12月14日 04:45, Laurent Pinchart wrote: > >> Hello Cao Minh-san, > >> > >> (this is a bit of a stupid question, and I apologize for that, but > >> what is the > >> proper way to address you, Cao-san, Cao Minh-san, Hiep-san, or > >> something else > >> ?) > > > > No problems! :) , Hiep is my name! Every one calls me Hiep, > > > >> On Thursday 10 December 2015 10:43:18 Cao Minh Hiep wrote: > >>>>>> Yes, CONFIG_DRM_I2C_ADV7511=y has already enabled in default > >>>>>> config at > >>>>>> v4.4-rc2. > >>>>>> I also have enabled CONFIG_DRM_SHMOBILE and CONFIG_FB_SH_MOBILE_HDMI > >>>>>> then test. > >>>>>> But It has nothing change. > >>>>>> Is there other configuration or reason could we think? > >>>>> > >>>>> Does this problem happen on your board? > >>>>> If not, Could you please send me your config file?. > >>>> > >>>> Sorry for the delay, I wanted to retry on my Koelsch board before > >>>> replying. > >>>> > >>>> The probe deferral error (-517) you're seeing is normal, it comes > >>>> from the > >>>> DU being probed before its dependencies. Probe is deferred and > >>>> retried, > >>>> and finally succeeds as shown by > >>>> > >>>> [drm] Initialized rcar-du 1.0.0 20130110 on minor 0 > >>>> > >>>> With a stock v4.4-rc2 kernel I get the same result, and I can then > >>>> use the > >>>> HDMI output without any issue with the modetest application. > >>>> > >>>> I've attached the kernel configuration I used for testing, just in > >>>> case. > >>> > >>> Thanks, I have changed our HDMI display device(Old one -> other > >>> newer one), > >>> and then I could show a image on the display successfully. This test is > >>> on Koelsch board. > >>> But I found that, before showing the image on HDMI display, > >>> I have to enable CONFIG_FRAMEBUFFER_CONSOLE =y or > >>> run a command something like "fbset -xres 640 -yres 480 -laced 0", in > >>> order to clear the first screen. > >>> > >>> On Lager, with the same test method, I could show a image on RGB > >>> display > >>> very well, > >>> but when I showed image on HDMI display, The image showed on display > >>> looks bad as attached picture. > >>> The attached picture: HDMI-Display-image-showed-from-Lager.jpg > >>> > >>> Please have a look and show me what i have to do! > >> > >> I'll try to reproduce that. Could you please send me the image file > >> and the > >> exact test procedure ? > > > > I tested on v4.4-rc2 on Lager board. > > > > CONFIG_DRM_RCAR_HDMI=y > > CONFIG_DRM_I2C_ADV7511=y > > VIDEO_ADV7511=y > > CONFIG_FRAMEBUFFER_CONSOLE =y > > > > I used the Morimoto-san's bmap tool to show image file. > > ./bmap /dev/fb0 ./picture.bmp > > > > I attach bmap file and the image file "picture.bmp". > > > > Regards, > > Jinso/Hiep.
diff --git a/drivers/pinctrl/sh-pfc/pfc-r8a7795.c b/drivers/pinctrl/sh-pfc/pfc-r8a7795.c index 29d001b8a727e154..bb5f37cbb9502d5f 100644 --- a/drivers/pinctrl/sh-pfc/pfc-r8a7795.c +++ b/drivers/pinctrl/sh-pfc/pfc-r8a7795.c @@ -495,7 +495,7 @@ FM(IP16_31_28) IP16_31_28 #define MOD_SEL1_13 FM(SEL_SCIF3_0) FM(SEL_SCIF3_1) #define MOD_SEL1_12 FM(SEL_SCIF2_0) FM(SEL_SCIF2_1) #define MOD_SEL1_11 FM(SEL_SCIF1_0) FM(SEL_SCIF1_1) -#define MOD_SEL1_10 FM(SEL_SCIF_0) FM(SEL_SCIF_1) +#define MOD_SEL1_10 FM(SEL_SATA_0) FM(SEL_SATA_1) #define MOD_SEL1_9 FM(SEL_REMOCON_0) FM(SEL_REMOCON_1) #define MOD_SEL1_6 FM(SEL_RCAN0_0) FM(SEL_RCAN0_1) #define MOD_SEL1_5 FM(SEL_PWM6_0) FM(SEL_PWM6_1) @@ -1033,7 +1033,7 @@ static const u16 pinmux_data[] = { PINMUX_IPSR_DATA(IP9_19_16, SD2_DAT3), PINMUX_IPSR_DATA(IP9_23_20, SD2_DS), - PINMUX_IPSR_MSEL(IP9_23_20, SATA_DEVSLP_B, SEL_SCIF_1), + PINMUX_IPSR_MSEL(IP9_23_20, SATA_DEVSLP_B, SEL_SATA_1), PINMUX_IPSR_DATA(IP9_27_24, SD3_DAT4), PINMUX_IPSR_MSEL(IP9_27_24, SD2_CD_A, SEL_SDHI2_0), @@ -1293,7 +1293,7 @@ static const u16 pinmux_data[] = { PINMUX_IPSR_DATA(IP15_11_8, SSI_SDATA6), PINMUX_IPSR_MSEL(IP15_11_8, SIM0_CLK_D, SEL_SIMCARD_3), - PINMUX_IPSR_MSEL(IP15_11_8, SATA_DEVSLP_A, SEL_SCIF_0), + PINMUX_IPSR_MSEL(IP15_11_8, SATA_DEVSLP_A, SEL_SATA_0), PINMUX_IPSR_DATA(IP15_15_12, SSI_SCK78), PINMUX_IPSR_MSEL(IP15_15_12, HRX2_B, SEL_HSCIF2_1),
Cfr. Manual Errata for Rev 0.50 of the R-Car Gen3 datasheet. This has no user-visible impact. Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> --- drivers/pinctrl/sh-pfc/pfc-r8a7795.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)