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
On 11/24/2014 10:38 AM, Javier Martinez Canillas wrote:
Hell Krzysztof
An unfortunate typo, this was Hello of course :-)
Best regards,
Javier
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info
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
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:
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
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
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
[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.
On Mon, Nov 24, 2014 at 6:46 PM, Javier Martinez Canillas
javier.marti...@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,
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
Hi Andreas,
On Mon, Nov 24, 2014 at 8:35 PM, Andreas Färber afaer...@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
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
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
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
[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
Javier Martinez Canillas javier.marti...@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
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:
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)
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
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:
Hi Javier,
On Thu, Nov 20, 2014 at 2:15 PM, Javier Martinez Canillas
javier.marti...@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
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().
On 20 November 2014 15:22, Vivek Gautam gautamvivek1...@gmail.com wrote:
Hi Javier,
On Thu, Nov 20, 2014 at 2:15 PM, Javier Martinez Canillas
javier.marti...@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
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
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 s...@canb.auug.org.au and
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,
Hi Vivek,
Vivek Gautam gautamvivek1...@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:
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
2014-11-21 0:26 GMT+09:00 Javier Martinez Canillas
javier.marti...@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
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 1setenv bootargs console=tty1
console=ttySAC3,115200 debug earlyprintk rw
Javier Martinez Canillas javier.marti...@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 1setenv
On Thu, Nov 20, 2014 at 10:22:54AM -0800, Kevin Hilman wrote:
Javier Martinez Canillas javier.marti...@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,
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
[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
Javier Martinez Canillas javier.marti...@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
Kevin Hilman khil...@kernel.org writes:
Javier Martinez Canillas javier.marti...@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
Hi,
On Thu, Nov 20, 2014 at 12:36 PM, Vivek Gautam
gautamvivek1...@gmail.com wrote:
Hi Javier, Kevin,
On Wed, Nov 19, 2014 at 10:22 PM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
[adding Paolo and Vivek as cc]
Hello,
On 11/18/2014 07:41 PM, Kevin Hilman wrote:
Javier Martinez Canillas javier.marti...@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().
2014-11-18 Kevin Hilman khil...@kernel.org:
Javier Martinez Canillas javier.marti...@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),
Gustavo Padovan gust...@padovan.org writes:
2014-11-18 Kevin Hilman khil...@kernel.org:
Javier Martinez Canillas javier.marti...@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
40 matches
Mail list logo
