[RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Javier Martinez Canillas]

The Exynos DRM driver register its sub-devices platform drivers in
the probe function but after commit 43c0767 ("of/platform: Move
platform devices under /sys/devices/platform"), this is causing
a deadlock in __driver_attach(). Fix this by moving the platform
drivers registration to exynos_drm_init().

Suggested-by: Andrzej Hajda <a.hajda@samsung.com>
Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
---

This issue was reported by both Krzysztof Kozlowski [0] and Kevin Hilman [1].

Inki Dae said that he will fix it property by separating the Exynos DRM
driver in different sub-modules but I post this patch as RFC anyways so
others can test if this fixes their boot issue.

[0]: https://lkml.org/lkml/2014/11/6/125
[1]: http://www.spinics.net/lists/linux-samsung-soc/msg39050.html

 drivers/gpu/drm/exynos/exynos_drm_drv.c | 163 ++++++++++++++++----------------
 1 file changed, 79 insertions(+), 84 deletions(-)

diff --git a/drivers/gpu/drm/exynos/exynos_drm_drv.c b/drivers/gpu/drm/exynos/exynos_drm_drv.c
index e277d4f..5386fea 100644
--- a/drivers/gpu/drm/exynos/exynos_drm_drv.c
+++ b/drivers/gpu/drm/exynos/exynos_drm_drv.c
@@ -559,15 +559,58 @@ static const struct component_master_ops exynos_drm_ops = {
 static int exynos_drm_platform_probe(struct platform_device *pdev)
 {
 	struct component_match *match;
-	int ret;
 
 	pdev->dev.coherent_dma_mask = DMA_BIT_MASK(32);
 	exynos_drm_driver.num_ioctls = ARRAY_SIZE(exynos_ioctls);
 
+	match = exynos_drm_match_add(&pdev->dev);
+	if (IS_ERR(match))
+		return PTR_ERR(match);
+
+	return component_master_add_with_match(&pdev->dev, &exynos_drm_ops,
+					       match);
+}
+
+static int exynos_drm_platform_remove(struct platform_device *pdev)
+{
+	component_master_del(&pdev->dev, &exynos_drm_ops);
+	return 0;
+}
+
+static struct platform_driver exynos_drm_platform_driver = {
+	.probe	= exynos_drm_platform_probe,
+	.remove	= exynos_drm_platform_remove,
+	.driver	= {
+		.name	= "exynos-drm",
+		.pm	= &exynos_drm_pm_ops,
+	},
+};
+
+static int exynos_drm_init(void)
+{
+	int ret;
+
+	/*
+	 * Register device object only in case of Exynos SoC.
+	 *
+	 * Below codes resolves temporarily infinite loop issue incurred
+	 * by Exynos drm driver when using multi-platform kernel.
+	 * So these codes will be replaced with more generic way later.
+	 */
+	if (!of_machine_is_compatible("samsung,exynos3") &&
+			!of_machine_is_compatible("samsung,exynos4") &&
+			!of_machine_is_compatible("samsung,exynos5"))
+		return -ENODEV;
+
+	exynos_drm_pdev = platform_device_register_simple("exynos-drm", -1,
+								NULL, 0);
+	if (IS_ERR(exynos_drm_pdev))
+		return PTR_ERR(exynos_drm_pdev);
+
 #ifdef CONFIG_DRM_EXYNOS_FIMD
 	ret = platform_driver_register(&fimd_driver);
 	if (ret < 0)
-		return ret;
+		goto err_unregister_pdev;
 #endif
 
 #ifdef CONFIG_DRM_EXYNOS_DP
@@ -591,21 +634,10 @@ static int exynos_drm_platform_probe(struct platform_device *pdev)
 		goto err_unregister_mixer_drv;
 #endif
 
-	match = exynos_drm_match_add(&pdev->dev);
-	if (IS_ERR(match)) {
-		ret = PTR_ERR(match);
-		goto err_unregister_hdmi_drv;
-	}
-
-	ret = component_master_add_with_match(&pdev->dev, &exynos_drm_ops,
-						match);
-	if (ret < 0)
-		goto err_unregister_hdmi_drv;
-
 #ifdef CONFIG_DRM_EXYNOS_G2D
 	ret = platform_driver_register(&g2d_driver);
 	if (ret < 0)
-		goto err_del_component_master;
+		goto err_unregister_hdmi_drv;
 #endif
 
 #ifdef CONFIG_DRM_EXYNOS_FIMC
@@ -636,9 +668,27 @@ static int exynos_drm_platform_probe(struct platform_device *pdev)
 		goto err_unregister_ipp_drv;
 #endif
 
-	return ret;
+#ifdef CONFIG_DRM_EXYNOS_VIDI
+	ret = exynos_drm_probe_vidi();
+	if (ret < 0)
+		goto err_unregister_ipp_dev;
+#endif
+
+	ret = platform_driver_register(&exynos_drm_platform_driver);
+	if (ret)
+		goto err_remove_vidi;
+
+	return 0;
+
+err_remove_vidi:
+#ifdef CONFIG_DRM_EXYNOS_VIDI
+	exynos_drm_remove_vidi();
+err_unregister_pd:
+#endif
 
 #ifdef CONFIG_DRM_EXYNOS_IPP
+err_unregister_ipp_dev:
+	exynos_platform_device_ipp_unregister();
 err_unregister_ipp_drv:
 	platform_driver_unregister(&ipp_driver);
 err_unregister_gsc_drv:
@@ -661,11 +711,9 @@ err_unregister_g2d_drv:
 
 #ifdef CONFIG_DRM_EXYNOS_G2D
 	platform_driver_unregister(&g2d_driver);
-err_del_component_master:
+err_unregister_hdmi_drv:
 #endif
-	component_master_del(&pdev->dev, &exynos_drm_ops);
 
-err_unregister_hdmi_drv:
 #ifdef CONFIG_DRM_EXYNOS_HDMI
 	platform_driver_unregister(&hdmi_driver);
 err_unregister_mixer_drv:
@@ -686,11 +734,21 @@ err_unregister_fimd_drv:
 #ifdef CONFIG_DRM_EXYNOS_FIMD
 	platform_driver_unregister(&fimd_driver);
 #endif
+
+err_unregister_pdev:
+	platform_device_unregister(exynos_drm_pdev);
+
 	return ret;
 }
 
-static int exynos_drm_platform_remove(struct platform_device *pdev)
+static void exynos_drm_exit(void)
 {
+	platform_driver_unregister(&exynos_drm_platform_driver);
+
+#ifdef CONFIG_DRM_EXYNOS_VIDI
+	exynos_drm_remove_vidi();
+#endif
+
 #ifdef CONFIG_DRM_EXYNOS_IPP
 	exynos_platform_device_ipp_unregister();
 	platform_driver_unregister(&ipp_driver);
@@ -721,75 +779,12 @@ static int exynos_drm_platform_remove(struct platform_device *pdev)
 	platform_driver_unregister(&fimd_driver);
 #endif
 
-#ifdef CONFIG_DRM_EXYNOS_DSI
-	platform_driver_unregister(&dsi_driver);
-#endif
-
 #ifdef CONFIG_DRM_EXYNOS_DP
 	platform_driver_unregister(&dp_driver);
 #endif
-	component_master_del(&pdev->dev, &exynos_drm_ops);
-	return 0;
-}
 
-static struct platform_driver exynos_drm_platform_driver = {
-	.probe	= exynos_drm_platform_probe,
-	.remove	= exynos_drm_platform_remove,
-	.driver	= {
-		.name	= "exynos-drm",
-		.pm	= &exynos_drm_pm_ops,
-	},
-};
-
-static int exynos_drm_init(void)
-{
-	int ret;
-
-	/*
-	 * Register device object only in case of Exynos SoC.
-	 *
-	 * Below codes resolves temporarily infinite loop issue incurred
-	 * by Exynos drm driver when using multi-platform kernel.
-	 * So these codes will be replaced with more generic way later.
-	 */
-	if (!of_machine_is_compatible("samsung,exynos3") &&
-			!of_machine_is_compatible("samsung,exynos4") &&
-			!of_machine_is_compatible("samsung,exynos5"))
-		return -ENODEV;
-
-	exynos_drm_pdev = platform_device_register_simple("exynos-drm", -1,
-								NULL, 0);
-	if (IS_ERR(exynos_drm_pdev))
-		return PTR_ERR(exynos_drm_pdev);
-
-#ifdef CONFIG_DRM_EXYNOS_VIDI
-	ret = exynos_drm_probe_vidi();
-	if (ret < 0)
-		goto err_unregister_pd;
-#endif
-
-	ret = platform_driver_register(&exynos_drm_platform_driver);
-	if (ret)
-		goto err_remove_vidi;
-
-	return 0;
-
-err_remove_vidi:
-#ifdef CONFIG_DRM_EXYNOS_VIDI
-	exynos_drm_remove_vidi();
-
-err_unregister_pd:
-#endif
-	platform_device_unregister(exynos_drm_pdev);
-
-	return ret;
-}
-
-static void exynos_drm_exit(void)
-{
-	platform_driver_unregister(&exynos_drm_platform_driver);
-#ifdef CONFIG_DRM_EXYNOS_VIDI
-	exynos_drm_remove_vidi();
+#ifdef CONFIG_DRM_EXYNOS_DSI
+	platform_driver_unregister(&dsi_driver);
 #endif
 	platform_device_unregister(exynos_drm_pdev);
 }
-- 
2.1.0

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Kevin Hilman]

Javier Martinez Canillas <javier.martinez@collabora.co.uk> writes:

> The Exynos DRM driver register its sub-devices platform drivers in
> the probe function but after commit 43c0767 ("of/platform: Move
> platform devices under /sys/devices/platform"), this is causing
> a deadlock in __driver_attach(). Fix this by moving the platform
> drivers registration to exynos_drm_init().
>
> Suggested-by: Andrzej Hajda <a.hajda@samsung.com>
> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> ---
>
> This issue was reported by both Krzysztof Kozlowski [0] and Kevin Hilman [1].
>
> Inki Dae said that he will fix it property by separating the Exynos DRM
> driver in different sub-modules but I post this patch as RFC anyways so
> others can test if this fixes their boot issue.

It fixes the DRM deadlock, issue for me on exynos5800-peach-pi, but then
it proceeds to panic in the workqueue code called by the asoc max98090
codec[1].

If I then disable CONFIG_SND_SOC_SNOW, I can get it to boot to a shell,
but I still don't have display output.

Is anyone at Samsung testing linux-next?  If so, on what platforms?  It
would really be nice if your linux-next work was tested on these
publically-available 542x/5800 platforms (peach-pi, peach-pit,
odroid-xu3) which would also allow lots of others to help you test and
validate.

Kevin

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Gustavo Padovan]

2014-11-18 Kevin Hilman <khilman@kernel.org>:

> Javier Martinez Canillas <javier.martinez@collabora.co.uk> writes:
> 
> > The Exynos DRM driver register its sub-devices platform drivers in
> > the probe function but after commit 43c0767 ("of/platform: Move
> > platform devices under /sys/devices/platform"), this is causing
> > a deadlock in __driver_attach(). Fix this by moving the platform
> > drivers registration to exynos_drm_init().
> >
> > Suggested-by: Andrzej Hajda <a.hajda@samsung.com>
> > Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> > ---
> >
> > This issue was reported by both Krzysztof Kozlowski [0] and Kevin Hilman [1].
> >
> > Inki Dae said that he will fix it property by separating the Exynos DRM
> > driver in different sub-modules but I post this patch as RFC anyways so
> > others can test if this fixes their boot issue.
> 
> It fixes the DRM deadlock, issue for me on exynos5800-peach-pi, but then
> it proceeds to panic in the workqueue code called by the asoc max98090
> codec[1].
> 
> If I then disable CONFIG_SND_SOC_SNOW, I can get it to boot to a shell,
> but I still don't have display output.
> 
> Is anyone at Samsung testing linux-next?  If so, on what platforms?  It
> would really be nice if your linux-next work was tested on these
> publically-available 542x/5800 platforms (peach-pi, peach-pit,
> odroid-xu3) which would also allow lots of others to help you test and
> validate.

It would also be good to add drm-exynos-next to the daily linux-next build.
Currently drm-exynos-next is ahead of linux-next. This patch from Javier for
example only applies on linux-next.

	Gustavo

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Kevin Hilman]

Gustavo Padovan <gustavo@padovan.org> writes:

> 2014-11-18 Kevin Hilman <khilman@kernel.org>:
>
>> Javier Martinez Canillas <javier.martinez@collabora.co.uk> writes:
>> 
>> > The Exynos DRM driver register its sub-devices platform drivers in
>> > the probe function but after commit 43c0767 ("of/platform: Move
>> > platform devices under /sys/devices/platform"), this is causing
>> > a deadlock in __driver_attach(). Fix this by moving the platform
>> > drivers registration to exynos_drm_init().
>> >
>> > Suggested-by: Andrzej Hajda <a.hajda@samsung.com>
>> > Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
>> > ---
>> >
>> > This issue was reported by both Krzysztof Kozlowski [0] and Kevin Hilman [1].
>> >
>> > Inki Dae said that he will fix it property by separating the Exynos DRM
>> > driver in different sub-modules but I post this patch as RFC anyways so
>> > others can test if this fixes their boot issue.
>> 
>> It fixes the DRM deadlock, issue for me on exynos5800-peach-pi, but then
>> it proceeds to panic in the workqueue code called by the asoc max98090
>> codec[1].
>> 
>> If I then disable CONFIG_SND_SOC_SNOW, I can get it to boot to a shell,
>> but I still don't have display output.
>> 
>> Is anyone at Samsung testing linux-next?  If so, on what platforms?  It
>> would really be nice if your linux-next work was tested on these
>> publically-available 542x/5800 platforms (peach-pi, peach-pit,
>> odroid-xu3) which would also allow lots of others to help you test and
>> validate.
>
> It would also be good to add drm-exynos-next to the daily linux-next build.
> Currently drm-exynos-next is ahead of linux-next. This patch from Javier for
> example only applies on linux-next.

Which tree is the drm-exynos-next branch in?

Kevin

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Javier Martinez Canillas]

Hello Kevin,

On 11/18/2014 11:46 PM, Kevin Hilman wrote:
>>> Is anyone at Samsung testing linux-next?  If so, on what platforms?  It
>>> would really be nice if your linux-next work was tested on these
>>> publically-available 542x/5800 platforms (peach-pi, peach-pit,
>>> odroid-xu3) which would also allow lots of others to help you test and
>>> validate.
>>
>> It would also be good to add drm-exynos-next to the daily linux-next build.
>> Currently drm-exynos-next is ahead of linux-next. This patch from Javier for
>> example only applies on linux-next.
> 
> Which tree is the drm-exynos-next branch in?
> 

It is in Inki Dae's drm-exynos tree:

git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git

Best regards,
Javier

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Javier Martinez Canillas]

[adding Paolo and Vivek as cc]

Hello,

On 11/18/2014 07:41 PM, Kevin Hilman wrote:
> 
> It fixes the DRM deadlock, issue for me on exynos5800-peach-pi, but then
> it proceeds to panic in the workqueue code called by the asoc max98090
> codec[1].
> 
> If I then disable CONFIG_SND_SOC_SNOW, I can get it to boot to a shell,
> but I still don't have display output.
> 

Paolo Pisati pointed out in another thread that he needed the patch
"[PATCH v2 2/2] arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy"
is also needed to get display working for exynos on linux-next.

I've pinged Kukjin to apply this as a -rc fix since is needed after
a5ec598 ("phy: exynos-dp-video: Use syscon support to control pmu register")
landed in 3.18 which broke the Exynos Display Port PHY:

exynos-dp-video-phy 10040728.video-phy: Failed to lookup PMU regmap

I've an Exynos5800 Peach Pi now so I wanted to test display on it. Just $subject
and [0] should be enough to have display working on Peach Pi with linux-next but
it fails to me with:

exynos-mipi-video-phy 10040714.video-phy: can't request region for resource [mem 0x10040714-0x1004071f]

The same issue was reported by Paolo a couple of days ago [1].

Vivek,

Any idea what could cause this regression on linux-next? As reported by Paolo this
works well for me in 3.18-rc5.

Best regards,
Javier

[0]: https://lkml.org/lkml/2014/10/30/394
[1]: http://www.spinics.net/lists/linux-samsung-soc/msg39032.html

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Kevin Hilman]

Javier Martinez Canillas <javier.martinez@collabora.co.uk> writes:

> [adding Paolo and Vivek as cc]
>
> Hello,
>
> On 11/18/2014 07:41 PM, Kevin Hilman wrote:
>> 
>> It fixes the DRM deadlock, issue for me on exynos5800-peach-pi, but then
>> it proceeds to panic in the workqueue code called by the asoc max98090
>> codec[1].
>> 
>> If I then disable CONFIG_SND_SOC_SNOW, I can get it to boot to a shell,
>> but I still don't have display output.
>> 
>
> Paolo Pisati pointed out in another thread that he needed the patch
> "[PATCH v2 2/2] arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy"
> is also needed to get display working for exynos on linux-next.
>
> I've pinged Kukjin to apply this as a -rc fix since is needed after
> a5ec598 ("phy: exynos-dp-video: Use syscon support to control pmu register")
> landed in 3.18 which broke the Exynos Display Port PHY:
>
> exynos-dp-video-phy 10040728.video-phy: Failed to lookup PMU regmap
>
> I've an Exynos5800 Peach Pi now so I wanted to test display on it. Just $subject
> and [0] should be enough to have display working on Peach Pi 

Yes, with those two patches, peach-pi display working on v3.18-rc5 for me.

> with linux-next but
> it fails to me with:
>
> exynos-mipi-video-phy 10040714.video-phy: can't request region for resource [mem 0x10040714-0x1004071f]
>
> The same issue was reported by Paolo a couple of days ago [1].

For me, with linux-next, I'm still getting the DRM deadlock.  Trying
your patch that moves things to module_init gets past the deadlock, but
still doesn't boot unless I disable CONFIG_SND_SOC_SNOW.  Doing that I
see the same video-phy error though.

Kevin

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Kevin Hilman]

Kevin Hilman <khilman@kernel.org> writes:

> Javier Martinez Canillas <javier.martinez@collabora.co.uk> writes:
>
>> [adding Paolo and Vivek as cc]
>>
>> Hello,
>>
>> On 11/18/2014 07:41 PM, Kevin Hilman wrote:
>>> 
>>> It fixes the DRM deadlock, issue for me on exynos5800-peach-pi, but then
>>> it proceeds to panic in the workqueue code called by the asoc max98090
>>> codec[1].
>>> 
>>> If I then disable CONFIG_SND_SOC_SNOW, I can get it to boot to a shell,
>>> but I still don't have display output.
>>> 
>>
>> Paolo Pisati pointed out in another thread that he needed the patch
>> "[PATCH v2 2/2] arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy"
>> is also needed to get display working for exynos on linux-next.
>>
>> I've pinged Kukjin to apply this as a -rc fix since is needed after
>> a5ec598 ("phy: exynos-dp-video: Use syscon support to control pmu register")
>> landed in 3.18 which broke the Exynos Display Port PHY:
>>
>> exynos-dp-video-phy 10040728.video-phy: Failed to lookup PMU regmap
>>
>> I've an Exynos5800 Peach Pi now so I wanted to test display on it. Just $subject
>> and [0] should be enough to have display working on Peach Pi 
>
> Yes, with those two patches, peach-pi display working on v3.18-rc5 for me.
>
>> with linux-next but
>> it fails to me with:
>>
>> exynos-mipi-video-phy 10040714.video-phy: can't request region for resource [mem 0x10040714-0x1004071f]
>>
>> The same issue was reported by Paolo a couple of days ago [1].
>
> For me, with linux-next, I'm still getting the DRM deadlock.  Trying
> your patch that moves things to module_init gets past the deadlock, but
> still doesn't boot unless I disable CONFIG_SND_SOC_SNOW.  Doing that I
> see the same video-phy error though.

Another interesting data point is that the 2 patches which get things
working on v3.18-rc5, when applied on Kukjin's for-next branch, result
in a kernel that boots (which is better than linux-next), but without
a working display. :(

Kevin

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Vivek Gautam]

Hi Javier, Kevin,



On Wed, Nov 19, 2014 at 10:22 PM, Javier Martinez Canillas
<javier.martinez@collabora.co.uk> wrote:
> [adding Paolo and Vivek as cc]
>
> Hello,
>
> On 11/18/2014 07:41 PM, Kevin Hilman wrote:
>>
>> It fixes the DRM deadlock, issue for me on exynos5800-peach-pi, but then
>> it proceeds to panic in the workqueue code called by the asoc max98090
>> codec[1].
>>
>> If I then disable CONFIG_SND_SOC_SNOW, I can get it to boot to a shell,
>> but I still don't have display output.
>>
>
> Paolo Pisati pointed out in another thread that he needed the patch
> "[PATCH v2 2/2] arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy"
> is also needed to get display working for exynos on linux-next.
>
> I've pinged Kukjin to apply this as a -rc fix since is needed after
> a5ec598 ("phy: exynos-dp-video: Use syscon support to control pmu register")
> landed in 3.18 which broke the Exynos Display Port PHY:
>
> exynos-dp-video-phy 10040728.video-phy: Failed to lookup PMU regmap
>
> I've an Exynos5800 Peach Pi now so I wanted to test display on it. Just $subject
> and [0] should be enough to have display working on Peach Pi with linux-next but
> it fails to me with:
>
> exynos-mipi-video-phy 10040714.video-phy: can't request region for resource [mem 0x10040714-0x1004071f]
>
> The same issue was reported by Paolo a couple of days ago [1].
>
> Vivek,
>
> Any idea what could cause this regression on linux-next? As reported by Paolo this
> works well for me in 3.18-rc5.

I tested linux-next on Exynos5800 peach-pi board with linux-next and and the two
patches $Subject and [0].

Below is my git hash:
4d9e6ee drm/exynos: Move platform drivers registration to module init
4545ed4 POSTED: arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
36391a5 Add linux-next specific files for 20141119
9b1ced1 Merge branch 'akpm/master'
282497e mm: add strictlimit knob

With this display works for me.
Without $Subject patch i get lookup in drm.

Javier can you tell me your git hash. Was it on yesterday's linux-next ?

>
> Best regards,
> Javier
>
> [0]: https://lkml.org/lkml/2014/10/30/394
> [1]: http://www.spinics.net/lists/linux-samsung-soc/msg39032.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
Best Regards
Vivek Gautam
Samsung R&D Institute, Bangalore
India

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Vivek Gautam]

Hi,


On Thu, Nov 20, 2014 at 12:36 PM, Vivek Gautam
<gautamvivek1987@gmail.com> wrote:
> Hi Javier, Kevin,
>
>
>
> On Wed, Nov 19, 2014 at 10:22 PM, Javier Martinez Canillas
> <javier.martinez@collabora.co.uk> wrote:
>> [adding Paolo and Vivek as cc]
>>
>> Hello,
>>
>> On 11/18/2014 07:41 PM, Kevin Hilman wrote:
>>>
>>> It fixes the DRM deadlock, issue for me on exynos5800-peach-pi, but then
>>> it proceeds to panic in the workqueue code called by the asoc max98090
>>> codec[1].
>>>
>>> If I then disable CONFIG_SND_SOC_SNOW, I can get it to boot to a shell,
>>> but I still don't have display output.
>>>
>>
>> Paolo Pisati pointed out in another thread that he needed the patch
>> "[PATCH v2 2/2] arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy"
>> is also needed to get display working for exynos on linux-next.
>>
>> I've pinged Kukjin to apply this as a -rc fix since is needed after
>> a5ec598 ("phy: exynos-dp-video: Use syscon support to control pmu register")
>> landed in 3.18 which broke the Exynos Display Port PHY:
>>
>> exynos-dp-video-phy 10040728.video-phy: Failed to lookup PMU regmap
>>
>> I've an Exynos5800 Peach Pi now so I wanted to test display on it. Just $subject
>> and [0] should be enough to have display working on Peach Pi with linux-next but
>> it fails to me with:
>>
>> exynos-mipi-video-phy 10040714.video-phy: can't request region for resource [mem 0x10040714-0x1004071f]
>>
>> The same issue was reported by Paolo a couple of days ago [1].
>>
>> Vivek,
>>
>> Any idea what could cause this regression on linux-next? As reported by Paolo this
>> works well for me in 3.18-rc5.
>
> I tested linux-next on Exynos5800 peach-pi board with linux-next and and the two
> patches $Subject and [0].
>
> Below is my git hash:
> 4d9e6ee drm/exynos: Move platform drivers registration to module init
> 4545ed4 POSTED: arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
> 36391a5 Add linux-next specific files for 20141119
> 9b1ced1 Merge branch 'akpm/master'
> 282497e mm: add strictlimit knob

used exynos_defconfig

>
> With this display works for me.
> Without $Subject patch i get lookup in drm.
>
> Javier can you tell me your git hash. Was it on yesterday's linux-next ?

With 3.18-rc5 i could see display on Exynos5800 peach-pi with
following git hash:

b6dca11 drm/exynos: dp: Remove support for unused dptx-phy
7cc5c2d ARM: exynos_defconfig: Enable options for display panel support
d0aca5e arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
fc14f9c Linux 3.18-rc5
e35c5a2 Merge tag 'armsoc-for-rc5' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc

I don't need this drm lockup patch with 3.18-rc5 (with exynos_defconfig).

I am checking further with linux-samsung, coz i could see weird
behavior as mentioned
in [1] with linux-samsun/for-next merged with above git hash.

>> [0]: https://lkml.org/lkml/2014/10/30/394
>> [1]: http://www.spinics.net/lists/linux-samsung-soc/msg39032.html




-- 
Best Regards
Vivek Gautam
Samsung R&D Institute, Bangalore
India

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Javier Martinez Canillas]

Hello Vivek,

On 11/20/2014 08:51 AM, Vivek Gautam wrote:
>>
>> I tested linux-next on Exynos5800 peach-pi board with linux-next and and the two
>> patches $Subject and [0].
>>
>> Below is my git hash:
>> 4d9e6ee drm/exynos: Move platform drivers registration to module init
>> 4545ed4 POSTED: arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
>> 36391a5 Add linux-next specific files for 20141119
>> 9b1ced1 Merge branch 'akpm/master'
>> 282497e mm: add strictlimit knob
> 
> used exynos_defconfig
>

Same here.

>>
>> With this display works for me.
>> Without $Subject patch i get lookup in drm.
>>

I tested with today linux-next (next-20141120) and display is indeed
working for me. So it seems that whatever caused the error in the
phy-exynos-mipi-video driver reported by Paolo, got fixed recently.

My working git hash is:

65a8d01 arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
a9b43cb drm/exynos: Move platform drivers registration to module init
5b83d7a Add linux-next specific files for 20141120
1172916 mm: add strictlimit knob

I did have to disable CONFIG_SND_SOC_SNOW though, otherwise the kernel
did not boot due the issue reported previously by Kevin.

>> Javier can you tell me your git hash. Was it on yesterday's linux-next ?
> 

In fact, my branch where I could reproduce the phy-exynos-mipi-video issue
was not based on yesterday's next but next-20141117. The git hash is:

9fb5d7c arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
f740096 drm/exynos: Move platform drivers registration to module init
efefb5c Add linux-next specific files for 20141117
8c944d7 mm: add strictlimit knob

> With 3.18-rc5 i could see display on Exynos5800 peach-pi with
> following git hash:
> 
> b6dca11 drm/exynos: dp: Remove support for unused dptx-phy
> 7cc5c2d ARM: exynos_defconfig: Enable options for display panel support
> d0aca5e arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
> fc14f9c Linux 3.18-rc5
> e35c5a2 Merge tag 'armsoc-for-rc5' of
> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
> 
> I don't need this drm lockup patch with 3.18-rc5 (with exynos_defconfig).
> 

Yes, that works because the commit that caused the Exynos DRM lockup was:

43c0767 ("of/platform: Move platform devices under /sys/devices/platform")

which landed in next-20141105.

Reverting 43c0767 and only applying [0] should have the same effect.

> I am checking further with linux-samsung, coz i could see weird
> behavior as mentioned
> in [1] with linux-samsun/for-next merged with above git hash.
>

Great, it should be good to know what caused:

exynos-mipi-video-phy 10040714.video-phy: can't request region for resource [mem 0x10040714-0x1004071f]

even when I could not reproduce it anymore with today's linux-next.

>>> [0]: https://lkml.org/lkml/2014/10/30/394
>>> [1]: http://www.spinics.net/lists/linux-samsung-soc/msg39032.html

Best regards,
Javier

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Vivek Gautam]

Hi Javier,


On Thu, Nov 20, 2014 at 2:15 PM, Javier Martinez Canillas
<javier.martinez@collabora.co.uk> wrote:
> Hello Vivek,
>
> On 11/20/2014 08:51 AM, Vivek Gautam wrote:
>>>
>>> I tested linux-next on Exynos5800 peach-pi board with linux-next and and the two
>>> patches $Subject and [0].
>>>
>>> Below is my git hash:
>>> 4d9e6ee drm/exynos: Move platform drivers registration to module init
>>> 4545ed4 POSTED: arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
>>> 36391a5 Add linux-next specific files for 20141119
>>> 9b1ced1 Merge branch 'akpm/master'
>>> 282497e mm: add strictlimit knob
>>
>> used exynos_defconfig
>>
>
> Same here.
>
>>>
>>> With this display works for me.
>>> Without $Subject patch i get lookup in drm.
>>>
>
> I tested with today linux-next (next-20141120) and display is indeed
> working for me. So it seems that whatever caused the error in the
> phy-exynos-mipi-video driver reported by Paolo, got fixed recently.
>
> My working git hash is:
>
> 65a8d01 arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
> a9b43cb drm/exynos: Move platform drivers registration to module init
> 5b83d7a Add linux-next specific files for 20141120
> 1172916 mm: add strictlimit knob
>
> I did have to disable CONFIG_SND_SOC_SNOW though, otherwise the kernel
> did not boot due the issue reported previously by Kevin.
>
>>> Javier can you tell me your git hash. Was it on yesterday's linux-next ?
>>
>
> In fact, my branch where I could reproduce the phy-exynos-mipi-video issue
> was not based on yesterday's next but next-20141117. The git hash is:
>
> 9fb5d7c arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
> f740096 drm/exynos: Move platform drivers registration to module init
> efefb5c Add linux-next specific files for 20141117
> 8c944d7 mm: add strictlimit knob
>
>> With 3.18-rc5 i could see display on Exynos5800 peach-pi with
>> following git hash:
>>
>> b6dca11 drm/exynos: dp: Remove support for unused dptx-phy
>> 7cc5c2d ARM: exynos_defconfig: Enable options for display panel support
>> d0aca5e arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
>> fc14f9c Linux 3.18-rc5
>> e35c5a2 Merge tag 'armsoc-for-rc5' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
>>
>> I don't need this drm lockup patch with 3.18-rc5 (with exynos_defconfig).
>>
>
> Yes, that works because the commit that caused the Exynos DRM lockup was:
>
> 43c0767 ("of/platform: Move platform devices under /sys/devices/platform")
>
> which landed in next-20141105.
>
> Reverting 43c0767 and only applying [0] should have the same effect.
>
>> I am checking further with linux-samsung, coz i could see weird
>> behavior as mentioned
>> in [1] with linux-samsun/for-next merged with above git hash.
>>
>
> Great, it should be good to know what caused:

On linux-samsung tree the only patch that's missing apart from dptx-phy patches
is the syscon patch from Pankaj Dubey:
b784b98 mfd: syscon: Decouple syscon interface from platform devices

So with below git hash, linux-samsung/for-next display works fine along with
other devices that request PMU system controller :

7bd219e drm/exynos: dp: Remove support for unused dptx-phy
e8f21fd arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
7099bde Revert "Revert "ARM: exynos_defconfig: Enable options for
display panel support""
713a994 mfd: syscon: Decouple syscon interface from platform devices
7552917 Revert "ARM: exynos_defconfig: Enable options for display
panel support"             /* This is Kukjin's for-next today */
ff0391a Merge branch 'v3.19-samsung-defconfig' into for-next
26c6283 Merge branch 'v3.18-samsung-fixes' into for-next
cf864fd Merge branch 'v3.18-samsung-defconfig' into for-next
98b6380 ARM: exynos_defconfig: Enable max77802 rtc and clock drivers
839275c ARM: exynos_defconfig: Use 16 minors per MMC block device
0526f27 ARM: dts: Explicitly set dr_mode on exynos5250-snow
fc14f9c Linux 3.18-rc5


>
> exynos-mipi-video-phy 10040714.video-phy: can't request region for resource [mem 0x10040714-0x1004071f]

The only reason i see this fails is since PMU is now requesting the
entire memory
region with base 0x10040000. We should convert the mipi-phy pmu
register handling
too through syscon.

>
> even when I could not reproduce it anymore with today's linux-next.
>
>>>> [0]: https://lkml.org/lkml/2014/10/30/394
>>>> [1]: http://www.spinics.net/lists/linux-samsung-soc/msg39032.html



-- 
Best Regards
Vivek Gautam
Samsung R&D Institute, Bangalore
India

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Inki Dae]

Hi Javier,

On 2014년 11월 18일 22:53, Javier Martinez Canillas wrote:
> The Exynos DRM driver register its sub-devices platform drivers in
> the probe function but after commit 43c0767 ("of/platform: Move
> platform devices under /sys/devices/platform"), this is causing
> a deadlock in __driver_attach(). Fix this by moving the platform
> drivers registration to exynos_drm_init().

Could you re-base this patch on top of exynos-drm-next? I tried to
separate sub drivers into independent drivers but it seems that we need
more times. So I will merge your patch.

Thanks,
Inki Dae

> 
> Suggested-by: Andrzej Hajda <a.hajda@samsung.com>
> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> ---
> 
> This issue was reported by both Krzysztof Kozlowski [0] and Kevin Hilman [1].
> 
> Inki Dae said that he will fix it property by separating the Exynos DRM
> driver in different sub-modules but I post this patch as RFC anyways so
> others can test if this fixes their boot issue.
> 
> [0]: https://lkml.org/lkml/2014/11/6/125
> [1]: http://www.spinics.net/lists/linux-samsung-soc/msg39050.html
> 
>  drivers/gpu/drm/exynos/exynos_drm_drv.c | 163 ++++++++++++++++----------------
>  1 file changed, 79 insertions(+), 84 deletions(-)
> 
> diff --git a/drivers/gpu/drm/exynos/exynos_drm_drv.c b/drivers/gpu/drm/exynos/exynos_drm_drv.c
> index e277d4f..5386fea 100644
> --- a/drivers/gpu/drm/exynos/exynos_drm_drv.c
> +++ b/drivers/gpu/drm/exynos/exynos_drm_drv.c
> @@ -559,15 +559,58 @@ static const struct component_master_ops exynos_drm_ops = {
>  static int exynos_drm_platform_probe(struct platform_device *pdev)
>  {
>  	struct component_match *match;
> -	int ret;
>  
>  	pdev->dev.coherent_dma_mask = DMA_BIT_MASK(32);
>  	exynos_drm_driver.num_ioctls = ARRAY_SIZE(exynos_ioctls);
>  
> +	match = exynos_drm_match_add(&pdev->dev);
> +	if (IS_ERR(match))
> +		return PTR_ERR(match);
> +
> +	return component_master_add_with_match(&pdev->dev, &exynos_drm_ops,
> +					       match);
> +}
> +
> +static int exynos_drm_platform_remove(struct platform_device *pdev)
> +{
> +	component_master_del(&pdev->dev, &exynos_drm_ops);
> +	return 0;
> +}
> +
> +static struct platform_driver exynos_drm_platform_driver = {
> +	.probe	= exynos_drm_platform_probe,
> +	.remove	= exynos_drm_platform_remove,
> +	.driver	= {
> +		.name	= "exynos-drm",
> +		.pm	= &exynos_drm_pm_ops,
> +	},
> +};
> +
> +static int exynos_drm_init(void)
> +{
> +	int ret;
> +
> +	/*
> +	 * Register device object only in case of Exynos SoC.
> +	 *
> +	 * Below codes resolves temporarily infinite loop issue incurred
> +	 * by Exynos drm driver when using multi-platform kernel.
> +	 * So these codes will be replaced with more generic way later.
> +	 */
> +	if (!of_machine_is_compatible("samsung,exynos3") &&
> +			!of_machine_is_compatible("samsung,exynos4") &&
> +			!of_machine_is_compatible("samsung,exynos5"))
> +		return -ENODEV;
> +
> +	exynos_drm_pdev = platform_device_register_simple("exynos-drm", -1,
> +								NULL, 0);
> +	if (IS_ERR(exynos_drm_pdev))
> +		return PTR_ERR(exynos_drm_pdev);
> +
>  #ifdef CONFIG_DRM_EXYNOS_FIMD
>  	ret = platform_driver_register(&fimd_driver);
>  	if (ret < 0)
> -		return ret;
> +		goto err_unregister_pdev;
>  #endif
>  
>  #ifdef CONFIG_DRM_EXYNOS_DP
> @@ -591,21 +634,10 @@ static int exynos_drm_platform_probe(struct platform_device *pdev)
>  		goto err_unregister_mixer_drv;
>  #endif
>  
> -	match = exynos_drm_match_add(&pdev->dev);
> -	if (IS_ERR(match)) {
> -		ret = PTR_ERR(match);
> -		goto err_unregister_hdmi_drv;
> -	}
> -
> -	ret = component_master_add_with_match(&pdev->dev, &exynos_drm_ops,
> -						match);
> -	if (ret < 0)
> -		goto err_unregister_hdmi_drv;
> -
>  #ifdef CONFIG_DRM_EXYNOS_G2D
>  	ret = platform_driver_register(&g2d_driver);
>  	if (ret < 0)
> -		goto err_del_component_master;
> +		goto err_unregister_hdmi_drv;
>  #endif
>  
>  #ifdef CONFIG_DRM_EXYNOS_FIMC
> @@ -636,9 +668,27 @@ static int exynos_drm_platform_probe(struct platform_device *pdev)
>  		goto err_unregister_ipp_drv;
>  #endif
>  
> -	return ret;
> +#ifdef CONFIG_DRM_EXYNOS_VIDI
> +	ret = exynos_drm_probe_vidi();
> +	if (ret < 0)
> +		goto err_unregister_ipp_dev;
> +#endif
> +
> +	ret = platform_driver_register(&exynos_drm_platform_driver);
> +	if (ret)
> +		goto err_remove_vidi;
> +
> +	return 0;
> +
> +err_remove_vidi:
> +#ifdef CONFIG_DRM_EXYNOS_VIDI
> +	exynos_drm_remove_vidi();
> +err_unregister_pd:
> +#endif
>  
>  #ifdef CONFIG_DRM_EXYNOS_IPP
> +err_unregister_ipp_dev:
> +	exynos_platform_device_ipp_unregister();
>  err_unregister_ipp_drv:
>  	platform_driver_unregister(&ipp_driver);
>  err_unregister_gsc_drv:
> @@ -661,11 +711,9 @@ err_unregister_g2d_drv:
>  
>  #ifdef CONFIG_DRM_EXYNOS_G2D
>  	platform_driver_unregister(&g2d_driver);
> -err_del_component_master:
> +err_unregister_hdmi_drv:
>  #endif
> -	component_master_del(&pdev->dev, &exynos_drm_ops);
>  
> -err_unregister_hdmi_drv:
>  #ifdef CONFIG_DRM_EXYNOS_HDMI
>  	platform_driver_unregister(&hdmi_driver);
>  err_unregister_mixer_drv:
> @@ -686,11 +734,21 @@ err_unregister_fimd_drv:
>  #ifdef CONFIG_DRM_EXYNOS_FIMD
>  	platform_driver_unregister(&fimd_driver);
>  #endif
> +
> +err_unregister_pdev:
> +	platform_device_unregister(exynos_drm_pdev);
> +
>  	return ret;
>  }
>  
> -static int exynos_drm_platform_remove(struct platform_device *pdev)
> +static void exynos_drm_exit(void)
>  {
> +	platform_driver_unregister(&exynos_drm_platform_driver);
> +
> +#ifdef CONFIG_DRM_EXYNOS_VIDI
> +	exynos_drm_remove_vidi();
> +#endif
> +
>  #ifdef CONFIG_DRM_EXYNOS_IPP
>  	exynos_platform_device_ipp_unregister();
>  	platform_driver_unregister(&ipp_driver);
> @@ -721,75 +779,12 @@ static int exynos_drm_platform_remove(struct platform_device *pdev)
>  	platform_driver_unregister(&fimd_driver);
>  #endif
>  
> -#ifdef CONFIG_DRM_EXYNOS_DSI
> -	platform_driver_unregister(&dsi_driver);
> -#endif
> -
>  #ifdef CONFIG_DRM_EXYNOS_DP
>  	platform_driver_unregister(&dp_driver);
>  #endif
> -	component_master_del(&pdev->dev, &exynos_drm_ops);
> -	return 0;
> -}
>  
> -static struct platform_driver exynos_drm_platform_driver = {
> -	.probe	= exynos_drm_platform_probe,
> -	.remove	= exynos_drm_platform_remove,
> -	.driver	= {
> -		.name	= "exynos-drm",
> -		.pm	= &exynos_drm_pm_ops,
> -	},
> -};
> -
> -static int exynos_drm_init(void)
> -{
> -	int ret;
> -
> -	/*
> -	 * Register device object only in case of Exynos SoC.
> -	 *
> -	 * Below codes resolves temporarily infinite loop issue incurred
> -	 * by Exynos drm driver when using multi-platform kernel.
> -	 * So these codes will be replaced with more generic way later.
> -	 */
> -	if (!of_machine_is_compatible("samsung,exynos3") &&
> -			!of_machine_is_compatible("samsung,exynos4") &&
> -			!of_machine_is_compatible("samsung,exynos5"))
> -		return -ENODEV;
> -
> -	exynos_drm_pdev = platform_device_register_simple("exynos-drm", -1,
> -								NULL, 0);
> -	if (IS_ERR(exynos_drm_pdev))
> -		return PTR_ERR(exynos_drm_pdev);
> -
> -#ifdef CONFIG_DRM_EXYNOS_VIDI
> -	ret = exynos_drm_probe_vidi();
> -	if (ret < 0)
> -		goto err_unregister_pd;
> -#endif
> -
> -	ret = platform_driver_register(&exynos_drm_platform_driver);
> -	if (ret)
> -		goto err_remove_vidi;
> -
> -	return 0;
> -
> -err_remove_vidi:
> -#ifdef CONFIG_DRM_EXYNOS_VIDI
> -	exynos_drm_remove_vidi();
> -
> -err_unregister_pd:
> -#endif
> -	platform_device_unregister(exynos_drm_pdev);
> -
> -	return ret;
> -}
> -
> -static void exynos_drm_exit(void)
> -{
> -	platform_driver_unregister(&exynos_drm_platform_driver);
> -#ifdef CONFIG_DRM_EXYNOS_VIDI
> -	exynos_drm_remove_vidi();
> +#ifdef CONFIG_DRM_EXYNOS_DSI
> +	platform_driver_unregister(&dsi_driver);
>  #endif
>  	platform_device_unregister(exynos_drm_pdev);
>  }
> 

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Pankaj Dubey]

On 20 November 2014 15:22, Vivek Gautam <gautamvivek1987@gmail.com> wrote:
> Hi Javier,
>
>
> On Thu, Nov 20, 2014 at 2:15 PM, Javier Martinez Canillas
> <javier.martinez@collabora.co.uk> wrote:
>> Hello Vivek,
>>
>> On 11/20/2014 08:51 AM, Vivek Gautam wrote:
>>>>
>>>> I tested linux-next on Exynos5800 peach-pi board with linux-next and and the two
>>>> patches $Subject and [0].
>>>>
>>>> Below is my git hash:
>>>> 4d9e6ee drm/exynos: Move platform drivers registration to module init
>>>> 4545ed4 POSTED: arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
>>>> 36391a5 Add linux-next specific files for 20141119
>>>> 9b1ced1 Merge branch 'akpm/master'
>>>> 282497e mm: add strictlimit knob
>>>
>>> used exynos_defconfig
>>>
>>
>> Same here.
>>
>>>>
>>>> With this display works for me.
>>>> Without $Subject patch i get lookup in drm.
>>>>
>>
>> I tested with today linux-next (next-20141120) and display is indeed
>> working for me. So it seems that whatever caused the error in the
>> phy-exynos-mipi-video driver reported by Paolo, got fixed recently.
>>
>> My working git hash is:
>>
>> 65a8d01 arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
>> a9b43cb drm/exynos: Move platform drivers registration to module init
>> 5b83d7a Add linux-next specific files for 20141120
>> 1172916 mm: add strictlimit knob
>>
>> I did have to disable CONFIG_SND_SOC_SNOW though, otherwise the kernel
>> did not boot due the issue reported previously by Kevin.
>>
>>>> Javier can you tell me your git hash. Was it on yesterday's linux-next ?
>>>
>>
>> In fact, my branch where I could reproduce the phy-exynos-mipi-video issue
>> was not based on yesterday's next but next-20141117. The git hash is:
>>
>> 9fb5d7c arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
>> f740096 drm/exynos: Move platform drivers registration to module init
>> efefb5c Add linux-next specific files for 20141117
>> 8c944d7 mm: add strictlimit knob
>>
>>> With 3.18-rc5 i could see display on Exynos5800 peach-pi with
>>> following git hash:
>>>
>>> b6dca11 drm/exynos: dp: Remove support for unused dptx-phy
>>> 7cc5c2d ARM: exynos_defconfig: Enable options for display panel support
>>> d0aca5e arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
>>> fc14f9c Linux 3.18-rc5
>>> e35c5a2 Merge tag 'armsoc-for-rc5' of
>>> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
>>>
>>> I don't need this drm lockup patch with 3.18-rc5 (with exynos_defconfig).
>>>
>>
>> Yes, that works because the commit that caused the Exynos DRM lockup was:
>>
>> 43c0767 ("of/platform: Move platform devices under /sys/devices/platform")
>>
>> which landed in next-20141105.
>>
>> Reverting 43c0767 and only applying [0] should have the same effect.
>>
>>> I am checking further with linux-samsung, coz i could see weird
>>> behavior as mentioned
>>> in [1] with linux-samsun/for-next merged with above git hash.
>>>
>>
>> Great, it should be good to know what caused:
>
> On linux-samsung tree the only patch that's missing apart from dptx-phy patches
> is the syscon patch from Pankaj Dubey:
> b784b98 mfd: syscon: Decouple syscon interface from platform devices
>

This patch has landed in mfd/for-next and linux-next. Without this on
kgene/for-next, any driver
seeking PMU register via syscon API will fail to get regmap handles.

Thanks,
Pankaj Dubey

> So with below git hash, linux-samsung/for-next display works fine along with
> other devices that request PMU system controller :
>
> 7bd219e drm/exynos: dp: Remove support for unused dptx-phy
> e8f21fd arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
> 7099bde Revert "Revert "ARM: exynos_defconfig: Enable options for
> display panel support""
> 713a994 mfd: syscon: Decouple syscon interface from platform devices
> 7552917 Revert "ARM: exynos_defconfig: Enable options for display
> panel support"             /* This is Kukjin's for-next today */
> ff0391a Merge branch 'v3.19-samsung-defconfig' into for-next
> 26c6283 Merge branch 'v3.18-samsung-fixes' into for-next
> cf864fd Merge branch 'v3.18-samsung-defconfig' into for-next
> 98b6380 ARM: exynos_defconfig: Enable max77802 rtc and clock drivers
> 839275c ARM: exynos_defconfig: Use 16 minors per MMC block device
> 0526f27 ARM: dts: Explicitly set dr_mode on exynos5250-snow
> fc14f9c Linux 3.18-rc5
>
>
>>
>> exynos-mipi-video-phy 10040714.video-phy: can't request region for resource [mem 0x10040714-0x1004071f]
>
> The only reason i see this fails is since PMU is now requesting the
> entire memory
> region with base 0x10040000. We should convert the mipi-phy pmu
> register handling
> too through syscon.
>
>>
>> even when I could not reproduce it anymore with today's linux-next.
>>
>>>>> [0]: https://lkml.org/lkml/2014/10/30/394
>>>>> [1]: http://www.spinics.net/lists/linux-samsung-soc/msg39032.html
>
>
>
> --
> Best Regards
> Vivek Gautam
> Samsung R&D Institute, Bangalore
> India
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Javier Martinez Canillas]

Hello Inki,

On 11/20/2014 03:07 PM, Inki Dae wrote:
> Could you re-base this patch on top of exynos-drm-next? I tried to
> separate sub drivers into independent drivers but it seems that we need
> more times. So I will merge your patch.
> 

Sure, I'll rebase on top of exynos-drm-next and re-post so you can apply it.

BTW, it would be great if exynos-drm-next is pulled in linux-next. That is
what most people use to test integration issues so you can catch earlier any
regression that may arise.

You have to email Stephen Rothwell <sfr@canb.auug.org.au> and point to your
tree and branch and he will be able to add it to linux-next.

> Thanks,
> Inki Dae
> 

Best regards,
Javier

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Inki Dae]

Hi Javier,

On 2014년 11월 20일 23:28, Javier Martinez Canillas wrote:
> Hello Inki,
> 
> On 11/20/2014 03:07 PM, Inki Dae wrote:
>> Could you re-base this patch on top of exynos-drm-next? I tried to
>> separate sub drivers into independent drivers but it seems that we need
>> more times. So I will merge your patch.
>>
> 
> Sure, I'll rebase on top of exynos-drm-next and re-post so you can apply it.
> 
> BTW, it would be great if exynos-drm-next is pulled in linux-next. That is
> what most people use to test integration issues so you can catch earlier any
> regression that may arise.
> 
> You have to email Stephen Rothwell <sfr@canb.auug.org.au> and point to your
> tree and branch and he will be able to add it to linux-next.

Thanks for information. Actually, I received a similar email privately
before. However, exynos-drm-next should go to drm-next first and than to
mainline by Dave who is DRM subsystem maintainer. I think all vendor
specific drm drivers would need to be checked by drm subsystem
maintainer because these changes might be affect drm subsystem or other
vendor specific drm drivers before go to mainline.

If needed, I will make a new branch, which is based on top of linux-next
so other people can check their systems.

Thanks,
Inki Dae

> 
>> Thanks,
>> Inki Dae
>>
> 
> Best regards,
> Javier
> 

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Javier Martinez Canillas]

Hello Inki,

On 11/20/2014 04:06 PM, Inki Dae wrote:
>> BTW, it would be great if exynos-drm-next is pulled in linux-next. That is
>> what most people use to test integration issues so you can catch earlier any
>> regression that may arise.
>> 
>> You have to email Stephen Rothwell <sfr@canb.auug.org.au> and point to your
>> tree and branch and he will be able to add it to linux-next.
> 
> Thanks for information. Actually, I received a similar email privately
> before. However, exynos-drm-next should go to drm-next first and than to
> mainline by Dave who is DRM subsystem maintainer. I think all vendor
> specific drm drivers would need to be checked by drm subsystem
> maintainer because these changes might be affect drm subsystem or other
> vendor specific drm drivers before go to mainline.
>

This is orthogonal to the normal upstreaming path. linux-next is an integration
tree that is created daily. So all the remote branches are merged and a git tag
published. The branch does not get rebased and history is not preserved between
two published linux-next tags.

This is just to test the integration of different subsystems to be sure that a
commit in one tree does not cause a regression in another one so issues can be
spot earlier. For example in the case of $subject, a change in the OF caused a
regression in the Exynos DRM driver.
 
> If needed, I will make a new branch, which is based on top of linux-next
> so other people can check their systems.
>

You don't really need another branch, git will take care of merge everything
in linux-next :)
 
> Thanks,
> Inki Dae
> 

Best regards,
Javier

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Paolo Pisati]

On Thu, Nov 20, 2014 at 03:22:23PM +0530, Vivek Gautam wrote:
>
> On linux-samsung tree the only patch that's missing apart from dptx-phy patches
> is the syscon patch from Pankaj Dubey:
> b784b98 mfd: syscon: Decouple syscon interface from platform devices
> 
> So with below git hash, linux-samsung/for-next display works fine along with
> other devices that request PMU system controller :
> 
> 7bd219e drm/exynos: dp: Remove support for unused dptx-phy
> e8f21fd arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
> 7099bde Revert "Revert "ARM: exynos_defconfig: Enable options for
> display panel support""
> 713a994 mfd: syscon: Decouple syscon interface from platform devices
> 7552917 Revert "ARM: exynos_defconfig: Enable options for display
> panel support"             /* This is Kukjin's for-next today */
> ff0391a Merge branch 'v3.19-samsung-defconfig' into for-next
> 26c6283 Merge branch 'v3.18-samsung-fixes' into for-next
> cf864fd Merge branch 'v3.18-samsung-defconfig' into for-next
> 98b6380 ARM: exynos_defconfig: Enable max77802 rtc and clock drivers
> 839275c ARM: exynos_defconfig: Use 16 minors per MMC block device
> 0526f27 ARM: dts: Explicitly set dr_mode on exynos5250-snow
> fc14f9c Linux 3.18-rc5

are you using a clean exynos_defconfig?
don't you need Javier's "drm/exynos: Move platform drivers registration to
module init" patch too?

kgene/for-next at:

7552917 Revert "ARM: exynos_defconfig: Enable options for display panel support"

plus:

5e1e068 arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
36d908e drm/exynos: dp: Remove support for unused dptx-phy
624bff2 POSTED: mfd: syscon: Decouple syscon interface from syscon devices
68944e3 Revert "Revert "ARM: exynos_defconfig: Enable options for display panel support""

hangs with a black screen (albeit backlight seems to be on) on boot.
I'm betting on Javier's patch at this point (i even tried disabling SND_SOC_SNOW
but that didn't help).
-- 
bye,
p.

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Kevin Hilman]

Hi Vivek,

Vivek Gautam <gautamvivek1987@gmail.com> writes:

[...]

> I tested linux-next on Exynos5800 peach-pi board with linux-next and and the two
> patches $Subject and [0].
>
> Below is my git hash:
> 4d9e6ee drm/exynos: Move platform drivers registration to module init
> 4545ed4 POSTED: arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
> 36391a5 Add linux-next specific files for 20141119
> 9b1ced1 Merge branch 'akpm/master'
> 282497e mm: add strictlimit knob
>
> With this display works for me.
> Without $Subject patch i get lookup in drm.

The current linux-next (next-20141120) is still not fully booting for
me.  I do see the penguins come up on the display, but it doesn't finish
booting.   Full boot log below.

I'm building using exynos_defconfig with CONFIG_SND_SOC_SNOW=n due to
other errors previously reported.  (Vivek, BTW, I'm curious how your peach-pi
is booting with the audio support enabled.)

Here's how I'm creating the tree, which appears to be the same as what
you guys are doing, but just to be thorough:

$ git reset --hard next/master
HEAD is now at 5b83d7ad9106 Add linux-next specific files for 20141120

$ pwclient git-am 5197701
Applying patch #5197701 using 'git am'
Description: [v2,2/2] arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
Applying: arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy

$ pwclient git-am 5328881
Applying patch #5328881 using 'git am'
Description: [RFC,1/1] drm/exynos: Move platform drivers registration to module init
Applying: drm/exynos: Move platform drivers registration to module init

$ git log --oneline -n5
b16800da58a3 drm/exynos: Move platform drivers registration to module init
87541edf8a17 arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
5b83d7ad9106 Add linux-next specific files for 20141120
fd7e97b09f45 Merge branch 'akpm/master'
11729160b2d7 mm: add strictlimit knob

Kevin


[1] 
Connected to chromebook2 console [channel connected] (~$quit to exit)
(user:khilman) is already connected


# PYBOOT: console: connected.
~$hardreset

Command(chromebook2 console)> hardreset
(user:khilman) Reboot chromebook2
Reboot: chromebook2 ; phidget 4 2 :  ('off', 1, 'on')


U-Boot 2013.04-gb98ed09 (Apr 30 2014 - 16:57:31) for Peach

CPU:Exynos5422@1800MHz

Board: Google Peach Pi, rev 13.6
I2C:   ready
DRAM:  3.5 GiB
PMIC max77802-pmic initialized
CPU:Exynos5422@1800MHz
TPS65090 PMIC EC init
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
SF: Detected W25Q32DW with page size 4 KiB, total 32 MiB
In:    cros-ec-keyb
Out:   serial
Err:   lcd
SF: Detected W25Q32DW with page size 4 KiB, total 32 MiB
ELOG: Event(17) added with size 13
Net:   No ethernet found.
Hit any key to stop autoboot:  2 

# PYBOOT: u-boot: taking control.
 0 
Exynos DP init done
Peach # 
Peach setenv stdout serial
# setenv stdout serialversion

Peach # versionsetenv preboot "usb start; sleep 1"


U-Boot 2013.04-gb98ed09 (Apr 30 2014 - 16:57:31) for Peach
armv7a-cros-linux-gnueabi-gcc.real (4.7.2_cos_gg_c8f69e0) 4.7.x-google 20130114 (prerelease)
GNU ld (binutils-2.22_cos_gg_2) 2.22
Peach # setenv preboot "usb start; sleep 1"setenv bootargs console=tty1 console=ttySAC3,115200 debug earlyprintk rw root=/dev/mmcblk1p3 rootwait rootfstype=ext3

Peach # setenv bootargs console=tty1 console=ttySAC3,115200 debug earlyprintk rw root=/dev/mmcblk1p3 rootwait rootfstype=ext3if test -n ${initenv}; then run initenv; fi

Peach # if test -n ${initenv}; then run initenv; fiif test -n ${preboot}; then run preboot; fi

Peach # if test -n ${preboot}; then run preboot; fisetenv autoload no; setenv autoboot no

(Re)start USB...
USB0:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
USB1:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 1 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices... 1 Ethernet Device(s) found
Peach # dhcp
dhcp
Waiting for Ethernet connection... done.
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 192.168.1.110
Peach # setenv serverip 192.168.1.2
setenv serverip 192.168.1.2
Peach # if test -n ${netargs}; then run netargs; fi
if test -n ${netargs}; then run netargs; fi
Peach # tftp 0x41000000 192.168.1.2:tmp/chromebook2-3T8ptb/uImage-48m8WK
tftp 0x41000000 192.168.1.2:tmp/chromebook2-3T8ptb/uImage-48m8WK
Using asx0 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.110
Filename 'tmp/chromebook2-3T8ptb/uImage-48m8WK'.
Load address: 0x41000000
Loading: *#################################################################
 #################################################################
 #################################################################
 ##########################################
 1.2 MiB/s
done
Bytes transferred = 3473930 (35020a hex)
Peach # printenv bootargs
printenv bootargs
bootargs=console=tty1 console=ttySAC3,115200 debug earlyprintk rw root=/dev/mmcblk1p3 rootwait rootfstype=ext3
Peach # bootm 0x41000000  

# PYBOOT: u-boot: jumping to kernel image
bootm 0x41000000  
## Booting kernel from Legacy Image at 41000000 ...
   Image Name:   Linux
   Created:      2014-11-20  16:21:32 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3473866 Bytes = 3.3 MiB
   Load Address: 41000000
   Entry Point:  41000040
   Verifying Checksum ... OK
   XIP Kernel Image ... OK

Starting kernel ...

Timer summary in microseconds:
       Mark    Elapsed  Stage
          0          0  reset
  4,305,689  4,305,689  board_init_f
  4,398,948     93,259  board_init_r
  4,550,725    151,777  id=64
  4,552,531      1,806  main_loop
  6,386,676  1,834,145  usb_start
 10,173,649  3,786,973  id=80
 10,173,649          0  eth_start
 10,728,307    554,658  bootp_start
 14,324,489  3,596,182  bootp_stop
 14,324,495          6  id=81
 14,324,622        127  id=82
 14,658,846    334,224  tftp_start
 17,453,672  2,794,826  tftp_done
 17,453,672          0  id=84
 17,679,605    225,933  bootm_start
 17,679,607          2  id=1
 17,684,369      4,762  id=2
 17,684,371          2  id=3
 17,731,321     46,950  id=5
 17,731,321          0  id=4
 17,731,322          1  id=6
 17,731,324          2  id=14
 17,736,845      5,521  id=7
 17,737,009        164  id=15
 17,739,102      2,093  start_kernel

Accumulated time:
                 7,015  SPI read
cleanup_before_linux_select: Console recording failed (1)
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.18.0-rc5-next-20141120-07674-gb16800da58a3 (khilman@paris) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-12ubuntu1) ) #7 SMP PREEMPT Thu Nov 20 08:21:03 PST 2014
[    0.000000] CPU: ARMv7 Processor [412fc0f3] revision 3 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] Machine model: Google Peach Pi Rev 10+
[    0.000000] Ignoring memory range 0x20000000 - 0x40000000
[    0.000000] cma: Reserved 64 MiB at 0xfbc00000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 786431
[    0.000000] free_area_init_node: node 0, pgdat c06b4380, node_mem_map edff6000
[    0.000000]   Normal zone: 1520 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 194560 pages, LIFO batch:31
[    0.000000]   HighMem zone: 4624 pages used for memmap
[    0.000000]   HighMem zone: 591871 pages, LIFO batch:31
[    0.000000] PERCPU: Embedded 9 pages/cpu @edf6c000 s7616 r8192 d21056 u36864
[    0.000000] pcpu-alloc: s7616 r8192 d21056 u36864 alloc=9*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 784911
[    0.000000] Kernel command line: console=tty1 console=ttySAC3,115200 debug earlyprintk rw root=/dev/mmcblk1p3 rootwait rootfstype=ext3
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 3047236K/3145724K available (4561K kernel code, 211K rwdata, 1584K rodata, 300K init, 284K bss, 32952K reserved, 65536K cma-reserved, 2301948K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06086d0   (6146 kB)
[    0.000000]       .init : 0xc0609000 - 0xc0654000   ( 300 kB)
[    0.000000]       .data : 0xc0654000 - 0xc0688cc0   ( 212 kB)
[    0.000000]        .bss : 0xc0688cc0 - 0xc06cff04   ( 285 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] GIC physical location is 0x10481000
[    0.000000] L2C: failed to init: -19
[    0.000000] Switching to timer-based delay loop, resolution 41ns
[    0.000003] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956969942ns
[    0.000207] Console: colour dummy device 80x30
[    0.000422] console [tty1] enabled
[    0.000440] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=120000)
[    0.000457] pid_max: default: 32768 minimum: 301
[    0.000566] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000578] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000955] CPU: Testing write buffer coherency: ok
[    0.001166] CPU0: update cpu_capacity 1535
[    0.001177] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.001277] Setting up static identity map for 0x404528b8 - 0x40452910
[    0.001435] ARM CCI driver probed
[    0.001851] Exynos MCPM support installed
[    0.030221] CPU1: Booted secondary processor
[    0.030256] CPU1: update cpu_capacity 1535
[    0.030259] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.040216] CPU2: Booted secondary processor
[    0.040241] CPU2: update cpu_capacity 1535
[    0.040245] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.050210] CPU3: Booted secondary processor
[    0.050236] CPU3: update cpu_capacity 1535
[    0.050240] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.060246] CPU4: Booted secondary processor
[    0.060345] CPU4: update cpu_capacity 448
[    0.060355] CPU4: thread -1, cpu 0, socket 1, mpidr 80000100
[    0.070236] CPU5: Booted secondary processor
[    0.070299] CPU5: update cpu_capacity 448
[    0.070309] CPU5: thread -1, cpu 1, socket 1, mpidr 80000101
[    0.080241] CPU6: Booted secondary processor
[    0.080303] CPU6: update cpu_capacity 448
[    0.080312] CPU6: thread -1, cpu 2, socket 1, mpidr 80000102
[    0.090238] CPU7: Booted secondary processor
[    0.090301] CPU7: update cpu_capacity 448
[    0.090310] CPU7: thread -1, cpu 3, socket 1, mpidr 80000103
[    0.090381] Brought up 8 CPUs
[    0.090489] SMP: Total of 8 processors activated.
[    0.090498] CPU: All CPU(s) started in SVC mode.
[    0.090976] devtmpfs: initialized
[    0.096059] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[    0.097372] pinctrl core: initialized pinctrl subsystem
[    0.111449] NET: Registered protocol family 16
[    0.112426] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.116449] gpiochip_add: registered GPIOs 0 to 7 on device: gpy7
[    0.116465] gpiochip_add: registered GPIOs 8 to 15 on device: gpx0
[    0.116477] gpiochip_add: registered GPIOs 16 to 23 on device: gpx1
[    0.116490] gpiochip_add: registered GPIOs 24 to 31 on device: gpx2
[    0.116502] gpiochip_add: registered GPIOs 32 to 39 on device: gpx3
[    0.117286] gpiochip_add: registered GPIOs 40 to 47 on device: gpc0
[    0.117300] gpiochip_add: registered GPIOs 48 to 55 on device: gpc1
[    0.117312] gpiochip_add: registered GPIOs 56 to 62 on device: gpc2
[    0.117324] gpiochip_add: registered GPIOs 63 to 66 on device: gpc3
[    0.117336] gpiochip_add: registered GPIOs 67 to 68 on device: gpc4
[    0.117347] gpiochip_add: registered GPIOs 69 to 76 on device: gpd1
[    0.117359] gpiochip_add: registered GPIOs 77 to 82 on device: gpy0
[    0.117371] gpiochip_add: registered GPIOs 83 to 86 on device: gpy1
[    0.117382] gpiochip_add: registered GPIOs 87 to 92 on device: gpy2
[    0.117394] gpiochip_add: registered GPIOs 93 to 100 on device: gpy3
[    0.117406] gpiochip_add: registered GPIOs 101 to 108 on device: gpy4
[    0.117418] gpiochip_add: registered GPIOs 109 to 116 on device: gpy5
[    0.117430] gpiochip_add: registered GPIOs 117 to 124 on device: gpy6
[    0.117953] gpiochip_add: registered GPIOs 125 to 132 on device: gpe0
[    0.117967] gpiochip_add: registered GPIOs 133 to 134 on device: gpe1
[    0.117979] gpiochip_add: registered GPIOs 135 to 140 on device: gpf0
[    0.117991] gpiochip_add: registered GPIOs 141 to 148 on device: gpf1
[    0.118003] gpiochip_add: registered GPIOs 149 to 156 on device: gpg0
[    0.118015] gpiochip_add: registered GPIOs 157 to 164 on device: gpg1
[    0.118027] gpiochip_add: registered GPIOs 165 to 166 on device: gpg2
[    0.118039] gpiochip_add: registered GPIOs 167 to 170 on device: gpj4
[    0.118540] gpiochip_add: registered GPIOs 171 to 178 on device: gpa0
[    0.118554] gpiochip_add: registered GPIOs 179 to 184 on device: gpa1
[    0.118567] gpiochip_add: registered GPIOs 185 to 192 on device: gpa2
[    0.118579] gpiochip_add: registered GPIOs 193 to 197 on device: gpb0
[    0.118591] gpiochip_add: registered GPIOs 198 to 202 on device: gpb1
[    0.118603] gpiochip_add: registered GPIOs 203 to 206 on device: gpb2
[    0.118615] gpiochip_add: registered GPIOs 207 to 214 on device: gpb3
[    0.118627] gpiochip_add: registered GPIOs 215 to 216 on device: gpb4
[    0.118639] gpiochip_add: registered GPIOs 217 to 224 on device: gph0
[    0.119217] gpiochip_add: registered GPIOs 225 to 231 on device: gpz
[    0.120479] exynos-audss-clk 3810000.audss-clock-controller: setup completed
[    0.126118] EXYNOS5420 PMU initialized
[    0.156206] of_get_named_gpiod_flags: parsed 'gpio' property of node '/regulator-usb300[0]' - status (0)
[    0.156512] of_get_named_gpiod_flags: parsed 'gpio' property of node '/regulator-usb301[0]' - status (0)
[    0.156776] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/fixed-regulator[0]'
[    0.158438] SCSI subsystem initialized
[    0.158872] usbcore: registered new interface driver usbfs
[    0.158975] usbcore: registered new interface driver hub
[    0.159130] usbcore: registered new device driver usb
[    0.159709] s3c-i2c 12c80000.i2c: slave address 0x50
[    0.159725] s3c-i2c 12c80000.i2c: bus frequency set to 65 KHz
[    0.159914] s3c-i2c 12c80000.i2c: i2c-2: S3C I2C adapter
[    0.162839] Advanced Linux Sound Architecture Driver Initialized.
[    0.163593] Switched to clocksource mct-frc
[    0.176435] NET: Registered protocol family 2
[    0.176856] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.176918] TCP bind hash table entries: 8192 (order: 5, 163840 bytes)
[    0.177018] TCP: Hash tables configured (established 8192 bind 8192)
[    0.177062] TCP: reno registered
[    0.177076] UDP hash table entries: 512 (order: 2, 24576 bytes)
[    0.177104] UDP-Lite hash table entries: 512 (order: 2, 24576 bytes)
[    0.177273] NET: Registered protocol family 1
[    0.179435] futex hash table entries: 2048 (order: 5, 131072 bytes)
[    0.192091] romfs: ROMFS MTD (C) 2007 Red Hat, Inc.
[    0.192701] bounce: pool size: 64 pages
[    0.192714] io scheduler noop registered
[    0.192726] io scheduler deadline registered
[    0.193141] io scheduler cfq registered (default)
[    0.193770] exynos-mipi-video-phy 10040714.video-phy: can't request region for resource [mem 0x10040714-0x1004071f]
[    0.193797] exynos-mipi-video-phy: probe of 10040714.video-phy failed with error -16
[    0.196533] pwm-backlight backlight: GPIO lookup for consumer enable
[    0.196547] pwm-backlight backlight: using device tree for GPIO lookup
[    0.196563] of_get_named_gpiod_flags: parsed 'enable-gpios' property of node '/backlight[0]' - status (0)
[    0.196615] platform backlight: Driver pwm-backlight requests probe deferral
[    0.199040] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330
[    0.199056] dma-pl330 3880000.adma: DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6
[    0.203061] dma-pl330 121a0000.pdma: Loaded driver for PL330 DMAC-241330
[    0.203077] dma-pl330 121a0000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.207134] dma-pl330 121b0000.pdma: Loaded driver for PL330 DMAC-241330
[    0.207149] dma-pl330 121b0000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.208279] dma-pl330 10800000.mdma: Loaded driver for PL330 DMAC-241330
[    0.208293] dma-pl330 10800000.mdma: DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[    0.286988] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    0.288461] samsung-uart 12c00000.serial: ttySAC0 at MMIO 0x12c00000 (irq = 83, base_baud = 0) is a S3C6400/10
[    0.288863] samsung-uart 12c10000.serial: ttySAC1 at MMIO 0x12c10000 (irq = 84, base_baud = 0) is a S3C6400/10
[    0.289379] samsung-uart 12c20000.serial: ttySAC2 at MMIO 0x12c20000 (irq = 85, base_baud = 0) is a S3C6400/10
[    0.289742] samsung-uart 12c30000.serial: ttySAC3 at MMIO 0x12c30000 (irq = 86, base_baud = 0) is a S3C6400/10
[    1.290234] console [ttySAC3] enabled
[    1.294923] [drm] Initialized drm 1.1.0 20060810
[    1.299061] platform 145b0000.dp-controller: Driver exynos-dp requests probe deferral
[    1.306789] platform panel: Driver panel-simple requests probe deferral
[    1.313174] error detecting cacheinfo..cpu0
[    1.324075] brd: module loaded
[    1.329303] loop: module loaded
[    1.331533] of_get_named_gpiod_flags: parsed 'cs-gpios' property of node '/spi@12d40000[0]' - status (0)
[    1.341346] cros-ec-spi spi2.0: Chrome EC device registered
[    1.346397] usbcore: registered new interface driver asix
[    1.351422] usbcore: registered new interface driver ax88179_178a
[    1.357544] usbcore: registered new interface driver cdc_ether
[    1.363317] usbcore: registered new interface driver smsc75xx
[    1.369045] usbcore: registered new interface driver smsc95xx
[    1.374756] usbcore: registered new interface driver net1080
[    1.380386] usbcore: registered new interface driver cdc_subset
[    1.386286] usbcore: registered new interface driver zaurus
[    1.391878] usbcore: registered new interface driver cdc_ncm
[    1.398031] usb@12000000 supply vdd33 not found, using dummy regulator
[    1.403982] usb@12000000 supply vdd10 not found, using dummy regulator
[    1.811857] usb@12400000 supply vdd33 not found, using dummy regulator
[    1.816963] usb@12400000 supply vdd10 not found, using dummy regulator
[    2.224710] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    2.228756] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 1
[    2.236621] xhci-hcd xhci-hcd.2.auto: irq 104, io mem 0x12000000
[    2.242490] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.249121] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.256319] usb usb1: Product: xHCI Host Controller
[    2.261175] usb usb1: Manufacturer: Linux 3.18.0-rc5-next-20141120-07674-gb16800da58a3 xhci-hcd
[    2.269853] usb usb1: SerialNumber: xhci-hcd.2.auto
[    2.275268] hub 1-0:1.0: USB hub found
[    2.278441] hub 1-0:1.0: 1 port detected
[    2.282685] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    2.287821] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 2
[    2.295593] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    2.302211] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.309412] usb usb2: Product: xHCI Host Controller
[    2.314266] usb usb2: Manufacturer: Linux 3.18.0-rc5-next-20141120-07674-gb16800da58a3 xhci-hcd
[    2.322944] usb usb2: SerialNumber: xhci-hcd.2.auto
[    2.328340] hub 2-0:1.0: USB hub found
[    2.331548] hub 2-0:1.0: 1 port detected
[    2.335826] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[    2.340919] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 3
[    2.348798] xhci-hcd xhci-hcd.5.auto: irq 105, io mem 0x12400000
[    2.354637] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    2.361287] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.368487] usb usb3: Product: xHCI Host Controller
[    2.373343] usb usb3: Manufacturer: Linux 3.18.0-rc5-next-20141120-07674-gb16800da58a3 xhci-hcd
[    2.382073] usb usb3: SerialNumber: xhci-hcd.5.auto
[    2.387408] hub 3-0:1.0: USB hub found
[    2.390625] hub 3-0:1.0: 1 port detected
[    2.394842] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[    2.399989] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 4
[    2.407752] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[    2.414379] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.421578] usb usb4: Product: xHCI Host Controller
[    2.426433] usb usb4: Manufacturer: Linux 3.18.0-rc5-next-20141120-07674-gb16800da58a3 xhci-hcd
[    2.435208] usb usb4: SerialNumber: xhci-hcd.5.auto
[    2.440516] hub 4-0:1.0: USB hub found
[    2.443716] hub 4-0:1.0: 1 port detected
[    2.447956] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.454113] ehci-exynos: EHCI EXYNOS driver
[    2.458394] of_get_named_gpiod_flags: can't parse 'samsung,vbus-gpio' property of node '/usb@12110000[0]'
[    2.468000] exynos-ehci 12110000.usb: EHCI Host Controller
[    2.473299] exynos-ehci 12110000.usb: new USB bus registered, assigned bus number 5
[    2.481187] exynos-ehci 12110000.usb: irq 103, io mem 0x12110000
[    2.588636] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[    2.603619] exynos-ehci 12110000.usb: USB 2.0 started, EHCI 1.00
[    2.608276] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
[    2.614936] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.622134] usb usb5: Product: EHCI Host Controller
[    2.626990] usb usb5: Manufacturer: Linux 3.18.0-rc5-next-20141120-07674-gb16800da58a3 ehci_hcd
[    2.635668] usb usb5: SerialNumber: 12110000.usb
[    2.640818] hub 5-0:1.0: USB hub found
[    2.644012] hub 5-0:1.0: 3 ports detected
[    2.648547] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    2.654158] ohci-exynos: OHCI EXYNOS driver
[    2.658475] exynos-ohci 12120000.usb: USB Host Controller
[    2.663736] exynos-ohci 12120000.usb: new USB bus registered, assigned bus number 6
[    2.671405] exynos-ohci 12120000.usb: irq 103, io mem 0x12120000
[    2.732742] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[    2.738084] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.745923] usb usb6: Product: USB Host Controller
[    2.750054] usb usb6: Manufacturer: Linux 3.18.0-rc5-next-20141120-07674-gb16800da58a3 ohci_hcd
[    2.758732] usb usb6: SerialNumber: 12120000.usb
[    2.763856] hub 6-0:1.0: USB hub found
[    2.767059] hub 6-0:1.0: 3 ports detected
[    2.771678] usbcore: registered new interface driver usb-storage
[    2.777028] usb 1-1: New USB device found, idVendor=0b95, idProduct=7720
[    2.783700] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.790857] usb 1-1: Product: AX88x72A
[    2.794567] usb 1-1: Manufacturer: ASIX Elec. Corp.
[    2.794605] mousedev: PS/2 mouse device common for all mice
[    2.796075] input: cros-ec-spi as /devices/platform/12d40000.spi/spi_master/spi2/spi2.0/cros-ec-keyb.1/input/input0
[    2.811973] s3c-rtc 101e0000.rtc: rtc core: registered s3c as rtc0
[    2.812999] i2c /dev entries driver
[    2.824990] usb 1-1: SerialNumber: 000001
[    2.829605] max77686 4-0009: Failed to find supply inb1
[    2.834312] max77802-pmic max77802-pmic: regulator init failed for 0
[    2.840650] platform max77802-pmic: Driver max77802-pmic requests probe deferral
[    2.850725] rtc (null): read_time: fail to read
[    2.853968] max77802-rtc max77802-rtc: rtc core: registered max77802-rtc as rtc1
[    2.883960] atmel_mxt_ts 8-004b: Direct firmware load for maxtouch.cfg failed with error -2
[    2.891137] atmel_mxt_ts 8-004b: Invalid object type T9
[    2.896087] atmel_mxt_ts 8-004b: Failed to initialize T9 resolution
[    2.902579] input: Atmel maXTouch Touchpad as /devices/platform/12e00000.i2c/i2c-8/8-004b/input/input1
[    2.911682] tpm_i2c_infineon 9-0020: 1.2 TPM (device-id 0x1A)
[    2.912243] atmel_mxt_ts 8-004b: Family: 130 Variant: 44 Firmware V3.0.AA Objects: 34
[    3.025430] tps65090 20-0048: No cache defaults, reading back from HW
[    3.035231] of_get_named_gpiod_flags: can't parse 'dcdc-ext-control-gpios' property of node '/spi@12d40000/cros-ec@0/i2c-tunnel/power-regulator@48[0]'
[    3.047242] of_get_named_gpiod_flags: can't parse 'dcdc-ext-control-gpios' property of node '/spi@12d40000/cros-ec@0/i2c-tunnel/power-regulator@48[0]'
[    3.060701] of_get_named_gpiod_flags: can't parse 'dcdc-ext-control-gpios' property of node '/spi@12d40000/cros-ec@0/i2c-tunnel/power-regulator@48[0]'
[    3.074284] TPS65090_RAILSDCDC1: supplied by vbat-supply
[    3.081034] TPS65090_RAILSDCDC2: supplied by vbat-supply
[    3.086488] TPS65090_RAILSDCDC3: supplied by vbat-supply
[    3.091938] vcd_led: supplied by vbat-supply
[    3.099456] video_mid: supplied by TPS65090_RAILSDCDC1
[    3.107815] wwan_r: supplied by TPS65090_RAILSDCDC2
[    3.115909] sdcard: supplied by TPS65090_RAILSDCDC2
[    3.120934] camout: supplied by TPS65090_RAILSDCDC2
[    3.125944] lcd_vdd: supplied by TPS65090_RAILSDCDC2
[    3.134130] video_mid_1a: supplied by TPS65090_RAILSDCDC1
[    3.139677] TPS65090_RAILSLDO1: supplied by vbat-supply
[    3.143639] TPS65090_RAILSLDO2: supplied by vbat-supply
[    3.251129] sbs-battery 20-000b: sbs-battery: battery gas gauge device registered
[    3.266644] 10060000.tmu supply vtmu not found, using dummy regulator
[    3.271971] exynos-tmu 10060000.tmu: Exynos: Thermal zone(therm_zone0) registered
[    3.279157] 10064000.tmu supply vtmu not found, using dummy regulator
[    3.285818] exynos-tmu 10064000.tmu: Exynos: Thermal zone(therm_zone0) registered
[    3.293033] 10068000.tmu supply vtmu not found, using dummy regulator
[    3.299860] exynos-tmu 10068000.tmu: Exynos: Thermal zone(therm_zone0) registered
[    3.307074] 1006c000.tmu supply vtmu not found, using dummy regulator
[    3.313640] exynos-tmu 1006c000.tmu: Exynos: Thermal zone(therm_zone0) registered
[    3.320779] 100a0000.tmu supply vtmu not found, using dummy regulator
[    3.327474] exynos-tmu 100a0000.tmu: Exynos: Thermal zone(therm_zone0) registered
[    3.335310] s3c2410-wdt 101d0000.watchdog: watchdog inactive, reset disabled, irq disabled
[    3.343888] device-mapper: ioctl: 4.29.0-ioctl (2014-10-28) initialised: dm-devel@redhat.com
[    3.351289] Driver 'mmcblk' needs updating - please use bus_type methods
[    3.358002] sdhci: Secure Digital Host Controller Interface driver
[    3.364111] sdhci: Copyright(c) Pierre Ossman
[    3.368671] Synopsys Designware Multimedia Card Interface Driver
[    3.375015] dwmmc_exynos 12200000.mmc: IDMAC supports 32-bit address mode.
[    3.381339] dwmmc_exynos 12200000.mmc: Using internal DMA controller.
[    3.387718] dwmmc_exynos 12200000.mmc: Version ID is 250a
[    3.393098] dwmmc_exynos 12200000.mmc: DW MMC controller at irq 107, 64 bit host data width, 64 deep fifo
[    3.402657] dwmmc_exynos 12200000.mmc: No vmmc regulator found
[    3.408443] dwmmc_exynos 12200000.mmc: No vqmmc regulator found
[    3.414354] dwmmc_exynos 12200000.mmc: GPIO lookup for consumer wp
[    3.420498] dwmmc_exynos 12200000.mmc: using device tree for GPIO lookup
[    3.427188] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@12200000[0]'
[    3.435950] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@12200000[0]'
[    3.444624] dwmmc_exynos 12200000.mmc: using lookup tables for GPIO lookup
[    3.451470] dwmmc_exynos 12200000.mmc: lookup for GPIO wp failed
[    3.483680] dwmmc_exynos 12200000.mmc: 1 slots initialized
[    3.488103] dwmmc_exynos 12220000.mmc: IDMAC supports 32-bit address mode.
[    3.494612] dwmmc_exynos 12220000.mmc: Using internal DMA controller.
[    3.500992] dwmmc_exynos 12220000.mmc: Version ID is 250a
[    3.506375] dwmmc_exynos 12220000.mmc: DW MMC controller at irq 109, 64 bit host data width, 64 deep fifo
[    3.515910] dwmmc_exynos 12220000.mmc: No vmmc regulator found
[    3.521703] dwmmc_exynos 12220000.mmc: No vqmmc regulator found
[    3.527609] dwmmc_exynos 12220000.mmc: GPIO lookup for consumer cd
[    3.531539] mmc0: BKOPS_EN bit is not set
[    3.535286] mmc_host mmc0: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0)
[    3.536232] mmc0: new HS200 MMC card at address 0001
[    3.537231] mmcblk0: mmc0:0001 MAG2GC 14.5 GiB 
[    3.537441] mmcblk0boot0: mmc0:0001 MAG2GC partition 1 4.00 MiB
[    3.537655] mmcblk0boot1: mmc0:0001 MAG2GC partition 2 4.00 MiB
[    3.537854] mmcblk0rpmb: mmc0:0001 MAG2GC partition 3 4.00 MiB
[    3.551363] GPT:partition_entry_array_crc32 values don't match: 0xf4d0e732 != 0x86775d22
[    3.551370] GPT:Primary header thinks Alt. header is not at the end of the disk.
[    3.551376] GPT:29999999 != 30535679
[    3.551382] GPT:Alternate GPT header not at the end of the disk.
[    3.551389] GPT:29999999 != 30535679
[    3.551395] GPT: Use GNU Parted to correct GPT errors.
[    3.551422]  mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12
[    3.614094] dwmmc_exynos 12220000.mmc: using device tree for GPIO lookup
[    3.620773] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/mmc@12220000[0]'
[    3.629539] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/mmc@12220000[0]'
[    3.638211] dwmmc_exynos 12220000.mmc: using lookup tables for GPIO lookup
[    3.645065] dwmmc_exynos 12220000.mmc: lookup for GPIO cd failed
[    3.651050] dwmmc_exynos 12220000.mmc: GPIO lookup for consumer wp
[    3.657205] dwmmc_exynos 12220000.mmc: using device tree for GPIO lookup
[    3.658085] asix 1-1:1.0 eth0: register 'asix' at usb-xhci-hcd.2.auto-1, ASIX AX88772 USB 2.0 Ethernet, c8:b3:73:43:e9:b9
[    3.674823] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@12220000[0]'
[    3.683617] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@12220000[0]'
[    3.692257] dwmmc_exynos 12220000.mmc: using lookup tables for GPIO lookup
[    3.699111] dwmmc_exynos 12220000.mmc: lookup for GPIO wp failed
[    3.733664] dwmmc_exynos 12220000.mmc: 1 slots initialized
[    3.739415] usbcore: registered new interface driver usbhid
[    3.743517] usbhid: USB HID core driver
[    3.748081] exynos-adc 12d10000.adc: failed getting regulator, err = -517
[    3.754135] platform 12d10000.adc: Driver exynos-adc requests probe deferral
[    3.762066] TCP: cubic registered
[    3.764438] NET: Registered protocol family 17
[    3.768886] NET: Registered protocol family 15
[    3.773550] Registering SWP/SWPB emulation handler
[    3.778072] big.LITTLE switcher initializing
[    3.782310] CPU0 paired with CPU7
[    3.785595] CPU1 paired with CPU6
[    3.788890] CPU2 paired with CPU5
[    3.792172] CPU3 paired with CPU4
[    3.795494] GIC ID for CPU 0 cluster 0 is 0
[    3.799658] GIC ID for CPU 1 cluster 0 is 1
[    3.803826] GIC ID for CPU 2 cluster 0 is 2
[    3.807972] GIC ID for CPU 3 cluster 0 is 3
[    3.812151] GIC ID for CPU 0 cluster 1 is 4
[    3.827347] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[    3.835688] mmc1: new high speed SDHC card at address e624
[    3.841376] mmcblk1: mmc1:e624 SU08G 7.40 GiB 
[    3.857069] GPT:partition_entry_array_crc32 values don't match: 0x979ea85d != 0x1ccb76fa
[    3.863709] GPT:Primary header thinks Alt. header is not at the end of the disk.
[    3.871073] GPT:5058495 != 15523839
[    3.874839] IRQ160 no longer affine to CPU4
[    3.875257] GPT:Alternate GPT header not at the end of the disk.
[    3.875303] CPU4: shutdown
[    3.884607] GIC ID for CPU 1 cluster 1 is 5
[    3.891535] GPT:5058495 != 15523839
[    3.895003] GPT: Use GNU Parted to correct GPT errors.
[    3.900139]  mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12
[    3.933996] IRQ161 no longer affine to CPU5
[    3.934391] CPU5: shutdown
[    3.940131] GIC ID for CPU 2 cluster 1 is 6
[    3.988990] IRQ162 no longer affine to CPU6
[    3.989370] CPU6: shutdown
[    3.995155] GIC ID for CPU 3 cluster 1 is 7
[    4.028971] IRQ163 no longer affine to CPU7
[    4.029350] CPU7: shutdown
[    4.035302] big.LITTLE switcher initialized
[    4.039809] pwm-backlight backlight: GPIO lookup for consumer enable
[    4.045278] pwm-backlight backlight: using device tree for GPIO lookup
[    4.051796] of_get_named_gpiod_flags: parsed 'enable-gpios' property of node '/backlight[0]' - status (0)
[    4.063753] platform 145b0000.dp-controller: Driver exynos-dp requests probe deferral
[    4.070327] panel-simple panel: GPIO lookup for consumer enable
[    4.076034] panel-simple panel: using device tree for GPIO lookup
[    4.082108] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/panel[0]'
[    4.090597] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/panel[0]'
[    4.099010] panel-simple panel: using lookup tables for GPIO lookup
[    4.105255] panel-simple panel: lookup for GPIO enable failed
[    4.113333] vdd_mif: supplied by TPS65090_RAILSDCDC2
[    4.117352] vdd_arm: supplied by TPS65090_RAILSDCDC1
[    4.122279] vdd_int: supplied by TPS65090_RAILSDCDC2
[    4.127232] vdd_g3d: supplied by TPS65090_RAILSDCDC2
[    4.132154] vdd_1v2: supplied by TPS65090_RAILSDCDC1
[    4.137105] vdd_kfc: supplied by TPS65090_RAILSDCDC2
[    4.142049] vdd_1v35: supplied by TPS65090_RAILSDCDC1
[    4.147072] vdd_emmc: supplied by TPS65090_RAILSDCDC1
[    4.152109] vdd_2v: supplied by TPS65090_RAILSDCDC1
[    4.156963] vdd_1v8: supplied by TPS65090_RAILSDCDC1
[    4.161788] vdd_1v0: supplied by vdd_1v35
[    4.165779] vdd_1v2_2: supplied by vdd_1v35
[    4.169941] vdd_1v8_3: supplied by vdd_2v
[    4.173942] vdd_sd: supplied by TPS65090_RAILSDCDC2
[    4.178770] vdd_1v8_5: supplied by vdd_2v
[    4.182762] vdd_1v8_6: supplied by vdd_2v
[    4.186769] vdd_1v8_7: supplied by vdd_2v
[    4.190761] vdd_ldo8: supplied by vdd_1v2
[    4.194755] vdd_ldo9: supplied by vdd_2v
[    4.198670] vdd_ldo10: supplied by vdd_2v
[    4.202625] vdd_ldo11: supplied by vdd_2v
[    4.206635] vdd_ldo12: supplied by TPS65090_RAILSDCDC2
[    4.211751] vdd_ldo13: supplied by vdd_2v
[    4.215748] vdd_ldo14: supplied by vdd_2v
[    4.219733] vdd_ldo15: supplied by vdd_1v2
[    4.223794] vdd_g3ds: supplied by vdd_1v35
[    4.227880] ldo_18: supplied by vdd_2v
[    4.231613] ldo_19: supplied by vdd_2v
[    4.235361] ldo_20: supplied by vdd_2v
[    4.239079] ldo_21: supplied by TPS65090_RAILSDCDC2
[    4.243946] ldo_23: supplied by TPS65090_RAILSDCDC2
[    4.248783] ldo_24: supplied by TPS65090_RAILSDCDC2
[    4.253664] ldo_25: supplied by TPS65090_RAILSDCDC2
[    4.258499] ldo_26: supplied by TPS65090_RAILSDCDC2
[    4.263366] ldo_27: supplied by vdd_1v35
[    4.267267] ldo_28: supplied by vdd_2v
[    4.271011] ldo_29: supplied by vdd_2v
[    4.274730] vdd_mifs: supplied by vdd_1v35
[    4.278805] ldo_32: supplied by TPS65090_RAILSDCDC2
[    4.283678] ldo_33: supplied by TPS65090_RAILSDCDC2
[    4.288508] ldo_34: supplied by TPS65090_RAILSDCDC2
[    4.293386] ldo_35: supplied by vdd_1v35
[    4.299000] exynos-drm exynos-drm: bound 14400000.fimd (ops fimd_component_ops)
[    4.304899] of_get_named_gpiod_flags: parsed 'samsung,hpd-gpio' property of node '/dp-controller@145B0000[0]' - status (0)
[    4.316443] exynos-drm exynos-drm: bound 145b0000.dp-controller (ops exynos_dp_ops)
[    4.323493] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    4.330082] [drm] No driver support for vblank timestamp query.
[    4.454614] exynos-dp 145b0000.dp-controller: EDID data does not include any extensions.
[    4.459609] exynos-dp 145b0000.dp-controller: EDID Read success!
[    4.461703] exynos-dp 145b0000.dp-controller: Link Training Clock Recovery success
[    4.463329] exynos-dp 145b0000.dp-controller: Link Training success!
[    4.547638] exynos-dp 145b0000.dp-controller: EDID data does not include any extensions.
[    4.552681] exynos-dp 145b0000.dp-controller: EDID Read success!
[    4.554768] exynos-dp 145b0000.dp-controller: Link Training Clock Recovery success
[    4.556392] exynos-dp 145b0000.dp-controller: Link Training success!
[    4.605445] Console: switching to colour frame buffer device 274x77
[    4.676011] exynos-drm exynos-drm: fb0:  frame buffer device
[    4.681645] exynos-drm exynos-drm: registered panic notifier
[    4.698616] [drm] Initialized exynos 1.0.0 20110530 on minor 0
[    4.703221] of_get_named_gpiod_flags: parsed 'gpios' property of node '/gpio-keys/power[0]' - status (0)
[    4.712549] gpio-18 (Power): gpiod_set_debounce: missing set() or set_debounce() operations
[    4.712701] power-domain: Power-off latency exceeded, new value 188750 ns
[    4.712944] power-domain: Power-off latency exceeded, new value 220333 ns
[    4.712968] power-domain: Power-off latency exceeded, new value 192042 ns
[    4.713303] power-domain: Power-off latency exceeded, new value 313000 ns
[    4.748143] input: gpio-keys as /devices/platform/gpio-keys/input/input2
[    4.754881] s3c-rtc 101e0000.rtc: setting system clock to 2014-11-19 16:02:50 UTC (1416412970)
[    4.785110] TPS65090_RAILSLDO2: disabling
[    4.787671] TPS65090_RAILSLDO1: disabling
[    4.793747] TPS65090_RAILSDCDC3: disabling
~$off
# PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'>
# PYBOOT: Time: 112.26 seconds.
# PYBOOT: Result: FAIL

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Javier Martinez Canillas]

Hello Paolo,

On 11/20/2014 04:57 PM, Paolo Pisati wrote:
> On Thu, Nov 20, 2014 at 03:22:23PM +0530, Vivek Gautam wrote:
>>
>> On linux-samsung tree the only patch that's missing apart from dptx-phy patches
>> is the syscon patch from Pankaj Dubey:
>> b784b98 mfd: syscon: Decouple syscon interface from platform devices
>> 
>> So with below git hash, linux-samsung/for-next display works fine along with
>> other devices that request PMU system controller :
>> 
>> 7bd219e drm/exynos: dp: Remove support for unused dptx-phy
>> e8f21fd arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
>> 7099bde Revert "Revert "ARM: exynos_defconfig: Enable options for
>> display panel support""
>> 713a994 mfd: syscon: Decouple syscon interface from platform devices
>> 7552917 Revert "ARM: exynos_defconfig: Enable options for display
>> panel support"             /* This is Kukjin's for-next today */
>> ff0391a Merge branch 'v3.19-samsung-defconfig' into for-next
>> 26c6283 Merge branch 'v3.18-samsung-fixes' into for-next
>> cf864fd Merge branch 'v3.18-samsung-defconfig' into for-next
>> 98b6380 ARM: exynos_defconfig: Enable max77802 rtc and clock drivers
>> 839275c ARM: exynos_defconfig: Use 16 minors per MMC block device
>> 0526f27 ARM: dts: Explicitly set dr_mode on exynos5250-snow
>> fc14f9c Linux 3.18-rc5
> 
> are you using a clean exynos_defconfig?
> don't you need Javier's "drm/exynos: Move platform drivers registration to
> module init" patch too?
> 

Since Kukjin's for-next is based on Linux 3.18-rc5, the OF patch that causes
the Exynos DRM deadlock is not there. That commit landed in next20141105.

> kgene/for-next at:
> 
> 7552917 Revert "ARM: exynos_defconfig: Enable options for display panel support"
> 
> plus:
> 
> 5e1e068 arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
> 36d908e drm/exynos: dp: Remove support for unused dptx-phy
> 624bff2 POSTED: mfd: syscon: Decouple syscon interface from syscon devices
> 68944e3 Revert "Revert "ARM: exynos_defconfig: Enable options for display panel support""
> 
> hangs with a black screen (albeit backlight seems to be on) on boot.
> I'm betting on Javier's patch at this point (i even tried disabling SND_SOC_SNOW
> but that didn't help).
> 

I only tested with next20141120 but Vivek tested with Kukjin for-next AFAIU.

What's your kernel command line and u-boot env vars?

Best regards,
Javier

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Inki Dae]

2014-11-21 0:26 GMT+09:00 Javier Martinez Canillas
<javier.martinez@collabora.co.uk>:
> Hello Inki,
>
> On 11/20/2014 04:06 PM, Inki Dae wrote:
>>> BTW, it would be great if exynos-drm-next is pulled in linux-next. That is
>>> what most people use to test integration issues so you can catch earlier any
>>> regression that may arise.
>>>
>>> You have to email Stephen Rothwell <sfr@canb.auug.org.au> and point to your
>>> tree and branch and he will be able to add it to linux-next.
>>
>> Thanks for information. Actually, I received a similar email privately
>> before. However, exynos-drm-next should go to drm-next first and than to
>> mainline by Dave who is DRM subsystem maintainer. I think all vendor
>> specific drm drivers would need to be checked by drm subsystem
>> maintainer because these changes might be affect drm subsystem or other
>> vendor specific drm drivers before go to mainline.
>>
>
> This is orthogonal to the normal upstreaming path. linux-next is an integration
> tree that is created daily. So all the remote branches are merged and a git tag
> published. The branch does not get rebased and history is not preserved between
> two published linux-next tags.
>
> This is just to test the integration of different subsystems to be sure that a
> commit in one tree does not cause a regression in another one so issues can be
> spot earlier. For example in the case of $subject, a change in the OF caused a
> regression in the Exynos DRM driver.
>
>> If needed, I will make a new branch, which is based on top of linux-next
>> so other people can check their systems.
>>
>
> You don't really need another branch, git will take care of merge everything
> in linux-next :)

Ah, sorry. There was my misunderstanding. drm-next already is merged
to linux-next so I think we can do the integration test if
exynos-drm-next is merged to drm-next earlier. Anyway, I will try to
consider your opinion.

Thanks,
Inki Dae

>
>> Thanks,
>> Inki Dae
>>
>
> Best regards,
> Javier
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Javier Martinez Canillas]

Hello,

For completeness I'll comment what we talked with Kevin on IRC
since probably this is the same issue that Paolo is facing.

On 11/20/2014 05:41 PM, Kevin Hilman wrote:
> Peach # setenv preboot "usb start; sleep 1"setenv bootargs console=tty1 console=ttySAC3,115200 debug earlyprintk rw root=/dev/mmcblk1p3 rootwait rootfstype=ext3

My kernel command line is almost the same with the difference that I'm using
clk_ignore_unused and I just checked that not passing that parameter, makes
linux-next to hang showing the same output log that Kevin reported.

Now, the question is why this does not happen with 3.18-rc+? My guess is that
the clock been disabled by the common clock framework got added recently and
it used to be unmanaged and left with the state set by the bootloader since
the kernel didn't know about it. That's why clk_ignore_unused was not needed.

Any ideas?

Best regards,
Javier

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Kevin Hilman]

Javier Martinez Canillas <javier.martinez@collabora.co.uk> writes:

> Hello,
>
> For completeness I'll comment what we talked with Kevin on IRC
> since probably this is the same issue that Paolo is facing.
>
> On 11/20/2014 05:41 PM, Kevin Hilman wrote:
>> Peach # setenv preboot "usb start; sleep 1"setenv bootargs
>> console=tty1 console=ttySAC3,115200 debug earlyprintk rw
>> root=/dev/mmcblk1p3 rootwait rootfstype=ext3
>
> My kernel command line is almost the same with the difference that I'm using
> clk_ignore_unused and I just checked that not passing that parameter, makes
> linux-next to hang showing the same output log that Kevin reported.

Ah!  Good find.  I confirm that adding clk_ignore_unused is getting me
booting again, but of course that is just masking a problem, so I hope
someone can shed light on which clock isn't being correctly managed.

Might I also suggest that folks have their default command-line to *not*
use clk_ignore_unused, since it's primary job is to workaround clock
bugs.

Kevin

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Paolo Pisati]

On Thu, Nov 20, 2014 at 10:22:54AM -0800, Kevin Hilman wrote:
> Javier Martinez Canillas <javier.martinez@collabora.co.uk> writes:
> 
> > Hello,
> >
> > For completeness I'll comment what we talked with Kevin on IRC
> > since probably this is the same issue that Paolo is facing.
> >
> > On 11/20/2014 05:41 PM, Kevin Hilman wrote:
> >> Peach # setenv preboot "usb start; sleep 1"setenv bootargs
> >> console=tty1 console=ttySAC3,115200 debug earlyprintk rw
> >> root=/dev/mmcblk1p3 rootwait rootfstype=ext3
> >
> > My kernel command line is almost the same with the difference that I'm using
> > clk_ignore_unused and I just checked that not passing that parameter, makes
> > linux-next to hang showing the same output log that Kevin reported.
> 
> Ah!  Good find.  I confirm that adding clk_ignore_unused is getting me
> booting again, but of course that is just masking a problem, so I hope
> someone can shed light on which clock isn't being correctly managed.
> 
> Might I also suggest that folks have their default command-line to *not*
> use clk_ignore_unused, since it's primary job is to workaround clock
> bugs.

i'm testing kgene/for-next (not linux-next), with:

flag@peachpi:~/linux$ cat /proc/cmdline
console=tty1 console=ttySAC3,115200 debug earlyprintk rw rootwait
root=/dev/mmcblk1p3

adding clk_ignore_unused didn't make any difference: it hangs on boot
showing a black screen with backlight on.

vanilla kgene/for-next as of today:

7552917 Revert "ARM: exynos_defconfig: Enable options for display panel support"
ff0391a Merge branch 'v3.19-samsung-defconfig' into for-next
26c6283 Merge branch 'v3.18-samsung-fixes' into for-next
cf864fd Merge branch 'v3.18-samsung-defconfig' into for-next
98b6380 ARM: exynos_defconfig: Enable max77802 rtc and clock drivers
839275c ARM: exynos_defconfig: Use 16 minors per MMC block device
0526f27 ARM: dts: Explicitly set dr_mode on exynos5250-snow
fc14f9c Linux 3.18-rc5
...

plus

5e1e068 arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
36d908e drm/exynos: dp: Remove support for unused dptx-phy
624bff2 POSTED: mfd: syscon: Decouple syscon interface from syscon devices
68944e3 Revert "Revert "ARM: exynos_defconfig: Enable options for display panel
support""

vanilla exynos_defconfig with SND_SOC_SNOW disabled.

I should probably try linux-next at this point, but i wonder if people who
reported kgene/for-next working were testing with a vanilla exynos_defconfig on
a peach pi.
-- 
bye,
p.

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Javier Martinez Canillas]

Hello Inki,

On 11/20/2014 06:01 PM, Inki Dae wrote:
> Ah, sorry. There was my misunderstanding. drm-next already is merged
> to linux-next so I think we can do the integration test if
> exynos-drm-next is merged to drm-next earlier. Anyway, I will try to
> consider your opinion.
> 

Cool, having exynos-drm-next in linux-next will be very useful indeed.

BTW, I didn't have time to forward port $subject yesterday but Gustavo
did and posted a series [0] that supersedes $subjects and also solves
other issues. It would be great if you can take a loot to those patches.

Best regards,
Javier

[0]: http://www.spinics.net/lists/linux-samsung-soc/msg39306.html

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Andreas Färber]

Am 21.11.2014 um 00:49 schrieb Paolo Pisati:
> vanilla kgene/for-next as of today:
> 
> 7552917 Revert "ARM: exynos_defconfig: Enable options for display panel support"
> ff0391a Merge branch 'v3.19-samsung-defconfig' into for-next
> 26c6283 Merge branch 'v3.18-samsung-fixes' into for-next
> cf864fd Merge branch 'v3.18-samsung-defconfig' into for-next
> 98b6380 ARM: exynos_defconfig: Enable max77802 rtc and clock drivers
> 839275c ARM: exynos_defconfig: Use 16 minors per MMC block device
> 0526f27 ARM: dts: Explicitly set dr_mode on exynos5250-snow
> fc14f9c Linux 3.18-rc5
> ...
> 
> plus
> 
> 5e1e068 arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
> 36d908e drm/exynos: dp: Remove support for unused dptx-phy
> 624bff2 POSTED: mfd: syscon: Decouple syscon interface from syscon devices
> 68944e3 Revert "Revert "ARM: exynos_defconfig: Enable options for display panel
> support""
> 
> vanilla exynos_defconfig with SND_SOC_SNOW disabled.
> 
> I should probably try linux-next at this point, but i wonder if people who
> reported kgene/for-next working were testing with a vanilla exynos_defconfig on
> a peach pi.

On Spring, I am able to boot my kgene/for-next based queue with just:

mfd: syscon: Decouple syscon interface from platform devices
arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy

with DRM_EXYNOS*=y (except IOMMU) and SND_SOC_SNOW=m enabled in the
config, while using simplefb rather than the Exynos DRM and thus
clk_ignore_unused.

Regarding SND_SOC_SNOW: Note that I recently submitted a patch to enable
module-loading, which is missing in kgene/for-next and -rc5 but is in
linux-next.git - it might uncover problems that previously went
unnoticed: https://patchwork.kernel.org/patch/5235951/
exynos_defconfig has SND_SOC_SNOW=y, whereas multi_v7_defconfig doesn't
have it.

Regards,
Andreas

-- 
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg

Peach Pi/Pit boot failures in linux-next (was Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init)

[Javier Martinez Canillas]

[adding Kukjin as cc and dropping dri-devel]

Hello Kevin,

On 11/20/2014 07:22 PM, Kevin Hilman wrote:
>> My kernel command line is almost the same with the difference that
>> I'm using clk_ignore_unused and I just checked that not passing
>> that parameter, makes linux-next to hang showing the same output
>> log that Kevin reported.
> 
> Ah!  Good find.  I confirm that adding clk_ignore_unused is getting
> me booting again, but of course that is just masking a problem, so I
> hope someone can shed light on which clock isn't being correctly
> managed.
> 

True, I'm renaming the thread subject to track these issues separately
of the original Exynos DRM bug since these are unrelated.

So, I see two different boot failures on the Peach Pi[t] Chromebooks:

1) next20141121 boot fails due snd-soc-snow

Disabling CONFIG_SND_SOC_SNOW makes the boot to got a little further
but still fails with the second issue:

2) next20141121 boot hangs if unused clocks are disabled.

I tried to root cause these two issues but didn't see anything evident
so I'll find a last known good commit and bisect. If anyone has an
idea of the possible causes for these issues that would be appreciated.
 
> Might I also suggest that folks have their default command-line to
> *not* use clk_ignore_unused, since it's primary job is to workaround
> clock bugs.
> 

Agreed, I disabled now as well to catch regressions early. I carried
those parameters from Snow since I needed clk_ignore_unused to have
simplefb working on that machine.

> Kevin
> 

Best regards,
Javier

Re: Peach Pi/Pit boot failures in linux-next (was Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init)

[Kevin Hilman]

Javier Martinez Canillas <javier.martinez@collabora.co.uk> writes:

> [adding Kukjin as cc and dropping dri-devel]
>
> Hello Kevin,
>
> On 11/20/2014 07:22 PM, Kevin Hilman wrote:
>>> My kernel command line is almost the same with the difference that
>>> I'm using clk_ignore_unused and I just checked that not passing
>>> that parameter, makes linux-next to hang showing the same output
>>> log that Kevin reported.
>> 
>> Ah!  Good find.  I confirm that adding clk_ignore_unused is getting
>> me booting again, but of course that is just masking a problem, so I
>> hope someone can shed light on which clock isn't being correctly
>> managed.
>> 
>
> True, I'm renaming the thread subject to track these issues separately
> of the original Exynos DRM bug since these are unrelated.
>
> So, I see two different boot failures on the Peach Pi[t] Chromebooks:
>
> 1) next20141121 boot fails due snd-soc-snow
>
> Disabling CONFIG_SND_SOC_SNOW makes the boot to got a little further
> but still fails with the second issue:
>
> 2) next20141121 boot hangs if unused clocks are disabled.
>
> I tried to root cause these two issues but didn't see anything evident
> so I'll find a last known good commit and bisect. If anyone has an
> idea of the possible causes for these issues that would be appreciated.

FWIW, in addition to the failures on 5800/peach-pi, I'm also seeing boot
failures in next-20141121 on the exynos5420-arndale-octa[1].  Adding
clk_ignore_unused gets things booting there as well.

What's interesting is that my exynos5422-odroid-xu3 is booting fine as
well as the exynos5420-arndale and the exynos5410-odroid-xu (shown as
exynos5410-smdk5410)

Whatever the issue, it definietly seems like a problem that was came
through a driver/subsystem tree because that these boards are all
booting fine with Kukjin's for-next, arm-soc/for-next and
mainline/v3.18-rc5 (all with just plain exynos_defconfig, and without
clk_ignore_unused.)  For example, just looking at peach-pi across all
these trees[2], you can see that it's only failing in linux-next.

Kevin

[1] http://status.armcloud.us/boot/?next-2014112?&exynos
[2] http://status.armcloud.us/boot/?exynos5800-peach-pi

NOTE: the exynos5422-odroid-xu3 is shown as exynos5420-smdk5420 since
      that's the DTS being used, and exynos5410-odroid-xu is shown as
      exynos5410-smdk5410, again due to the DTS being used.

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Ajay kumar]

[-- Attachment #1: Type: text/plain, Size: 3953 bytes --]

Hi,

I have rebased my bridge series on top of linux-next.

This is my git log:
4b38a6f Revert "Revert "ARM: exynos_defconfig: Enable options for
display panel support""
6fb39a7 ARM: dts: peach-pit: represent the connection between bridge
and panel using videoport and endpoints
aee649c ARM: dts: snow: represent the connection between bridge and
panel using videoport and endpoints
5b76d8d drm/bridge: Add i2c based driver for ps8622/ps8625 bridge
581257f Documentation: bridge: Add documentation for ps8622 DT properties
178e8b9 Documentation: devicetree: Add vendor prefix for parade
0ceea75 Documentation: drm: bridge: move to video/bridge
f143e2e drm/bridge: ptn3460: use gpiod interface
2d5cb9d drm/bridge: ptn3460: probe connector at the end of bridge attach
32ac563 drm/bridge: ptn3460: support drm_panel
91c6c30 drm/exynos: dp: support drm_bridge
7eea7eb drm/bridge: ptn3460: Convert to i2c driver model
602f343 drm/bridge: make bridge registration independent of drm flow
14c7143 drm/bridge: do not pass drm_bridge_funcs to drm_bridge_init
2c01ac4 drm/bridge: ptn3460: Few trivial cleanups
7415f6c arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
28655d1 drm/exynos: Move platform drivers registration to module init
ed6778a Add linux-next specific files for 20141121

I have attached the rebased patches as well.
I tested it on snow, peach_pit and peach_pi without *clk_ignore_unused*.
Display is totally fine with exynos_defconfig (booting is fine even
with CONFIG_SND_SOC_SNOW=y)

Regards,
Ajay Kumar


On Fri, Nov 21, 2014 at 5:03 PM, Andreas Färber <afaerber@suse.de> wrote:
> Am 21.11.2014 um 00:49 schrieb Paolo Pisati:
>> vanilla kgene/for-next as of today:
>>
>> 7552917 Revert "ARM: exynos_defconfig: Enable options for display panel support"
>> ff0391a Merge branch 'v3.19-samsung-defconfig' into for-next
>> 26c6283 Merge branch 'v3.18-samsung-fixes' into for-next
>> cf864fd Merge branch 'v3.18-samsung-defconfig' into for-next
>> 98b6380 ARM: exynos_defconfig: Enable max77802 rtc and clock drivers
>> 839275c ARM: exynos_defconfig: Use 16 minors per MMC block device
>> 0526f27 ARM: dts: Explicitly set dr_mode on exynos5250-snow
>> fc14f9c Linux 3.18-rc5
>> ...
>>
>> plus
>>
>> 5e1e068 arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
>> 36d908e drm/exynos: dp: Remove support for unused dptx-phy
>> 624bff2 POSTED: mfd: syscon: Decouple syscon interface from syscon devices
>> 68944e3 Revert "Revert "ARM: exynos_defconfig: Enable options for display panel
>> support""
>>
>> vanilla exynos_defconfig with SND_SOC_SNOW disabled.
>>
>> I should probably try linux-next at this point, but i wonder if people who
>> reported kgene/for-next working were testing with a vanilla exynos_defconfig on
>> a peach pi.
>
> On Spring, I am able to boot my kgene/for-next based queue with just:
>
> mfd: syscon: Decouple syscon interface from platform devices
> arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
>
> with DRM_EXYNOS*=y (except IOMMU) and SND_SOC_SNOW=m enabled in the
> config, while using simplefb rather than the Exynos DRM and thus
> clk_ignore_unused.
>
> Regarding SND_SOC_SNOW: Note that I recently submitted a patch to enable
> module-loading, which is missing in kgene/for-next and -rc5 but is in
> linux-next.git - it might uncover problems that previously went
> unnoticed: https://patchwork.kernel.org/patch/5235951/
> exynos_defconfig has SND_SOC_SNOW=y, whereas multi_v7_defconfig doesn't
> have it.
>
> Regards,
> Andreas
>
> --
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: Tot.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 20037 bytes --]

[-- Attachment #3: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: Peach Pi/Pit boot failures in linux-next (was Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init)

[Javier Martinez Canillas]

Hello Kevin,

On 11/21/2014 05:38 PM, Kevin Hilman wrote:
>> So, I see two different boot failures on the Peach Pi[t] Chromebooks:
>>
>> 1) next20141121 boot fails due snd-soc-snow
>>
>> Disabling CONFIG_SND_SOC_SNOW makes the boot to got a little further
>> but still fails with the second issue:
>>
>> 2) next20141121 boot hangs if unused clocks are disabled.
>>
>> I tried to root cause these two issues but didn't see anything evident
>> so I'll find a last known good commit and bisect. If anyone has an
>> idea of the possible causes for these issues that would be appreciated.
> 
> FWIW, in addition to the failures on 5800/peach-pi, I'm also seeing boot
> failures in next-20141121 on the exynos5420-arndale-octa[1].  Adding
> clk_ignore_unused gets things booting there as well.
> 
> What's interesting is that my exynos5422-odroid-xu3 is booting fine as
> well as the exynos5420-arndale and the exynos5410-odroid-xu (shown as
> exynos5410-smdk5410)
> 
> Whatever the issue, it definietly seems like a problem that was came
> through a driver/subsystem tree because that these boards are all
> booting fine with Kukjin's for-next, arm-soc/for-next and
> mainline/v3.18-rc5 (all with just plain exynos_defconfig, and without
> clk_ignore_unused.)  For example, just looking at peach-pi across all
> these trees[2], you can see that it's only failing in linux-next.
>

By bisecting I found that the commit introducing both regressions is:

ae43b32 ("ARM: 8202/1: dmaengine: pl330: Add runtime Power Management support v12")

By reverting ae43b32, next-20141121 boots with both CONFIG_SND_SOC_SNOW=y
and *without* clk_ignore_unused.

Krzysztof,

I see you are the author of the patch, maybe you can take a look why this
is causing regressions in some Exynos boards?

Thanks a lot and best regards,
Javier

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Javier Martinez Canillas]

Hello Ajay,

On 11/21/2014 06:32 PM, Ajay kumar wrote:
> Hi,
> 
> I have rebased my bridge series on top of linux-next.
> 
> This is my git log:
> 4b38a6f Revert "Revert "ARM: exynos_defconfig: Enable options for
> display panel support""
> 6fb39a7 ARM: dts: peach-pit: represent the connection between bridge
> and panel using videoport and endpoints
> aee649c ARM: dts: snow: represent the connection between bridge and
> panel using videoport and endpoints
> 5b76d8d drm/bridge: Add i2c based driver for ps8622/ps8625 bridge
> 581257f Documentation: bridge: Add documentation for ps8622 DT properties
> 178e8b9 Documentation: devicetree: Add vendor prefix for parade
> 0ceea75 Documentation: drm: bridge: move to video/bridge
> f143e2e drm/bridge: ptn3460: use gpiod interface
> 2d5cb9d drm/bridge: ptn3460: probe connector at the end of bridge attach
> 32ac563 drm/bridge: ptn3460: support drm_panel
> 91c6c30 drm/exynos: dp: support drm_bridge
> 7eea7eb drm/bridge: ptn3460: Convert to i2c driver model
> 602f343 drm/bridge: make bridge registration independent of drm flow
> 14c7143 drm/bridge: do not pass drm_bridge_funcs to drm_bridge_init
> 2c01ac4 drm/bridge: ptn3460: Few trivial cleanups
> 7415f6c arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
> 28655d1 drm/exynos: Move platform drivers registration to module init
> ed6778a Add linux-next specific files for 20141121
> 
> I have attached the rebased patches as well.
> I tested it on snow, peach_pit and peach_pi without *clk_ignore_unused*.
> Display is totally fine with exynos_defconfig (booting is fine even
> with CONFIG_SND_SOC_SNOW=y)
> 

Thanks for forward porting your patches to linux-next. Unfortunately I
won't have time to test them until Monday but I wonder why you didn't
have the boot issues that we have with next-20141121.

I found that the commit ae43b32 ("ARM: 8202/1: dmaengine: pl330: Add
runtime Power Management support v12") had to be reverted in order to
boot linux-next.

Best regards,
Javier

Re: Peach Pi/Pit boot failures in linux-next (was Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init)

[Krzysztof Kozlowski]

W dniu 21.11.2014 o 21:49, Javier Martinez Canillas pisze:
> Hello Kevin,
>
> On 11/21/2014 05:38 PM, Kevin Hilman wrote:
>>> So, I see two different boot failures on the Peach Pi[t] Chromebooks:
>>>
>>> 1) next20141121 boot fails due snd-soc-snow
>>>
>>> Disabling CONFIG_SND_SOC_SNOW makes the boot to got a little further
>>> but still fails with the second issue:
>>>
>>> 2) next20141121 boot hangs if unused clocks are disabled.
>>>
>>> I tried to root cause these two issues but didn't see anything evident
>>> so I'll find a last known good commit and bisect. If anyone has an
>>> idea of the possible causes for these issues that would be appreciated.
>>
>> FWIW, in addition to the failures on 5800/peach-pi, I'm also seeing boot
>> failures in next-20141121 on the exynos5420-arndale-octa[1].  Adding
>> clk_ignore_unused gets things booting there as well.
>>
>> What's interesting is that my exynos5422-odroid-xu3 is booting fine as
>> well as the exynos5420-arndale and the exynos5410-odroid-xu (shown as
>> exynos5410-smdk5410)
>>
>> Whatever the issue, it definietly seems like a problem that was came
>> through a driver/subsystem tree because that these boards are all
>> booting fine with Kukjin's for-next, arm-soc/for-next and
>> mainline/v3.18-rc5 (all with just plain exynos_defconfig, and without
>> clk_ignore_unused.)  For example, just looking at peach-pi across all
>> these trees[2], you can see that it's only failing in linux-next.
>>
>
> By bisecting I found that the commit introducing both regressions is:
>
> ae43b32 ("ARM: 8202/1: dmaengine: pl330: Add runtime Power Management support v12")
>
> By reverting ae43b32, next-20141121 boots with both CONFIG_SND_SOC_SNOW=y
> and *without* clk_ignore_unused.
>
> Krzysztof,
>
> I see you are the author of the patch, maybe you can take a look why this
> is causing regressions in some Exynos boards?

Oh crap... I'll look at it on Monday. However I don't have Peach Pi so any 
information would be useful. Can you post dmesg and your config? (is it 
exynos_defconfig?)

Additionally can you boot the board with DMATEST enabled (without reverting 
my commit so probably with clk_ignore_unsed and with SND_SNOW disabled) and 
run dmatest on all channels? Something like:
   echo 2000 > /sys/module/dmatest/parameters/timeout
   echo 2 > /sys/module/dmatest/parameters/iterations
   for i in `ls /sys/class/dma/`
   do
     echo $i > /sys/module/dmatest/parameters/channel
     echo 1 > /sys/module/dmatest/parameters/run
   done

... and post these results also.

I will test it on Arndale Octa, maybe the cause is the same. Unfortunately 
it seems Arndale Octa does not have any sound enabled in DTS so it may be 
hard to test I2S bus (which is used by audio).

Best regards,
Krzysztof

Re: Peach Pi/Pit boot failures in linux-next (was Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init)

[Javier Martinez Canillas]

[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]

Hell Krzysztof,

On 11/22/2014 11:21 AM, Krzysztof Kozlowski wrote:
>>
>> By bisecting I found that the commit introducing both regressions is:
>>
>> ae43b32 ("ARM: 8202/1: dmaengine: pl330: Add runtime Power Management support v12")
>>
>> By reverting ae43b32, next-20141121 boots with both CONFIG_SND_SOC_SNOW=y
>> and *without* clk_ignore_unused.
>>
>> Krzysztof,
>>
>> I see you are the author of the patch, maybe you can take a look why this
>> is causing regressions in some Exynos boards?
> 
> Oh crap... I'll look at it on Monday. However I don't have Peach Pi so any 
> information would be useful. Can you post dmesg and your config? (is it 
> exynos_defconfig?)
>

Yes, I'm using exynos_defconfig. I'm testing with latest linux-next, HEAD:

commit ed6778a ("Add linux-next specific files for 20141121")

The boot log of the hang in the Exynos5420 Peach Pit is sent as an
attachment. CONFIG_SND_SOC_SNOW was enabled and without clk_ignore_unused.

> Additionally can you boot the board with DMATEST enabled (without reverting 
> my commit so probably with clk_ignore_unsed and with SND_SNOW disabled) and 
> run dmatest on all channels? Something like:
>    echo 2000 > /sys/module/dmatest/parameters/timeout
>    echo 2 > /sys/module/dmatest/parameters/iterations
>    for i in `ls /sys/class/dma/`
>    do
>      echo $i > /sys/module/dmatest/parameters/channel
>      echo 1 > /sys/module/dmatest/parameters/run
>    done
> 
> ... and post these results also.
>

I'm attaching the log of the tests as well. To run the test
CONFIG_SND_SOC_SNOW was disabled and booted with clk_ignore_unused.
 
> I will test it on Arndale Octa, maybe the cause is the same. Unfortunately 
> it seems Arndale Octa does not have any sound enabled in DTS so it may be 
> hard to test I2S bus (which is used by audio).
>

Ok, please let me know if you need anything else from me.
 
> Best regards,
> Krzysztof

Best regards,
Javier

[-- Attachment #2: bootlog.txt --]
[-- Type: text/plain, Size: 30401 bytes --]

U-Boot 2013.04-gb98ed09 (Mar 07 2014 - 12:25:37) for Peach

CPU:    Exynos5420@1800MHz

Board: Google Peach Pit, rev 9.0
I2C:   ready
DRAM:  2 GiB
PMIC max77802-pmic initialized
CPU:    Exynos5420@1800MHz
TPS65090 PMIC EC init
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
SF: Detected W25Q32DW with page size 4 KiB, total 32 MiB
In:    cros-ec-keyb
Out:   lcd
Err:   lcd
SF: Detected W25Q32DW with page size 4 KiB, total 32 MiB
ELOG: Event(17) added with size 13
Net:   No ethernet found.
Hit any key to stop autoboot:  0
reading uImage
3336553 bytes read in 163 ms (19.5 MiB/s)
## Booting kernel from Legacy Image at 42000000 ...
   Image Name:   Linux
   Created:      2014-11-24   8:30:31 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3336489 Bytes = 3.2 MiB
   Load Address: 40008000
   Entry Point:  40008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Timer summary in microseconds:
       Mark    Elapsed  Stage
          0          0  reset
  3,471,164  3,471,164  board_init_f
  3,567,283     96,119  board_init_r
  3,712,040    144,757  id=64
  3,714,761      2,721  main_loop
  4,063,547    348,786  bootm_start
  4,063,549          2  id=1
  4,069,252      5,703  id=2
  4,069,254          2  id=3
  4,123,769     54,515  id=4
  4,123,770          1  id=5
  4,123,772          2  id=6
  4,123,773          1  id=14
  4,225,455    101,682  id=7
  4,225,465         10  id=15
  4,229,519      4,054  start_kernel

Accumulated time:
                 6,956  SPI read
cleanup_before_linux_select: Console recording failed (1)
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.18.0-rc5-next-20141121 (javier@minerva) (gcc vers                                                                                                                                                ion 4.6.3 (Debian 4.6.3-14) ) #87 SMP PREEMPT Mon Nov 24 09:09:36 CET 2014
[    0.000000] CPU: ARMv7 Processor [412fc0f3] revision 3 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] Machine model: Google Peach Pit Rev 6+
[    0.000000] Ignoring memory range 0x20000000 - 0x40000000
[    0.000000] cma: Reserved 64 MiB at 0x9c000000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 393216
[    0.000000] free_area_init_node: node 0, pgdat c067a000, node_mem_map eebf600                                                                                                                                                0
[    0.000000]   Normal zone: 1520 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 194560 pages, LIFO batch:31
[    0.000000]   HighMem zone: 1552 pages used for memmap
[    0.000000]   HighMem zone: 198656 pages, LIFO batch:31
[    0.000000] PERCPU: Embedded 9 pages/cpu @eeb7e000 s7616 r8192 d21056 u36864
[    0.000000] pcpu-alloc: s7616 r8192 d21056 u36864 alloc=9*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pag                                                                                                                                                es: 391696
[    0.000000] Kernel command line: console=ttySAC3,115200N8 debug earlyprintk r                                                                                                                                                oot=/dev/mmcblk1p2 rootwait rw no_console_suspend
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1486972K/1572864K available (4400K kernel code, 218K rwda                                                                                                                                                ta, 1504K rodata, 300K init, 284K bss, 20356K reserved, 65536K cma-reserved, 729                                                                                                                                                088K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc05cc5b8   (5906 kB)
[    0.000000]       .init : 0xc05cd000 - 0xc0618000   ( 300 kB)
[    0.000000]       .data : 0xc0618000 - 0xc064e940   ( 219 kB)
[    0.000000]        .bss : 0xc064e940 - 0xc0695a44   ( 285 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] GIC physical location is 0x10481000
[    0.000000] L2C: failed to init: -19
[    0.000000] Switching to timer-based delay loop, resolution 41ns
[    0.000003] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 17895                                                                                                                                                6969942ns
[    0.000215] Console: colour dummy device 80x30
[    0.000231] Calibrating delay loop (skipped), value calculated using timer fr                                                                                                                                                equency.. 48.00 BogoMIPS (lpj=120000)
[    0.000240] pid_max: default: 32768 minimum: 301
[    0.000340] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000347] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000731] CPU: Testing write buffer coherency: ok
[    0.000938] CPU0: update cpu_capacity 1535
[    0.000945] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.001042] Setting up static identity map for 0x4042c780 - 0x4042c7d8
[    0.001198] ARM CCI driver probed
[    0.001615] Exynos MCPM support installed
[    0.030221] CPU1: Booted secondary processor
[    0.030256] CPU1: update cpu_capacity 1535
[    0.030260] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.040219] CPU2: Booted secondary processor
[    0.040245] CPU2: update cpu_capacity 1535
[    0.040248] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.050208] CPU3: Booted secondary processor
[    0.050233] CPU3: update cpu_capacity 1535
[    0.050237] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.060245] CPU4: Booted secondary processor
[    0.060344] CPU4: update cpu_capacity 448
[    0.060355] CPU4: thread -1, cpu 0, socket 1, mpidr 80000100
[    0.070236] CPU5: Booted secondary processor
[    0.070298] CPU5: update cpu_capacity 448
[    0.070307] CPU5: thread -1, cpu 1, socket 1, mpidr 80000101
[    0.080243] CPU6: Booted secondary processor
[    0.080305] CPU6: update cpu_capacity 448
[    0.080314] CPU6: thread -1, cpu 2, socket 1, mpidr 80000102
[    0.090237] CPU7: Booted secondary processor
[    0.090300] CPU7: update cpu_capacity 448
[    0.090310] CPU7: thread -1, cpu 3, socket 1, mpidr 80000103
[    0.090387] Brought up 8 CPUs
[    0.090419] SMP: Total of 8 processors activated.
[    0.090425] CPU: All CPU(s) started in SVC mode.
[    0.090902] devtmpfs: initialized
[    0.096013] VFP support v0.3: implementor 41 architecture 4 part 30 variant f                                                                                                                                                 rev 0
[    0.097714] pinctrl core: initialized pinctrl subsystem
[    0.112040] NET: Registered protocol family 16
[    0.113045] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.117023] gpiochip_add: registered GPIOs 0 to 7 on device: gpy7
[    0.117033] gpiochip_add: registered GPIOs 8 to 15 on device: gpx0
[    0.117041] gpiochip_add: registered GPIOs 16 to 23 on device: gpx1
[    0.117049] gpiochip_add: registered GPIOs 24 to 31 on device: gpx2
[    0.117057] gpiochip_add: registered GPIOs 32 to 39 on device: gpx3
[    0.117854] gpiochip_add: registered GPIOs 40 to 47 on device: gpc0
[    0.117863] gpiochip_add: registered GPIOs 48 to 55 on device: gpc1
[    0.117871] gpiochip_add: registered GPIOs 56 to 62 on device: gpc2
[    0.117879] gpiochip_add: registered GPIOs 63 to 66 on device: gpc3
[    0.117886] gpiochip_add: registered GPIOs 67 to 68 on device: gpc4
[    0.117894] gpiochip_add: registered GPIOs 69 to 76 on device: gpd1
[    0.117901] gpiochip_add: registered GPIOs 77 to 82 on device: gpy0
[    0.117909] gpiochip_add: registered GPIOs 83 to 86 on device: gpy1
[    0.117916] gpiochip_add: registered GPIOs 87 to 92 on device: gpy2
[    0.117924] gpiochip_add: registered GPIOs 93 to 100 on device: gpy3
[    0.117931] gpiochip_add: registered GPIOs 101 to 108 on device: gpy4
[    0.117939] gpiochip_add: registered GPIOs 109 to 116 on device: gpy5
[    0.117946] gpiochip_add: registered GPIOs 117 to 124 on device: gpy6
[    0.118471] gpiochip_add: registered GPIOs 125 to 132 on device: gpe0
[    0.118479] gpiochip_add: registered GPIOs 133 to 134 on device: gpe1
[    0.118487] gpiochip_add: registered GPIOs 135 to 140 on device: gpf0
[    0.118495] gpiochip_add: registered GPIOs 141 to 148 on device: gpf1
[    0.118502] gpiochip_add: registered GPIOs 149 to 156 on device: gpg0
[    0.118510] gpiochip_add: registered GPIOs 157 to 164 on device: gpg1
[    0.118517] gpiochip_add: registered GPIOs 165 to 166 on device: gpg2
[    0.118525] gpiochip_add: registered GPIOs 167 to 170 on device: gpj4
[    0.119033] gpiochip_add: registered GPIOs 171 to 178 on device: gpa0
[    0.119042] gpiochip_add: registered GPIOs 179 to 184 on device: gpa1
[    0.119050] gpiochip_add: registered GPIOs 185 to 192 on device: gpa2
[    0.119057] gpiochip_add: registered GPIOs 193 to 197 on device: gpb0
[    0.119065] gpiochip_add: registered GPIOs 198 to 202 on device: gpb1
[    0.119073] gpiochip_add: registered GPIOs 203 to 206 on device: gpb2
[    0.119080] gpiochip_add: registered GPIOs 207 to 214 on device: gpb3
[    0.119088] gpiochip_add: registered GPIOs 215 to 216 on device: gpb4
[    0.119095] gpiochip_add: registered GPIOs 217 to 224 on device: gph0
[    0.119676] gpiochip_add: registered GPIOs 225 to 231 on device: gpz
[    0.120916] exynos-audss-clk 3810000.audss-clock-controller: setup completed
[    0.126679] EXYNOS5420 PMU initialized
[    0.156211] of_get_named_gpiod_flags: parsed 'gpio' property of node '/regula                                                                                                                                                tor-usb300[0]' - status (0)
[    0.156509] of_get_named_gpiod_flags: parsed 'gpio' property of node '/regula                                                                                                                                                tor-usb301[0]' - status (0)
[    0.156767] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/f                                                                                                                                                ixed-regulator[0]'
[    0.158409] SCSI subsystem initialized
[    0.158841] usbcore: registered new interface driver usbfs
[    0.158941] usbcore: registered new interface driver hub
[    0.159093] usbcore: registered new device driver usb
[    0.159672] s3c-i2c 12c80000.i2c: slave address 0x50
[    0.159684] s3c-i2c 12c80000.i2c: bus frequency set to 65 KHz
[    0.159870] s3c-i2c 12c80000.i2c: i2c-2: S3C I2C adapter
[    0.162807] Advanced Linux Sound Architecture Driver Initialized.
[    0.163569] Switched to clocksource mct-frc
[    0.176514] NET: Registered protocol family 2
[    0.176937] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.176994] TCP bind hash table entries: 8192 (order: 5, 163840 bytes)
[    0.177086] TCP: Hash tables configured (established 8192 bind 8192)
[    0.177126] TCP: reno registered
[    0.177137] UDP hash table entries: 512 (order: 2, 24576 bytes)
[    0.177161] UDP-Lite hash table entries: 512 (order: 2, 24576 bytes)
[    0.177327] NET: Registered protocol family 1
[    0.179529] futex hash table entries: 2048 (order: 5, 131072 bytes)
[    0.192419] romfs: ROMFS MTD (C) 2007 Red Hat, Inc.
[    0.193042] bounce: pool size: 64 pages
[    0.193054] io scheduler noop registered
[    0.193063] io scheduler deadline registered
[    0.193477] io scheduler cfq registered (default)
[    0.193698] exynos-dp-video-phy 10040728.video-phy: Failed to lookup PMU regm                                                                                                                                                ap
[    0.193946] exynos-mipi-video-phy 10040714.video-phy: can't request region fo                                                                                                                                                r resource [mem 0x10040714-0x1004071f]
[    0.193963] exynos-mipi-video-phy: probe of 10040714.video-phy failed with er                                                                                                                                                ror -16
[    0.198698] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330
[    0.198708] dma-pl330 3880000.adma:  DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 N                                                                                                                                                um_Events-6
[    0.202828] dma-pl330 121a0000.pdma: Loaded driver for PL330 DMAC-241330
[    0.202837] dma-pl330 121a0000.pdma:         DBUFF-32x4bytes Num_Chans-8 Num_                                                                                                                                                Peri-32 Num_Events-32
[    0.206913] dma-pl330 121b0000.pdma: Loaded driver for PL330 DMAC-241330
[    0.206923] dma-pl330 121b0000.pdma:         DBUFF-32x4bytes Num_Chans-8 Num_                                                                                                                                                Peri-32 Num_Events-32
[    0.208044] dma-pl330 10800000.mdma: Loaded driver for PL330 DMAC-241330
[    0.208053] dma-pl330 10800000.mdma:         DBUFF-64x8bytes Num_Chans-8 Num_                                                                                                                                                Peri-1 Num_Events-32
[    0.311556] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    0.313006] samsung-uart 12c00000.serial: ttySAC0 at MMIO 0x12c00000 (irq = 8                                                                                                                                                3, base_baud = 0) is a S3C6400/10
[    0.313353] samsung-uart 12c10000.serial: ttySAC1 at MMIO 0x12c10000 (irq = 8                                                                                                                                                4, base_baud = 0) is a S3C6400/10
[    0.313737] samsung-uart 12c20000.serial: ttySAC2 at MMIO 0x12c20000 (irq = 8                                                                                                                                                5, base_baud = 0) is a S3C6400/10
[    0.314079] samsung-uart 12c30000.serial: ttySAC3 at MMIO 0x12c30000 (irq = 8                                                                                                                                                6, base_baud = 0) is a S3C6400/10
[    1.285505] console [ttySAC3] enabled
[    1.290414] error detecting cacheinfo..cpu0
[    1.300324] brd: module loaded
[    1.305533] loop: module loaded
[    1.307769] of_get_named_gpiod_flags: parsed 'cs-gpios' property of node '/sp                                                                                                                                                i@12d40000[0]' - status (0)
[    1.317550] cros-ec-spi spi2.0: Chrome EC device registered
[    1.322624] usbcore: registered new interface driver asix
[    1.327708] usbcore: registered new interface driver ax88179_178a
[    1.333717] usbcore: registered new interface driver cdc_ether
[    1.339554] usbcore: registered new interface driver smsc75xx
[    1.345469] usbcore: registered new interface driver smsc95xx
[    1.351085] usbcore: registered new interface driver net1080
[    1.356671] usbcore: registered new interface driver cdc_subset
[    1.362516] usbcore: registered new interface driver zaurus
[    1.368106] usbcore: registered new interface driver cdc_ncm
[    1.374271] usb@12000000 supply vdd33 not found, using dummy regulator
[    1.380223] usb@12000000 supply vdd10 not found, using dummy regulator
[    1.788070] usb@12400000 supply vdd33 not found, using dummy regulator
[    1.793174] usb@12400000 supply vdd10 not found, using dummy regulator
[    2.200906] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    2.204947] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus nu                                                                                                                                                mber 1
[    2.212818] xhci-hcd xhci-hcd.2.auto: irq 104, io mem 0x12000000
[    2.218705] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.225314] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=                                                                                                                                                1
[    2.232513] usb usb1: Product: xHCI Host Controller
[    2.237370] usb usb1: Manufacturer: Linux 3.18.0-rc5-next-20141121 xhci-hcd
[    2.244311] usb usb1: SerialNumber: xhci-hcd.2.auto
[    2.249760] hub 1-0:1.0: USB hub found
[    2.252902] hub 1-0:1.0: 1 port detected
[    2.257145] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    2.262278] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus nu                                                                                                                                                mber 2
[    2.270050] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    2.276667] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=                                                                                                                                                1
[    2.283867] usb usb2: Product: xHCI Host Controller
[    2.288724] usb usb2: Manufacturer: Linux 3.18.0-rc5-next-20141121 xhci-hcd
[    2.295663] usb usb2: SerialNumber: xhci-hcd.2.auto
[    2.301072] hub 2-0:1.0: USB hub found
[    2.304272] hub 2-0:1.0: 1 port detected
[    2.308530] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[    2.313642] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus nu                                                                                                                                                mber 3
[    2.321518] xhci-hcd xhci-hcd.5.auto: irq 105, io mem 0x12400000
[    2.327360] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    2.334010] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=                                                                                                                                                1
[    2.341207] usb usb3: Product: xHCI Host Controller
[    2.346065] usb usb3: Manufacturer: Linux 3.18.0-rc5-next-20141121 xhci-hcd
[    2.353005] usb usb3: SerialNumber: xhci-hcd.5.auto
[    2.358476] hub 3-0:1.0: USB hub found
[    2.361617] hub 3-0:1.0: 1 port detected
[    2.365839] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[    2.370979] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus nu                                                                                                                                                mber 4
[    2.378742] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[    2.385368] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=                                                                                                                                                1
[    2.392566] usb usb4: Product: xHCI Host Controller
[    2.397424] usb usb4: Manufacturer: Linux 3.18.0-rc5-next-20141121 xhci-hcd
[    2.404456] usb usb4: SerialNumber: xhci-hcd.5.auto
[    2.409779] hub 4-0:1.0: USB hub found
[    2.412953] hub 4-0:1.0: 1 port detected
[    2.417236] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.423366] ehci-exynos: EHCI EXYNOS driver
[    2.427669] of_get_named_gpiod_flags: can't parse 'samsung,vbus-gpio' propert                                                                                                                                                y of node '/usb@12110000[0]'
[    2.437249] exynos-ehci 12110000.usb: EHCI Host Controller
[    2.442554] exynos-ehci 12110000.usb: new USB bus registered, assigned bus nu                                                                                                                                                mber 5
[    2.450278] exynos-ehci 12110000.usb: irq 103, io mem 0x12110000
[    2.463601] exynos-ehci 12110000.usb: USB 2.0 started, EHCI 1.00
[    2.468245] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
[    2.474924] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=                                                                                                                                                1
[    2.482109] usb usb5: Product: EHCI Host Controller
[    2.486966] usb usb5: Manufacturer: Linux 3.18.0-rc5-next-20141121 ehci_hcd
[    2.493925] usb usb5: SerialNumber: 12110000.usb
[    2.499062] hub 5-0:1.0: USB hub found
[    2.502236] hub 5-0:1.0: 3 ports detected
[    2.506818] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    2.512413] ohci-exynos: OHCI EXYNOS driver
[    2.516819] exynos-ohci 12120000.usb: USB Host Controller
[    2.521945] exynos-ohci 12120000.usb: new USB bus registered, assigned bus nu                                                                                                                                                mber 6
[    2.529639] exynos-ohci 12120000.usb: irq 103, io mem 0x12120000
[    2.592724] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[    2.598043] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.606177] usb usb6: Product: USB Host Controller
[    2.610014] usb usb6: Manufacturer: Linux 3.18.0-rc5-next-20141121 ohci_hcd
[    2.616952] usb usb6: SerialNumber: 12120000.usb
[    2.622079] hub 6-0:1.0: USB hub found
[    2.625303] hub 6-0:1.0: 3 ports detected
[    2.629912] usbcore: registered new interface driver usb-storage
[    2.635746] mousedev: PS/2 mouse device common for all mice
[    2.641231] input: cros-ec-spi as /devices/platform/12d40000.spi/spi_master/spi2/spi2.0/cros-ec-keyb.1/input/input0
[    2.652124] s3c-rtc 101e0000.rtc: rtc disabled, re-enabling
[    2.656847] rtc (null): read_time: fail to read
[    2.661451] s3c-rtc 101e0000.rtc: rtc core: registered s3c as rtc0
[    2.667474] s3c-rtc 101e0000.rtc: warning: invalid RTC value so initializing it
[    2.675012] i2c /dev entries driver
[    2.683411] max77686 4-0009: Failed to find supply inb1
[    2.687297] max77802-pmic max77802-pmic: regulator init failed for 0
[    2.693539] platform max77802-pmic: Driver max77802-pmic requests probe deferral
[    2.703658] rtc (null): read_time: fail to read
[    2.706888] max77802-rtc max77802-rtc: rtc core: registered max77802-rtc as rtc1
[    2.735598] atmel_mxt_ts 8-004b: Direct firmware load for maxtouch.cfg failed with error -2
[    2.743869] input: Atmel maXTouch Touchpad as /devices/platform/12e00000.i2c/i2c-8/8-004b/input/input1
[    2.752176] atmel_mxt_ts 8-004b: Family: 130 Variant: 35 Firmware V2.0.AA Objects: 23
[    2.759662] tpm_i2c_infineon 9-0020: 1.2 TPM (device-id 0x1A)
[    2.850320] tps65090 20-0048: No cache defaults, reading back from HW
[    2.860084] of_get_named_gpiod_flags: can't parse 'dcdc-ext-control-gpios' property of node '/spi@12d40000/cros-ec@0/i2c-tunnel/power-regulator@48[0]'
[    2.872087] of_get_named_gpiod_flags: can't parse 'dcdc-ext-control-gpios' property of node '/spi@12d40000/cros-ec@0/i2c-tunnel/power-regulator@48[0]'
[    2.885548] of_get_named_gpiod_flags: can't parse 'dcdc-ext-control-gpios' property of node '/spi@12d40000/cros-ec@0/i2c-tunnel/power-regulator@48[0]'
[    2.899156] TPS65090_RAILSDCDC1: supplied by vbat-supply
[    2.905922] TPS65090_RAILSDCDC2: supplied by vbat-supply
[    2.911409] TPS65090_RAILSDCDC3: supplied by vbat-supply
[    2.916895] vcd_led: supplied by vbat-supply
[    2.925688] video_mid: supplied by TPS65090_RAILSDCDC1
[    2.935378] wwan_r: supplied by TPS65090_RAILSDCDC2
[    2.943517] sdcard: supplied by TPS65090_RAILSDCDC2
[    2.948578] camout: supplied by TPS65090_RAILSDCDC2
[    2.953627] lcd_vdd: supplied by TPS65090_RAILSDCDC2
[    2.963097] video_mid_1a: supplied by TPS65090_RAILSDCDC1
[    2.968693] TPS65090_RAILSLDO1: supplied by vbat-supply
[    2.972631] TPS65090_RAILSLDO2: supplied by vbat-supply
[    3.160792] sbs-battery 20-000b: sbs-battery: battery gas gauge device registered
[    3.181250] 10060000.tmu supply vtmu not found, using dummy regulator
[    3.186795] exynos-tmu 10060000.tmu: Exynos: Thermal zone(therm_zone0) registered
[    3.193925] 10064000.tmu supply vtmu not found, using dummy regulator
[    3.200838] exynos-tmu 10064000.tmu: Exynos: Thermal zone(therm_zone0) registered
[    3.207729] 10068000.tmu supply vtmu not found, using dummy regulator
[    3.214394] exynos-tmu 10068000.tmu: Exynos: Thermal zone(therm_zone0) registered
[    3.221517] 1006c000.tmu supply vtmu not found, using dummy regulator
[    3.228207] exynos-tmu 1006c000.tmu: Exynos: Thermal zone(therm_zone0) registered
[    3.235385] 100a0000.tmu supply vtmu not found, using dummy regulator
[    3.242243] exynos-tmu 100a0000.tmu: Exynos: Thermal zone(therm_zone0) registered
[    3.249910] s3c2410-wdt 101d0000.watchdog: watchdog inactive, reset disabled, irq disabled
[    3.258347] device-mapper: ioctl: 4.29.0-ioctl (2014-10-28) initialised: dm-devel@redhat.com
[    3.265869] Driver 'mmcblk' needs updating - please use bus_type methods
[    3.272606] sdhci: Secure Digital Host Controller Interface driver
[    3.278737] sdhci: Copyright(c) Pierre Ossman
[    3.283255] Synopsys Designware Multimedia Card Interface Driver
[    3.289595] dwmmc_exynos 12200000.mmc: IDMAC supports 32-bit address mode.
[    3.295918] dwmmc_exynos 12200000.mmc: Using internal DMA controller.
[    3.302303] dwmmc_exynos 12200000.mmc: Version ID is 250a
[    3.307735] dwmmc_exynos 12200000.mmc: DW MMC controller at irq 107, 64 bit host data width, 64 deep fifo
[    3.317242] dwmmc_exynos 12200000.mmc: No vmmc regulator found
[    3.323029] dwmmc_exynos 12200000.mmc: No vqmmc regulator found
[    3.328938] dwmmc_exynos 12200000.mmc: GPIO lookup for consumer wp
[    3.335086] dwmmc_exynos 12200000.mmc: using device tree for GPIO lookup
[    3.341768] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@12200000[0]'
[    3.350530] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@12200000[0]'
[    3.359202] dwmmc_exynos 12200000.mmc: using lookup tables for GPIO lookup
[    3.366061] dwmmc_exynos 12200000.mmc: lookup for GPIO wp failed
[    3.398715] dwmmc_exynos 12200000.mmc: 1 slots initialized
[    3.403537] dwmmc_exynos 12220000.mmc: IDMAC supports 32-bit address mode.
[    3.409627] dwmmc_exynos 12220000.mmc: Using internal DMA controller.
[    3.416015] dwmmc_exynos 12220000.mmc: Version ID is 250a
[    3.421400] dwmmc_exynos 12220000.mmc: DW MMC controller at irq 109, 64 bit host data width, 64 deep fifo
[    3.430943] dwmmc_exynos 12220000.mmc: No vmmc regulator found
[    3.436744] dwmmc_exynos 12220000.mmc: No vqmmc regulator found
[    3.441627] mmc0: BKOPS_EN bit is not set
[    3.445568] mmc_host mmc0: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0)
[    3.446428] mmc0: new HS200 MMC card at address 0001
[    3.447543] mmcblk0: mmc0:0001 MAG2GC 14.5 GiB
[    3.447812] mmcblk0boot0: mmc0:0001 MAG2GC partition 1 4.00 MiB
[    3.448098] mmcblk0boot1: mmc0:0001 MAG2GC partition 2 4.00 MiB
[    3.448401] mmcblk0rpmb: mmc0:0001 MAG2GC partition 3 4.00 MiB
[    3.460925]  mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12
[    3.489326] dwmmc_exynos 12220000.mmc: GPIO lookup for consumer cd
[    3.495477] dwmmc_exynos 12220000.mmc: using device tree for GPIO lookup
[    3.502154] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/mmc@12220000[0]'
[    3.510937] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/mmc@12220000[0]'
[    3.519586] dwmmc_exynos 12220000.mmc: using lookup tables for GPIO lookup
[    3.526442] dwmmc_exynos 12220000.mmc: lookup for GPIO cd failed
[    3.532432] dwmmc_exynos 12220000.mmc: GPIO lookup for consumer wp
[    3.538598] dwmmc_exynos 12220000.mmc: using device tree for GPIO lookup
[    3.545267] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@12220000[0]'
[    3.554027] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@12220000[0]'
[    3.562701] dwmmc_exynos 12220000.mmc: using lookup tables for GPIO lookup
[    3.569560] dwmmc_exynos 12220000.mmc: lookup for GPIO wp failed
[    3.603642] dwmmc_exynos 12220000.mmc: 1 slots initialized
[    3.609436] usbcore: registered new interface driver usbhid
[    3.613526] usbhid: USB HID core driver
[    3.618167] exynos-adc 12d10000.adc: failed getting regulator, err = -517
[    3.624142] platform 12d10000.adc: Driver exynos-adc requests probe deferral
[   24.188722] random: nonblocking pool is initialized

[-- Attachment #3: dmatest.txt --]
[-- Type: text/plain, Size: 27457 bytes --]

# echo 2000 > /sys/module/dmatest/parameters/timeout
# echo 2 > /sys/module/dmatest/parameters/iterations
# for i in `ls /sys/class/dma/`; do echo $i > /sys/module/dmatest/parameters/channel; echo 1 > /sys/module/dmatest/parameters/run; done
[   67.723959] dmatest: Started 1 threads using dma0chan0
[   67.724092] dma-pl330 3880000.adma: fill_queue:1954 Bad Desc(2)
[   67.724249] dmatest: dma0chan0-copy0: dstbuf[0x1708] not copied! Expected d1, got 37
[   67.724256] dmatest: dma0chan0-copy0: dstbuf[0x1709] not copied! Expected d0, got 36
[   67.724264] dmatest: dma0chan0-copy0: dstbuf[0x170a] not copied! Expected cf, got 35
[   67.724271] dmatest: dma0chan0-copy0: dstbuf[0x170b] not copied! Expected ce, got 34
[   67.724277] dmatest: dma0chan0-copy0: dstbuf[0x170c] not copied! Expected cd, got 33
[   67.724285] dmatest: dma0chan0-copy0: dstbuf[0x170d] not copied! Expected cc, got 32
[   67.724292] dmatest: dma0chan0-copy0: dstbuf[0x170e] not copied! Expected cb, got 31
[   67.724298] dmatest: dma0chan0-copy0: dstbuf[0x170f] not copied! Expected ca, got 30
[   67.724305] dmatest: dma0chan0-copy0: dstbuf[0x1710] not copied! Expected c9, got 2f
[   67.724312] dmatest: dma0chan0-copy0: dstbuf[0x1711] not copied! Expected c8, got 2e
[   67.724318] dmatest: dma0chan0-copy0: dstbuf[0x1712] not copied! Expected c7, got 2d
[   67.724325] dmatest: dma0chan0-copy0: dstbuf[0x1713] not copied! Expected c6, got 2c
[   67.724332] dmatest: dma0chan0-copy0: dstbuf[0x1714] not copied! Expected c5, got 2b
[   67.724338] dmatest: dma0chan0-copy0: dstbuf[0x1715] not copied! Expected c4, got 2a
[   67.724345] dmatest: dma0chan0-copy0: dstbuf[0x1716] not copied! Expected c3, got 29
[   67.724351] dmatest: dma0chan0-copy0: dstbuf[0x1717] not copied! Expected c2, got 28
[   67.724358] dmatest: dma0chan0-copy0: dstbuf[0x1718] not copied! Expected c1, got 27
[   67.724365] dmatest: dma0chan0-copy0: dstbuf[0x1719] not copied! Expected c0, got 26
[   67.724371] dmatest: dma0chan0-copy0: dstbuf[0x171a] not copied! Expected df, got 25
[   67.724378] dmatest: dma0chan0-copy0: dstbuf[0x171b] not copied! Expected de, got 24
[   67.724384] dmatest: dma0chan0-copy0: dstbuf[0x171c] not copied! Expected dd, got 23
[   67.724391] dmatest: dma0chan0-copy0: dstbuf[0x171d] not copied! Expected dc, got 22
[   67.724398] dmatest: dma0chan0-copy0: dstbuf[0x171e] not copied! Expected db, got 21
[   67.724404] dmatest: dma0chan0-copy0: dstbuf[0x171f] not copied! Expected da, got 20
[   67.724411] dmatest: dma0chan0-copy0: dstbuf[0x1720] not copied! Expected d9, got 3f
[   67.724417] dmatest: dma0chan0-copy0: dstbuf[0x1721] not copied! Expected d8, got 3e
[   67.724424] dmatest: dma0chan0-copy0: dstbuf[0x1722] not copied! Expected d7, got 3d
[   67.724431] dmatest: dma0chan0-copy0: dstbuf[0x1723] not copied! Expected d6, got 3c
[   67.724437] dmatest: dma0chan0-copy0: dstbuf[0x1724] not copied! Expected d5, got 3b
[   67.724444] dmatest: dma0chan0-copy0: dstbuf[0x1725] not copied! Expected d4, got 3a
[   67.724451] dmatest: dma0chan0-copy0: dstbuf[0x1726] not copied! Expected d3, got 39
[   67.724457] dmatest: dma0chan0-copy0: dstbuf[0x1727] not copied! Expected d2, got 38
[   67.724483] dmatest: dma0chan0-copy0: 4381 errors suppressed
[   67.724514] dmatest: dma0chan0-copy0: result #1: 'data error' with src_off=0x298e dst_off=0x1708 len=0x113d (4413)
[   67.724606] dma-pl330 3880000.adma: fill_queue:1954 Bad Desc(3)
[   67.724728] dmatest: dma0chan0-copy0: dstbuf[0x14a7] not copied! Expected c1, got 38
[   67.724735] dmatest: dma0chan0-copy0: dstbuf[0x14a8] not copied! Expected c0, got 37
[   67.724742] dmatest: dma0chan0-copy0: dstbuf[0x14a9] not copied! Expected df, got 36
[   67.724750] dmatest: dma0chan0-copy0: dstbuf[0x14aa] not copied! Expected de, got 35
[   67.724757] dmatest: dma0chan0-copy0: dstbuf[0x14ab] not copied! Expected dd, got 34
[   67.724763] dmatest: dma0chan0-copy0: dstbuf[0x14ac] not copied! Expected dc, got 33
[   67.724770] dmatest: dma0chan0-copy0: dstbuf[0x14ad] not copied! Expected db, got 32
[   67.724777] dmatest: dma0chan0-copy0: dstbuf[0x14ae] not copied! Expected da, got 31
[   67.724783] dmatest: dma0chan0-copy0: dstbuf[0x14af] not copied! Expected d9, got 30
[   67.724790] dmatest: dma0chan0-copy0: dstbuf[0x14b0] not copied! Expected d8, got 2f
[   67.724796] dmatest: dma0chan0-copy0: dstbuf[0x14b1] not copied! Expected d7, got 2e
[   67.724803] dmatest: dma0chan0-copy0: dstbuf[0x14b2] not copied! Expected d6, got 2d
[   67.724810] dmatest: dma0chan0-copy0: dstbuf[0x14b3] not copied! Expected d5, got 2c
[   67.724816] dmatest: dma0chan0-copy0: dstbuf[0x14b4] not copied! Expected d4, got 2b
[   67.724823] dmatest: dma0chan0-copy0: dstbuf[0x14b5] not copied! Expected d3, got 2a
[   67.724829] dmatest: dma0chan0-copy0: dstbuf[0x14b6] not copied! Expected d2, got 29
[   67.724836] dmatest: dma0chan0-copy0: dstbuf[0x14b7] not copied! Expected d1, got 28
[   67.724842] dmatest: dma0chan0-copy0: dstbuf[0x14b8] not copied! Expected d0, got 27
[   67.724848] dmatest: dma0chan0-copy0: dstbuf[0x14b9] not copied! Expected cf, got 26
[   67.724855] dmatest: dma0chan0-copy0: dstbuf[0x14ba] not copied! Expected ce, got 25
[   67.724861] dmatest: dma0chan0-copy0: dstbuf[0x14bb] not copied! Expected cd, got 24
[   67.724868] dmatest: dma0chan0-copy0: dstbuf[0x14bc] not copied! Expected cc, got 23
[   67.724875] dmatest: dma0chan0-copy0: dstbuf[0x14bd] not copied! Expected cb, got 22
[   67.724881] dmatest: dma0chan0-copy0: dstbuf[0x14be] not copied! Expected ca, got 21
[   67.724888] dmatest: dma0chan0-copy0: dstbuf[0x14bf] not copied! Expected c9, got 20
[   67.724895] dmatest: dma0chan0-copy0: dstbuf[0x14c0] not copied! Expected c8, got 3f
[   67.724901] dmatest: dma0chan0-copy0: dstbuf[0x14c1] not copied! Expected c7, got 3e
[   67.724908] dmatest: dma0chan0-copy0: dstbuf[0x14c2] not copied! Expected c6, got 3d
[   67.724914] dmatest: dma0chan0-copy0: dstbuf[0x14c3] not copied! Expected c5, got 3c
[   67.724921] dmatest: dma0chan0-copy0: dstbuf[0x14c4] not copied! Expected c4, got 3b
[   67.724928] dmatest: dma0chan0-copy0: dstbuf[0x14c5] not copied! Expected c3, got 3a
[   67.724935] dmatest: dma0chan0-copy0: dstbuf[0x14c6] not copied! Expected c2, got 39
[   67.724987] dmatest: dma0chan0-copy0: 10741 errors suppressed
[   67.724996] dmatest: dma0chan0-copy0: result #2: 'data error' with src_off=0x33e dst_off=0x14a7 len=0x2a15 (10773)
[   67.725012] dmatest: dma0chan0-copy0: summary 2 tests, 2 failures 1953 iops 13671 KB/s (0)
[   68.274078] dmatest: Started 1 threads using dma0chan1
[   68.274209] dma-pl330 3880000.adma: fill_queue:1954 Bad Desc(2)
[   68.274317] dmatest: dma0chan1-copy0: dstbuf[0x247] not copied! Expected cf, got 38
[   68.274324] dmatest: dma0chan1-copy0: dstbuf[0x248] not copied! Expected ce, got 37
[   68.274331] dmatest: dma0chan1-copy0: dstbuf[0x249] not copied! Expected cd, got 36
[   68.274338] dmatest: dma0chan1-copy0: dstbuf[0x24a] not copied! Expected cc, got 35
[   68.274345] dmatest: dma0chan1-copy0: dstbuf[0x24b] not copied! Expected cb, got 34
[   68.274351] dmatest: dma0chan1-copy0: dstbuf[0x24c] not copied! Expected ca, got 33
[   68.274358] dmatest: dma0chan1-copy0: dstbuf[0x24d] not copied! Expected c9, got 32
[   68.274365] dmatest: dma0chan1-copy0: dstbuf[0x24e] not copied! Expected c8, got 31
[   68.274371] dmatest: dma0chan1-copy0: dstbuf[0x24f] not copied! Expected c7, got 30
[   68.274378] dmatest: dma0chan1-copy0: dstbuf[0x250] not copied! Expected c6, got 2f
[   68.274384] dmatest: dma0chan1-copy0: dstbuf[0x251] not copied! Expected c5, got 2e
[   68.274391] dmatest: dma0chan1-copy0: dstbuf[0x252] not copied! Expected c4, got 2d
[   68.274398] dmatest: dma0chan1-copy0: dstbuf[0x253] not copied! Expected c3, got 2c
[   68.274405] dmatest: dma0chan1-copy0: dstbuf[0x254] not copied! Expected c2, got 2b
[   68.274412] dmatest: dma0chan1-copy0: dstbuf[0x255] not copied! Expected c1, got 2a
[   68.274418] dmatest: dma0chan1-copy0: dstbuf[0x256] not copied! Expected c0, got 29
[   68.274425] dmatest: dma0chan1-copy0: dstbuf[0x257] not copied! Expected df, got 28
[   68.274431] dmatest: dma0chan1-copy0: dstbuf[0x258] not copied! Expected de, got 27
[   68.274438] dmatest: dma0chan1-copy0: dstbuf[0x259] not copied! Expected dd, got 26
[   68.274445] dmatest: dma0chan1-copy0: dstbuf[0x25a] not copied! Expected dc, got 25
[   68.274451] dmatest: dma0chan1-copy0: dstbuf[0x25b] not copied! Expected db, got 24
[   68.274458] dmatest: dma0chan1-copy0: dstbuf[0x25c] not copied! Expected da, got 23
[   68.274464] dmatest: dma0chan1-copy0: dstbuf[0x25d] not copied! Expected d9, got 22
[   68.274471] dmatest: dma0chan1-copy0: dstbuf[0x25e] not copied! Expected d8, got 21
[   68.274478] dmatest: dma0chan1-copy0: dstbuf[0x25f] not copied! Expected d7, got 20
[   68.274484] dmatest: dma0chan1-copy0: dstbuf[0x260] not copied! Expected d6, got 3f
[   68.274491] dmatest: dma0chan1-copy0: dstbuf[0x261] not copied! Expected d5, got 3e
[   68.274498] dmatest: dma0chan1-copy0: dstbuf[0x262] not copied! Expected d4, got 3d
[   68.274505] dmatest: dma0chan1-copy0: dstbuf[0x263] not copied! Expected d3, got 3c
[   68.274511] dmatest: dma0chan1-copy0: dstbuf[0x264] not copied! Expected d2, got 3b
[   68.274518] dmatest: dma0chan1-copy0: dstbuf[0x265] not copied! Expected d1, got 3a
[   68.274525] dmatest: dma0chan1-copy0: dstbuf[0x266] not copied! Expected d0, got 39
[   68.274582] dmatest: dma0chan1-copy0: 11923 errors suppressed
[   68.274604] dmatest: dma0chan1-copy0: result #1: 'data error' with src_off=0x970 dst_off=0x247 len=0x2eb3 (11955)
[   68.274693] dma-pl330 3880000.adma: fill_queue:1954 Bad Desc(3)
[   68.274804] dmatest: dma0chan1-copy0: dstbuf[0x88f] not copied! Expected c2, got 30
[   68.274811] dmatest: dma0chan1-copy0: dstbuf[0x890] not copied! Expected c1, got 2f
[   68.274818] dmatest: dma0chan1-copy0: dstbuf[0x891] not copied! Expected c0, got 2e
[   68.274824] dmatest: dma0chan1-copy0: dstbuf[0x892] not copied! Expected df, got 2d
[   68.274831] dmatest: dma0chan1-copy0: dstbuf[0x893] not copied! Expected de, got 2c
[   68.274836] dmatest: dma0chan1-copy0: dstbuf[0x894] not copied! Expected dd, got 2b
[   68.274843] dmatest: dma0chan1-copy0: dstbuf[0x895] not copied! Expected dc, got 2a
[   68.274850] dmatest: dma0chan1-copy0: dstbuf[0x896] not copied! Expected db, got 29
[   68.274856] dmatest: dma0chan1-copy0: dstbuf[0x897] not copied! Expected da, got 28
[   68.274863] dmatest: dma0chan1-copy0: dstbuf[0x898] not copied! Expected d9, got 27
[   68.274870] dmatest: dma0chan1-copy0: dstbuf[0x899] not copied! Expected d8, got 26
[   68.274876] dmatest: dma0chan1-copy0: dstbuf[0x89a] not copied! Expected d7, got 25
[   68.274883] dmatest: dma0chan1-copy0: dstbuf[0x89b] not copied! Expected d6, got 24
[   68.274890] dmatest: dma0chan1-copy0: dstbuf[0x89c] not copied! Expected d5, got 23
[   68.274896] dmatest: dma0chan1-copy0: dstbuf[0x89d] not copied! Expected d4, got 22
[   68.274903] dmatest: dma0chan1-copy0: dstbuf[0x89e] not copied! Expected d3, got 21
[   68.274909] dmatest: dma0chan1-copy0: dstbuf[0x89f] not copied! Expected d2, got 20
[   68.274916] dmatest: dma0chan1-copy0: dstbuf[0x8a0] not copied! Expected d1, got 3f
[   68.274923] dmatest: dma0chan1-copy0: dstbuf[0x8a1] not copied! Expected d0, got 3e
[   68.274930] dmatest: dma0chan1-copy0: dstbuf[0x8a2] not copied! Expected cf, got 3d
[   68.274936] dmatest: dma0chan1-copy0: dstbuf[0x8a3] not copied! Expected ce, got 3c
[   68.274943] dmatest: dma0chan1-copy0: dstbuf[0x8a4] not copied! Expected cd, got 3b
[   68.274950] dmatest: dma0chan1-copy0: dstbuf[0x8a5] not copied! Expected cc, got 3a
[   68.274956] dmatest: dma0chan1-copy0: dstbuf[0x8a6] not copied! Expected cb, got 39
[   68.274963] dmatest: dma0chan1-copy0: dstbuf[0x8a7] not copied! Expected ca, got 38
[   68.274970] dmatest: dma0chan1-copy0: dstbuf[0x8a8] not copied! Expected c9, got 37
[   68.274976] dmatest: dma0chan1-copy0: dstbuf[0x8a9] not copied! Expected c8, got 36
[   68.274983] dmatest: dma0chan1-copy0: dstbuf[0x8aa] not copied! Expected c7, got 35
[   68.274989] dmatest: dma0chan1-copy0: dstbuf[0x8ab] not copied! Expected c6, got 34
[   68.274996] dmatest: dma0chan1-copy0: dstbuf[0x8ac] not copied! Expected c5, got 33
[   68.275003] dmatest: dma0chan1-copy0: dstbuf[0x8ad] not copied! Expected c4, got 32
[   68.275010] dmatest: dma0chan1-copy0: dstbuf[0x8ae] not copied! Expected c3, got 31
[   68.275042] dmatest: dma0chan1-copy0: 6082 errors suppressed
[   68.275079] dmatest: dma0chan1-copy0: result #2: 'data error' with src_off=0x225d dst_off=0x88f len=0x17e2 (6114)
[   68.275093] dmatest: dma0chan1-copy0: summary 2 tests, 2 failures 2074 iops 17634 KB/s (0)
[   68.819684] dmatest: Started 1 threads using dma0chan10
[   68.820811] dma-pl330 3880000.adma: fill_queue:1954 Bad Desc(2)
[   68.820935] dmatest: dma0chan10-copy: dstbuf[0x27] not copied! Expected ca, got 38
[   68.820942] dmatest: dma0chan10-copy: dstbuf[0x28] not copied! Expected c9, got 37
[   68.820950] dmatest: dma0chan10-copy: dstbuf[0x29] not copied! Expected c8, got 36
[   68.820957] dmatest: dma0chan10-copy: dstbuf[0x2a] not copied! Expected c7, got 35
[   68.820963] dmatest: dma0chan10-copy: dstbuf[0x2b] not copied! Expected c6, got 34
[   68.820970] dmatest: dma0chan10-copy: dstbuf[0x2c] not copied! Expected c5, got 33
[   68.820977] dmatest: dma0chan10-copy: dstbuf[0x2d] not copied! Expected c4, got 32
[   68.820984] dmatest: dma0chan10-copy: dstbuf[0x2e] not copied! Expected c3, got 31
[   68.820991] dmatest: dma0chan10-copy: dstbuf[0x2f] not copied! Expected c2, got 30
[   68.820997] dmatest: dma0chan10-copy: dstbuf[0x30] not copied! Expected c1, got 2f
[   68.821004] dmatest: dma0chan10-copy: dstbuf[0x31] not copied! Expected c0, got 2e
[   68.821010] dmatest: dma0chan10-copy: dstbuf[0x32] not copied! Expected df, got 2d
[   68.821017] dmatest: dma0chan10-copy: dstbuf[0x33] not copied! Expected de, got 2c
[   68.821024] dmatest: dma0chan10-copy: dstbuf[0x34] not copied! Expected dd, got 2b
[   68.821030] dmatest: dma0chan10-copy: dstbuf[0x35] not copied! Expected dc, got 2a
[   68.821037] dmatest: dma0chan10-copy: dstbuf[0x36] not copied! Expected db, got 29
[   68.821044] dmatest: dma0chan10-copy: dstbuf[0x37] not copied! Expected da, got 28
[   68.821050] dmatest: dma0chan10-copy: dstbuf[0x38] not copied! Expected d9, got 27
[   68.821057] dmatest: dma0chan10-copy: dstbuf[0x39] not copied! Expected d8, got 26
[   68.821063] dmatest: dma0chan10-copy: dstbuf[0x3a] not copied! Expected d7, got 25
[   68.821070] dmatest: dma0chan10-copy: dstbuf[0x3b] not copied! Expected d6, got 24
[   68.821077] dmatest: dma0chan10-copy: dstbuf[0x3c] not copied! Expected d5, got 23
[   68.821083] dmatest: dma0chan10-copy: dstbuf[0x3d] not copied! Expected d4, got 22
[   68.821090] dmatest: dma0chan10-copy: dstbuf[0x3e] not copied! Expected d3, got 21
[   68.821097] dmatest: dma0chan10-copy: dstbuf[0x3f] not copied! Expected d2, got 20
[   68.821104] dmatest: dma0chan10-copy: dstbuf[0x40] not copied! Expected d1, got 3f
[   68.821110] dmatest: dma0chan10-copy: dstbuf[0x41] not copied! Expected d0, got 3e
[   68.821117] dmatest: dma0chan10-copy: dstbuf[0x42] not copied! Expected cf, got 3d
[   68.821123] dmatest: dma0chan10-copy: dstbuf[0x43] not copied! Expected ce, got 3c
[   68.821130] dmatest: dma0chan10-copy: dstbuf[0x44] not copied! Expected cd, got 3b
[   68.821137] dmatest: dma0chan10-copy: dstbuf[0x45] not copied! Expected cc, got 3a
[   68.821143] dmatest: dma0chan10-copy: dstbuf[0x46] not copied! Expected cb, got 39
[   68.821162] dmatest: dma0chan10-copy: 2954 errors suppressed
[   68.821220] dmatest: dma0chan10-copy: result #1: 'data error' with src_off=0x19b5 dst_off=0x27 len=0xbaa (2986)
[   68.821311] dma-pl330 3880000.adma: fill_queue:1954 Bad Desc(3)
[   68.821453] dmatest: dma0chan10-copy: dstbuf[0x2878] not copied! Expected d3, got 27
[   68.821460] dmatest: dma0chan10-copy: dstbuf[0x2879] not copied! Expected d2, got 26
[   68.821467] dmatest: dma0chan10-copy: dstbuf[0x287a] not copied! Expected d1, got 25
[   68.821474] dmatest: dma0chan10-copy: dstbuf[0x287b] not copied! Expected d0, got 24
[   68.821481] dmatest: dma0chan10-copy: dstbuf[0x287c] not copied! Expected cf, got 23
[   68.821487] dmatest: dma0chan10-copy: dstbuf[0x287d] not copied! Expected ce, got 22
[   68.821494] dmatest: dma0chan10-copy: dstbuf[0x287e] not copied! Expected cd, got 21
[   68.821501] dmatest: dma0chan10-copy: dstbuf[0x287f] not copied! Expected cc, got 20
[   68.821507] dmatest: dma0chan10-copy: dstbuf[0x2880] not copied! Expected cb, got 3f
[   68.821514] dmatest: dma0chan10-copy: dstbuf[0x2881] not copied! Expected ca, got 3e
[   68.821520] dmatest: dma0chan10-copy: dstbuf[0x2882] not copied! Expected c9, got 3d
[   68.821527] dmatest: dma0chan10-copy: dstbuf[0x2883] not copied! Expected c8, got 3c
[   68.821533] dmatest: dma0chan10-copy: dstbuf[0x2884] not copied! Expected c7, got 3b
[   68.821539] dmatest: dma0chan10-copy: dstbuf[0x2885] not copied! Expected c6, got 3a
[   68.821546] dmatest: dma0chan10-copy: dstbuf[0x2886] not copied! Expected c5, got 39
[   68.821552] dmatest: dma0chan10-copy: dstbuf[0x2887] not copied! Expected c4, got 38
[   68.821559] dmatest: dma0chan10-copy: dstbuf[0x2888] not copied! Expected c3, got 37
[   68.821566] dmatest: dma0chan10-copy: dstbuf[0x2889] not copied! Expected c2, got 36
[   68.821572] dmatest: dma0chan10-copy: dstbuf[0x288a] not copied! Expected c1, got 35
[   68.821579] dmatest: dma0chan10-copy: dstbuf[0x288b] not copied! Expected c0, got 34
[   68.821585] dmatest: dma0chan10-copy: dstbuf[0x288c] not copied! Expected df, got 33
[   68.821592] dmatest: dma0chan10-copy: dstbuf[0x288d] not copied! Expected de, got 32
[   68.821599] dmatest: dma0chan10-copy: dstbuf[0x288e] not copied! Expected dd, got 31
[   68.821605] dmatest: dma0chan10-copy: dstbuf[0x288f] not copied! Expected dc, got 30
[   68.821612] dmatest: dma0chan10-copy: dstbuf[0x2890] not copied! Expected db, got 2f
[   68.821619] dmatest: dma0chan10-copy: dstbuf[0x2891] not copied! Expected da, got 2e
[   68.821625] dmatest: dma0chan10-copy: dstbuf[0x2892] not copied! Expected d9, got 2d
[   68.821632] dmatest: dma0chan10-copy: dstbuf[0x2893] not copied! Expected d8, got 2c
[   68.821638] dmatest: dma0chan10-copy: dstbuf[0x2894] not copied! Expected d7, got 2b
[   68.821645] dmatest: dma0chan10-copy: dstbuf[0x2895] not copied! Expected d6, got 2a
[   68.821652] dmatest: dma0chan10-copy: dstbuf[0x2896] not copied! Expected d5, got 29
[   68.821658] dmatest: dma0chan10-copy: dstbuf[0x2897] not copied! Expected d4, got 28
[   68.821689] dmatest: dma0chan10-copy: 5791 errors suppressed
[   68.821697] dmatest: dma0chan10-copy: result #2: 'data error' with src_off=0x274c dst_off=0x2878 len=0x16bf (5823)
[   68.821712] dmatest: dma0chan10-copy: summary 2 tests, 2 failures 2047 iops 8188 KB/s (0)
[   69.365033] dmatest: Started 1 threads using dma0chan11
[   69.370538] dmatest: dma0chan11-copy: summary 2 tests, 0 failures 1146 iops 9169 KB/s (0)
[   69.378363] dmatest: Started 1 threads using dma1chan17
[   69.383455] dmatest: dma1chan17-copy: summary 2 tests, 0 failures 396 iops 4754 KB/s (0)
[   69.391512] dmatest: Started 1 threads using dma1chan7
[   69.392997] dmatest: dma1chan7-copy0: summary 2 tests, 0 failures 1389 iops 17373 KB/s (0)
[   69.405052] dmatest: Started 1 threads using dma1chan8
[   69.405903] dmatest: dma1chan8-copy0: summary 2 tests, 0 failures 2481 iops 14888 KB/s (0)
[   69.418350] dmatest: Started 1 threads using dma1chan9
[   69.419984] dmatest: dma1chan9-copy0: summary 2 tests, 0 failures 1259 iops 10075 KB/s (0)
[   69.431711] dmatest: Started 1 threads using dma2chan0
[   69.433114] dmatest: dma2chan0-copy0: summary 2 tests, 0 failures 1474 iops 13274 KB/s (0)
[   69.445069] dmatest: Started 1 threads using dma2chan1
[   69.446481] dmatest: dma2chan1-copy0: summary 2 tests, 0 failures 1464 iops 5124 KB/s (0)
[   69.458341] dmatest: Started 1 threads using dma2chan10
[   69.460484] dmatest: dma2chan10-copy: summary 2 tests, 0 failures 953 iops 4768 KB/s (0)
[   69.471613] dmatest: Started 1 threads using dma2chan11
[   69.473915] dmatest: dma2chan11-copy: summary 2 tests, 0 failures 886 iops 7092 KB/s (0)
[   69.484888] dmatest: Started 1 threads using dma2chan12
[   69.489277] dmatest: dma2chan12-copy: summary 2 tests, 0 failures 460 iops 4605 KB/s (0)
[   69.498158] dmatest: Started 1 threads using dma2chan13
[   69.501608] dmatest: dma2chan13-copy: summary 2 tests, 0 failures 587 iops 3820 KB/s (0)
[   69.511434] dmatest: Started 1 threads using dma2chan14
[   69.512411] dmatest: dma2chan14-copy: summary 2 tests, 0 failures 2150 iops 19354 KB/s (0)
[   69.524881] dmatest: Started 1 threads using dma2chan15
[   69.525701] dmatest: dma2chan15-copy: summary 2 tests, 0 failures 2583 iops 10335 KB/s (0)
[   69.538325] dmatest: Started 1 threads using dma2chan16
[   69.539158] dmatest: dma2chan16-copy: summary 2 tests, 0 failures 2538 iops 2538 KB/s (0)
[   69.551685] dmatest: Started 1 threads using dma2chan17
[   69.552621] dmatest: dma2chan17-copy: summary 2 tests, 0 failures 2244 iops 6734 KB/s (0)
[   69.565043] dmatest: Started 1 threads using dma2chan18
[   69.566242] dmatest: dma2chan18-copy: summary 2 tests, 0 failures 1736 iops 18229 KB/s (0)
[   69.578491] dmatest: Started 1 threads using dma2chan19
[   69.583024] dmatest: dma2chan19-copy: summary 2 tests, 0 failures 445 iops 4009 KB/s (0)
[   69.591762] dmatest: Started 1 threads using dma2chan2
[   69.593431] dmatest: dma2chan2-copy0: summary 2 tests, 0 failures 1233 iops 9253 KB/s (0)
[   69.605037] dmatest: Started 1 threads using dma2chan20
[   69.609930] dmatest: dma2chan20-copy: summary 2 tests, 0 failures 412 iops 3508 KB/s (0)
[   69.618307] dmatest: Started 1 threads using dma2chan21
[   69.619503] dmatest: dma2chan21-copy: summary 2 tests, 0 failures 1736 iops 15625 KB/s (0)
[   69.631753] dmatest: Started 1 threads using dma2chan22
[   69.632714] dmatest: dma2chan22-copy: summary 2 tests, 0 failures 2166 iops 7583 KB/s (0)
[   69.645118] dmatest: Started 1 threads using dma2chan23
[   69.648877] dmatest: dma2chan23-copy: summary 2 tests, 0 failures 538 iops 6197 KB/s (0)
[   69.658384] dmatest: Started 1 threads using dma2chan24
[   69.663247] dmatest: dma2chan24-copy: summary 2 tests, 0 failures 415 iops 3531 KB/s (0)
[   69.671663] dmatest: Started 1 threads using dma2chan25
[   69.674798] dmatest: dma2chan25-copy: summary 2 tests, 0 failures 647 iops 6476 KB/s (0)
[   69.684935] dmatest: Started 1 threads using dma2chan26
[   69.685713] dmatest: dma2chan26-copy: summary 2 tests, 0 failures 2728 iops 1364 KB/s (0)
[   69.698294] dmatest: Started 1 threads using dma2chan27
[   69.700545] dmatest: dma2chan27-copy: summary 2 tests, 0 failures 907 iops 9981 KB/s (0)
[   69.711565] dmatest: Started 1 threads using dma2chan28
[   69.713510] dmatest: dma2chan28-copy: summary 2 tests, 0 failures 1047 iops 7333 KB/s (0)
[   69.724927] dmatest: Started 1 threads using dma2chan29
[   69.727278] dmatest: dma2chan29-copy: summary 2 tests, 0 failures 867 iops 7809 KB/s (0)
[   69.738191] dmatest: Started 1 threads using dma2chan3
[   69.739853] dmatest: dma2chan3-copy0: summary 2 tests, 0 failures 1239 iops 13019 KB/s (0)
[   69.751559] dmatest: Started 1 threads using dma2chan30
[   69.755905] dmatest: dma2chan30-copy: summary 2 tests, 0 failures 465 iops 3255 KB/s (0)
[   69.764832] dmatest: Started 1 threads using dma2chan31
[   69.766147] dmatest: dma2chan31-copy: summary 2 tests, 0 failures 1576 iops 12608 KB/s (0)
[   69.778275] dmatest: Started 1 threads using dma2chan4
[   69.779854] dmatest: dma2chan4-copy0: summary 2 tests, 0 failures 1305 iops 16971 KB/s (0)
[   69.791634] dmatest: Started 1 threads using dma2chan5
[   69.792449] dmatest: dma2chan5-copy0: summary 2 tests, 0 failures 2604 iops 11718 KB/s (0)
[   69.804993] dmatest: Started 1 threads using dma2chan6
[   69.805931] dmatest: dma2chan6-copy0: summary 2 tests, 0 failures 2244 iops 4489 KB/s (0)
[   69.818268] dmatest: Started 1 threads using dma2chan7
[   69.822196] dmatest: dma2chan7-copy0: summary 2 tests, 0 failures 514 iops 6179 KB/s (0)
[   69.831452] dmatest: Started 1 threads using dma2chan8
[   69.832348] dmatest: dma2chan8-copy0: summary 2 tests, 0 failures 2347 iops 3521 KB/s (0)
[   69.844726] dmatest: Started 1 threads using dma2chan9
[   69.846064] dmatest: dma2chan9-copy0: summary 2 tests, 0 failures 1546 iops 14694 KB/s (0)
[   69.858085] dmatest: Started 1 threads using dma3chan0
[   69.858880] dmatest: dma3chan0-copy0: summary 2 tests, 0 failures 2670 iops 22696 KB/s (0)
[   69.871443] dmatest: Started 1 threads using dma3chan1
[   69.872190] dmatest: dma3chan1-copy0: summary 2 tests, 0 failures 2849 iops 28490 KB/s (0)
[   69.884803] dmatest: Started 1 threads using dma3chan2
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
bash: echo: write error: Device or resource busy
# [   71.883635] dmatest: dma3chan2-copy0: result #1: 'test timed out' with src_off=0xda3 dst_off=0x740 len=0x2a62 (0)
[   73.888635] dmatest: dma3chan2-copy0: result #2: 'test timed out' with src_off=0xb56 dst_off=0xd5e len=0x2f37 (0)
[   73.897442] dmatest: dma3chan2-copy0: summary 2 tests, 2 failures 0 iops 5 KB/s (0)

Re: Peach Pi/Pit boot failures in linux-next (was Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init)

[Javier Martinez Canillas]

On 11/24/2014 10:38 AM, Javier Martinez Canillas wrote:
> Hell Krzysztof

An unfortunate typo, this was "Hello" of course :-)

Best regards,
Javier

Re: Peach Pi/Pit boot failures in linux-next (was Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init)

[Krzysztof Kozlowski]

On pią, 2014-11-21 at 21:49 +0100, Javier Martinez Canillas wrote:
> Hello Kevin,
> 
> On 11/21/2014 05:38 PM, Kevin Hilman wrote:
> >> So, I see two different boot failures on the Peach Pi[t] Chromebooks:
> >>
> >> 1) next20141121 boot fails due snd-soc-snow
> >>
> >> Disabling CONFIG_SND_SOC_SNOW makes the boot to got a little further
> >> but still fails with the second issue:
> >>
> >> 2) next20141121 boot hangs if unused clocks are disabled.
> >>
> >> I tried to root cause these two issues but didn't see anything evident
> >> so I'll find a last known good commit and bisect. If anyone has an
> >> idea of the possible causes for these issues that would be appreciated.
> > 
> > FWIW, in addition to the failures on 5800/peach-pi, I'm also seeing boot
> > failures in next-20141121 on the exynos5420-arndale-octa[1].  Adding
> > clk_ignore_unused gets things booting there as well.
> > 
> > What's interesting is that my exynos5422-odroid-xu3 is booting fine as
> > well as the exynos5420-arndale and the exynos5410-odroid-xu (shown as
> > exynos5410-smdk5410)
> > 
> > Whatever the issue, it definietly seems like a problem that was came
> > through a driver/subsystem tree because that these boards are all
> > booting fine with Kukjin's for-next, arm-soc/for-next and
> > mainline/v3.18-rc5 (all with just plain exynos_defconfig, and without
> > clk_ignore_unused.)  For example, just looking at peach-pi across all
> > these trees[2], you can see that it's only failing in linux-next.
> >
> 
> By bisecting I found that the commit introducing both regressions is:
> 
> ae43b32 ("ARM: 8202/1: dmaengine: pl330: Add runtime Power Management support v12")
> 
> By reverting ae43b32, next-20141121 boots with both CONFIG_SND_SOC_SNOW=y
> and *without* clk_ignore_unused.
> 
> Krzysztof,
> 
> I see you are the author of the patch, maybe you can take a look why this
> is causing regressions in some Exynos boards?
> 

OK, I got some ideas (no need to run tests mentioned in my previous
email). Apparently the mout_audss clock (or one of its parents up to
EPLL clock) must be enabled. Configuration like this works:
$ cat /sys/kernel/debug/clk/clk_summary
    fout_epll                             1            1   100000000          0 0
       mout_sclk_epll                     1            1   100000000          0 0
          mout_mau_epll_clk               1            1   100000000          0 0
             mau_epll                     1            1   100000000          0 0
                mout_audss                1            2   100000000          0 0
                   dout_srp               0            1   100000000          0 0
                      adma                0            1   100000000          0 0
                      srp_clk             0            0   100000000          0 0
                      dout_aud_bus           0            0   100000000          0 0
                         i2s_bus           0            0   100000000          0 0
                   mout_i2s               0            0   100000000          0 0
                      dout_i2s            0            0   100000000          0 0
                         sclk_i2s           0            0   100000000          0 0


Reverting my patch enables the adma clock which effectively enables mout_audss.

Now I have to find the answer which driver uses epll/audss without enabling it explicitly...

Best regards,
Krzysztof

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Javier Martinez Canillas]

Hello Ajay,

On 11/21/2014 09:57 PM, Javier Martinez Canillas wrote:
> On 11/21/2014 06:32 PM, Ajay kumar wrote:
>> Hi,
>> 
>> I have rebased my bridge series on top of linux-next.
>> 
>> This is my git log:
>> 4b38a6f Revert "Revert "ARM: exynos_defconfig: Enable options for
>> display panel support""
>> 6fb39a7 ARM: dts: peach-pit: represent the connection between bridge
>> and panel using videoport and endpoints
>> aee649c ARM: dts: snow: represent the connection between bridge and
>> panel using videoport and endpoints
>> 5b76d8d drm/bridge: Add i2c based driver for ps8622/ps8625 bridge
>> 581257f Documentation: bridge: Add documentation for ps8622 DT properties
>> 178e8b9 Documentation: devicetree: Add vendor prefix for parade
>> 0ceea75 Documentation: drm: bridge: move to video/bridge
>> f143e2e drm/bridge: ptn3460: use gpiod interface
>> 2d5cb9d drm/bridge: ptn3460: probe connector at the end of bridge attach
>> 32ac563 drm/bridge: ptn3460: support drm_panel
>> 91c6c30 drm/exynos: dp: support drm_bridge
>> 7eea7eb drm/bridge: ptn3460: Convert to i2c driver model
>> 602f343 drm/bridge: make bridge registration independent of drm flow
>> 14c7143 drm/bridge: do not pass drm_bridge_funcs to drm_bridge_init
>> 2c01ac4 drm/bridge: ptn3460: Few trivial cleanups
>> 7415f6c arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
>> 28655d1 drm/exynos: Move platform drivers registration to module init
>> ed6778a Add linux-next specific files for 20141121
>> 
>> I have attached the rebased patches as well.
>> I tested it on snow, peach_pit and peach_pi without *clk_ignore_unused*.
>> Display is totally fine with exynos_defconfig (booting is fine even
>> with CONFIG_SND_SOC_SNOW=y)
>> 
> 
> Thanks for forward porting your patches to linux-next. Unfortunately I
> won't have time to test them until Monday but I wonder why you didn't
> have the boot issues that we have with next-20141121.
>

I tested your ToT patches on top of next-20141121, this is my git log:

93fe3d7 Revert "Revert "ARM: exynos_defconfig: Enable options for display panel support""
552f74e ARM: dts: peach-pit: represent the connection between bridge and panel using videoport and endpoints
dbbc293 ARM: dts: snow: represent the connection between bridge and panel using videoport and endpoints
d8687f8 drm/bridge: Add i2c based driver for ps8622/ps8625 bridge
f29a649 Documentation: bridge: Add documentation for ps8622 DT properties
6ade887 Documentation: devicetree: Add vendor prefix for parade
d81c42d Documentation: drm: bridge: move to video/bridge
50b9828 drm/bridge: ptn3460: use gpiod interface
1274c56 drm/bridge: ptn3460: probe connector at the end of bridge attach
f3cf063 drm/bridge: ptn3460: support drm_panel
cab682b drm/exynos: dp: support drm_bridge
6e78916 drm/bridge: ptn3460: Convert to i2c driver model
93f4b5f drm/bridge: make bridge registration independent of drm flow
81a038f drm/bridge: do not pass drm_bridge_funcs to drm_bridge_init
eb6996e drm/bridge: ptn3460: Few trivial cleanups
c41fa5d arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
51b2c75 drm/exynos: Move platform drivers registration to module init
ed6778a Add linux-next specific files for 20141121
 
> I found that the commit ae43b32 ("ARM: 8202/1: dmaengine: pl330: Add
> runtime Power Management support v12") had to be reverted in order to
> boot linux-next.
>

Display works but I needed to revert the mentioned commit, otherwise
the boot hangs as reported before. I'm using exynos_defconfig and this
kernel command line:

console=ttySAC3,115200N8 debug earlyprintk root=/dev/mmcblk1p2 rootwait rw

Best regards,
Javier

Re: Peach Pi/Pit boot failures in linux-next (was Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init)

[Krzysztof Kozlowski]

On pon, 2014-11-24 at 10:38 +0100, Javier Martinez Canillas wrote:
> Hell Krzysztof,
> 
> On 11/22/2014 11:21 AM, Krzysztof Kozlowski wrote:
> >>
> >> By bisecting I found that the commit introducing both regressions is:
> >>
> >> ae43b32 ("ARM: 8202/1: dmaengine: pl330: Add runtime Power Management support v12")
> >>
> >> By reverting ae43b32, next-20141121 boots with both CONFIG_SND_SOC_SNOW=y
> >> and *without* clk_ignore_unused.
> >>
> >> Krzysztof,
> >>
> >> I see you are the author of the patch, maybe you can take a look why this
> >> is causing regressions in some Exynos boards?
> > 
> > Oh crap... I'll look at it on Monday. However I don't have Peach Pi so any 
> > information would be useful. Can you post dmesg and your config? (is it 
> > exynos_defconfig?)
> >
> 
> Yes, I'm using exynos_defconfig. I'm testing with latest linux-next, HEAD:
> 
> commit ed6778a ("Add linux-next specific files for 20141121")
> 
> The boot log of the hang in the Exynos5420 Peach Pit is sent as an
> attachment. CONFIG_SND_SOC_SNOW was enabled and without clk_ignore_unused.
> 
> > Additionally can you boot the board with DMATEST enabled (without reverting 
> > my commit so probably with clk_ignore_unsed and with SND_SNOW disabled) and 
> > run dmatest on all channels? Something like:
> >    echo 2000 > /sys/module/dmatest/parameters/timeout
> >    echo 2 > /sys/module/dmatest/parameters/iterations
> >    for i in `ls /sys/class/dma/`
> >    do
> >      echo $i > /sys/module/dmatest/parameters/channel
> >      echo 1 > /sys/module/dmatest/parameters/run
> >    done
> > 
> > ... and post these results also.
> >
> 
> I'm attaching the log of the tests as well. To run the test
> CONFIG_SND_SOC_SNOW was disabled and booted with clk_ignore_unused.
>  
> > I will test it on Arndale Octa, maybe the cause is the same. Unfortunately 
> > it seems Arndale Octa does not have any sound enabled in DTS so it may be 
> > hard to test I2S bus (which is used by audio).
> >
> 
> Ok, please let me know if you need anything else from me.

Thanks! I replied before seeing your response. Anyway the dmatests are
the same I got on Arndale Octa.

It seems that mau_epll has to be enabled... or something is wrong with
clock hierarchy.

Best regards,
Krzysztof

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Vivek Gautam]

[-- Attachment #1: Type: text/plain, Size: 4908 bytes --]

Hi Javier,


On Mon, Nov 24, 2014 at 3:35 PM, Javier Martinez Canillas
<javier.martinez@collabora.co.uk> wrote:
> Hello Ajay,
>
> On 11/21/2014 09:57 PM, Javier Martinez Canillas wrote:
>> On 11/21/2014 06:32 PM, Ajay kumar wrote:
>>> Hi,
>>>
>>> I have rebased my bridge series on top of linux-next.
>>>
>>> This is my git log:
>>> 4b38a6f Revert "Revert "ARM: exynos_defconfig: Enable options for
>>> display panel support""
>>> 6fb39a7 ARM: dts: peach-pit: represent the connection between bridge
>>> and panel using videoport and endpoints
>>> aee649c ARM: dts: snow: represent the connection between bridge and
>>> panel using videoport and endpoints
>>> 5b76d8d drm/bridge: Add i2c based driver for ps8622/ps8625 bridge
>>> 581257f Documentation: bridge: Add documentation for ps8622 DT properties
>>> 178e8b9 Documentation: devicetree: Add vendor prefix for parade
>>> 0ceea75 Documentation: drm: bridge: move to video/bridge
>>> f143e2e drm/bridge: ptn3460: use gpiod interface
>>> 2d5cb9d drm/bridge: ptn3460: probe connector at the end of bridge attach
>>> 32ac563 drm/bridge: ptn3460: support drm_panel
>>> 91c6c30 drm/exynos: dp: support drm_bridge
>>> 7eea7eb drm/bridge: ptn3460: Convert to i2c driver model
>>> 602f343 drm/bridge: make bridge registration independent of drm flow
>>> 14c7143 drm/bridge: do not pass drm_bridge_funcs to drm_bridge_init
>>> 2c01ac4 drm/bridge: ptn3460: Few trivial cleanups
>>> 7415f6c arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
>>> 28655d1 drm/exynos: Move platform drivers registration to module init
>>> ed6778a Add linux-next specific files for 20141121
>>>
>>> I have attached the rebased patches as well.
>>> I tested it on snow, peach_pit and peach_pi without *clk_ignore_unused*.
>>> Display is totally fine with exynos_defconfig (booting is fine even
>>> with CONFIG_SND_SOC_SNOW=y)
>>>
>>
>> Thanks for forward porting your patches to linux-next. Unfortunately I
>> won't have time to test them until Monday but I wonder why you didn't
>> have the boot issues that we have with next-20141121.
>>
>
> I tested your ToT patches on top of next-20141121, this is my git log:
>
> 93fe3d7 Revert "Revert "ARM: exynos_defconfig: Enable options for display panel support""
> 552f74e ARM: dts: peach-pit: represent the connection between bridge and panel using videoport and endpoints
> dbbc293 ARM: dts: snow: represent the connection between bridge and panel using videoport and endpoints
> d8687f8 drm/bridge: Add i2c based driver for ps8622/ps8625 bridge
> f29a649 Documentation: bridge: Add documentation for ps8622 DT properties
> 6ade887 Documentation: devicetree: Add vendor prefix for parade
> d81c42d Documentation: drm: bridge: move to video/bridge
> 50b9828 drm/bridge: ptn3460: use gpiod interface
> 1274c56 drm/bridge: ptn3460: probe connector at the end of bridge attach
> f3cf063 drm/bridge: ptn3460: support drm_panel
> cab682b drm/exynos: dp: support drm_bridge
> 6e78916 drm/bridge: ptn3460: Convert to i2c driver model
> 93f4b5f drm/bridge: make bridge registration independent of drm flow
> 81a038f drm/bridge: do not pass drm_bridge_funcs to drm_bridge_init
> eb6996e drm/bridge: ptn3460: Few trivial cleanups
> c41fa5d arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
> 51b2c75 drm/exynos: Move platform drivers registration to module init
> ed6778a Add linux-next specific files for 20141121
>
>> I found that the commit ae43b32 ("ARM: 8202/1: dmaengine: pl330: Add
>> runtime Power Management support v12") had to be reverted in order to
>> boot linux-next.
>>
>
> Display works but I needed to revert the mentioned commit, otherwise
> the boot hangs as reported before. I'm using exynos_defconfig and this
> kernel command line:
>
> console=ttySAC3,115200N8 debug earlyprintk root=/dev/mmcblk1p2 rootwait rw

My git log --oneline gives following git hash
vivek@vivek-linuxpc:~/MAINLINE_KERNEL/linux-next$ git log --oneline

9af3770 arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
1558298 drm/exynos: Move platform drivers registration to module init
4df404f Revert "Revert "ARM: exynos_defconfig: Enable options for
display panel support""
ed6778a Add linux-next specific files for 20141121
eb052c1 Merge branch 'akpm/master'
9c46812 mm: add strictlimit knob

Also attached my config (which is just made out of exynos_defconfig) :
config_next20141124

The boot arguments used are:
[    0.000000] Kernel command line: root=/dev/mmcblk1p1 rootwait ro
console=ttySAC3,115200 debug earlyprintk init=/linuxrc

Also attached the complete log: kernel-log_next20141124.

I am still not sure how SND_SOC creates a problem for you. I did not
revert any patch (apart from the display config revert)
as seen in my git hash.

So with this setup, my peach-pi boots up fine, display comes up;
CONFIG_SND_SOC is still enabled.


-- 
Best Regards
Vivek Gautam
Samsung R&D Institute, Bangalore
India

[-- Attachment #2: config_next20141124 --]
[-- Type: application/octet-stream, Size: 81025 bytes --]

#
# Automatically generated file; DO NOT EDIT.
# Linux/arm 3.18.0-rc5 Kernel Configuration
#
CONFIG_ARM=y
CONFIG_ARM_HAS_SG_CHAIN=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_ARM_DMA_USE_IOMMU=y
CONFIG_ARM_DMA_IOMMU_ALIGNMENT=8
CONFIG_MIGHT_HAVE_PCI=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_HAVE_PROC_CPU=y
CONFIG_NO_IOPORT_MAP=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_BANDGAP=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_VECTORS_BASE=0xffff0000
CONFIG_ARM_PATCH_PHYS_VIRT=y
CONFIG_GENERIC_BUG=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y

#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
CONFIG_CROSS_MEMORY_ATTACH=y
# CONFIG_FHANDLE is not set
CONFIG_USELIB=y
# CONFIG_AUDIT is not set
CONFIG_HAVE_ARCH_AUDITSYSCALL=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_HARDIRQS_SW_RESEND=y
CONFIG_GENERIC_IRQ_CHIP=y
CONFIG_IRQ_DOMAIN=y
CONFIG_HANDLE_DOMAIN_IRQ=y
# CONFIG_IRQ_DOMAIN_DEBUG is not set
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_ARCH_HAS_TICK_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
CONFIG_NO_HZ_IDLE=y
# CONFIG_NO_HZ_FULL is not set
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y

#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
# CONFIG_IRQ_TIME_ACCOUNTING is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set

#
# RCU Subsystem
#
CONFIG_PREEMPT_RCU=y
# CONFIG_TASKS_RCU is not set
CONFIG_RCU_STALL_COMMON=y
# CONFIG_RCU_USER_QS is not set
CONFIG_RCU_FANOUT=32
CONFIG_RCU_FANOUT_LEAF=16
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_RCU_FAST_NO_HZ is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_RCU_BOOST is not set
# CONFIG_RCU_NOCB_CPU is not set
# CONFIG_BUILD_BIN2C is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_LOG_CPU_MAX_BUF_SHIFT=12
CONFIG_GENERIC_SCHED_CLOCK=y
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_CGROUP_FREEZER is not set
# CONFIG_CGROUP_DEVICE is not set
# CONFIG_CPUSETS is not set
# CONFIG_CGROUP_CPUACCT is not set
# CONFIG_MEMCG is not set
# CONFIG_CGROUP_SCHED is not set
# CONFIG_BLK_CGROUP is not set
# CONFIG_CHECKPOINT_RESTORE is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
CONFIG_PID_NS=y
CONFIG_NET_NS=y
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_SYSFS_DEPRECATED is not set
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_XZ=y
CONFIG_RD_LZO=y
CONFIG_RD_LZ4=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
CONFIG_HAVE_UID16=y
CONFIG_BPF=y
# CONFIG_EXPERT is not set
CONFIG_UID16=y
CONFIG_OBSOLETE_SYSCALLS=y
# CONFIG_SGETMASK_SYSCALL is not set
CONFIG_SYSFS_SYSCALL=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
# CONFIG_BPF_SYSCALL is not set
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_ADVISE_SYSCALLS=y
CONFIG_NTP=y
# CONFIG_EMBEDDED is not set
CONFIG_HAVE_PERF_EVENTS=y
CONFIG_PERF_USE_VMALLOC=y

#
# Kernel Performance Events And Counters
#
# CONFIG_PERF_EVENTS is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLUB_DEBUG=y
CONFIG_COMPAT_BRK=y
# CONFIG_SLAB is not set
CONFIG_SLUB=y
CONFIG_SLUB_CPU_PARTIAL=y
# CONFIG_PROFILING is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
# CONFIG_JUMP_LABEL is not set
# CONFIG_UPROBES is not set
# CONFIG_HAVE_64BIT_ALIGNED_ACCESS is not set
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_ARCH_USE_BUILTIN_BSWAP=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_HAVE_DMA_CONTIGUOUS=y
CONFIG_GENERIC_SMP_IDLE_THREAD=y
CONFIG_GENERIC_IDLE_POLL_SETUP=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_CLK=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_HAVE_PERF_REGS=y
CONFIG_HAVE_PERF_USER_STACK_DUMP=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y
CONFIG_ARCH_WANT_IPC_PARSE_VERSION=y
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_HAVE_CC_STACKPROTECTOR=y
# CONFIG_CC_STACKPROTECTOR is not set
CONFIG_CC_STACKPROTECTOR_NONE=y
# CONFIG_CC_STACKPROTECTOR_REGULAR is not set
# CONFIG_CC_STACKPROTECTOR_STRONG is not set
CONFIG_HAVE_CONTEXT_TRACKING=y
CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y
CONFIG_HAVE_MOD_ARCH_SPECIFIC=y
CONFIG_MODULES_USE_ELF_REL=y
CONFIG_CLONE_BACKWARDS=y
CONFIG_OLD_SIGSUSPEND3=y
CONFIG_OLD_SIGACTION=y

#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_MODULE_SIG is not set
# CONFIG_MODULE_COMPRESS is not set
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_LBDAF=y
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_BLK_DEV_BSGLIB is not set
# CONFIG_BLK_DEV_INTEGRITY is not set
# CONFIG_BLK_CMDLINE_PARSER is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_AIX_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
# CONFIG_CMDLINE_PARTITION is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_UNINLINE_SPIN_UNLOCK=y
CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y
CONFIG_RWSEM_SPIN_ON_OWNER=y
CONFIG_FREEZER=y

#
# System Type
#
CONFIG_MMU=y
CONFIG_ARCH_MULTIPLATFORM=y
# CONFIG_ARCH_REALVIEW is not set
# CONFIG_ARCH_VERSATILE is not set
# CONFIG_ARCH_AT91 is not set
# CONFIG_ARCH_CLPS711X is not set
# CONFIG_ARCH_GEMINI is not set
# CONFIG_ARCH_EBSA110 is not set
# CONFIG_ARCH_EP93XX is not set
# CONFIG_ARCH_FOOTBRIDGE is not set
# CONFIG_ARCH_NETX is not set
# CONFIG_ARCH_IOP13XX is not set
# CONFIG_ARCH_IOP32X is not set
# CONFIG_ARCH_IOP33X is not set
# CONFIG_ARCH_IXP4XX is not set
# CONFIG_ARCH_DOVE is not set
# CONFIG_ARCH_MV78XX0 is not set
# CONFIG_ARCH_ORION5X is not set
# CONFIG_ARCH_MMP is not set
# CONFIG_ARCH_KS8695 is not set
# CONFIG_ARCH_W90X900 is not set
# CONFIG_ARCH_LPC32XX is not set
# CONFIG_ARCH_PXA is not set
# CONFIG_ARCH_MSM is not set
# CONFIG_ARCH_SHMOBILE_LEGACY is not set
# CONFIG_ARCH_RPC is not set
# CONFIG_ARCH_SA1100 is not set
# CONFIG_ARCH_S3C24XX is not set
# CONFIG_ARCH_S3C64XX is not set
# CONFIG_ARCH_DAVINCI is not set
# CONFIG_ARCH_OMAP1 is not set

#
# Multiple platform selection
#

#
# CPU Core family selection
#
# CONFIG_ARCH_MULTI_V6 is not set
CONFIG_ARCH_MULTI_V7=y
CONFIG_ARCH_MULTI_V6_V7=y
# CONFIG_ARCH_MULTI_CPU_AUTO is not set
# CONFIG_ARCH_VIRT is not set
# CONFIG_ARCH_MVEBU is not set
# CONFIG_ARCH_BCM is not set
# CONFIG_ARCH_BERLIN is not set
# CONFIG_ARCH_HIGHBANK is not set
# CONFIG_ARCH_HISI is not set
# CONFIG_ARCH_KEYSTONE is not set
# CONFIG_ARCH_MESON is not set
# CONFIG_ARCH_MXC is not set
# CONFIG_ARCH_MEDIATEK is not set

#
# TI OMAP/AM/DM/DRA Family
#
# CONFIG_ARCH_OMAP3 is not set
# CONFIG_ARCH_OMAP4 is not set
# CONFIG_SOC_OMAP5 is not set
# CONFIG_SOC_AM33XX is not set
# CONFIG_SOC_AM43XX is not set
# CONFIG_SOC_DRA7XX is not set
# CONFIG_ARCH_QCOM is not set
# CONFIG_ARCH_ROCKCHIP is not set
# CONFIG_ARCH_SOCFPGA is not set
# CONFIG_PLAT_SPEAR is not set
# CONFIG_ARCH_STI is not set
# CONFIG_ARCH_S5PV210 is not set
CONFIG_ARCH_EXYNOS=y
CONFIG_ARCH_EXYNOS3=y
CONFIG_ARCH_EXYNOS4=y
CONFIG_ARCH_EXYNOS5=y

#
# EXYNOS SoCs
#
CONFIG_SOC_EXYNOS3250=y
CONFIG_CPU_EXYNOS4210=y
CONFIG_SOC_EXYNOS4212=y
CONFIG_SOC_EXYNOS4412=y
CONFIG_SOC_EXYNOS4415=y
CONFIG_SOC_EXYNOS5250=y
CONFIG_SOC_EXYNOS5260=y
CONFIG_SOC_EXYNOS5410=y
CONFIG_SOC_EXYNOS5420=y
CONFIG_SOC_EXYNOS5440=y
CONFIG_SOC_EXYNOS5800=y
CONFIG_EXYNOS5420_MCPM=y
CONFIG_EXYNOS_CPU_SUSPEND=y
CONFIG_PLAT_SAMSUNG=y

#
# Samsung Common options
#

#
# Boot options
#
CONFIG_S5P_DEV_MFC=y

#
# Power management
#
# CONFIG_SAMSUNG_PM_CHECK is not set
# CONFIG_ARCH_SHMOBILE_MULTI is not set
# CONFIG_ARCH_SUNXI is not set
# CONFIG_ARCH_SIRF is not set
# CONFIG_ARCH_TEGRA is not set
# CONFIG_ARCH_U8500 is not set
# CONFIG_ARCH_VEXPRESS is not set
# CONFIG_ARCH_WM8850 is not set
# CONFIG_ARCH_ZYNQ is not set

#
# Processor Type
#
CONFIG_CPU_V7=y
CONFIG_CPU_32v6K=y
CONFIG_CPU_32v7=y
CONFIG_CPU_ABRT_EV7=y
CONFIG_CPU_PABRT_V7=y
CONFIG_CPU_CACHE_V7=y
CONFIG_CPU_CACHE_VIPT=y
CONFIG_CPU_COPY_V6=y
CONFIG_CPU_TLB_V7=y
CONFIG_CPU_HAS_ASID=y
CONFIG_CPU_CP15=y
CONFIG_CPU_CP15_MMU=y

#
# Processor Features
#
# CONFIG_ARM_LPAE is not set
# CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set
CONFIG_ARM_THUMB=y
# CONFIG_ARM_THUMBEE is not set
CONFIG_ARM_VIRT_EXT=y
CONFIG_SWP_EMULATE=y
# CONFIG_CPU_ICACHE_DISABLE is not set
# CONFIG_CPU_DCACHE_DISABLE is not set
# CONFIG_CPU_BPREDICT_DISABLE is not set
CONFIG_KUSER_HELPERS=y
CONFIG_OUTER_CACHE=y
CONFIG_OUTER_CACHE_SYNC=y
CONFIG_MIGHT_HAVE_CACHE_L2X0=y
CONFIG_CACHE_L2X0=y
CONFIG_CACHE_PL310=y
# CONFIG_PL310_ERRATA_588369 is not set
# CONFIG_PL310_ERRATA_727915 is not set
# CONFIG_PL310_ERRATA_753970 is not set
# CONFIG_PL310_ERRATA_769419 is not set
CONFIG_ARM_L1_CACHE_SHIFT_6=y
CONFIG_ARM_L1_CACHE_SHIFT=6
CONFIG_ARM_DMA_MEM_BUFFERABLE=y
# CONFIG_ARM_KERNMEM_PERMS is not set
CONFIG_MULTI_IRQ_HANDLER=y
# CONFIG_ARM_ERRATA_430973 is not set
# CONFIG_ARM_ERRATA_643719 is not set
# CONFIG_ARM_ERRATA_720789 is not set
# CONFIG_ARM_ERRATA_754322 is not set
# CONFIG_ARM_ERRATA_754327 is not set
# CONFIG_ARM_ERRATA_764369 is not set
# CONFIG_ARM_ERRATA_775420 is not set
# CONFIG_ARM_ERRATA_798181 is not set
# CONFIG_ARM_ERRATA_773022 is not set

#
# Bus support
#
CONFIG_ARM_AMBA=y
# CONFIG_PCI is not set
# CONFIG_PCI_SYSCALL is not set
# CONFIG_PCCARD is not set

#
# Kernel Features
#
CONFIG_HAVE_SMP=y
CONFIG_SMP=y
CONFIG_SMP_ON_UP=y
CONFIG_ARM_CPU_TOPOLOGY=y
# CONFIG_SCHED_MC is not set
# CONFIG_SCHED_SMT is not set
CONFIG_HAVE_ARM_SCU=y
CONFIG_HAVE_ARM_ARCH_TIMER=y
CONFIG_MCPM=y
CONFIG_BIG_LITTLE=y
CONFIG_BL_SWITCHER=y
CONFIG_BL_SWITCHER_DUMMY_IF=y
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_NR_CPUS=8
CONFIG_HOTPLUG_CPU=y
# CONFIG_ARM_PSCI is not set
CONFIG_ARCH_NR_GPIO=512
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_COUNT=y
CONFIG_HZ_FIXED=200
CONFIG_HZ=200
CONFIG_SCHED_HRTICK=y
# CONFIG_THUMB2_KERNEL is not set
CONFIG_AEABI=y
# CONFIG_OABI_COMPAT is not set
CONFIG_ARCH_HAS_HOLES_MEMORYMODEL=y
# CONFIG_ARCH_SPARSEMEM_DEFAULT is not set
# CONFIG_ARCH_SELECT_MEMORY_MODEL is not set
CONFIG_HAVE_ARCH_PFN_VALID=y
CONFIG_HIGHMEM=y
# CONFIG_HIGHPTE is not set
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_HAVE_MEMBLOCK=y
CONFIG_NO_BOOTMEM=y
CONFIG_MEMORY_ISOLATION=y
# CONFIG_HAVE_BOOTMEM_INFO_NODE is not set
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_COMPACTION=y
CONFIG_MIGRATION=y
# CONFIG_PHYS_ADDR_T_64BIT is not set
CONFIG_ZONE_DMA_FLAG=0
CONFIG_BOUNCE=y
# CONFIG_KSM is not set
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
# CONFIG_CLEANCACHE is not set
# CONFIG_FRONTSWAP is not set
CONFIG_CMA=y
# CONFIG_CMA_DEBUG is not set
CONFIG_CMA_AREAS=7
# CONFIG_ZPOOL is not set
# CONFIG_ZBUD is not set
# CONFIG_ZSMALLOC is not set
CONFIG_FORCE_MAX_ZONEORDER=11
CONFIG_ALIGNMENT_TRAP=y
# CONFIG_UACCESS_WITH_MEMCPY is not set
# CONFIG_SECCOMP is not set
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
# CONFIG_XEN is not set

#
# Boot options
#
CONFIG_USE_OF=y
CONFIG_ATAGS=y
# CONFIG_DEPRECATED_PARAM_STRUCT is not set
CONFIG_ZBOOT_ROM_TEXT=0x0
CONFIG_ZBOOT_ROM_BSS=0x0
CONFIG_ARM_APPENDED_DTB=y
CONFIG_ARM_ATAG_DTB_COMPAT=y
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y
# CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND is not set
CONFIG_CMDLINE="root=/dev/ram0 rw ramdisk=8192 initrd=0x41000000,8M console=ttySAC1,115200 init=/linuxrc mem=256M"
CONFIG_CMDLINE_FROM_BOOTLOADER=y
# CONFIG_CMDLINE_EXTEND is not set
# CONFIG_CMDLINE_FORCE is not set
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_AUTO_ZRELADDR=y

#
# CPU Power Management
#

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# CPU Idle
#
# CONFIG_CPU_IDLE is not set
# CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED is not set

#
# Floating point emulation
#

#
# At least one emulation must be selected
#
CONFIG_VFP=y
CONFIG_VFPv3=y
CONFIG_NEON=y
# CONFIG_KERNEL_MODE_NEON is not set

#
# Userspace binary formats
#
CONFIG_BINFMT_ELF=y
CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
CONFIG_BINFMT_SCRIPT=y
# CONFIG_HAVE_AOUT is not set
# CONFIG_BINFMT_MISC is not set
CONFIG_COREDUMP=y

#
# Power management options
#
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
# CONFIG_HIBERNATION is not set
CONFIG_PM_SLEEP=y
CONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not set
CONFIG_PM_RUNTIME=y
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_APM_EMULATION is not set
CONFIG_PM_OPP=y
CONFIG_PM_CLK=y
CONFIG_PM_GENERIC_DOMAINS=y
# CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set
CONFIG_PM_GENERIC_DOMAINS_SLEEP=y
CONFIG_PM_GENERIC_DOMAINS_RUNTIME=y
CONFIG_PM_GENERIC_DOMAINS_OF=y
CONFIG_CPU_PM=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARM_CPU_SUSPEND=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_DIAG is not set
CONFIG_UNIX=y
# CONFIG_UNIX_DIAG is not set
CONFIG_XFRM=y
CONFIG_XFRM_ALGO=y
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
CONFIG_NET_KEY=y
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE_DEMUX is not set
CONFIG_NET_IP_TUNNEL=m
# CONFIG_SYN_COOKIES is not set
# CONFIG_NET_IPVTI is not set
# CONFIG_NET_UDP_TUNNEL is not set
# CONFIG_NET_FOU is not set
# CONFIG_NET_FOU_IP_TUNNELS is not set
# CONFIG_GENEVE is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
CONFIG_INET_LRO=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_INET_UDP_DIAG is not set
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
CONFIG_IPV6=m
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_MIP6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
CONFIG_INET6_XFRM_MODE_TRANSPORT=m
CONFIG_INET6_XFRM_MODE_TUNNEL=m
CONFIG_INET6_XFRM_MODE_BEET=m
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
# CONFIG_IPV6_VTI is not set
CONFIG_IPV6_SIT=m
# CONFIG_IPV6_SIT_6RD is not set
CONFIG_IPV6_NDISC_NODETYPE=y
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_IPV6_GRE is not set
# CONFIG_IPV6_MULTIPLE_TABLES is not set
# CONFIG_IPV6_MROUTE is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NET_PTP_CLASSIFY is not set
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_L2TP is not set
# CONFIG_BRIDGE is not set
CONFIG_HAVE_NET_DSA=y
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_PHONET is not set
# CONFIG_6LOWPAN is not set
# CONFIG_IEEE802154 is not set
# CONFIG_NET_SCHED is not set
# CONFIG_DCB is not set
# CONFIG_BATMAN_ADV is not set
# CONFIG_OPENVSWITCH is not set
# CONFIG_VSOCKETS is not set
# CONFIG_NETLINK_MMAP is not set
# CONFIG_NETLINK_DIAG is not set
# CONFIG_NET_MPLS_GSO is not set
# CONFIG_HSR is not set
CONFIG_RPS=y
CONFIG_RFS_ACCEL=y
CONFIG_XPS=y
# CONFIG_CGROUP_NET_PRIO is not set
# CONFIG_CGROUP_NET_CLASSID is not set
CONFIG_NET_RX_BUSY_POLL=y
CONFIG_BQL=y
# CONFIG_BPF_JIT is not set
CONFIG_NET_FLOW_LIMIT=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
CONFIG_WIRELESS=y
# CONFIG_CFG80211 is not set
# CONFIG_LIB80211 is not set

#
# CFG80211 needs to be enabled for MAC80211
#
# CONFIG_WIMAX is not set
# CONFIG_RFKILL is not set
CONFIG_RFKILL_REGULATOR=y
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set
# CONFIG_CEPH_LIB is not set
# CONFIG_NFC is not set
CONFIG_HAVE_BPF_JIT=y

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER=y
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_FW_LOADER_USER_HELPER_FALLBACK is not set
CONFIG_ALLOW_DEV_COREDUMP=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_GENERIC_CPU_DEVICES is not set
CONFIG_REGMAP=y
CONFIG_REGMAP_I2C=y
CONFIG_REGMAP_SPI=y
CONFIG_REGMAP_MMIO=y
CONFIG_REGMAP_IRQ=y
CONFIG_DMA_SHARED_BUFFER=y
# CONFIG_FENCE_TRACE is not set
CONFIG_DMA_CMA=y

#
# Default contiguous memory area size:
#
CONFIG_CMA_SIZE_MBYTES=64
CONFIG_CMA_SIZE_SEL_MBYTES=y
# CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set
# CONFIG_CMA_SIZE_SEL_MIN is not set
# CONFIG_CMA_SIZE_SEL_MAX is not set
CONFIG_CMA_ALIGNMENT=8

#
# Bus devices
#
# CONFIG_BRCMSTB_GISB_ARB is not set
CONFIG_ARM_CCI=y
# CONFIG_VEXPRESS_CONFIG is not set
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
CONFIG_DTC=y
CONFIG_OF=y

#
# Device Tree and Open Firmware support
#
# CONFIG_OF_UNITTEST is not set
CONFIG_OF_FLATTREE=y
CONFIG_OF_EARLY_FLATTREE=y
CONFIG_OF_ADDRESS=y
CONFIG_OF_IRQ=y
CONFIG_OF_NET=y
CONFIG_OF_MDIO=y
CONFIG_OF_RESERVED_MEM=y
CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_NULL_BLK is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
CONFIG_BLK_DEV_CRYPTOLOOP=y
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=8192
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_MG_DISK is not set
# CONFIG_BLK_DEV_RBD is not set

#
# Misc devices
#
# CONFIG_SENSORS_LIS3LV02D is not set
# CONFIG_AD525X_DPOT is not set
# CONFIG_DUMMY_IRQ is not set
# CONFIG_ICS932S401 is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_APDS9802ALS is not set
# CONFIG_ISL29003 is not set
# CONFIG_ISL29020 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_SENSORS_BH1780 is not set
# CONFIG_SENSORS_BH1770 is not set
# CONFIG_SENSORS_APDS990X is not set
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not set
# CONFIG_TI_DAC7512 is not set
# CONFIG_BMP085_I2C is not set
# CONFIG_BMP085_SPI is not set
# CONFIG_USB_SWITCH_FSA9480 is not set
# CONFIG_LATTICE_ECP3_CONFIG is not set
CONFIG_SRAM=y
# CONFIG_C2PORT is not set

#
# EEPROM support
#
# CONFIG_EEPROM_AT24 is not set
# CONFIG_EEPROM_AT25 is not set
# CONFIG_EEPROM_LEGACY is not set
# CONFIG_EEPROM_MAX6875 is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_EEPROM_93XX46 is not set

#
# Texas Instruments shared transport line discipline
#
# CONFIG_TI_ST is not set
# CONFIG_SENSORS_LIS3_SPI is not set
# CONFIG_SENSORS_LIS3_I2C is not set

#
# Altera FPGA firmware download module
#
# CONFIG_ALTERA_STAPL is not set

#
# Intel MIC Bus Driver
#

#
# Intel MIC Host Driver
#

#
# Intel MIC Card Driver
#
# CONFIG_ECHO is not set
# CONFIG_CXL_BASE is not set

#
# SCSI device support
#
CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_NETLINK is not set
# CONFIG_SCSI_MQ_DEFAULT is not set
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set

#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_ISCSI_BOOT_SYSFS is not set
# CONFIG_SCSI_UFSHCD is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_DH is not set
# CONFIG_SCSI_OSD_INITIATOR is not set
# CONFIG_ATA is not set
CONFIG_MD=y
# CONFIG_BLK_DEV_MD is not set
# CONFIG_BCACHE is not set
CONFIG_BLK_DEV_DM_BUILTIN=y
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=m
# CONFIG_DM_SNAPSHOT is not set
# CONFIG_DM_THIN_PROVISIONING is not set
# CONFIG_DM_CACHE is not set
# CONFIG_DM_ERA is not set
# CONFIG_DM_MIRROR is not set
# CONFIG_DM_RAID is not set
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set
# CONFIG_DM_UEVENT is not set
# CONFIG_DM_FLAKEY is not set
# CONFIG_DM_VERITY is not set
# CONFIG_DM_SWITCH is not set
# CONFIG_TARGET_CORE is not set
CONFIG_NETDEVICES=y
CONFIG_MII=y
CONFIG_NET_CORE=y
# CONFIG_BONDING is not set
# CONFIG_DUMMY is not set
# CONFIG_EQUALIZER is not set
# CONFIG_NET_TEAM is not set
# CONFIG_MACVLAN is not set
# CONFIG_VXLAN is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_NLMON is not set

#
# CAIF transport drivers
#

#
# Distributed Switch Architecture drivers
#
# CONFIG_NET_DSA_MV88E6XXX is not set
# CONFIG_NET_DSA_MV88E6060 is not set
# CONFIG_NET_DSA_MV88E6XXX_NEED_PPU is not set
# CONFIG_NET_DSA_MV88E6131 is not set
# CONFIG_NET_DSA_MV88E6123_61_65 is not set
# CONFIG_NET_DSA_MV88E6171 is not set
# CONFIG_NET_DSA_MV88E6352 is not set
# CONFIG_NET_DSA_BCM_SF2 is not set
CONFIG_ETHERNET=y
# CONFIG_ALTERA_TSE is not set
# CONFIG_NET_XGENE is not set
CONFIG_NET_VENDOR_ARC=y
# CONFIG_ARC_EMAC is not set
# CONFIG_EMAC_ROCKCHIP is not set
CONFIG_NET_CADENCE=y
CONFIG_NET_VENDOR_BROADCOM=y
# CONFIG_B44 is not set
# CONFIG_BCMGENET is not set
# CONFIG_SYSTEMPORT is not set
CONFIG_NET_VENDOR_CIRRUS=y
# CONFIG_CS89x0 is not set
# CONFIG_DM9000 is not set
# CONFIG_DNET is not set
CONFIG_NET_VENDOR_FARADAY=y
# CONFIG_FTMAC100 is not set
# CONFIG_FTGMAC100 is not set
CONFIG_NET_VENDOR_HISILICON=y
# CONFIG_HIX5HD2_GMAC is not set
CONFIG_NET_VENDOR_INTEL=y
CONFIG_NET_VENDOR_I825XX=y
CONFIG_NET_VENDOR_MARVELL=y
# CONFIG_MVMDIO is not set
CONFIG_NET_VENDOR_MICREL=y
# CONFIG_KS8842 is not set
# CONFIG_KS8851 is not set
# CONFIG_KS8851_MLL is not set
CONFIG_NET_VENDOR_MICROCHIP=y
# CONFIG_ENC28J60 is not set
CONFIG_NET_VENDOR_NATSEMI=y
CONFIG_NET_VENDOR_8390=y
# CONFIG_AX88796 is not set
# CONFIG_ETHOC is not set
CONFIG_NET_VENDOR_QUALCOMM=y
# CONFIG_QCA7000 is not set
CONFIG_NET_VENDOR_SAMSUNG=y
# CONFIG_SXGBE_ETH is not set
CONFIG_NET_VENDOR_SEEQ=y
CONFIG_NET_VENDOR_SMSC=y
# CONFIG_SMC91X is not set
# CONFIG_SMC911X is not set
CONFIG_SMSC911X=y
# CONFIG_SMSC911X_ARCH_HOOKS is not set
CONFIG_NET_VENDOR_STMICRO=y
# CONFIG_STMMAC_ETH is not set
CONFIG_NET_VENDOR_VIA=y
# CONFIG_VIA_RHINE is not set
# CONFIG_VIA_VELOCITY is not set
CONFIG_NET_VENDOR_WIZNET=y
# CONFIG_WIZNET_W5100 is not set
# CONFIG_WIZNET_W5300 is not set
CONFIG_PHYLIB=y

#
# MII PHY device drivers
#
# CONFIG_AT803X_PHY is not set
# CONFIG_AMD_PHY is not set
# CONFIG_AMD_XGBE_PHY is not set
# CONFIG_MARVELL_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_QSEMI_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_SMSC_PHY is not set
# CONFIG_BROADCOM_PHY is not set
# CONFIG_BCM7XXX_PHY is not set
# CONFIG_BCM87XX_PHY is not set
# CONFIG_ICPLUS_PHY is not set
# CONFIG_REALTEK_PHY is not set
# CONFIG_NATIONAL_PHY is not set
# CONFIG_STE10XP is not set
# CONFIG_LSI_ET1011C_PHY is not set
# CONFIG_MICREL_PHY is not set
# CONFIG_FIXED_PHY is not set
# CONFIG_MDIO_BITBANG is not set
# CONFIG_MDIO_BUS_MUX_GPIO is not set
# CONFIG_MDIO_BUS_MUX_MMIOREG is not set
# CONFIG_MDIO_BCM_UNIMAC is not set
# CONFIG_MICREL_KS8995MA is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
CONFIG_USB_NET_DRIVERS=y
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_RTL8152 is not set
CONFIG_USB_USBNET=y
CONFIG_USB_NET_AX8817X=y
CONFIG_USB_NET_AX88179_178A=y
CONFIG_USB_NET_CDCETHER=y
# CONFIG_USB_NET_CDC_EEM is not set
CONFIG_USB_NET_CDC_NCM=y
# CONFIG_USB_NET_HUAWEI_CDC_NCM is not set
# CONFIG_USB_NET_CDC_MBIM is not set
# CONFIG_USB_NET_DM9601 is not set
# CONFIG_USB_NET_SR9700 is not set
# CONFIG_USB_NET_SR9800 is not set
CONFIG_USB_NET_SMSC75XX=y
CONFIG_USB_NET_SMSC95XX=y
# CONFIG_USB_NET_GL620A is not set
CONFIG_USB_NET_NET1080=y
# CONFIG_USB_NET_PLUSB is not set
# CONFIG_USB_NET_MCS7830 is not set
# CONFIG_USB_NET_RNDIS_HOST is not set
CONFIG_USB_NET_CDC_SUBSET=y
# CONFIG_USB_ALI_M5632 is not set
# CONFIG_USB_AN2720 is not set
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
# CONFIG_USB_EPSON2888 is not set
# CONFIG_USB_KC2190 is not set
CONFIG_USB_NET_ZAURUS=y
# CONFIG_USB_NET_CX82310_ETH is not set
# CONFIG_USB_NET_KALMIA is not set
# CONFIG_USB_NET_QMI_WWAN is not set
# CONFIG_USB_NET_INT51X1 is not set
# CONFIG_USB_IPHETH is not set
# CONFIG_USB_SIERRA_NET is not set
# CONFIG_USB_VL600 is not set
CONFIG_WLAN=y
# CONFIG_HOSTAP is not set
# CONFIG_WL_TI is not set

#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#
# CONFIG_WAN is not set
# CONFIG_ISDN is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set
# CONFIG_INPUT_SPARSEKMAP is not set
CONFIG_INPUT_MATRIXKMAP=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not set
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT1070 is not set
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_LKKBD is not set
CONFIG_KEYBOARD_GPIO=y
# CONFIG_KEYBOARD_GPIO_POLLED is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_TCA8418 is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_LM8333 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
CONFIG_KEYBOARD_SAMSUNG=y
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_OMAP4 is not set
# CONFIG_KEYBOARD_XTKBD is not set
CONFIG_KEYBOARD_CROS_EC=y
# CONFIG_KEYBOARD_CAP11XX is not set
CONFIG_INPUT_LEDS=y
CONFIG_INPUT_MOUSE=y
# CONFIG_MOUSE_PS2 is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
CONFIG_MOUSE_CYAPA=y
# CONFIG_MOUSE_ELAN_I2C is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_GPIO is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
# CONFIG_MOUSE_SYNAPTICS_USB is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_OF_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_ADS7846 is not set
# CONFIG_TOUCHSCREEN_AD7877 is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_TOUCHSCREEN_AR1021_I2C is not set
CONFIG_TOUCHSCREEN_ATMEL_MXT=y
# CONFIG_TOUCHSCREEN_AUO_PIXCIR is not set
# CONFIG_TOUCHSCREEN_BU21013 is not set
# CONFIG_TOUCHSCREEN_CY8CTMG110 is not set
# CONFIG_TOUCHSCREEN_CYTTSP_CORE is not set
# CONFIG_TOUCHSCREEN_CYTTSP4_CORE is not set
# CONFIG_TOUCHSCREEN_DYNAPRO is not set
# CONFIG_TOUCHSCREEN_HAMPSHIRE is not set
# CONFIG_TOUCHSCREEN_EETI is not set
# CONFIG_TOUCHSCREEN_EGALAX is not set
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_ILI210X is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
# CONFIG_TOUCHSCREEN_ELO is not set
# CONFIG_TOUCHSCREEN_WACOM_W8001 is not set
# CONFIG_TOUCHSCREEN_WACOM_I2C is not set
# CONFIG_TOUCHSCREEN_MAX11801 is not set
# CONFIG_TOUCHSCREEN_MCS5000 is not set
# CONFIG_TOUCHSCREEN_MMS114 is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_INEXIO is not set
# CONFIG_TOUCHSCREEN_MK712 is not set
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_EDT_FT5X06 is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_PIXCIR is not set
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
# CONFIG_TOUCHSCREEN_TSC_SERIO is not set
# CONFIG_TOUCHSCREEN_TSC2005 is not set
# CONFIG_TOUCHSCREEN_TSC2007 is not set
# CONFIG_TOUCHSCREEN_ST1232 is not set
# CONFIG_TOUCHSCREEN_SUR40 is not set
# CONFIG_TOUCHSCREEN_TPS6507X is not set
# CONFIG_TOUCHSCREEN_ZFORCE is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_AMBAKMI is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_SERIO_ALTERA_PS2 is not set
# CONFIG_SERIO_PS2MULT is not set
# CONFIG_SERIO_ARC_PS2 is not set
# CONFIG_SERIO_APBPS2 is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_TTY=y
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_VT_CONSOLE_SLEEP=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_N_GSM is not set
# CONFIG_TRACE_SINK is not set
CONFIG_DEVKMEM=y

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_DEPRECATED_OPTIONS=y
# CONFIG_SERIAL_8250_CONSOLE is not set
CONFIG_SERIAL_8250_DMA=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
# CONFIG_SERIAL_8250_DW is not set
# CONFIG_SERIAL_8250_EM is not set

#
# Non-8250 serial port support
#
# CONFIG_SERIAL_AMBA_PL010 is not set
# CONFIG_SERIAL_AMBA_PL011 is not set
# CONFIG_SERIAL_EARLYCON_ARM_SEMIHOST is not set
CONFIG_SERIAL_SAMSUNG=y
CONFIG_SERIAL_SAMSUNG_UARTS_4=y
CONFIG_SERIAL_SAMSUNG_UARTS=4
CONFIG_SERIAL_SAMSUNG_CONSOLE=y
# CONFIG_SERIAL_MAX3100 is not set
# CONFIG_SERIAL_MAX310X is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_OF_PLATFORM=y
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_SC16IS7XX is not set
# CONFIG_SERIAL_BCM63XX is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_IFX6X60 is not set
# CONFIG_SERIAL_XILINX_PS_UART is not set
# CONFIG_SERIAL_ARC is not set
# CONFIG_SERIAL_FSL_LPUART is not set
# CONFIG_SERIAL_ST_ASC is not set
# CONFIG_HVC_DCC is not set
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
CONFIG_HW_RANDOM_EXYNOS=y
CONFIG_HW_RANDOM_TPM=y
# CONFIG_R3964 is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_TCG_TPM=y
# CONFIG_TCG_TIS_I2C_ATMEL is not set
CONFIG_TCG_TIS_I2C_INFINEON=y
# CONFIG_TCG_TIS_I2C_NUVOTON is not set
# CONFIG_TCG_ST33_I2C is not set
# CONFIG_XILLYBUS is not set

#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_MUX=y

#
# Multiplexer I2C Chip support
#
CONFIG_I2C_ARB_GPIO_CHALLENGE=y
# CONFIG_I2C_MUX_GPIO is not set
# CONFIG_I2C_MUX_PCA9541 is not set
# CONFIG_I2C_MUX_PCA954x is not set
# CONFIG_I2C_MUX_PINCTRL is not set
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_ALGOBIT=y

#
# I2C Hardware Bus support
#

#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_CBUS_GPIO is not set
# CONFIG_I2C_DESIGNWARE_PLATFORM is not set
CONFIG_I2C_EXYNOS5=y
CONFIG_I2C_GPIO=y
# CONFIG_I2C_NOMADIK is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_PXA_PCI is not set
# CONFIG_I2C_RK3X is not set
CONFIG_HAVE_S3C2410_I2C=y
CONFIG_I2C_S3C2410=y
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_XILINX is not set

#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_DIOLAN_U2C is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_ROBOTFUZZ_OSIF is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set

#
# Other I2C/SMBus bus drivers
#
CONFIG_I2C_CROS_EC_TUNNEL=y
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y

#
# SPI Master Controller Drivers
#
# CONFIG_SPI_ALTERA is not set
# CONFIG_SPI_BITBANG is not set
# CONFIG_SPI_CADENCE is not set
# CONFIG_SPI_GPIO is not set
# CONFIG_SPI_FSL_SPI is not set
# CONFIG_SPI_OC_TINY is not set
# CONFIG_SPI_PL022 is not set
# CONFIG_SPI_PXA2XX_PCI is not set
# CONFIG_SPI_ROCKCHIP is not set
CONFIG_SPI_S3C64XX=y
# CONFIG_SPI_SC18IS602 is not set
# CONFIG_SPI_XCOMM is not set
# CONFIG_SPI_XILINX is not set
# CONFIG_SPI_DESIGNWARE is not set

#
# SPI Protocol Masters
#
# CONFIG_SPI_SPIDEV is not set
# CONFIG_SPI_TLE62X0 is not set
# CONFIG_SPMI is not set
# CONFIG_HSI is not set

#
# PPS support
#
# CONFIG_PPS is not set

#
# PPS generators support
#

#
# PTP clock support
#
# CONFIG_PTP_1588_CLOCK is not set

#
# Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks.
#
CONFIG_PINCTRL=y

#
# Pin controllers
#
CONFIG_PINMUX=y
CONFIG_PINCONF=y
# CONFIG_DEBUG_PINCTRL is not set
# CONFIG_PINCTRL_SINGLE is not set
CONFIG_PINCTRL_SAMSUNG=y
CONFIG_PINCTRL_EXYNOS=y
CONFIG_PINCTRL_EXYNOS5440=y
CONFIG_ARCH_HAVE_CUSTOM_GPIO_H=y
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
CONFIG_ARCH_REQUIRE_GPIOLIB=y
CONFIG_GPIOLIB=y
CONFIG_GPIO_DEVRES=y
CONFIG_OF_GPIO=y
CONFIG_DEBUG_GPIO=y
# CONFIG_GPIO_SYSFS is not set

#
# Memory mapped GPIO drivers:
#
# CONFIG_GPIO_74XX_MMIO is not set
# CONFIG_GPIO_GENERIC_PLATFORM is not set
# CONFIG_GPIO_DWAPB is not set
# CONFIG_GPIO_EM is not set
# CONFIG_GPIO_ZEVIO is not set
# CONFIG_GPIO_PL061 is not set
# CONFIG_GPIO_SCH311X is not set
# CONFIG_GPIO_SYSCON is not set
# CONFIG_GPIO_GRGPIO is not set

#
# I2C GPIO expanders:
#
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCF857X is not set
# CONFIG_GPIO_SX150X is not set
# CONFIG_GPIO_ADP5588 is not set
# CONFIG_GPIO_ADNP is not set

#
# PCI GPIO expanders:
#

#
# SPI GPIO expanders:
#
# CONFIG_GPIO_MAX7301 is not set
# CONFIG_GPIO_MCP23S08 is not set
# CONFIG_GPIO_MC33880 is not set
# CONFIG_GPIO_74X164 is not set

#
# AC97 GPIO expanders:
#

#
# LPC GPIO expanders:
#

#
# MODULbus GPIO expanders:
#

#
# USB GPIO expanders:
#
# CONFIG_W1 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_GENERIC_ADC_BATTERY is not set
# CONFIG_TEST_POWER is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2781 is not set
# CONFIG_BATTERY_DS2782 is not set
CONFIG_BATTERY_SBS=y
# CONFIG_BATTERY_BQ27x00 is not set
# CONFIG_BATTERY_MAX17040 is not set
# CONFIG_BATTERY_MAX17042 is not set
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_LP8727 is not set
# CONFIG_CHARGER_GPIO is not set
# CONFIG_CHARGER_MANAGER is not set
# CONFIG_CHARGER_MAX8997 is not set
# CONFIG_CHARGER_BQ2415X is not set
# CONFIG_CHARGER_BQ24190 is not set
# CONFIG_CHARGER_BQ24735 is not set
# CONFIG_CHARGER_SMB347 is not set
CONFIG_CHARGER_TPS65090=y
# CONFIG_POWER_RESET is not set
# CONFIG_POWER_AVS is not set
# CONFIG_HWMON is not set
CONFIG_THERMAL=y
CONFIG_THERMAL_OF=y
CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y
# CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set
# CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set
# CONFIG_THERMAL_GOV_FAIR_SHARE is not set
CONFIG_THERMAL_GOV_STEP_WISE=y
# CONFIG_THERMAL_GOV_BANG_BANG is not set
# CONFIG_THERMAL_GOV_USER_SPACE is not set
# CONFIG_CLOCK_THERMAL is not set
# CONFIG_THERMAL_EMULATION is not set

#
# Texas Instruments thermal drivers
#
# CONFIG_TI_SOC_THERMAL is not set

#
# Samsung thermal drivers
#
CONFIG_EXYNOS_THERMAL=y
CONFIG_EXYNOS_THERMAL_CORE=y
CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_CORE=y
# CONFIG_WATCHDOG_NOWAYOUT is not set

#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_GPIO_WATCHDOG is not set
# CONFIG_XILINX_WATCHDOG is not set
# CONFIG_ARM_SP805_WATCHDOG is not set
# CONFIG_CADENCE_WATCHDOG is not set
CONFIG_HAVE_S3C2410_WATCHDOG=y
CONFIG_S3C2410_WATCHDOG=y
# CONFIG_DW_WATCHDOG is not set
# CONFIG_MAX63XX_WATCHDOG is not set
# CONFIG_MEN_A21_WDT is not set

#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set
CONFIG_SSB_POSSIBLE=y

#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set
CONFIG_BCMA_POSSIBLE=y

#
# Broadcom specific AMBA
#
# CONFIG_BCMA is not set

#
# Multifunction device drivers
#
CONFIG_MFD_CORE=y
# CONFIG_MFD_AS3711 is not set
# CONFIG_MFD_AS3722 is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_AAT2870_CORE is not set
# CONFIG_MFD_BCM590XX is not set
# CONFIG_MFD_AXP20X is not set
CONFIG_MFD_CROS_EC=y
CONFIG_MFD_CROS_EC_I2C=y
CONFIG_MFD_CROS_EC_SPI=y
# CONFIG_MFD_ASIC3 is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_MFD_DA9052_SPI is not set
# CONFIG_MFD_DA9052_I2C is not set
# CONFIG_MFD_DA9055 is not set
# CONFIG_MFD_DA9063 is not set
# CONFIG_MFD_DLN2 is not set
# CONFIG_MFD_MC13XXX_SPI is not set
# CONFIG_MFD_MC13XXX_I2C is not set
# CONFIG_MFD_HI6421_PMIC is not set
# CONFIG_HTC_EGPIO is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_HTC_I2CPLD is not set
# CONFIG_INTEL_SOC_PMIC is not set
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not set
# CONFIG_MFD_88PM805 is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_MAX14577 is not set
CONFIG_MFD_MAX77686=y
CONFIG_MFD_MAX77693=y
# CONFIG_MFD_MAX8907 is not set
# CONFIG_MFD_MAX8925 is not set
CONFIG_MFD_MAX8997=y
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_MENF21BMC is not set
# CONFIG_EZX_PCAP is not set
# CONFIG_MFD_VIPERBOARD is not set
# CONFIG_MFD_RETU is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_MFD_PM8921_CORE is not set
# CONFIG_MFD_RTSX_USB is not set
# CONFIG_MFD_RC5T583 is not set
# CONFIG_MFD_RK808 is not set
# CONFIG_MFD_RN5T618 is not set
CONFIG_MFD_SEC_CORE=y
# CONFIG_MFD_SI476X_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_MFD_SMSC is not set
# CONFIG_ABX500_CORE is not set
# CONFIG_MFD_STMPE is not set
CONFIG_MFD_SYSCON=y
# CONFIG_MFD_TI_AM335X_TSCADC is not set
# CONFIG_MFD_LP3943 is not set
# CONFIG_MFD_LP8788 is not set
# CONFIG_MFD_PALMAS is not set
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
CONFIG_MFD_TPS65090=y
# CONFIG_MFD_TPS65217 is not set
# CONFIG_MFD_TPS65218 is not set
# CONFIG_MFD_TPS6586X is not set
# CONFIG_MFD_TPS65910 is not set
# CONFIG_MFD_TPS65912 is not set
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_MFD_TPS65912_SPI is not set
# CONFIG_MFD_TPS80031 is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_TWL6040_CORE is not set
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_MFD_LM3533 is not set
# CONFIG_MFD_TC3589X is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_MFD_T7L66XB is not set
# CONFIG_MFD_TC6387XB is not set
# CONFIG_MFD_TC6393XB is not set
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_ARIZONA_SPI is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM831X_SPI is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not set
CONFIG_REGULATOR_FIXED_VOLTAGE=y
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
# CONFIG_REGULATOR_USERSPACE_CONSUMER is not set
# CONFIG_REGULATOR_ACT8865 is not set
# CONFIG_REGULATOR_AD5398 is not set
# CONFIG_REGULATOR_ANATOP is not set
# CONFIG_REGULATOR_DA9210 is not set
# CONFIG_REGULATOR_DA9211 is not set
# CONFIG_REGULATOR_FAN53555 is not set
CONFIG_REGULATOR_GPIO=y
# CONFIG_REGULATOR_ISL9305 is not set
# CONFIG_REGULATOR_ISL6271A is not set
# CONFIG_REGULATOR_LP3971 is not set
# CONFIG_REGULATOR_LP3972 is not set
# CONFIG_REGULATOR_LP872X is not set
# CONFIG_REGULATOR_LP8755 is not set
# CONFIG_REGULATOR_LTC3589 is not set
# CONFIG_REGULATOR_MAX1586 is not set
# CONFIG_REGULATOR_MAX8649 is not set
# CONFIG_REGULATOR_MAX8660 is not set
# CONFIG_REGULATOR_MAX8952 is not set
# CONFIG_REGULATOR_MAX8973 is not set
CONFIG_REGULATOR_MAX8997=y
CONFIG_REGULATOR_MAX77686=y
CONFIG_REGULATOR_MAX77693=y
CONFIG_REGULATOR_MAX77802=y
# CONFIG_REGULATOR_PFUZE100 is not set
# CONFIG_REGULATOR_PWM is not set
CONFIG_REGULATOR_S2MPA01=y
CONFIG_REGULATOR_S2MPS11=y
CONFIG_REGULATOR_S5M8767=y
# CONFIG_REGULATOR_TPS51632 is not set
# CONFIG_REGULATOR_TPS62360 is not set
# CONFIG_REGULATOR_TPS65023 is not set
# CONFIG_REGULATOR_TPS6507X is not set
CONFIG_REGULATOR_TPS65090=y
# CONFIG_REGULATOR_TPS6524X is not set
# CONFIG_MEDIA_SUPPORT is not set

#
# Graphics support
#

#
# Direct Rendering Manager
#
CONFIG_DRM=y
CONFIG_DRM_KMS_HELPER=y
CONFIG_DRM_KMS_FB_HELPER=y
# CONFIG_DRM_LOAD_EDID_FIRMWARE is not set

#
# I2C encoder or helper chips
#
# CONFIG_DRM_I2C_CH7006 is not set
# CONFIG_DRM_I2C_SIL164 is not set
# CONFIG_DRM_I2C_NXP_TDA998X is not set
CONFIG_DRM_PTN3460=y
CONFIG_DRM_EXYNOS=y
# CONFIG_DRM_EXYNOS_IOMMU is not set
# CONFIG_DRM_EXYNOS_DMABUF is not set
CONFIG_DRM_EXYNOS_FIMD=y
# CONFIG_DRM_EXYNOS_DPI is not set
# CONFIG_DRM_EXYNOS_DSI is not set
CONFIG_DRM_EXYNOS_DP=y
# CONFIG_DRM_EXYNOS_HDMI is not set
# CONFIG_DRM_EXYNOS_VIDI is not set
# CONFIG_DRM_EXYNOS_G2D is not set
# CONFIG_DRM_EXYNOS_IPP is not set
# CONFIG_DRM_UDL is not set
# CONFIG_DRM_ARMADA is not set
# CONFIG_DRM_TILCDC is not set
CONFIG_DRM_PANEL=y

#
# Display Panels
#
CONFIG_DRM_PANEL_SIMPLE=y
# CONFIG_DRM_PANEL_LD9040 is not set
# CONFIG_DRM_PANEL_S6E8AA0 is not set
# CONFIG_DRM_STI is not set

#
# Frame buffer Devices
#
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
CONFIG_FB_CMDLINE=y
# CONFIG_FB_DDC is not set
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_FOREIGN_ENDIAN is not set
# CONFIG_FB_SYS_FOPS is not set
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set

#
# Frame buffer hardware drivers
#
# CONFIG_FB_ARMCLCD is not set
# CONFIG_FB_OPENCORES is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_S3C is not set
# CONFIG_FB_SMSCUFX is not set
# CONFIG_FB_UDL is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_BROADSHEET is not set
# CONFIG_FB_AUO_K190X is not set
CONFIG_FB_SIMPLE=y
CONFIG_EXYNOS_VIDEO=y
CONFIG_EXYNOS_MIPI_DSI=y
# CONFIG_EXYNOS_LCD_S6E8AX0 is not set
# CONFIG_FB_SSD1307 is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_LCD_CLASS_DEVICE=y
# CONFIG_LCD_L4F00242T03 is not set
# CONFIG_LCD_LMS283GF05 is not set
# CONFIG_LCD_LTV350QV is not set
# CONFIG_LCD_ILI922X is not set
# CONFIG_LCD_ILI9320 is not set
# CONFIG_LCD_TDO24M is not set
# CONFIG_LCD_VGG2432A4 is not set
CONFIG_LCD_PLATFORM=y
# CONFIG_LCD_S6E63M0 is not set
# CONFIG_LCD_LD9040 is not set
# CONFIG_LCD_AMS369FG06 is not set
# CONFIG_LCD_LMS501KF03 is not set
# CONFIG_LCD_HX8357 is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_GENERIC=y
CONFIG_BACKLIGHT_PWM=y
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_LM3630A is not set
# CONFIG_BACKLIGHT_LM3639 is not set
# CONFIG_BACKLIGHT_LP855X is not set
# CONFIG_BACKLIGHT_GPIO is not set
# CONFIG_BACKLIGHT_LV5207LP is not set
# CONFIG_BACKLIGHT_BD6107 is not set
# CONFIG_VGASTATE is not set
CONFIG_VIDEOMODE_HELPERS=y
CONFIG_HDMI=y

#
# Console display driver support
#
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
CONFIG_SOUND=y
# CONFIG_SOUND_OSS_CORE is not set
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_DMAENGINE_PCM=y
CONFIG_SND_COMPRESS_OFFLOAD=y
CONFIG_SND_JACK=y
# CONFIG_SND_SEQUENCER is not set
# CONFIG_SND_MIXER_OSS is not set
# CONFIG_SND_PCM_OSS is not set
# CONFIG_SND_HRTIMER is not set
# CONFIG_SND_DYNAMIC_MINORS is not set
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
# CONFIG_SND_RAWMIDI_SEQ is not set
# CONFIG_SND_OPL3_LIB_SEQ is not set
# CONFIG_SND_OPL4_LIB_SEQ is not set
# CONFIG_SND_SBAWE_SEQ is not set
# CONFIG_SND_EMU10K1_SEQ is not set
CONFIG_SND_DRIVERS=y
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_ALOOP is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# HD-Audio
#
CONFIG_SND_ARM=y
# CONFIG_SND_ARMAACI is not set
CONFIG_SND_SPI=y
CONFIG_SND_USB=y
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_UA101 is not set
# CONFIG_SND_USB_CAIAQ is not set
# CONFIG_SND_USB_6FIRE is not set
# CONFIG_SND_USB_HIFACE is not set
# CONFIG_SND_BCD2000 is not set
CONFIG_SND_SOC=y
CONFIG_SND_SOC_GENERIC_DMAENGINE_PCM=y
# CONFIG_SND_ATMEL_SOC is not set
# CONFIG_SND_DESIGNWARE_I2S is not set

#
# SoC Audio for Freescale CPUs
#

#
# Common SoC Audio options for Freescale CPUs:
#
# CONFIG_SND_SOC_FSL_ASRC is not set
# CONFIG_SND_SOC_FSL_SAI is not set
# CONFIG_SND_SOC_FSL_SSI is not set
# CONFIG_SND_SOC_FSL_SPDIF is not set
# CONFIG_SND_SOC_FSL_ESAI is not set
# CONFIG_SND_SOC_IMX_AUDMUX is not set
# CONFIG_SND_SOC_ROCKCHIP_I2S is not set
CONFIG_SND_SOC_SAMSUNG=y
CONFIG_SND_SAMSUNG_I2S=y
# CONFIG_SND_SOC_SAMSUNG_SMDK_WM8994 is not set
# CONFIG_SND_SOC_SAMSUNG_SMDK_SPDIF is not set
# CONFIG_SND_SOC_SMDK_WM8994_PCM is not set
CONFIG_SND_SOC_SNOW=y
# CONFIG_SND_SOC_ODROIDX2 is not set
CONFIG_SND_SOC_I2C_AND_SPI=y

#
# CODEC drivers
#
# CONFIG_SND_SOC_ADAU1701 is not set
# CONFIG_SND_SOC_AK4104 is not set
# CONFIG_SND_SOC_AK4554 is not set
# CONFIG_SND_SOC_AK4642 is not set
# CONFIG_SND_SOC_AK5386 is not set
# CONFIG_SND_SOC_ALC5623 is not set
# CONFIG_SND_SOC_CS35L32 is not set
# CONFIG_SND_SOC_CS42L51_I2C is not set
# CONFIG_SND_SOC_CS42L52 is not set
# CONFIG_SND_SOC_CS42L56 is not set
# CONFIG_SND_SOC_CS42L73 is not set
# CONFIG_SND_SOC_CS4265 is not set
# CONFIG_SND_SOC_CS4270 is not set
# CONFIG_SND_SOC_CS4271_I2C is not set
# CONFIG_SND_SOC_CS4271_SPI is not set
# CONFIG_SND_SOC_CS42XX8_I2C is not set
# CONFIG_SND_SOC_HDMI_CODEC is not set
# CONFIG_SND_SOC_ES8328 is not set
CONFIG_SND_SOC_MAX98090=y
CONFIG_SND_SOC_MAX98095=y
# CONFIG_SND_SOC_PCM1681 is not set
# CONFIG_SND_SOC_PCM1792A is not set
# CONFIG_SND_SOC_PCM512x_I2C is not set
# CONFIG_SND_SOC_PCM512x_SPI is not set
# CONFIG_SND_SOC_RT5631 is not set
# CONFIG_SND_SOC_RT5677_SPI is not set
# CONFIG_SND_SOC_SGTL5000 is not set
# CONFIG_SND_SOC_SIRF_AUDIO_CODEC is not set
# CONFIG_SND_SOC_SPDIF is not set
# CONFIG_SND_SOC_SSM2602_SPI is not set
# CONFIG_SND_SOC_SSM2602_I2C is not set
# CONFIG_SND_SOC_SSM4567 is not set
# CONFIG_SND_SOC_STA350 is not set
# CONFIG_SND_SOC_TAS2552 is not set
# CONFIG_SND_SOC_TAS5086 is not set
# CONFIG_SND_SOC_TFA9879 is not set
# CONFIG_SND_SOC_TLV320AIC23_I2C is not set
# CONFIG_SND_SOC_TLV320AIC23_SPI is not set
# CONFIG_SND_SOC_TLV320AIC31XX is not set
# CONFIG_SND_SOC_TLV320AIC3X is not set
# CONFIG_SND_SOC_TS3A227E is not set
# CONFIG_SND_SOC_WM8510 is not set
# CONFIG_SND_SOC_WM8523 is not set
# CONFIG_SND_SOC_WM8580 is not set
# CONFIG_SND_SOC_WM8711 is not set
# CONFIG_SND_SOC_WM8728 is not set
# CONFIG_SND_SOC_WM8731 is not set
# CONFIG_SND_SOC_WM8737 is not set
# CONFIG_SND_SOC_WM8741 is not set
# CONFIG_SND_SOC_WM8750 is not set
# CONFIG_SND_SOC_WM8753 is not set
# CONFIG_SND_SOC_WM8770 is not set
# CONFIG_SND_SOC_WM8776 is not set
# CONFIG_SND_SOC_WM8804 is not set
# CONFIG_SND_SOC_WM8903 is not set
# CONFIG_SND_SOC_WM8962 is not set
# CONFIG_SND_SOC_WM8978 is not set
# CONFIG_SND_SOC_TPA6130A2 is not set
# CONFIG_SND_SIMPLE_CARD is not set
# CONFIG_SOUND_PRIME is not set

#
# HID support
#
CONFIG_HID=y
# CONFIG_HID_BATTERY_STRENGTH is not set
# CONFIG_HIDRAW is not set
# CONFIG_UHID is not set
CONFIG_HID_GENERIC=y

#
# Special HID drivers
#
CONFIG_HID_A4TECH=y
# CONFIG_HID_ACRUX is not set
CONFIG_HID_APPLE=y
# CONFIG_HID_APPLEIR is not set
# CONFIG_HID_AUREAL is not set
CONFIG_HID_BELKIN=y
CONFIG_HID_CHERRY=y
CONFIG_HID_CHICONY=y
# CONFIG_HID_PRODIKEYS is not set
# CONFIG_HID_CP2112 is not set
CONFIG_HID_CYPRESS=y
# CONFIG_HID_DRAGONRISE is not set
# CONFIG_HID_EMS_FF is not set
# CONFIG_HID_ELECOM is not set
# CONFIG_HID_ELO is not set
CONFIG_HID_EZKEY=y
# CONFIG_HID_HOLTEK is not set
# CONFIG_HID_GT683R is not set
# CONFIG_HID_HUION is not set
# CONFIG_HID_KEYTOUCH is not set
# CONFIG_HID_KYE is not set
# CONFIG_HID_UCLOGIC is not set
# CONFIG_HID_WALTOP is not set
# CONFIG_HID_GYRATION is not set
# CONFIG_HID_ICADE is not set
# CONFIG_HID_TWINHAN is not set
CONFIG_HID_KENSINGTON=y
# CONFIG_HID_LCPOWER is not set
# CONFIG_HID_LENOVO is not set
CONFIG_HID_LOGITECH=y
# CONFIG_HID_LOGITECH_HIDPP is not set
# CONFIG_LOGITECH_FF is not set
# CONFIG_LOGIRUMBLEPAD2_FF is not set
# CONFIG_LOGIG940_FF is not set
# CONFIG_LOGIWHEELS_FF is not set
# CONFIG_HID_MAGICMOUSE is not set
CONFIG_HID_MICROSOFT=y
CONFIG_HID_MONTEREY=y
# CONFIG_HID_MULTITOUCH is not set
# CONFIG_HID_NTRIG is not set
# CONFIG_HID_ORTEK is not set
# CONFIG_HID_PANTHERLORD is not set
# CONFIG_HID_PENMOUNT is not set
# CONFIG_HID_PETALYNX is not set
# CONFIG_HID_PICOLCD is not set
CONFIG_HID_PLANTRONICS=y
# CONFIG_HID_PRIMAX is not set
# CONFIG_HID_ROCCAT is not set
# CONFIG_HID_SAITEK is not set
# CONFIG_HID_SAMSUNG is not set
# CONFIG_HID_SONY is not set
# CONFIG_HID_SPEEDLINK is not set
# CONFIG_HID_STEELSERIES is not set
# CONFIG_HID_SUNPLUS is not set
# CONFIG_HID_RMI is not set
# CONFIG_HID_GREENASIA is not set
# CONFIG_HID_SMARTJOYPLUS is not set
# CONFIG_HID_TIVO is not set
# CONFIG_HID_TOPSEED is not set
# CONFIG_HID_THINGM is not set
# CONFIG_HID_THRUSTMASTER is not set
# CONFIG_HID_WACOM is not set
# CONFIG_HID_WIIMOTE is not set
# CONFIG_HID_XINMO is not set
# CONFIG_HID_ZEROPLUS is not set
# CONFIG_HID_ZYDACRON is not set
# CONFIG_HID_SENSOR_HUB is not set

#
# USB HID support
#
CONFIG_USB_HID=y
# CONFIG_HID_PID is not set
# CONFIG_USB_HIDDEV is not set

#
# I2C HID support
#
# CONFIG_I2C_HID is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_COMMON=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB=y
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y

#
# Miscellaneous USB options
#
CONFIG_USB_DEFAULT_PERSIST=y
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG is not set
# CONFIG_USB_OTG_WHITELIST is not set
# CONFIG_USB_OTG_FSM is not set
# CONFIG_USB_MON is not set
# CONFIG_USB_WUSB_CBAF is not set

#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_XHCI_HCD=y
CONFIG_USB_XHCI_PLATFORM=y
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_EHCI_EXYNOS=y
# CONFIG_USB_EHCI_HCD_PLATFORM is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
# CONFIG_USB_ISP1362_HCD is not set
# CONFIG_USB_FUSBH200_HCD is not set
# CONFIG_USB_FOTG210_HCD is not set
# CONFIG_USB_MAX3421_HCD is not set
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_EXYNOS=y
# CONFIG_USB_OHCI_HCD_PLATFORM is not set
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_HCD_TEST_MODE is not set

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set

#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#

#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_REALTEK is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_ONETOUCH is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
# CONFIG_USB_STORAGE_ENE_UB6250 is not set
# CONFIG_USB_UAS is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USBIP_CORE is not set
# CONFIG_USB_MUSB_HDRC is not set
CONFIG_USB_DWC3=y
# CONFIG_USB_DWC3_HOST is not set
# CONFIG_USB_DWC3_GADGET is not set
CONFIG_USB_DWC3_DUAL_ROLE=y

#
# Platform Glue Driver Support
#
CONFIG_USB_DWC3_EXYNOS=y

#
# Debugging features
#
# CONFIG_USB_DWC3_DEBUG is not set
# CONFIG_DWC3_HOST_USB3_LPM_ENABLE is not set
# CONFIG_USB_DWC2 is not set
# CONFIG_USB_CHIPIDEA is not set

#
# USB port drivers
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_EHSET_TEST_FIXTURE is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_YUREX is not set
# CONFIG_USB_EZUSB_FX2 is not set
CONFIG_USB_HSIC_USB3503=y
# CONFIG_USB_LINK_LAYER_TEST is not set

#
# USB Physical Layer drivers
#
# CONFIG_USB_PHY is not set
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_AM335X_PHY_USB is not set
# CONFIG_USB_GPIO_VBUS is not set
# CONFIG_USB_ISP1301 is not set
# CONFIG_USB_ULPI is not set
CONFIG_USB_GADGET=y
# CONFIG_USB_GADGET_DEBUG is not set
# CONFIG_USB_GADGET_DEBUG_FILES is not set
# CONFIG_USB_GADGET_DEBUG_FS is not set
CONFIG_USB_GADGET_VBUS_DRAW=2
CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2

#
# USB Peripheral Controller
#
# CONFIG_USB_FUSB300 is not set
# CONFIG_USB_FOTG210_UDC is not set
# CONFIG_USB_GR_UDC is not set
# CONFIG_USB_R8A66597 is not set
# CONFIG_USB_PXA27X is not set
# CONFIG_USB_MV_UDC is not set
# CONFIG_USB_MV_U3D is not set
# CONFIG_USB_M66592 is not set
# CONFIG_USB_NET2272 is not set
# CONFIG_USB_GADGET_XILINX is not set
# CONFIG_USB_DUMMY_HCD is not set
# CONFIG_USB_CONFIGFS is not set
# CONFIG_USB_ZERO is not set
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_ETH is not set
# CONFIG_USB_G_NCM is not set
# CONFIG_USB_GADGETFS is not set
# CONFIG_USB_FUNCTIONFS is not set
# CONFIG_USB_MASS_STORAGE is not set
# CONFIG_USB_G_SERIAL is not set
# CONFIG_USB_MIDI_GADGET is not set
# CONFIG_USB_G_PRINTER is not set
# CONFIG_USB_CDC_COMPOSITE is not set
# CONFIG_USB_G_ACM_MS is not set
# CONFIG_USB_G_MULTI is not set
# CONFIG_USB_G_HID is not set
# CONFIG_USB_G_DBGP is not set
# CONFIG_USB_LED_TRIG is not set
# CONFIG_UWB is not set
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_CLKGATE is not set

#
# MMC/SD/SDIO Card Drivers
#
CONFIG_MMC_BLOCK=y
CONFIG_MMC_BLOCK_MINORS=16
CONFIG_MMC_BLOCK_BOUNCE=y
# CONFIG_SDIO_UART is not set
# CONFIG_MMC_TEST is not set

#
# MMC/SD/SDIO Host Controller Drivers
#
# CONFIG_MMC_ARMMMCI is not set
CONFIG_MMC_SDHCI=y
# CONFIG_MMC_SDHCI_PLTFM is not set
CONFIG_MMC_SDHCI_S3C=y
CONFIG_MMC_SDHCI_S3C_DMA=y
CONFIG_MMC_DW=y
CONFIG_MMC_DW_IDMAC=y
CONFIG_MMC_DW_PLTFM=y
CONFIG_MMC_DW_EXYNOS=y
# CONFIG_MMC_DW_K3 is not set
# CONFIG_MMC_VUB300 is not set
# CONFIG_MMC_USHC is not set
# CONFIG_MMC_USDHI6ROL0 is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y

#
# LED drivers
#
# CONFIG_LEDS_LM3530 is not set
# CONFIG_LEDS_LM3642 is not set
# CONFIG_LEDS_PCA9532 is not set
# CONFIG_LEDS_GPIO is not set
# CONFIG_LEDS_LP3944 is not set
# CONFIG_LEDS_LP5521 is not set
# CONFIG_LEDS_LP5523 is not set
# CONFIG_LEDS_LP5562 is not set
# CONFIG_LEDS_LP8501 is not set
# CONFIG_LEDS_LP8860 is not set
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_PCA963X is not set
# CONFIG_LEDS_DAC124S085 is not set
# CONFIG_LEDS_PWM is not set
# CONFIG_LEDS_REGULATOR is not set
# CONFIG_LEDS_BD2802 is not set
# CONFIG_LEDS_LT3593 is not set
# CONFIG_LEDS_TCA6507 is not set
# CONFIG_LEDS_MAX8997 is not set
# CONFIG_LEDS_LM355x is not set

#
# LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM)
#
# CONFIG_LEDS_BLINKM is not set
# CONFIG_LEDS_SYSCON is not set

#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
# CONFIG_LEDS_TRIGGER_TIMER is not set
# CONFIG_LEDS_TRIGGER_ONESHOT is not set
# CONFIG_LEDS_TRIGGER_HEARTBEAT is not set
# CONFIG_LEDS_TRIGGER_BACKLIGHT is not set
# CONFIG_LEDS_TRIGGER_CPU is not set
# CONFIG_LEDS_TRIGGER_GPIO is not set
# CONFIG_LEDS_TRIGGER_DEFAULT_ON is not set

#
# iptables trigger is under Netfilter config (LED target)
#
# CONFIG_LEDS_TRIGGER_TRANSIENT is not set
# CONFIG_LEDS_TRIGGER_CAMERA is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_EDAC is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_SYSTOHC=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set

#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_DS3232 is not set
# CONFIG_RTC_DRV_HYM8563 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_MAX8997 is not set
CONFIG_RTC_DRV_MAX77686=y
CONFIG_RTC_DRV_MAX77802=y
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_ISL12022 is not set
# CONFIG_RTC_DRV_ISL12057 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF2127 is not set
# CONFIG_RTC_DRV_PCF8523 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF85063 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_BQ32K is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set
# CONFIG_RTC_DRV_EM3027 is not set
# CONFIG_RTC_DRV_RV3029C2 is not set
CONFIG_RTC_DRV_S5M=y

#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T93 is not set
# CONFIG_RTC_DRV_M41T94 is not set
# CONFIG_RTC_DRV_DS1305 is not set
# CONFIG_RTC_DRV_DS1343 is not set
# CONFIG_RTC_DRV_DS1347 is not set
# CONFIG_RTC_DRV_DS1390 is not set
# CONFIG_RTC_DRV_MAX6902 is not set
# CONFIG_RTC_DRV_R9701 is not set
# CONFIG_RTC_DRV_RS5C348 is not set
# CONFIG_RTC_DRV_DS3234 is not set
# CONFIG_RTC_DRV_PCF2123 is not set
# CONFIG_RTC_DRV_RX4581 is not set
# CONFIG_RTC_DRV_MCP795 is not set

#
# Platform RTC drivers
#
# CONFIG_RTC_DRV_CMOS is not set
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_DS2404 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_V3020 is not set

#
# on-CPU RTC drivers
#
CONFIG_HAVE_S3C_RTC=y
CONFIG_RTC_DRV_S3C=y
# CONFIG_RTC_DRV_PL030 is not set
# CONFIG_RTC_DRV_PL031 is not set
# CONFIG_RTC_DRV_SNVS is not set
# CONFIG_RTC_DRV_XGENE is not set

#
# HID Sensor RTC drivers
#
# CONFIG_RTC_DRV_HID_SENSOR_TIME is not set
CONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set

#
# DMA Devices
#
# CONFIG_AMBA_PL08X is not set
# CONFIG_DW_DMAC_CORE is not set
# CONFIG_DW_DMAC is not set
CONFIG_PL330_DMA=y
# CONFIG_FSL_EDMA is not set
# CONFIG_NBPFAXI_DMA is not set
CONFIG_DMA_ENGINE=y
CONFIG_DMA_OF=y

#
# DMA Clients
#
# CONFIG_ASYNC_TX_DMA is not set
# CONFIG_DMATEST is not set
# CONFIG_AUXDISPLAY is not set
# CONFIG_UIO is not set
# CONFIG_VFIO is not set
# CONFIG_VIRT_DRIVERS is not set

#
# Virtio drivers
#
# CONFIG_VIRTIO_MMIO is not set

#
# Microsoft Hyper-V guest support
#
# CONFIG_STAGING is not set

#
# SOC (System On Chip) specific Drivers
#
# CONFIG_SOC_TI is not set
CONFIG_CLKDEV_LOOKUP=y
CONFIG_HAVE_CLK_PREPARE=y
CONFIG_COMMON_CLK=y

#
# Common Clock Framework
#
CONFIG_COMMON_CLK_MAX_GEN=y
CONFIG_COMMON_CLK_MAX77686=y
CONFIG_COMMON_CLK_MAX77802=y
# CONFIG_COMMON_CLK_SI5351 is not set
# CONFIG_COMMON_CLK_SI570 is not set
CONFIG_COMMON_CLK_S2MPS11=y
# CONFIG_COMMON_CLK_PXA is not set
# CONFIG_COMMON_CLK_QCOM is not set
CONFIG_COMMON_CLK_SAMSUNG=y

#
# Hardware Spinlock drivers
#

#
# Clock Source drivers
#
CONFIG_CLKSRC_OF=y
CONFIG_ARM_ARCH_TIMER=y
CONFIG_ARM_ARCH_TIMER_EVTSTREAM=y
# CONFIG_ATMEL_PIT is not set
CONFIG_CLKSRC_EXYNOS_MCT=y
CONFIG_CLKSRC_SAMSUNG_PWM=y
# CONFIG_SH_TIMER_CMT is not set
# CONFIG_SH_TIMER_MTU2 is not set
# CONFIG_SH_TIMER_TMU is not set
# CONFIG_EM_TIMER_STI is not set
# CONFIG_CLKSRC_VERSATILE is not set
# CONFIG_MAILBOX is not set
CONFIG_IOMMU_API=y
CONFIG_IOMMU_SUPPORT=y
CONFIG_OF_IOMMU=y
CONFIG_EXYNOS_IOMMU=y
# CONFIG_EXYNOS_IOMMU_DEBUG is not set

#
# Remoteproc drivers
#
# CONFIG_STE_MODEM_RPROC is not set

#
# Rpmsg drivers
#

#
# SOC (System On Chip) specific Drivers
#
# CONFIG_PM_DEVFREQ is not set
# CONFIG_EXTCON is not set
# CONFIG_MEMORY is not set
CONFIG_IIO=y
# CONFIG_IIO_BUFFER is not set
# CONFIG_IIO_TRIGGER is not set

#
# Accelerometers
#
# CONFIG_BMA180 is not set
# CONFIG_BMC150_ACCEL is not set
# CONFIG_IIO_ST_ACCEL_3AXIS is not set
# CONFIG_KXSD9 is not set
# CONFIG_MMA8452 is not set
# CONFIG_KXCJK1013 is not set

#
# Analog to digital converters
#
# CONFIG_AD7266 is not set
# CONFIG_AD7291 is not set
# CONFIG_AD7298 is not set
# CONFIG_AD7476 is not set
# CONFIG_AD7791 is not set
# CONFIG_AD7793 is not set
# CONFIG_AD7887 is not set
# CONFIG_AD7923 is not set
# CONFIG_AD799X is not set
CONFIG_EXYNOS_ADC=y
# CONFIG_MAX1027 is not set
# CONFIG_MAX1363 is not set
# CONFIG_MCP320X is not set
# CONFIG_MCP3422 is not set
# CONFIG_NAU7802 is not set
# CONFIG_TI_ADC081C is not set
# CONFIG_TI_ADC128S052 is not set
# CONFIG_VF610_ADC is not set

#
# Amplifiers
#
# CONFIG_AD8366 is not set

#
# Hid Sensor IIO Common
#

#
# Digital to analog converters
#
# CONFIG_AD5064 is not set
# CONFIG_AD5360 is not set
# CONFIG_AD5380 is not set
# CONFIG_AD5421 is not set
# CONFIG_AD5446 is not set
# CONFIG_AD5449 is not set
# CONFIG_AD5504 is not set
# CONFIG_AD5624R_SPI is not set
# CONFIG_AD5686 is not set
# CONFIG_AD5755 is not set
# CONFIG_AD5764 is not set
# CONFIG_AD5791 is not set
# CONFIG_AD7303 is not set
# CONFIG_MAX517 is not set
# CONFIG_MAX5821 is not set
# CONFIG_MCP4725 is not set
# CONFIG_MCP4922 is not set

#
# Frequency Synthesizers DDS/PLL
#

#
# Clock Generator/Distribution
#
# CONFIG_AD9523 is not set

#
# Phase-Locked Loop (PLL) frequency synthesizers
#
# CONFIG_ADF4350 is not set

#
# Digital gyroscope sensors
#
# CONFIG_ADIS16080 is not set
# CONFIG_ADIS16130 is not set
# CONFIG_ADIS16136 is not set
# CONFIG_ADIS16260 is not set
# CONFIG_ADXRS450 is not set
# CONFIG_BMG160 is not set
# CONFIG_IIO_ST_GYRO_3AXIS is not set
# CONFIG_ITG3200 is not set

#
# Humidity sensors
#
# CONFIG_DHT11 is not set
# CONFIG_SI7005 is not set
# CONFIG_SI7020 is not set

#
# Inertial measurement units
#
# CONFIG_ADIS16400 is not set
# CONFIG_ADIS16480 is not set
# CONFIG_INV_MPU6050_IIO is not set

#
# Light sensors
#
# CONFIG_ADJD_S311 is not set
# CONFIG_AL3320A is not set
# CONFIG_APDS9300 is not set
# CONFIG_CM32181 is not set
# CONFIG_CM36651 is not set
# CONFIG_GP2AP020A00F is not set
# CONFIG_ISL29125 is not set
# CONFIG_LTR501 is not set
# CONFIG_TCS3414 is not set
# CONFIG_TCS3472 is not set
# CONFIG_SENSORS_TSL2563 is not set
# CONFIG_TSL4531 is not set
# CONFIG_VCNL4000 is not set

#
# Magnetometer sensors
#
# CONFIG_AK8975 is not set
# CONFIG_AK09911 is not set
# CONFIG_MAG3110 is not set
# CONFIG_IIO_ST_MAGN_3AXIS is not set

#
# Inclinometer sensors
#

#
# Pressure sensors
#
# CONFIG_BMP280 is not set
# CONFIG_MPL115 is not set
# CONFIG_MPL3115 is not set
# CONFIG_IIO_ST_PRESS is not set
# CONFIG_T5403 is not set

#
# Lightning sensors
#
# CONFIG_AS3935 is not set

#
# Temperature sensors
#
# CONFIG_MLX90614 is not set
# CONFIG_TMP006 is not set
CONFIG_PWM=y
CONFIG_PWM_SYSFS=y
# CONFIG_PWM_FSL_FTM is not set
# CONFIG_PWM_PCA9685 is not set
CONFIG_PWM_SAMSUNG=y
CONFIG_IRQCHIP=y
CONFIG_ARM_GIC=y
CONFIG_GIC_NON_BANKED=y
# CONFIG_IPACK_BUS is not set
# CONFIG_RESET_CONTROLLER is not set
# CONFIG_FMC is not set

#
# PHY Subsystem
#
CONFIG_GENERIC_PHY=y
CONFIG_PHY_EXYNOS_MIPI_VIDEO=y
CONFIG_PHY_EXYNOS_DP_VIDEO=y
# CONFIG_BCM_KONA_USB2_PHY is not set
CONFIG_PHY_EXYNOS5250_SATA=y
CONFIG_PHY_SAMSUNG_USB2=y
CONFIG_PHY_EXYNOS4210_USB2=y
CONFIG_PHY_EXYNOS4X12_USB2=y
CONFIG_PHY_EXYNOS5250_USB2=y
CONFIG_PHY_EXYNOS5_USBDRD=y
# CONFIG_POWERCAP is not set
# CONFIG_MCB is not set

#
# Android
#
# CONFIG_ANDROID is not set

#
# File systems
#
CONFIG_DCACHE_WORD_ACCESS=y
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_DEFAULTS_TO_ORDERED=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_EXT4_FS=y
# CONFIG_EXT4_FS_POSIX_ACL is not set
# CONFIG_EXT4_FS_SECURITY is not set
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_FANOTIFY is not set
# CONFIG_QUOTA is not set
# CONFIG_QUOTACTL is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set
# CONFIG_OVERLAY_FS is not set

#
# Caches
#
# CONFIG_FSCACHE is not set

#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_KERNFS=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_CONFIGFS_FS is not set
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_LOGFS is not set
CONFIG_CRAMFS=y
# CONFIG_SQUASHFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX6FS_FS is not set
CONFIG_ROMFS_FS=y
CONFIG_ROMFS_BACKED_BY_BLOCK=y
CONFIG_ROMFS_ON_BLOCK=y
# CONFIG_PSTORE is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
# CONFIG_F2FS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_CEPH_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_MAC_ROMAN is not set
# CONFIG_NLS_MAC_CELTIC is not set
# CONFIG_NLS_MAC_CENTEURO is not set
# CONFIG_NLS_MAC_CROATIAN is not set
# CONFIG_NLS_MAC_CYRILLIC is not set
# CONFIG_NLS_MAC_GAELIC is not set
# CONFIG_NLS_MAC_GREEK is not set
# CONFIG_NLS_MAC_ICELAND is not set
# CONFIG_NLS_MAC_INUIT is not set
# CONFIG_NLS_MAC_ROMANIAN is not set
# CONFIG_NLS_MAC_TURKISH is not set
# CONFIG_NLS_UTF8 is not set

#
# Kernel hacking
#

#
# printk and dmesg options
#
CONFIG_PRINTK_TIME=y
CONFIG_MESSAGE_LOGLEVEL_DEFAULT=4
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_DYNAMIC_DEBUG is not set

#
# Compile-time checks and compiler options
#
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_INFO_REDUCED is not set
# CONFIG_DEBUG_INFO_SPLIT is not set
# CONFIG_DEBUG_INFO_DWARF4 is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=1024
# CONFIG_STRIP_ASM_SYMS is not set
# CONFIG_READABLE_ASM is not set
# CONFIG_UNUSED_SYMBOLS is not set
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_SECTION_MISMATCH is not set
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
CONFIG_MAGIC_SYSRQ=y
CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x1
CONFIG_DEBUG_KERNEL=y

#
# Memory Debugging
#
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
CONFIG_HAVE_DEBUG_KMEMLEAK=y
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_VM is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_DEBUG_HIGHMEM is not set
# CONFIG_DEBUG_SHIRQ is not set

#
# Debug Lockups and Hangs
#
# CONFIG_LOCKUP_DETECTOR is not set
CONFIG_DETECT_HUNG_TASK=y
CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=120
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
# CONFIG_PANIC_ON_OOPS is not set
CONFIG_PANIC_ON_OOPS_VALUE=0
CONFIG_PANIC_TIMEOUT=0
CONFIG_SCHED_DEBUG=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_SCHED_STACK_END_CHECK is not set
# CONFIG_TIMER_STATS is not set
CONFIG_DEBUG_PREEMPT=y

#
# Lock Debugging (spinlocks, mutexes, etc...)
#
CONFIG_DEBUG_RT_MUTEXES=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
# CONFIG_DEBUG_WW_MUTEX_SLOWPATH is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_ATOMIC_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_LOCK_TORTURE_TEST is not set
# CONFIG_STACKTRACE is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_PI_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_DEBUG_CREDENTIALS is not set

#
# RCU Debugging
#
# CONFIG_SPARSE_RCU_POINTER is not set
# CONFIG_TORTURE_TEST is not set
# CONFIG_RCU_TORTURE_TEST is not set
CONFIG_RCU_CPU_STALL_TIMEOUT=21
# CONFIG_RCU_CPU_STALL_INFO is not set
# CONFIG_RCU_TRACE is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_NOTIFIER_ERROR_INJECTION is not set
# CONFIG_FAULT_INJECTION is not set
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_HAVE_C_RECORDMCOUNT=y
CONFIG_TRACING_SUPPORT=y
CONFIG_FTRACE=y
# CONFIG_FUNCTION_TRACER is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_PREEMPT_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_ENABLE_DEFAULT_TRACERS is not set
# CONFIG_FTRACE_SYSCALLS is not set
# CONFIG_TRACER_SNAPSHOT is not set
CONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
# CONFIG_PROFILE_ALL_BRANCHES is not set
# CONFIG_STACK_TRACER is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_PROBE_EVENTS is not set
# CONFIG_TRACEPOINT_BENCHMARK is not set

#
# Runtime Testing
#
# CONFIG_LKDTM is not set
# CONFIG_TEST_LIST_SORT is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_RBTREE_TEST is not set
# CONFIG_INTERVAL_TREE_TEST is not set
# CONFIG_PERCPU_TEST is not set
# CONFIG_ATOMIC64_SELFTEST is not set
# CONFIG_TEST_STRING_HELPERS is not set
# CONFIG_TEST_KSTRTOX is not set
# CONFIG_TEST_RHASHTABLE is not set
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_TEST_LKM is not set
# CONFIG_TEST_USER_COPY is not set
# CONFIG_TEST_BPF is not set
# CONFIG_TEST_FIRMWARE is not set
# CONFIG_TEST_UDELAY is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
# CONFIG_ARM_PTDUMP is not set
# CONFIG_STRICT_DEVMEM is not set
CONFIG_ARM_UNWIND=y
CONFIG_DEBUG_USER=y
# CONFIG_DEBUG_LL is not set
CONFIG_DEBUG_LL_INCLUDE="mach/debug-macro.S"
# CONFIG_DEBUG_UART_PL01X is not set
# CONFIG_DEBUG_UART_8250 is not set
# CONFIG_DEBUG_UART_BCM63XX is not set
CONFIG_UNCOMPRESS_INCLUDE="debug/uncompress.h"
# CONFIG_PID_IN_CONTEXTIDR is not set
# CONFIG_DEBUG_SET_MODULE_RONX is not set
# CONFIG_CORESIGHT is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY_DMESG_RESTRICT is not set
# CONFIG_SECURITY is not set
CONFIG_SECURITYFS=y
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_DEFAULT_SECURITY=""
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=m
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
# CONFIG_CRYPTO_USER is not set
CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_PCRYPT is not set
CONFIG_CRYPTO_WORKQUEUE=y
# CONFIG_CRYPTO_CRYPTD is not set
# CONFIG_CRYPTO_MCRYPTD is not set
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_TEST is not set

#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_SEQIV is not set

#
# Block modes
#
CONFIG_CRYPTO_CBC=y
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not set
# CONFIG_CRYPTO_ECB is not set
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_XTS is not set

#
# Hash modes
#
# CONFIG_CRYPTO_CMAC is not set
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_VMAC is not set

#
# Digest
#
CONFIG_CRYPTO_CRC32C=y
# CONFIG_CRYPTO_CRC32 is not set
# CONFIG_CRYPTO_CRCT10DIF is not set
# CONFIG_CRYPTO_GHASH is not set
# CONFIG_CRYPTO_MD4 is not set
# CONFIG_CRYPTO_MD5 is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA1_ARM is not set
CONFIG_CRYPTO_SHA256=y
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set

#
# Ciphers
#
CONFIG_CRYPTO_AES=y
# CONFIG_CRYPTO_AES_ARM is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set

#
# Compression
#
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_ZLIB is not set
# CONFIG_CRYPTO_LZO is not set
# CONFIG_CRYPTO_LZ4 is not set
# CONFIG_CRYPTO_LZ4HC is not set

#
# Random Number Generation
#
CONFIG_CRYPTO_ANSI_CPRNG=m
# CONFIG_CRYPTO_DRBG_MENU is not set
# CONFIG_CRYPTO_USER_API_HASH is not set
# CONFIG_CRYPTO_USER_API_SKCIPHER is not set
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_S5P is not set
# CONFIG_BINARY_PRINTF is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_STRNCPY_FROM_USER=y
CONFIG_GENERIC_STRNLEN_USER=y
CONFIG_GENERIC_NET_UTILS=y
CONFIG_GENERIC_PCI_IOMAP=y
CONFIG_GENERIC_IO=y
CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y
CONFIG_FLEX_ARRAY=y
CONFIG_RHASHTABLE=y
CONFIG_CRC_CCITT=y
CONFIG_CRC16=y
# CONFIG_CRC_T10DIF is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC32_SELFTEST is not set
CONFIG_CRC32_SLICEBY8=y
# CONFIG_CRC32_SLICEBY4 is not set
# CONFIG_CRC32_SARWATE is not set
# CONFIG_CRC32_BIT is not set
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
# CONFIG_CRC8 is not set
# CONFIG_CRC64_ECMA is not set
CONFIG_HALFMD4=y
# CONFIG_AUDIT_ARCH_COMPAT_GENERIC is not set
# CONFIG_RANDOM32_SELFTEST is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_LZO_COMPRESS=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_LZ4_DECOMPRESS=y
CONFIG_XZ_DEC=y
CONFIG_XZ_DEC_X86=y
CONFIG_XZ_DEC_POWERPC=y
CONFIG_XZ_DEC_IA64=y
CONFIG_XZ_DEC_ARM=y
CONFIG_XZ_DEC_ARMTHUMB=y
CONFIG_XZ_DEC_SPARC=y
CONFIG_XZ_DEC_BCJ=y
# CONFIG_XZ_DEC_TEST is not set
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_DECOMPRESS_XZ=y
CONFIG_DECOMPRESS_LZO=y
CONFIG_DECOMPRESS_LZ4=y
CONFIG_GENERIC_ALLOCATOR=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_DMA=y
CONFIG_CPU_RMAP=y
CONFIG_DQL=y
CONFIG_NLATTR=y
CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y
# CONFIG_AVERAGE is not set
# CONFIG_CORDIC is not set
# CONFIG_DDR is not set
CONFIG_LIBFDT=y
CONFIG_FONT_SUPPORT=y
CONFIG_FONTS=y
# CONFIG_FONT_8x8 is not set
# CONFIG_FONT_8x16 is not set
# CONFIG_FONT_6x11 is not set
CONFIG_FONT_7x14=y
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
# CONFIG_FONT_6x10 is not set
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set
# CONFIG_FONT_10x18 is not set
CONFIG_ARCH_HAS_SG_CHAIN=y
# CONFIG_VIRTUALIZATION is not set

[-- Attachment #3: kernel-log_next20141124 --]
[-- Type: application/octet-stream, Size: 35935 bytes --]

U-Boot 2013.04 (May 14 2014 - 14:09:35) for Peach

CPU:    Exynos5800@900MHz

Board: Google Peach Pi, rev 11.6
I2C:   ready
DRAM:  3.5 GiB
PMIC max77802-pmic initialized
CPU:    Exynos5800@1800MHz
TPS65090 PMIC EC init
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
SF: Detected W25Q32DW with page size 4 KiB, total 32 MiB
In:    cros-ec-keyb
Out:   lcd
Err:   lcd
SF: Detected W25Q32DW with page size 4 KiB, total 32 MiB
elog_is_event_valid: bad checksum
ELOG: Event(17) added with size 13
Net:   No ethernet found.
Hit any key to stop autoboot:  0 
Exynos DP init done
Peach # 
Peach # 
Peach # mmc dev 1
mmc1 is current device
Peach # mmc rescan 
Peach # ext2load mmc 1:1 0x20008000 /boot/vmlinux_pi.uimg
3500836 bytes read in 175 ms (19.1 MiB/s)
Peach # setenv bootargs 'root=/dev/mmcblk1p1 rootwait ro console=ttySAC3,115200 debug earlyprintk init=/linuxrc'
Peach # bootm 0x20008000
## Loading kernel from FIT Image at 20008000 ...
   Using 'config@1' configuration
   Trying 'kernel@1' kernel subimage
     Description:  Vanilla Linux kernel
     Type:         Kernel Image (no loading done)
     Compression:  uncompressed
     Data Start:   0x200080e0
     Data Size:    3457584 Bytes = 3.3 MiB
   Verifying Hash Integrity ... OK
## Loading fdt from FIT Image at 20008000 ...
   Using 'config@1' configuration
   Trying 'fdt@1' fdt subimage
     Description:  exynos5800-peach-pi.dtb
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x203543c4
     Data Size:    42018 Bytes = 41 KiB
     Architecture: ARM
     Hash algo:    sha1
     Hash value:   022e447ac41750fbeca8bcddc837452c0172d217
   Verifying Hash Integrity ... sha1+ OK
   Booting using the fdt blob at 0x203543c4
   XIP Kernel Image (no loading done) ... OK
   Loading Device Tree to 3ffe6000, end 3ffff951 ... OK
boot_kernel.c: ft_board_setup: warning: g_crossystem_data is NULL

Starting kernel ...

Timer summary in microseconds:
       Mark    Elapsed  Stage
          0          0  reset
    127,217    127,217  board_init_f
    170,919     43,702  board_init_r
    245,248     74,329  id=64
    247,458      2,210  main_loop
169,723,974169,476,516  bootm_start
169,723,975          1  id=1
169,728,895      4,920  id=100
169,728,897          2  id=101
169,728,898          1  id=102
169,732,670      3,772  id=110
169,761,020     28,350  id=105
169,761,021          1  id=106
169,761,025          4  id=107
169,761,026          1  id=108
169,761,027          1  id=109
169,765,697      4,670  id=90
169,765,699          2  id=91
169,765,700          1  id=92
169,810,336     44,636  id=95
169,810,339          3  id=96
169,810,341          2  id=97
169,810,342          1  id=98
169,810,344          2  id=99
169,820,411     10,067  id=7
169,833,047     12,636  id=15
169,836,255      3,208  start_kernel

Accumulated time:
                 6,926  SPI read
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.18.0-rc5-next-20141121-00003-g9af3770 (vivek@vivek-linuxpc) (gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1) ) #7 SMP PREEMPT Mon Nov 24 15:50:3
0 IST 2014
[    0.000000] CPU: ARMv7 Processor [412fc0f3] revision 3 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] Machine model: Google Peach Pi Rev 10+
[    0.000000] cma: Reserved 64 MiB at 0xfbc00000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 917503
[    0.000000] free_area_init_node: node 0, pgdat c06caec0, node_mem_map edbf6000
[    0.000000]   Normal zone: 1520 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 194560 pages, LIFO batch:31
[    0.000000]   HighMem zone: 5648 pages used for memmap
[    0.000000]   HighMem zone: 722943 pages, LIFO batch:31
[    0.000000] PERCPU: Embedded 9 pages/cpu @edb6c000 s7616 r8192 d21056 u36864
[    0.000000] pcpu-alloc: s7616 r8192 d21056 u36864 alloc=9*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 915983
[    0.000000] Kernel command line: root=/dev/mmcblk1p1 rootwait ro console=ttySAC3,115200 debug earlyprintk init=/linuxrc
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 3567280K/3670012K available (4585K kernel code, 222K rwdata, 1640K rodata, 300K init, 284K bss, 37196K reserved, 65536K cma-reserved, 2826236K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc061c9e8   (6227 kB)
[    0.000000]       .init : 0xc061d000 - 0xc0668000   ( 300 kB)
[    0.000000]       .data : 0xc0668000 - 0xc069f800   ( 222 kB)
[    0.000000]        .bss : 0xc069f800 - 0xc06e6a84   ( 285 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] GIC physical location is 0x10481000
[    0.000000] L2C: failed to init: -19
[    0.000000] Switching to timer-based delay loop, resolution 41ns
[    0.000003] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956969942ns
[    0.000211] Console: colour dummy device 80x30
[    0.000227] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=120000)
[    0.000236] pid_max: default: 32768 minimum: 301
[    0.000341] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000349] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000724] CPU: Testing write buffer coherency: ok
[    0.000931] CPU0: update cpu_capacity 1535
[    0.000938] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.001035] Setting up static identity map for 0x20458ca0 - 0x20458cf8
[    0.001189] ARM CCI driver probed
[    0.001602] Exynos MCPM support installed
[    0.030219] CPU1: Booted secondary processor
[    0.030255] CPU1: update cpu_capacity 1535
[    0.030259] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.040214] CPU2: Booted secondary processor
[    0.040239] CPU2: update cpu_capacity 1535
[    0.040243] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.050208] CPU3: Booted secondary processor
[    0.050234] CPU3: update cpu_capacity 1535
[    0.050238] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.060246] CPU4: Booted secondary processor
[    0.060343] CPU4: update cpu_capacity 448
[    0.060353] CPU4: thread -1, cpu 0, socket 1, mpidr 80000100
[    0.070236] CPU5: Booted secondary processor
[    0.070298] CPU5: update cpu_capacity 448
[    0.070307] CPU5: thread -1, cpu 1, socket 1, mpidr 80000101
[    0.080239] CPU6: Booted secondary processor
[    0.080300] CPU6: update cpu_capacity 448
[    0.080309] CPU6: thread -1, cpu 2, socket 1, mpidr 80000102
[    0.090238] CPU7: Booted secondary processor
[    0.090300] CPU7: update cpu_capacity 448
[    0.090310] CPU7: thread -1, cpu 3, socket 1, mpidr 80000103
[    0.090379] Brought up 8 CPUs
[    0.090412] SMP: Total of 8 processors activated.
[    0.090418] CPU: All CPU(s) started in SVC mode.
[    0.090886] devtmpfs: initialized
[    0.095914] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[    0.097206] pinctrl core: initialized pinctrl subsystem
[    0.111287] NET: Registered protocol family 16
[    0.112252] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.116270] gpiochip_add: registered GPIOs 0 to 7 on device: gpy7
[    0.116280] gpiochip_add: registered GPIOs 8 to 15 on device: gpx0
[    0.116288] gpiochip_add: registered GPIOs 16 to 23 on device: gpx1
[    0.116296] gpiochip_add: registered GPIOs 24 to 31 on device: gpx2
[    0.116303] gpiochip_add: registered GPIOs 32 to 39 on device: gpx3
[    0.117084] gpiochip_add: registered GPIOs 40 to 47 on device: gpc0
[    0.117093] gpiochip_add: registered GPIOs 48 to 55 on device: gpc1
[    0.117101] gpiochip_add: registered GPIOs 56 to 62 on device: gpc2
[    0.117108] gpiochip_add: registered GPIOs 63 to 66 on device: gpc3
[    0.117116] gpiochip_add: registered GPIOs 67 to 68 on device: gpc4
[    0.117123] gpiochip_add: registered GPIOs 69 to 76 on device: gpd1
[    0.117131] gpiochip_add: registered GPIOs 77 to 82 on device: gpy0
[    0.117138] gpiochip_add: registered GPIOs 83 to 86 on device: gpy1
[    0.117145] gpiochip_add: registered GPIOs 87 to 92 on device: gpy2
[    0.117153] gpiochip_add: registered GPIOs 93 to 100 on device: gpy3
[    0.117160] gpiochip_add: registered GPIOs 101 to 108 on device: gpy4
[    0.117168] gpiochip_add: registered GPIOs 109 to 116 on device: gpy5
[    0.117175] gpiochip_add: registered GPIOs 117 to 124 on device: gpy6
[    0.117698] gpiochip_add: registered GPIOs 125 to 132 on device: gpe0
[    0.117706] gpiochip_add: registered GPIOs 133 to 134 on device: gpe1
[    0.117714] gpiochip_add: registered GPIOs 135 to 140 on device: gpf0
[    0.117721] gpiochip_add: registered GPIOs 141 to 148 on device: gpf1
[    0.117729] gpiochip_add: registered GPIOs 149 to 156 on device: gpg0
[    0.117736] gpiochip_add: registered GPIOs 157 to 164 on device: gpg1
[    0.117743] gpiochip_add: registered GPIOs 165 to 166 on device: gpg2
[    0.117751] gpiochip_add: registered GPIOs 167 to 170 on device: gpj4
[    0.118252] gpiochip_add: registered GPIOs 171 to 178 on device: gpa0
[    0.118261] gpiochip_add: registered GPIOs 179 to 184 on device: gpa1
[    0.118269] gpiochip_add: registered GPIOs 185 to 192 on device: gpa2
[    0.118276] gpiochip_add: registered GPIOs 193 to 197 on device: gpb0
[    0.118284] gpiochip_add: registered GPIOs 198 to 202 on device: gpb1
[    0.118291] gpiochip_add: registered GPIOs 203 to 206 on device: gpb2
[    0.118299] gpiochip_add: registered GPIOs 207 to 214 on device: gpb3
[    0.118306] gpiochip_add: registered GPIOs 215 to 216 on device: gpb4
[    0.118314] gpiochip_add: registered GPIOs 217 to 224 on device: gph0
[    0.118884] gpiochip_add: registered GPIOs 225 to 231 on device: gpz
[    0.120094] exynos-audss-clk 3810000.audss-clock-controller: setup completed
[    0.125762] EXYNOS5420 PMU initialized
[    0.151276] of_get_named_gpiod_flags: parsed 'gpio' property of node '/regulator-usb300[0]' - status (0)
[    0.151581] of_get_named_gpiod_flags: parsed 'gpio' property of node '/regulator-usb301[0]' - status (0)
[    0.151834] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/fixed-regulator[0]'
[    0.153488] SCSI subsystem initialized
[    0.153924] usbcore: registered new interface driver usbfs
[    0.154018] usbcore: registered new interface driver hub
[    0.154170] usbcore: registered new device driver usb
[    0.154751] s3c-i2c 12c80000.i2c: slave address 0x50
[    0.154763] s3c-i2c 12c80000.i2c: bus frequency set to 65 KHz
[    0.154951] s3c-i2c 12c80000.i2c: i2c-2: S3C I2C adapter
[    0.157873] Advanced Linux Sound Architecture Driver Initialized.
[    0.158616] Switched to clocksource mct-frc
[    0.171531] NET: Registered protocol family 2
[    0.171947] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.172003] TCP bind hash table entries: 8192 (order: 5, 163840 bytes)
[    0.172098] TCP: Hash tables configured (established 8192 bind 8192)
[    0.172137] TCP: reno registered
[    0.172148] UDP hash table entries: 512 (order: 2, 24576 bytes)
[    0.172172] UDP-Lite hash table entries: 512 (order: 2, 24576 bytes)
[    0.172333] NET: Registered protocol family 1
[    0.174498] futex hash table entries: 2048 (order: 5, 131072 bytes)
[    0.187158] romfs: ROMFS MTD (C) 2007 Red Hat, Inc.
[    0.187754] bounce: pool size: 64 pages
[    0.187764] io scheduler noop registered
[    0.187772] io scheduler deadline registered
[    0.188181] io scheduler cfq registered (default)
[    0.188812] exynos-mipi-video-phy 10040714.video-phy: can't request region for resource [mem 0x10040714-0x1004071f]
[    0.188830] exynos-mipi-video-phy: probe of 10040714.video-phy failed with error -16
[    0.191592] pwm-backlight backlight: GPIO lookup for consumer enable
[    0.191599] pwm-backlight backlight: using device tree for GPIO lookup
[    0.191610] of_get_named_gpiod_flags: parsed 'enable-gpios' property of node '/backlight[0]' - status (0)
[    0.191658] platform backlight: Driver pwm-backlight requests probe deferral
[    0.194067] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330
[    0.194076] dma-pl330 3880000.adma:  DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6
[    0.198066] dma-pl330 121a0000.pdma: Loaded driver for PL330 DMAC-241330
[    0.198076] dma-pl330 121a0000.pdma:         DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.202114] dma-pl330 121b0000.pdma: Loaded driver for PL330 DMAC-241330
[    0.202123] dma-pl330 121b0000.pdma:         DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.203232] dma-pl330 10800000.mdma: Loaded driver for PL330 DMAC-241330
[    0.203241] dma-pl330 10800000.mdma:         DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[    0.336361] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    0.337749] samsung-uart 12c00000.serial: ttySAC0 at MMIO 0x12c00000 (irq = 83, base_baud = 0) is a S3C6400/10
[    0.338081] samsung-uart 12c10000.serial: ttySAC1 at MMIO 0x12c10000 (irq = 84, base_baud = 0) is a S3C6400/10
[    0.338410] samsung-uart 12c20000.serial: ttySAC2 at MMIO 0x12c20000 (irq = 85, base_baud = 0) is a S3C6400/10
[    0.338766] samsung-uart 12c30000.serial: ttySAC3 at MMIO 0x12c30000 (irq = 86, base_baud = 0) is a S3C6400/10
[    1.329189] console [ttySAC3] enabled
[    1.333838] [drm] Initialized drm 1.1.0 20060810
[    1.337963] platform 145b0000.dp-controller: Driver exynos-dp requests probe deferral
[    1.345742] platform panel: Driver panel-simple requests probe deferral
[    1.352126] error detecting cacheinfo..cpu0
[    1.362869] brd: module loaded
[    1.368024] loop: module loaded
[    1.370256] of_get_named_gpiod_flags: parsed 'cs-gpios' property of node '/spi@12d40000[0]' - status (0)
[    1.380043] cros-ec-spi spi2.0: Chrome EC device registered
[    1.385116] usbcore: registered new interface driver asix
[    1.390140] usbcore: registered new interface driver ax88179_178a
[    1.396229] usbcore: registered new interface driver cdc_ether
[    1.402036] usbcore: registered new interface driver smsc75xx
[    1.407764] usbcore: registered new interface driver smsc95xx
[    1.413469] usbcore: registered new interface driver net1080
[    1.419111] usbcore: registered new interface driver cdc_subset
[    1.425008] usbcore: registered new interface driver zaurus
[    1.430596] usbcore: registered new interface driver cdc_ncm
[    1.436767] usb@12000000 supply vdd33 not found, using dummy regulator
[    1.442702] usb@12000000 supply vdd10 not found, using dummy regulator
[    1.850560] usb@12400000 supply vdd33 not found, using dummy regulator
[    1.855656] usb@12400000 supply vdd10 not found, using dummy regulator
[    2.263403] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    2.267448] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 1
[    2.275317] xhci-hcd xhci-hcd.2.auto: irq 104, io mem 0x12000000
[    2.281180] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.287814] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.295013] usb usb1: Product: xHCI Host Controller
[    2.299870] usb usb1: Manufacturer: Linux 3.18.0-rc5-next-20141121-00003-g9af3770 xhci-hcd
[    2.308111] usb usb1: SerialNumber: xhci-hcd.2.auto
[    2.313529] hub 1-0:1.0: USB hub found
[    2.316721] hub 1-0:1.0: 1 port detected
[    2.320946] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    2.326083] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 2
[    2.333847] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    2.340472] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.347670] usb usb2: Product: xHCI Host Controller
[    2.352527] usb usb2: Manufacturer: Linux 3.18.0-rc5-next-20141121-00003-g9af3770 xhci-hcd
[    2.360769] usb usb2: SerialNumber: xhci-hcd.2.auto
[    2.366173] hub 2-0:1.0: USB hub found
[    2.369376] hub 2-0:1.0: 1 port detected
[    2.373652] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[    2.378744] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 3
[    2.386616] xhci-hcd xhci-hcd.5.auto: irq 105, io mem 0x12400000
[    2.392462] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    2.399115] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.406313] usb usb3: Product: xHCI Host Controller
[    2.411170] usb usb3: Manufacturer: Linux 3.18.0-rc5-next-20141121-00003-g9af3770 xhci-hcd
[    2.419491] usb usb3: SerialNumber: xhci-hcd.5.auto
[    2.424803] hub 3-0:1.0: USB hub found
[    2.428001] hub 3-0:1.0: 1 port detected
[    2.432239] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[    2.437383] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 4
[    2.445141] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[    2.451771] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.458971] usb usb4: Product: xHCI Host Controller
[    2.463828] usb usb4: Manufacturer: Linux 3.18.0-rc5-next-20141121-00003-g9af3770 xhci-hcd
[    2.472158] usb usb4: SerialNumber: xhci-hcd.5.auto
[    2.477471] hub 4-0:1.0: USB hub found
[    2.480676] hub 4-0:1.0: 1 port detected
[    2.484935] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.491072] ehci-exynos: EHCI EXYNOS driver
[    2.495389] of_get_named_gpiod_flags: can't parse 'samsung,vbus-gpio' property of node '/usb@12110000[0]'
[    2.504954] exynos-ehci 12110000.usb: EHCI Host Controller
[    2.510258] exynos-ehci 12110000.usb: new USB bus registered, assigned bus number 5
[    2.517977] exynos-ehci 12110000.usb: irq 103, io mem 0x12110000
[    2.533639] exynos-ehci 12110000.usb: USB 2.0 started, EHCI 1.00
[    2.538278] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
[    2.544950] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.552148] usb usb5: Product: EHCI Host Controller
[    2.557005] usb usb5: Manufacturer: Linux 3.18.0-rc5-next-20141121-00003-g9af3770 ehci_hcd
[    2.565246] usb usb5: SerialNumber: 12110000.usb
[    2.570384] hub 5-0:1.0: USB hub found
[    2.573580] hub 5-0:1.0: 3 ports detected
[    2.578141] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    2.583828] ohci-exynos: OHCI EXYNOS driver
[    2.588049] exynos-ohci 12120000.usb: USB Host Controller
[    2.593286] exynos-ohci 12120000.usb: new USB bus registered, assigned bus number 6
[    2.600978] exynos-ohci 12120000.usb: irq 103, io mem 0x12120000
[    2.662768] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[    2.668090] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.675877] usb usb6: Product: USB Host Controller
[    2.680061] usb usb6: Manufacturer: Linux 3.18.0-rc5-next-20141121-00003-g9af3770 ohci_hcd
[    2.688302] usb usb6: SerialNumber: 12120000.usb
[    2.693420] hub 6-0:1.0: USB hub found
[    2.696651] hub 6-0:1.0: 3 ports detected
[    2.701254] usbcore: registered new interface driver usb-storage
[    2.707092] mousedev: PS/2 mouse device common for all mice
[    2.712580] input: cros-ec-spi as /devices/platform/12d40000.spi/spi_master/spi2/spi2.0/cros-ec-keyb.1/input/input0
[    2.723453] s3c-rtc 101e0000.rtc: rtc disabled, re-enabling
[    2.728386] s3c-rtc 101e0000.rtc: rtc core: registered s3c as rtc0
[    2.734583] i2c /dev entries driver
[    2.742883] max77686 4-0009: Failed to find supply inb1
[    2.746765] max77802-pmic max77802-pmic: regulator init failed for 0
[    2.753009] platform max77802-pmic: Driver max77802-pmic requests probe deferral
[    2.763141] rtc (null): read_time: fail to read
[    2.766383] max77802-rtc max77802-rtc: rtc core: registered max77802-rtc as rtc1
[    2.796251] atmel_mxt_ts 8-004b: Direct firmware load for maxtouch.cfg failed with error -2
[    2.803977] atmel_mxt_ts 8-004b: Invalid object type T9
[    2.808361] atmel_mxt_ts 8-004b: Failed to initialize T9 resolution
[    2.814957] input: Atmel maXTouch Touchpad as /devices/platform/12e00000.i2c/i2c-8/8-004b/input/input1
[    2.824243] atmel_mxt_ts 8-004b: Family: 130 Variant: 44 Firmware V3.0.AA Objects: 34
[    2.831772] tpm_i2c_infineon 9-0020: 1.2 TPM (device-id 0x1A)
[    2.858106] tpm_i2c_infineon 9-0020: Issuing TPM_STARTUP
[    3.040391] tps65090 20-0048: No cache defaults, reading back from HW
[    3.049969] of_get_named_gpiod_flags: can't parse 'dcdc-ext-control-gpios' property of node '/spi@12d40000/cros-ec@0/i2c-tunnel/power-regulator@48[0]'
[    3.061971] of_get_named_gpiod_flags: can't parse 'dcdc-ext-control-gpios' property of node '/spi@12d40000/cros-ec@0/i2c-tunnel/power-regulator@48[0]'
[    3.075431] of_get_named_gpiod_flags: can't parse 'dcdc-ext-control-gpios' property of node '/spi@12d40000/cros-ec@0/i2c-tunnel/power-regulator@48[0]'
[    3.089011] TPS65090_RAILSDCDC1: supplied by vbat-supply
[    3.095771] TPS65090_RAILSDCDC2: supplied by vbat-supply
[    3.101225] TPS65090_RAILSDCDC3: supplied by vbat-supply
[    3.106671] vcd_led: supplied by vbat-supply
[    3.115488] video_mid: supplied by TPS65090_RAILSDCDC1
[    3.125085] wwan_r: supplied by TPS65090_RAILSDCDC2
[    3.133326] sdcard: supplied by TPS65090_RAILSDCDC2
[    3.138366] camout: supplied by TPS65090_RAILSDCDC2
[    3.143400] lcd_vdd: supplied by TPS65090_RAILSDCDC2
[    3.152897] video_mid_1a: supplied by TPS65090_RAILSDCDC1
[    3.158448] TPS65090_RAILSLDO1: supplied by vbat-supply
[    3.162407] TPS65090_RAILSLDO2: supplied by vbat-supply
[    3.263019] sbs-battery 20-000b: sbs-battery: battery gas gauge device registered
[    3.279144] 10060000.tmu supply vtmu not found, using dummy regulator
[    3.284706] exynos-tmu 10060000.tmu: Exynos: Thermal zone(therm_zone0) registered
[    3.291663] 10064000.tmu supply vtmu not found, using dummy regulator
[    3.298601] exynos-tmu 10064000.tmu: Exynos: Thermal zone(therm_zone0) registered
[    3.305531] 10068000.tmu supply vtmu not found, using dummy regulator
[    3.312464] exynos-tmu 10068000.tmu: Exynos: Thermal zone(therm_zone0) registered
[    3.319413] 1006c000.tmu supply vtmu not found, using dummy regulator
[    3.326352] exynos-tmu 1006c000.tmu: Exynos: Thermal zone(therm_zone0) registered
[    3.333293] 100a0000.tmu supply vtmu not found, using dummy regulator
[    3.340229] exynos-tmu 100a0000.tmu: Exynos: Thermal zone(therm_zone0) registered
[    3.348091] s3c2410-wdt 101d0000.watchdog: watchdog inactive, reset disabled, irq disabled
[    3.356183] device-mapper: ioctl: 4.29.0-ioctl (2014-10-28) initialised: dm-devel@redhat.com
[    3.363784] Driver 'mmcblk' needs updating - please use bus_type methods
[    3.370497] sdhci: Secure Digital Host Controller Interface driver
[    3.376610] sdhci: Copyright(c) Pierre Ossman
[    3.381159] Synopsys Designware Multimedia Card Interface Driver
[    3.387693] dwmmc_exynos 12200000.mmc: IDMAC supports 32-bit address mode.
[    3.393834] dwmmc_exynos 12200000.mmc: Using internal DMA controller.
[    3.400208] dwmmc_exynos 12200000.mmc: Version ID is 250a
[    3.405598] dwmmc_exynos 12200000.mmc: DW MMC controller at irq 107, 64 bit host data width, 64 deep fifo
[    3.415148] dwmmc_exynos 12200000.mmc: No vmmc regulator found
[    3.420940] dwmmc_exynos 12200000.mmc: No vqmmc regulator found
[    3.426897] dwmmc_exynos 12200000.mmc: GPIO lookup for consumer wp
[    3.432980] dwmmc_exynos 12200000.mmc: using device tree for GPIO lookup
[    3.439661] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@12200000[0]'
[    3.448471] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@12200000[0]'
[    3.457106] dwmmc_exynos 12200000.mmc: using lookup tables for GPIO lookup
[    3.463958] dwmmc_exynos 12200000.mmc: lookup for GPIO wp failed
[    3.498736] dwmmc_exynos 12200000.mmc: 1 slots initialized
[    3.503553] dwmmc_exynos 12220000.mmc: IDMAC supports 32-bit address mode.
[    3.509761] dwmmc_exynos 12220000.mmc: Using internal DMA controller.
[    3.516048] dwmmc_exynos 12220000.mmc: Version ID is 250a
[    3.521459] dwmmc_exynos 12220000.mmc: DW MMC controller at irq 109, 64 bit host data width, 64 deep fifo
[    3.530999] dwmmc_exynos 12220000.mmc: No vmmc regulator found
[    3.536823] dwmmc_exynos 12220000.mmc: No vqmmc regulator found
[    3.541634] mmc0: BKOPS_EN bit is not set
[    3.545451] mmc_host mmc0: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0)
[    3.546642] mmc0: new HS200 MMC card at address 0001
[    3.561623] dwmmc_exynos 12220000.mmc: GPIO lookup for consumer cd
[    3.561632] mmcblk0: mmc0:0001 MAG2GC 14.5 GiB 
[    3.572378] dwmmc_exynos 12220000.mmc: using device tree for GPIO lookup
[    3.572386] mmcblk0boot0: mmc0:0001 MAG2GC partition 1 4.00 MiB
[    3.583782] mmcblk0boot1: mmc0:0001 MAG2GC partition 2 4.00 MiB
[    3.583987] mmcblk0rpmb: mmc0:0001 MAG2GC partition 3 4.00 MiB
[    3.588486]  mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12
[    3.602170] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/mmc@12220000[0]'
[    3.610933] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/mmc@12220000[0]'
[    3.619607] dwmmc_exynos 12220000.mmc: using lookup tables for GPIO lookup
[    3.626462] dwmmc_exynos 12220000.mmc: lookup for GPIO cd failed
[    3.632449] dwmmc_exynos 12220000.mmc: GPIO lookup for consumer wp
[    3.638631] dwmmc_exynos 12220000.mmc: using device tree for GPIO lookup
[    3.645286] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@12220000[0]'
[    3.654048] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@12220000[0]'
[    3.662721] dwmmc_exynos 12220000.mmc: using lookup tables for GPIO lookup
[    3.669576] dwmmc_exynos 12220000.mmc: lookup for GPIO wp failed
[    3.703685] dwmmc_exynos 12220000.mmc: 1 slots initialized
[    3.709351] usbcore: registered new interface driver usbhid
[    3.713441] usbhid: USB HID core driver
[    3.718075] exynos-adc 12d10000.adc: failed getting regulator, err = -517
[    3.724057] platform 12d10000.adc: Driver exynos-adc requests probe deferral
[    3.739801] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[    3.748109] mmc1: new high speed SDHC card at address 59b4
[    3.753816] max98090 7-0010: MAX98091 REVID=0x51
[    3.754097] mmcblk1: mmc1:59b4 00000 7.34 GiB 
[    3.756122]  mmcblk1: p1
[    3.766029] max98090 7-0010: Conditional paths are not supported for supply widgets (DMICL_ENA -> [DMIC] -> DMIC Mux)
[    3.775654] max98090 7-0010: ASoC: no dapm match for DMICL_ENA --> DMIC --> DMIC Mux
[    3.783371] max98090 7-0010: ASoC: Failed to add route DMICL_ENA -> DMIC -> DMIC Mux
[    3.791096] max98090 7-0010: Conditional paths are not supported for supply widgets (DMICR_ENA -> [DMIC] -> DMIC Mux)
[    3.801688] max98090 7-0010: ASoC: no dapm match for DMICR_ENA --> DMIC --> DMIC Mux
[    3.809437] max98090 7-0010: ASoC: Failed to add route DMICR_ENA -> DMIC -> DMIC Mux
[    3.817175] max98090 7-0010: Control not supported for path STENL Mux -> [NULL] -> DACL
[    3.825098] max98090 7-0010: ASoC: no dapm match for STENL Mux --> NULL --> DACL
[    3.832476] max98090 7-0010: ASoC: Failed to add route STENL Mux -> NULL -> DACL
[    3.839849] max98090 7-0010: Control not supported for path STENL Mux -> [NULL] -> DACR
[    3.847826] max98090 7-0010: ASoC: no dapm match for STENL Mux --> NULL --> DACR
[    3.855202] max98090 7-0010: ASoC: Failed to add route STENL Mux -> NULL -> DACR
[    3.864009] snow-audio sound: HiFi <-> 3830000.i2s mapping ok
[    3.868717] samsung-i2s 3830000.i2s: We don't serve that!
[    3.875710] TCP: cubic registered
[    3.877546] NET: Registered protocol family 17
[    3.882013] NET: Registered protocol family 15
[    3.886699] Registering SWP/SWPB emulation handler
[    3.891185] big.LITTLE switcher initializing
[    3.895426] CPU0 paired with CPU7
[    3.898721] CPU1 paired with CPU6
[    3.902003] CPU2 paired with CPU5
[    3.905314] CPU3 paired with CPU4
[    3.908597] GIC ID for CPU 0 cluster 0 is 0
[    3.912775] GIC ID for CPU 1 cluster 0 is 1
[    3.916938] GIC ID for CPU 2 cluster 0 is 2
[    3.921102] GIC ID for CPU 3 cluster 0 is 3
[    3.925268] GIC ID for CPU 0 cluster 1 is 4
[    3.964057] IRQ160 no longer affine to CPU4
[    3.964498] CPU4: shutdown
[    3.970271] GIC ID for CPU 1 cluster 1 is 5
[    4.014019] IRQ161 no longer affine to CPU5
[    4.014410] CPU5: shutdown
[    4.020163] GIC ID for CPU 2 cluster 1 is 6
[    4.054007] IRQ162 no longer affine to CPU6
[    4.054389] CPU6: shutdown
[    4.060130] GIC ID for CPU 3 cluster 1 is 7
[    4.099001] IRQ163 no longer affine to CPU7
[    4.099381] CPU7: shutdown
[    4.105321] big.LITTLE switcher initialized
[    4.109767] pwm-backlight backlight: GPIO lookup for consumer enable
[    4.115290] pwm-backlight backlight: using device tree for GPIO lookup
[    4.121796] of_get_named_gpiod_flags: parsed 'enable-gpios' property of node '/backlight[0]' - status (0)
[    4.133419] platform 145b0000.dp-controller: Driver exynos-dp requests probe deferral
[    4.139967] panel-simple panel: GPIO lookup for consumer enable
[    4.145674] panel-simple panel: using device tree for GPIO lookup
[    4.151761] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/panel[0]'
[    4.160248] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/panel[0]'
[    4.168663] panel-simple panel: using lookup tables for GPIO lookup
[    4.174908] panel-simple panel: lookup for GPIO enable failed
[    4.183012] vdd_mif: supplied by TPS65090_RAILSDCDC2
[    4.187126] vdd_arm: supplied by TPS65090_RAILSDCDC1
[    4.192072] vdd_int: supplied by TPS65090_RAILSDCDC2
[    4.197010] vdd_g3d: supplied by TPS65090_RAILSDCDC2
[    4.201853] vdd_1v2: supplied by TPS65090_RAILSDCDC1
[    4.206898] vdd_kfc: supplied by TPS65090_RAILSDCDC2
[    4.211744] vdd_1v35: supplied by TPS65090_RAILSDCDC1
[    4.216780] vdd_emmc: supplied by TPS65090_RAILSDCDC1
[    4.221803] vdd_2v: supplied by TPS65090_RAILSDCDC1
[    4.226666] vdd_1v8: supplied by TPS65090_RAILSDCDC1
[    4.231492] vdd_1v0: supplied by vdd_1v35
[    4.235473] vdd_1v2_2: supplied by vdd_1v35
[    4.239647] vdd_1v8_3: supplied by vdd_2v
[    4.243633] vdd_sd: supplied by TPS65090_RAILSDCDC2
[    4.248466] vdd_1v8_5: supplied by vdd_2v
[    4.252481] vdd_1v8_6: supplied by vdd_2v
[    4.256468] vdd_1v8_7: supplied by vdd_2v
[    4.260463] vdd_ldo8: supplied by vdd_1v2
[    4.264444] vdd_ldo9: supplied by vdd_2v
[    4.268339] vdd_ldo10: supplied by vdd_2v
[    4.272343] vdd_ldo11: supplied by vdd_2v
[    4.276327] vdd_ldo12: supplied by TPS65090_RAILSDCDC2
[    4.281458] vdd_ldo13: supplied by vdd_2v
[    4.285438] vdd_ldo14: supplied by vdd_2v
[    4.289429] vdd_ldo15: supplied by vdd_1v2
[    4.293493] vdd_g3ds: supplied by vdd_1v35
[    4.297584] ldo_18: supplied by vdd_2v
[    4.301315] ldo_19: supplied by vdd_2v
[    4.305136] ldo_20: supplied by vdd_2v
[    4.308783] ldo_21: supplied by TPS65090_RAILSDCDC2
[    4.313640] ldo_23: supplied by TPS65090_RAILSDCDC2
[    4.318467] ldo_24: supplied by TPS65090_RAILSDCDC2
[    4.323353] ldo_25: supplied by TPS65090_RAILSDCDC2
[    4.328294] ldo_26: supplied by TPS65090_RAILSDCDC2
[    4.333065] ldo_27: supplied by vdd_1v35
[    4.336971] ldo_28: supplied by vdd_2v
[    4.340698] ldo_29: supplied by vdd_2v
[    4.344434] vdd_mifs: supplied by vdd_1v35
[    4.348490] ldo_32: supplied by TPS65090_RAILSDCDC2
[    4.353364] ldo_33: supplied by TPS65090_RAILSDCDC2
[    4.358232] ldo_34: supplied by TPS65090_RAILSDCDC2
[    4.363076] ldo_35: supplied by vdd_1v35
[    4.368720] exynos-drm exynos-drm: bound 14400000.fimd (ops fimd_component_ops)
[    4.374690] of_get_named_gpiod_flags: parsed 'samsung,hpd-gpio' property of node '/dp-controller@145B0000[0]' - status (0)
[    4.386129] exynos-drm exynos-drm: bound 145b0000.dp-controller (ops exynos_dp_ops)
[    4.393226] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    4.399819] [drm] No driver support for vblank timestamp query.
[    4.524628] exynos-dp 145b0000.dp-controller: EDID data does not include any extensions.
[    4.529553] exynos-dp 145b0000.dp-controller: EDID Read success!
[    4.531488] exynos-dp 145b0000.dp-controller: Link Training Clock Recovery success
[    4.533015] exynos-dp 145b0000.dp-controller: Link Training success!
[    4.617151] exynos-dp 145b0000.dp-controller: EDID data does not include any extensions.
[    4.622077] exynos-dp 145b0000.dp-controller: EDID Read success!
[    4.624013] exynos-dp 145b0000.dp-controller: Link Training Clock Recovery success
[    4.625540] exynos-dp 145b0000.dp-controller: Link Training success!
[    4.675230] Console: switching to colour frame buffer device 274x77
[    4.745570] exynos-drm exynos-drm: fb0:  frame buffer device
[    4.751208] exynos-drm exynos-drm: registered panic notifier
[    4.768640] [drm] Initialized exynos 1.0.0 20110530 on minor 0
[    4.773209] of_get_named_gpiod_flags: parsed 'gpios' property of node '/gpio-keys/power[0]' - status (0)
[    4.782512] gpio-18 (Power): gpiod_set_debounce: missing set() or set_debounce() operations
[    4.782865] power-domain: Power-off latency exceeded, new value 387792 ns
[    4.782890] power-domain: Power-off latency exceeded, new value 212375 ns
[    4.783091] power-domain: Power-off latency exceeded, new value 178667 ns
[    4.783225] power-domain: Power-off latency exceeded, new value 283500 ns
[    4.818134] input: gpio-keys as /devices/platform/gpio-keys/input/input2
[    4.824848] s3c-rtc 101e0000.rtc: setting system clock to 2008-01-01 08:53:13 UTC (1199177593)
[    4.855533] vdd_1v2_2: disabling
[    4.857392] TPS65090_RAILSLDO2: disabling
[    4.861291] TPS65090_RAILSLDO1: disabling
[    4.867006] TPS65090_RAILSDCDC3: disabling
[    4.870358] ALSA device list:
[    4.872571]   #0: Peach-Pi-I2S-MAX98091
[    4.878093] EXT3-fs (mmcblk1p1): error: couldn't mount because of unsupported optional features (240)
[    4.886589] EXT2-fs (mmcblk1p1): error: couldn't mount because of unsupported optional features (244)
[    4.896921] EXT4-fs (mmcblk1p1): INFO: recovery required on readonly filesystem
[    4.902762] EXT4-fs (mmcblk1p1): write access will be enabled during recovery
[    4.963017] random: nonblocking pool is initialized
[    4.967471] EXT4-fs (mmcblk1p1): recovery complete
[    4.975076] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data mode. Opts: (null)
[    4.981709] VFS: Mounted root (ext4 filesystem) readonly on device 179:65.
[    4.992284] devtmpfs: mounted
[    4.993925] Freeing unused kernel memory: 300K (c061d000 - c0668000)
[    5.111865] EXT4-fs (mmcblk1p1): re-mounted. Opts: data=ordered
Initializing random number generator... done.
Starting network...

Welcome to SmallRoot FS
ID : root
PW :
Samsung login: root
# uname -a
# Linux Samsung 3.18.0-rc5-next-20141121-00003-g9af3770 #7 SMP PREEMPT Mon Nov 24 15:50:30 IST 2014 armv7l GNU/Linux
# # 
# # 
#

[-- Attachment #4: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: Peach Pi/Pit boot failures in linux-next (was Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init)

[Javier Martinez Canillas]

Hello Krzysztof,

On 11/24/2014 11:13 AM, Krzysztof Kozlowski wrote:
>> Ok, please let me know if you need anything else from me.
> 
> Thanks! I replied before seeing your response. Anyway the dmatests are
> the same I got on Arndale Octa.
> 
> It seems that mau_epll has to be enabled... or something is wrong with
> clock hierarchy.
>

Another strange thing is that the problem does not happen for some people
using the same board, kernel and config options. For example Vivek and Ajay
report that they can't reproduce the issue on a Peach Pi using next-20141121
and exynos_defconfig without using clk_ignore_unused.

Best regards,
Javier

Re: Peach Pi/Pit boot failures in linux-next (was Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init)

[Krzysztof Kozlowski]

On pon, 2014-11-24 at 12:07 +0100, Javier Martinez Canillas wrote:
> Hello Krzysztof,
> 
> On 11/24/2014 11:13 AM, Krzysztof Kozlowski wrote:
> >> Ok, please let me know if you need anything else from me.
> > 
> > Thanks! I replied before seeing your response. Anyway the dmatests are
> > the same I got on Arndale Octa.
> > 
> > It seems that mau_epll has to be enabled... or something is wrong with
> > clock hierarchy.
> >
> 
> Another strange thing is that the problem does not happen for some people
> using the same board, kernel and config options. For example Vivek and Ajay
> report that they can't reproduce the issue on a Peach Pi using next-20141121
> and exynos_defconfig without using clk_ignore_unused.

Maybe they have different bootloader which messes here by enabling some
clock?

Anyway it is reproducible on at least some Arndale Octa (Kevin's and
mine) and Peach Pi boards (yours).

Best regards,
Krzysztof

Re: Peach Pi/Pit boot failures in linux-next (was Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init)

[Javier Martinez Canillas]

[adding Tushar Behera and Doug Anderson to cc list]

Hello,

On 11/24/2014 12:12 PM, Krzysztof Kozlowski wrote:
> On pon, 2014-11-24 at 12:07 +0100, Javier Martinez Canillas wrote:
>> Hello Krzysztof,
>> 
>> > It seems that mau_epll has to be enabled... or something is wrong with
>> > clock hierarchy.
>> >
>> 
>> Another strange thing is that the problem does not happen for some people
>> using the same board, kernel and config options. For example Vivek and Ajay
>> report that they can't reproduce the issue on a Peach Pi using next-20141121
>> and exynos_defconfig without using clk_ignore_unused.
> 
> Maybe they have different bootloader which messes here by enabling some
> clock?
> 
> Anyway it is reproducible on at least some Arndale Octa (Kevin's and
> mine) and Peach Pi boards (yours).
> 

This issue started to look extremely familiar to me so I searched in
my mail inbox and found that the same problem was previously reported
by Kevin a couple of months ago [0] and Tushar provided a fix [1].

I tested linux-next + [1] and that indeed fixes the hang on Peach.

To save you a click, the problem as explained by Tushar is that the
AUDSS mux has two parents: XXTI crystal and MAU_EPLL clock. But when
the output of AUDSS mux is gated, no operations can be made on the
clocks provided by MAU block. For some reason the kernel just oops
so it seems to be a H/W errata?

Mike was not fond about the solution proposed in [1] but something
along those lines would be needed maybe Tushar can comment on that.

Vivek and Ajay,

As explained in [0], you are not facing this issue because your RW
U-Boot seems to predate when audio support was enabled by default.

Can you try executing "sound init" in the U-Boot prompt and see if
that triggers the hang for you?

Best regards,
Javier

[0]: http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/262259.html
[1]: http://www.spinics.net/lists/arm-kernel/msg337970.html

Re: Peach Pi/Pit boot failures in linux-next (was Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init)

[Vivek Gautam]

On Mon, Nov 24, 2014 at 6:46 PM, Javier Martinez Canillas
<javier.martinez@collabora.co.uk> wrote:
> [adding Tushar Behera and Doug Anderson to cc list]
>
> Hello,
>
> On 11/24/2014 12:12 PM, Krzysztof Kozlowski wrote:
>> On pon, 2014-11-24 at 12:07 +0100, Javier Martinez Canillas wrote:
>>> Hello Krzysztof,
>>>
>>> > It seems that mau_epll has to be enabled... or something is wrong with
>>> > clock hierarchy.
>>> >
>>>
>>> Another strange thing is that the problem does not happen for some people
>>> using the same board, kernel and config options. For example Vivek and Ajay
>>> report that they can't reproduce the issue on a Peach Pi using next-20141121
>>> and exynos_defconfig without using clk_ignore_unused.
>>
>> Maybe they have different bootloader which messes here by enabling some
>> clock?
>>
>> Anyway it is reproducible on at least some Arndale Octa (Kevin's and
>> mine) and Peach Pi boards (yours).
>>
>
> This issue started to look extremely familiar to me so I searched in
> my mail inbox and found that the same problem was previously reported
> by Kevin a couple of months ago [0] and Tushar provided a fix [1].
>
> I tested linux-next + [1] and that indeed fixes the hang on Peach.
>
> To save you a click, the problem as explained by Tushar is that the
> AUDSS mux has two parents: XXTI crystal and MAU_EPLL clock. But when
> the output of AUDSS mux is gated, no operations can be made on the
> clocks provided by MAU block. For some reason the kernel just oops
> so it seems to be a H/W errata?
>
> Mike was not fond about the solution proposed in [1] but something
> along those lines would be needed maybe Tushar can comment on that.
>
> Vivek and Ajay,
>
> As explained in [0], you are not facing this issue because your RW
> U-Boot seems to predate when audio support was enabled by default.

We are using one from Google's build-bot:
"U-Boot 2013.04-g1eced1c (Nov 20 2014 - 21:27:46) for Peach"

>
> Can you try executing "sound init" in the U-Boot prompt and see if
> that triggers the hang for you?

But yes, doing *sound init* do trigger the hang.

>
> Best regards,
> Javier
>
> [0]: http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/262259.html
> [1]: http://www.spinics.net/lists/arm-kernel/msg337970.html



-- 
Best Regards
Vivek Gautam
Samsung R&D Institute, Bangalore
India

Re: Peach Pi/Pit boot failures in linux-next (was Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init)

[Krzysztof Kozlowski]

On pon, 2014-11-24 at 14:16 +0100, Javier Martinez Canillas wrote:
> [adding Tushar Behera and Doug Anderson to cc list]
> 
> Hello,
> 
> On 11/24/2014 12:12 PM, Krzysztof Kozlowski wrote:
> > On pon, 2014-11-24 at 12:07 +0100, Javier Martinez Canillas wrote:
> >> Hello Krzysztof,
> >> 
> >> > It seems that mau_epll has to be enabled... or something is wrong with
> >> > clock hierarchy.
> >> >
> >> 
> >> Another strange thing is that the problem does not happen for some people
> >> using the same board, kernel and config options. For example Vivek and Ajay
> >> report that they can't reproduce the issue on a Peach Pi using next-20141121
> >> and exynos_defconfig without using clk_ignore_unused.
> > 
> > Maybe they have different bootloader which messes here by enabling some
> > clock?
> > 
> > Anyway it is reproducible on at least some Arndale Octa (Kevin's and
> > mine) and Peach Pi boards (yours).
> > 
> 
> This issue started to look extremely familiar to me so I searched in
> my mail inbox and found that the same problem was previously reported
> by Kevin a couple of months ago [0] and Tushar provided a fix [1].
> 
> I tested linux-next + [1] and that indeed fixes the hang on Peach.
> 
> To save you a click, the problem as explained by Tushar is that the
> AUDSS mux has two parents: XXTI crystal and MAU_EPLL clock. But when
> the output of AUDSS mux is gated, no operations can be made on the
> clocks provided by MAU block. For some reason the kernel just oops
> so it seems to be a H/W errata?
> 
> Mike was not fond about the solution proposed in [1] but something
> along those lines would be needed maybe Tushar can comment on that.
> 
> Vivek and Ajay,
> 
> As explained in [0], you are not facing this issue because your RW
> U-Boot seems to predate when audio support was enabled by default.
> 
> Can you try executing "sound init" in the U-Boot prompt and see if
> that triggers the hang for you?
> 
> Best regards,
> Javier
> 
> [0]: http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/262259.html
> [1]: http://www.spinics.net/lists/arm-kernel/msg337970.html

Thank you for digging this out.

It looks like mau_epll is needed to keep audio powered on...

Disabling the adma device (from DT) helps. But then
$ cat /sys/kernel/debug/clk/clk_summary
stops working. Just like ISP clocks (need to keep ISP domain on to read clk_summary).

When mau_epll is disabled all of reads and writes to Audio registers
fail. When system tries to disable unused adma clock it stucks because
Audio domain is off...

Still this is strange.

Best regards,
Krzysztof

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Andreas Färber]

Hi,

Am 24.11.2014 um 11:05 schrieb Javier Martinez Canillas:
> On 11/21/2014 09:57 PM, Javier Martinez Canillas wrote:
>> On 11/21/2014 06:32 PM, Ajay kumar wrote:
>>> I have rebased my bridge series on top of linux-next.
>>>
>>> This is my git log:
>>> 4b38a6f Revert "Revert "ARM: exynos_defconfig: Enable options for
>>> display panel support""
>>> 6fb39a7 ARM: dts: peach-pit: represent the connection between bridge
>>> and panel using videoport and endpoints
>>> aee649c ARM: dts: snow: represent the connection between bridge and
>>> panel using videoport and endpoints
>>> 5b76d8d drm/bridge: Add i2c based driver for ps8622/ps8625 bridge
>>> 581257f Documentation: bridge: Add documentation for ps8622 DT properties
>>> 178e8b9 Documentation: devicetree: Add vendor prefix for parade
>>> 0ceea75 Documentation: drm: bridge: move to video/bridge
>>> f143e2e drm/bridge: ptn3460: use gpiod interface
>>> 2d5cb9d drm/bridge: ptn3460: probe connector at the end of bridge attach
>>> 32ac563 drm/bridge: ptn3460: support drm_panel
>>> 91c6c30 drm/exynos: dp: support drm_bridge
>>> 7eea7eb drm/bridge: ptn3460: Convert to i2c driver model
>>> 602f343 drm/bridge: make bridge registration independent of drm flow
>>> 14c7143 drm/bridge: do not pass drm_bridge_funcs to drm_bridge_init
>>> 2c01ac4 drm/bridge: ptn3460: Few trivial cleanups
>>> 7415f6c arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
>>> 28655d1 drm/exynos: Move platform drivers registration to module init
>>> ed6778a Add linux-next specific files for 20141121
>>>
>>> I have attached the rebased patches as well.
>>> I tested it on snow, peach_pit and peach_pi without *clk_ignore_unused*.
>>> Display is totally fine with exynos_defconfig (booting is fine even
>>> with CONFIG_SND_SOC_SNOW=y)
>>
>> Thanks for forward porting your patches to linux-next. Unfortunately I
>> won't have time to test them until Monday but I wonder why you didn't
>> have the boot issues that we have with next-20141121.
> 
> I tested your ToT patches on top of next-20141121, this is my git log:
> 
> 93fe3d7 Revert "Revert "ARM: exynos_defconfig: Enable options for display panel support""
> 552f74e ARM: dts: peach-pit: represent the connection between bridge and panel using videoport and endpoints
> dbbc293 ARM: dts: snow: represent the connection between bridge and panel using videoport and endpoints
> d8687f8 drm/bridge: Add i2c based driver for ps8622/ps8625 bridge
> f29a649 Documentation: bridge: Add documentation for ps8622 DT properties
> 6ade887 Documentation: devicetree: Add vendor prefix for parade
> d81c42d Documentation: drm: bridge: move to video/bridge
> 50b9828 drm/bridge: ptn3460: use gpiod interface
> 1274c56 drm/bridge: ptn3460: probe connector at the end of bridge attach
> f3cf063 drm/bridge: ptn3460: support drm_panel
> cab682b drm/exynos: dp: support drm_bridge
> 6e78916 drm/bridge: ptn3460: Convert to i2c driver model
> 93f4b5f drm/bridge: make bridge registration independent of drm flow
> 81a038f drm/bridge: do not pass drm_bridge_funcs to drm_bridge_init
> eb6996e drm/bridge: ptn3460: Few trivial cleanups
> c41fa5d arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
> 51b2c75 drm/exynos: Move platform drivers registration to module init
> ed6778a Add linux-next specific files for 20141121
>  
>> I found that the commit ae43b32 ("ARM: 8202/1: dmaengine: pl330: Add
>> runtime Power Management support v12") had to be reverted in order to
>> boot linux-next.
>>
> 
> Display works but I needed to revert the mentioned commit, otherwise
> the boot hangs as reported before. I'm using exynos_defconfig and this
> kernel command line:
> 
> console=ttySAC3,115200N8 debug earlyprintk root=/dev/mmcblk1p2 rootwait rw

I tested Spring with next-20141124, and finally got it to work! :)
Thanks a lot, Ajay and Javier!

To be on the safe side, I reverted the patch pointed out by Javier and
was still using clk_ignore_unused.

Ajay, note that your rebased Snow patch has the last hunk indented one
level too deep.

I'll post a cleaned-up bridge patch for Spring later.

Cheers,
Andreas

-- 
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg

Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init

[Ajay kumar]

Hi Andreas,

On Mon, Nov 24, 2014 at 8:35 PM, Andreas Färber <afaerber@suse.de> wrote:
> Hi,
>
> Am 24.11.2014 um 11:05 schrieb Javier Martinez Canillas:
>> On 11/21/2014 09:57 PM, Javier Martinez Canillas wrote:
>>> On 11/21/2014 06:32 PM, Ajay kumar wrote:
>>>> I have rebased my bridge series on top of linux-next.
>>>>
>>>> This is my git log:
>>>> 4b38a6f Revert "Revert "ARM: exynos_defconfig: Enable options for
>>>> display panel support""
>>>> 6fb39a7 ARM: dts: peach-pit: represent the connection between bridge
>>>> and panel using videoport and endpoints
>>>> aee649c ARM: dts: snow: represent the connection between bridge and
>>>> panel using videoport and endpoints
>>>> 5b76d8d drm/bridge: Add i2c based driver for ps8622/ps8625 bridge
>>>> 581257f Documentation: bridge: Add documentation for ps8622 DT properties
>>>> 178e8b9 Documentation: devicetree: Add vendor prefix for parade
>>>> 0ceea75 Documentation: drm: bridge: move to video/bridge
>>>> f143e2e drm/bridge: ptn3460: use gpiod interface
>>>> 2d5cb9d drm/bridge: ptn3460: probe connector at the end of bridge attach
>>>> 32ac563 drm/bridge: ptn3460: support drm_panel
>>>> 91c6c30 drm/exynos: dp: support drm_bridge
>>>> 7eea7eb drm/bridge: ptn3460: Convert to i2c driver model
>>>> 602f343 drm/bridge: make bridge registration independent of drm flow
>>>> 14c7143 drm/bridge: do not pass drm_bridge_funcs to drm_bridge_init
>>>> 2c01ac4 drm/bridge: ptn3460: Few trivial cleanups
>>>> 7415f6c arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
>>>> 28655d1 drm/exynos: Move platform drivers registration to module init
>>>> ed6778a Add linux-next specific files for 20141121
>>>>
>>>> I have attached the rebased patches as well.
>>>> I tested it on snow, peach_pit and peach_pi without *clk_ignore_unused*.
>>>> Display is totally fine with exynos_defconfig (booting is fine even
>>>> with CONFIG_SND_SOC_SNOW=y)
>>>
>>> Thanks for forward porting your patches to linux-next. Unfortunately I
>>> won't have time to test them until Monday but I wonder why you didn't
>>> have the boot issues that we have with next-20141121.
>>
>> I tested your ToT patches on top of next-20141121, this is my git log:
>>
>> 93fe3d7 Revert "Revert "ARM: exynos_defconfig: Enable options for display panel support""
>> 552f74e ARM: dts: peach-pit: represent the connection between bridge and panel using videoport and endpoints
>> dbbc293 ARM: dts: snow: represent the connection between bridge and panel using videoport and endpoints
>> d8687f8 drm/bridge: Add i2c based driver for ps8622/ps8625 bridge
>> f29a649 Documentation: bridge: Add documentation for ps8622 DT properties
>> 6ade887 Documentation: devicetree: Add vendor prefix for parade
>> d81c42d Documentation: drm: bridge: move to video/bridge
>> 50b9828 drm/bridge: ptn3460: use gpiod interface
>> 1274c56 drm/bridge: ptn3460: probe connector at the end of bridge attach
>> f3cf063 drm/bridge: ptn3460: support drm_panel
>> cab682b drm/exynos: dp: support drm_bridge
>> 6e78916 drm/bridge: ptn3460: Convert to i2c driver model
>> 93f4b5f drm/bridge: make bridge registration independent of drm flow
>> 81a038f drm/bridge: do not pass drm_bridge_funcs to drm_bridge_init
>> eb6996e drm/bridge: ptn3460: Few trivial cleanups
>> c41fa5d arm: dts: Exynos5: Use pmu_system_controller phandle for dp phy
>> 51b2c75 drm/exynos: Move platform drivers registration to module init
>> ed6778a Add linux-next specific files for 20141121
>>
>>> I found that the commit ae43b32 ("ARM: 8202/1: dmaengine: pl330: Add
>>> runtime Power Management support v12") had to be reverted in order to
>>> boot linux-next.
>>>
>>
>> Display works but I needed to revert the mentioned commit, otherwise
>> the boot hangs as reported before. I'm using exynos_defconfig and this
>> kernel command line:
>>
>> console=ttySAC3,115200N8 debug earlyprintk root=/dev/mmcblk1p2 rootwait rw
>
> I tested Spring with next-20141124, and finally got it to work! :)
That's great to hear!

> Thanks a lot, Ajay and Javier!
>
> To be on the safe side, I reverted the patch pointed out by Javier and
> was still using clk_ignore_unused.
>
> Ajay, note that your rebased Snow patch has the last hunk indented one
> level too deep.
Ahh, right. I just saw that. I am not sure if these patches go in just
like this,
or I need to rebase on top of kukjin's for-next or some other branch/tree!
Will take care of this, then.

>
> I'll post a cleaned-up bridge patch for Spring later.
Ok, AFAIK, peach_pit DT properties can be reused.

Ajay