Re: [PATCH] ARM: dts: Odroid XU4: fix USB3.0 ports

Hi Richard, On 24 January 2017 at 19:18, Richard Genoud wrote: > Since commit 2164a476205ccc ("usb: dwc3: set SUSPHY bit for all cores"), > the USB ports on odroid-XU4 don't work anymore. > > Inserting an usb key (USB2.0) on the USB3.0 port result in: > [ 64.488264]

Re: [PATCH] ARM: dts: Odroid XU4: fix USB3.0 ports

Hi Richard, On 24 January 2017 at 19:18, Richard Genoud wrote: > Since commit 2164a476205ccc ("usb: dwc3: set SUSPHY bit for all cores"), > the USB ports on odroid-XU4 don't work anymore. > > Inserting an usb key (USB2.0) on the USB3.0 port result in: > [ 64.488264] xhci-hcd xhci-hcd.2.auto:

Re: [PATCH] usb: dwc3-exynos fix unspecified suspend clk error handling

Hi Bartlomiej, On 10 January 2017 at 23:33, Bartlomiej Zolnierkiewicz <b.zolnier...@samsung.com> wrote: > > Hi, > > On Tuesday, January 10, 2017 11:23:38 PM Anand Moon wrote: >> Hi Shuah, >> >> On 10 January 2017 at 21:58, Shuah Khan <shua...@osg.samsung.

Re: [PATCH] usb: dwc3-exynos fix unspecified suspend clk error handling

Hi Bartlomiej, On 10 January 2017 at 23:33, Bartlomiej Zolnierkiewicz wrote: > > Hi, > > On Tuesday, January 10, 2017 11:23:38 PM Anand Moon wrote: >> Hi Shuah, >> >> On 10 January 2017 at 21:58, Shuah Khan wrote: >> > On 01/10/2017 09:05 AM, Bartlomi

Re: [PATCH] usb: dwc3-exynos fix unspecified suspend clk error handling

Hi Shuah, On 10 January 2017 at 21:58, Shuah Khan wrote: > On 01/10/2017 09:05 AM, Bartlomiej Zolnierkiewicz wrote: >> >> Hi, >> >> On Tuesday, January 10, 2017 07:36:35 AM Shuah Khan wrote: >>> On 01/10/2017 07:16 AM, Shuah Khan wrote: On 01/10/2017 05:05 AM,

Re: [PATCH] usb: dwc3-exynos fix unspecified suspend clk error handling

Hi Shuah, On 10 January 2017 at 21:58, Shuah Khan wrote: > On 01/10/2017 09:05 AM, Bartlomiej Zolnierkiewicz wrote: >> >> Hi, >> >> On Tuesday, January 10, 2017 07:36:35 AM Shuah Khan wrote: >>> On 01/10/2017 07:16 AM, Shuah Khan wrote: On 01/10/2017 05:05 AM, Bartlomiej Zolnierkiewicz

Re: [PATCH 0/4] ARM: exynos: Fix Odroid U3 USB/LAN when TFTP booting (power sequence)

Hi Krzysztof, On 9 January 2017 at 23:47, Krzysztof Kozlowski <k...@kernel.org> wrote: > On Mon, Jan 09, 2017 at 11:34:48PM +0530, Anand Moon wrote: >> Hi Krzysztof, >> >> On 7 January 2017 at 14:21, Krzysztof Kozlowski <k...@kernel.org> wrote: >> > Hi

Re: [PATCH 0/4] ARM: exynos: Fix Odroid U3 USB/LAN when TFTP booting (power sequence)

Hi Krzysztof, On 9 January 2017 at 23:47, Krzysztof Kozlowski wrote: > On Mon, Jan 09, 2017 at 11:34:48PM +0530, Anand Moon wrote: >> Hi Krzysztof, >> >> On 7 January 2017 at 14:21, Krzysztof Kozlowski wrote: >> > Hi, >> > >> > Thanks to Markus

Re: [PATCH 0/4] ARM: exynos: Fix Odroid U3 USB/LAN when TFTP booting (power sequence)

Hi Krzysztof, On 7 January 2017 at 14:21, Krzysztof Kozlowski wrote: > Hi, > > Thanks to Markus Reichl, I got an Odroid U3 to work with. Thanks to Peter > Chen, we got a power sequence generic library which solves my long > standing Odroid U3 problem - no LAN9730 if it was

Re: [PATCH 0/4] ARM: exynos: Fix Odroid U3 USB/LAN when TFTP booting (power sequence)

Hi Krzysztof, On 7 January 2017 at 14:21, Krzysztof Kozlowski wrote: > Hi, > > Thanks to Markus Reichl, I got an Odroid U3 to work with. Thanks to Peter > Chen, we got a power sequence generic library which solves my long > standing Odroid U3 problem - no LAN9730 if it was enabled by bootloader.

Re: [PATCH] ARM: dts: Add missing CPU frequencies for Exynos5422/5800

ould be some race in thermal or the step wise governor for exynos is not working correctly. Better option is to print the cpufreq for cpu0 and cpu4 and respective temp and plot a graph along timeline. It will give us clear idea on how much time is spend on high frequency on stress testing. #!/bin/bash t=0 while true : do a=`cat /sys/devices/virtual/thermal/thermal_zone0/temp` b=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq` c=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq` d=`cat /sys/devices/system/cpu/cpu4/cpufreq/scaling_cur_freq` e=`cat /sys/devices/system/cpu/cpu4/cpufreq/cpuinfo_cur_freq` (( t += 5 )) echo $t,$a,$b,$d,$e sleep 1 done Best Regards -Anand Moon

Re: [PATCH] ARM: dts: Add missing CPU frequencies for Exynos5422/5800

ermal or the step wise governor for exynos is not working correctly. Better option is to print the cpufreq for cpu0 and cpu4 and respective temp and plot a graph along timeline. It will give us clear idea on how much time is spend on high frequency on stress testing. #!/bin/bash t=0 while true : do a=`cat /sys/devices/virtual/thermal/thermal_zone0/temp` b=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq` c=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq` d=`cat /sys/devices/system/cpu/cpu4/cpufreq/scaling_cur_freq` e=`cat /sys/devices/system/cpu/cpu4/cpufreq/cpuinfo_cur_freq` (( t += 5 )) echo $t,$a,$b,$d,$e sleep 1 done Best Regards -Anand Moon

Re: [RFC PATCH net v2 1/3] net: phy: add an option to disable EEE advertisement

.4 > iperf3 tcp test summary at my end Test Complete. Summary Results: [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-100.00 sec 10.9 GBytes 936 Mbits/sec0 sender [ 4] 0.00-100.00 sec 10.9 GBytes 936 Mbits/sec receiver CPU Utilization: local/sender 5.7% (0.2%u/5.5%s), remote/receiver 11.9% (0.9%u/11.0%s) iperf3 udp test summary at my end. Test Complete. Summary Results: [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 4] 0.00-100.00 sec 12.5 MBytes 1.05 Mbits/sec 0.025 ms 0/1599 (0%) [ 4] Sent 1599 datagrams CPU Utilization: local/sender 0.1% (0.0%u/0.1%s), remote/receiver 0.0% (0.0%u/0.0%s) Best Regards -Anand Moon > > ___ > linux-amlogic mailing list > linux-amlo...@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-amlogic

Re: [RFC PATCH net v2 1/3] net: phy: add an option to disable EEE advertisement

e. Summary Results: [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-100.00 sec 10.9 GBytes 936 Mbits/sec0 sender [ 4] 0.00-100.00 sec 10.9 GBytes 936 Mbits/sec receiver CPU Utilization: local/sender 5.7% (0.2%u/5.5%s), remote/receiver 11.9% (0.9%u/11.0%s) iperf3 udp test summary at my end. Test Complete. Summary Results: [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 4] 0.00-100.00 sec 12.5 MBytes 1.05 Mbits/sec 0.025 ms 0/1599 (0%) [ 4] Sent 1599 datagrams CPU Utilization: local/sender 0.1% (0.0%u/0.1%s), remote/receiver 0.0% (0.0%u/0.0%s) Best Regards -Anand Moon > > ___ > linux-amlogic mailing list > linux-amlo...@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-amlogic

Re: [PATCH net 1/3] net: phy: realtek: add eee advertisement disable options

Hi Jerone, On 17 November 2016 at 15:50, Jerome Brunet <jbru...@baylibre.com> wrote: > On Wed, 2016-11-16 at 22:36 +0530, Anand Moon wrote: >> Hi Jerome. >> >> On 15 November 2016 at 19:59, Jerome Brunet <jbru...@baylibre.com> >> wrote: >> > &

Re: [PATCH net 1/3] net: phy: realtek: add eee advertisement disable options

Hi Jerone, On 17 November 2016 at 15:50, Jerome Brunet wrote: > On Wed, 2016-11-16 at 22:36 +0530, Anand Moon wrote: >> Hi Jerome. >> >> On 15 November 2016 at 19:59, Jerome Brunet >> wrote: >> > >> > On some platforms, energy efficient ethernet wi

Re: [PATCH net 1/3] net: phy: realtek: add eee advertisement disable options

atus= _read_status, > .ack_interrupt = _ack_interrupt, > .config_intr= _config_intr, > @@ -164,6 +226,7 @@ static struct phy_driver realtek_drvs[] = { > .phy_id_mask= 0x001fffff, > .features = PHY_GBIT_FEATURES, &g

Re: [PATCH net 1/3] net: phy: realtek: add eee advertisement disable options

_mask= 0x001f, > .features = PHY_GBIT_FEATURES, > .flags = PHY_HAS_INTERRUPT, > + .probe = _phy_probe, > .config_aneg= _config_aneg, > .config_init= _config_init, > .read_status= _read_status, > -- > 2.7.4 > How about adding callback functionality for .soft_reset to handle BMCR where we update the Auto-Negotiation for the phy, as per the datasheet of the rtl8211f. -Best Regard Anand Moon > > ___ > linux-amlogic mailing list > linux-amlo...@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-amlogic

Re: [PATCH 1/2] host: ehci-exynos: Convert to use the SET_SYSTEM_SLEEP_PM_OPS

Hi Krzysztof, On 10 October 2016 at 00:09, Krzysztof Kozlowski <k...@kernel.org> wrote: > On Sun, Oct 09, 2016 at 11:57:59PM +0530, Anand Moon wrote: >> hi Krzysztof, >> >> On 9 October 2016 at 22:57, Krzysztof Kozlowski <k...@kernel.org> wrote: >> >

Re: [PATCH 1/2] host: ehci-exynos: Convert to use the SET_SYSTEM_SLEEP_PM_OPS

Hi Krzysztof, On 10 October 2016 at 00:09, Krzysztof Kozlowski wrote: > On Sun, Oct 09, 2016 at 11:57:59PM +0530, Anand Moon wrote: >> hi Krzysztof, >> >> On 9 October 2016 at 22:57, Krzysztof Kozlowski wrote: >> > On Sun, Oct 09, 2016 at 10:45:40PM +0530, Anand

Re: [PATCH 1/2] host: ehci-exynos: Convert to use the SET_SYSTEM_SLEEP_PM_OPS

hi Alan/Krzysztof, On 10 October 2016 at 02:47, Alan Stern <st...@rowland.harvard.edu> wrote: > On Sun, 9 Oct 2016, Krzysztof Kozlowski wrote: > >> On Sun, Oct 09, 2016 at 02:34:14PM +, Anand Moon wrote: >> > Move the ehci-exynos system PM callbacks wi

Re: [PATCH 1/2] host: ehci-exynos: Convert to use the SET_SYSTEM_SLEEP_PM_OPS

hi Alan/Krzysztof, On 10 October 2016 at 02:47, Alan Stern wrote: > On Sun, 9 Oct 2016, Krzysztof Kozlowski wrote: > >> On Sun, Oct 09, 2016 at 02:34:14PM +, Anand Moon wrote: >> > Move the ehci-exynos system PM callbacks within #ifdef CONFIG_PM_SLEEP >> > as

Re: [PATCH 1/2] host: ehci-exynos: Convert to use the SET_SYSTEM_SLEEP_PM_OPS

hi Krzysztof, On 10 October 2016 at 00:09, Krzysztof Kozlowski <k...@kernel.org> wrote: > On Sun, Oct 09, 2016 at 11:57:59PM +0530, Anand Moon wrote: >> hi Krzysztof, >> >> On 9 October 2016 at 22:57, Krzysztof Kozlowski <k...@kernel.org> wrote: >> >

Re: [PATCH 1/2] host: ehci-exynos: Convert to use the SET_SYSTEM_SLEEP_PM_OPS

hi Krzysztof, On 10 October 2016 at 00:09, Krzysztof Kozlowski wrote: > On Sun, Oct 09, 2016 at 11:57:59PM +0530, Anand Moon wrote: >> hi Krzysztof, >> >> On 9 October 2016 at 22:57, Krzysztof Kozlowski wrote: >> > On Sun, Oct 09, 2016 at 10:45:40PM +0530, Anand

Re: [PATCH 1/2] host: ehci-exynos: Convert to use the SET_SYSTEM_SLEEP_PM_OPS

hi Krzysztof, On 9 October 2016 at 22:57, Krzysztof Kozlowski <k...@kernel.org> wrote: > On Sun, Oct 09, 2016 at 10:45:40PM +0530, Anand Moon wrote: >> Hi Krzysztof, >> >> On 9 October 2016 at 22:04, Krzysztof Kozlowski <k...@kernel.org> wrote: >> > On Su

Re: [PATCH 1/2] host: ehci-exynos: Convert to use the SET_SYSTEM_SLEEP_PM_OPS

hi Krzysztof, On 9 October 2016 at 22:57, Krzysztof Kozlowski wrote: > On Sun, Oct 09, 2016 at 10:45:40PM +0530, Anand Moon wrote: >> Hi Krzysztof, >> >> On 9 October 2016 at 22:04, Krzysztof Kozlowski wrote: >> > On Sun, Oct 09, 2016 at 02:34:14PM +, Anand M

Re: [PATCH 1/2] host: ehci-exynos: Convert to use the SET_SYSTEM_SLEEP_PM_OPS

Hi Krzysztof, On 9 October 2016 at 22:04, Krzysztof Kozlowski <k...@kernel.org> wrote: > On Sun, Oct 09, 2016 at 02:34:14PM +0000, Anand Moon wrote: >> Move the ehci-exynos system PM callbacks within #ifdef CONFIG_PM_SLEEP >> as to avoid them being build when not used. This

Re: [PATCH 1/2] host: ehci-exynos: Convert to use the SET_SYSTEM_SLEEP_PM_OPS

Hi Krzysztof, On 9 October 2016 at 22:04, Krzysztof Kozlowski wrote: > On Sun, Oct 09, 2016 at 02:34:14PM +0000, Anand Moon wrote: >> Move the ehci-exynos system PM callbacks within #ifdef CONFIG_PM_SLEEP >> as to avoid them being build when not used. This also a

[PATCH 1/2] host: ehci-exynos: Convert to use the SET_SYSTEM_SLEEP_PM_OPS

Move the ehci-exynos system PM callbacks within #ifdef CONFIG_PM_SLEEP as to avoid them being build when not used. This also allows us to use the SET_SYSTEM_SLEEP_PM_OPS macro which simplifies the code. Signed-off-by: Anand Moon <linux.am...@gmail.com> --- drivers/usb/host/ehci-exynos.

[PATCH 1/2] host: ehci-exynos: Convert to use the SET_SYSTEM_SLEEP_PM_OPS

Move the ehci-exynos system PM callbacks within #ifdef CONFIG_PM_SLEEP as to avoid them being build when not used. This also allows us to use the SET_SYSTEM_SLEEP_PM_OPS macro which simplifies the code. Signed-off-by: Anand Moon --- drivers/usb/host/ehci-exynos.c | 14 ++ 1 file

[PATCH 2/2] host: ohci-exynos: Convert to use the SET_SYSTEM_SLEEP_PM_OPS

Move the ohci-exynos system PM callbacks within #ifdef CONFIG_PM_SLEEP as to avoid them being build when not used. This also allows us to use the SET_SYSTEM_SLEEP_PM_OPS macro which simplifies the code. Signed-off-by: Anand Moon <linux.am...@gmail.com> --- drivers/usb/host/ohci-exynos.

[PATCH 2/2] host: ohci-exynos: Convert to use the SET_SYSTEM_SLEEP_PM_OPS

Move the ohci-exynos system PM callbacks within #ifdef CONFIG_PM_SLEEP as to avoid them being build when not used. This also allows us to use the SET_SYSTEM_SLEEP_PM_OPS macro which simplifies the code. Signed-off-by: Anand Moon --- drivers/usb/host/ohci-exynos.c | 20 +--- 1

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

Hi Vivek, On 5 October 2016 at 10:15, Vivek Gautam <vivek.gau...@codeaurora.org> wrote: > Hi Anand, > > > On Tue, Oct 4, 2016 at 8:39 PM, Anand Moon <linux.am...@gmail.com> wrote: >> Hi Vivek, >> > > [snip] > >> >> What I feel is that

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

Hi Vivek, On 5 October 2016 at 10:15, Vivek Gautam wrote: > Hi Anand, > > > On Tue, Oct 4, 2016 at 8:39 PM, Anand Moon wrote: >> Hi Vivek, >> > > [snip] > >> >> What I feel is that their need to be some reset of usb phy so that >> device are a

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

4.8 kernel on peach/smdk542x board and > see if dwc3 usb works or not. > You may need to the patches mentioned in [9.1] and [9.2] mentioned above. > > [9.1] https://lkml.org/lkml/2014/4/28/234 base: platform: name the device already during allocation Dose not help. it's not useful at a

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

orks or not. > You may need to the patches mentioned in [9.1] and [9.2] mentioned above. > > [9.1] https://lkml.org/lkml/2014/4/28/234 base: platform: name the device already during allocation Dose not help. it's not useful at all. What I feel is that their need to be some reset of usb ph

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

v 1, Class=root_hub, Driver=xhci-hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p, 480M I fell that Ethernet driver r8152 is not getting registered to xhci-hcd to bus port 06 which lead to other ports to miss configure, some time the Ethernet port get register to bus port 04 Their is also a possibility that all the port are not getting proper power from the S2MPS11 PMIC and possible some reset of the phy is needed to reconfigure the exynos USB HSIC controller. Best Regards -Anand Moon

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

t 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p, 480M I fell that Ethernet driver r8152 is not getting registered to xhci-hcd to bus port 06 which lead to other ports to miss configure, some time the Ethernet port get register to bus port 04 Their is also a possibility that all the port are not getting proper power from the S2MPS11 PMIC and possible some reset of the phy is needed to reconfigure the exynos USB HSIC controller. Best Regards -Anand Moon

Re: [PATCH] ARM: dts: exynos: Only Odroid XU3-family boards use DTSI with CPU thermal nodes

Hi Krzysztof, On 11 May 2016 at 11:19, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: > On 05/10/2016 09:45 PM, Anand Moon wrote: >> Hi Krzysztof, >> >> Sorry I am not able to explain my self clearly. >> But I have once gain tested these changes. >>

Re: [PATCH] ARM: dts: exynos: Only Odroid XU3-family boards use DTSI with CPU thermal nodes

Hi Krzysztof, On 11 May 2016 at 11:19, Krzysztof Kozlowski wrote: > On 05/10/2016 09:45 PM, Anand Moon wrote: >> Hi Krzysztof, >> >> Sorry I am not able to explain my self clearly. >> But I have once gain tested these changes. >> >> Only

Re: [PATCH] ARM: dts: exynos: Only Odroid XU3-family boards use DTSI with CPU thermal nodes

Hi Krzysztof, On 10 May 2016 at 19:33, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: > On 05/10/2016 04:00 PM, Anand Moon wrote: >> Hi Krzysztof, >> >> On 10 May 2016 at 18:13, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: >>> On 05/10/2016

Re: [PATCH] ARM: dts: exynos: Only Odroid XU3-family boards use DTSI with CPU thermal nodes

Hi Krzysztof, On 10 May 2016 at 19:33, Krzysztof Kozlowski wrote: > On 05/10/2016 04:00 PM, Anand Moon wrote: >> Hi Krzysztof, >> >> On 10 May 2016 at 18:13, Krzysztof Kozlowski wrote: >>> On 05/10/2016 11:29 AM, Anand Moon wrote: >>>>> >>>&

Re: [PATCH] ARM: dts: exynos: Only Odroid XU3-family boards use DTSI with CPU thermal nodes

Hi Krzysztof, On 10 May 2016 at 18:13, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: > On 05/10/2016 11:29 AM, Anand Moon wrote: >>> >>> I am sorry but I do not understand. >>> 1. Are you saying that my patch causes the issue? >>> 2. Are y

Re: [PATCH] ARM: dts: exynos: Only Odroid XU3-family boards use DTSI with CPU thermal nodes

Hi Krzysztof, On 10 May 2016 at 18:13, Krzysztof Kozlowski wrote: > On 05/10/2016 11:29 AM, Anand Moon wrote: >>> >>> I am sorry but I do not understand. >>> 1. Are you saying that my patch causes the issue? >>> 2. Are you saying that I should not send

Re: [PATCH] ARM: dts: exynos: Only Odroid XU3-family boards use DTSI with CPU thermal nodes

Hi Krzysztof, On 10 May 2016 at 13:45, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: > On 05/10/2016 08:43 AM, Anand Moon wrote: >> Hi Krzysztof , >> >> On 9 May 2016 at 11:49, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: >>> Include th

Re: [PATCH] ARM: dts: exynos: Only Odroid XU3-family boards use DTSI with CPU thermal nodes

Hi Krzysztof, On 10 May 2016 at 13:45, Krzysztof Kozlowski wrote: > On 05/10/2016 08:43 AM, Anand Moon wrote: >> Hi Krzysztof , >> >> On 9 May 2016 at 11:49, Krzysztof Kozlowski wrote: >>> Include the CPU thermal nodes directly in Odroid XU3-family common DTS &

Re: [PATCH] ARM: dts: exynos: Only Odroid XU3-family boards use DTSI with CPU thermal nodes

thermal zone > - * > - * Copyright (c) 2015 Lukasz Majewski <l.majew...@samsung.com> > - * Anand Moon <linux.am...@gmail.com> > - * > - * This program is free software; you can redistribute it and/or modify > - * it under the terms of the GNU

Re: [PATCH] ARM: dts: exynos: Only Odroid XU3-family boards use DTSI with CPU thermal nodes

cpu-thermal.dtsi > deleted file mode 100644 > index 3e4c4ad96d63.. > --- a/arch/arm/boot/dts/exynos5422-cpu-thermal.dtsi > +++ /dev/null > @@ -1,103 +0,0 @@ > -/* > - * Device tree sources for Exynos5422 thermal zone > - * > - * Copyright (c) 2015 Lukasz Ma

Re: Watchdog reset trigger for eMMC

Hi Marek On 2 May 2016 at 11:57, Marek Szyprowski <m.szyprow...@samsung.com> wrote: > Hi Anand > > > On 2016-04-30 08:06, Anand Moon wrote: >> >> Hi All, >> >> Using microSD card when I try to write into /dev/watchdog device >> it

Re: Watchdog reset trigger for eMMC

Hi Marek On 2 May 2016 at 11:57, Marek Szyprowski wrote: > Hi Anand > > > On 2016-04-30 08:06, Anand Moon wrote: >> >> Hi All, >> >> Using microSD card when I try to write into /dev/watchdog device >> it trigge

Watchdog reset trigger for eMMC

idxu4e:~# --- I would like to know what is way board reset after watchdog reset after timeout. Best Regards -Anand Moon

Watchdog reset trigger for eMMC

idxu4e:~# --- I would like to know what is way board reset after watchdog reset after timeout. Best Regards -Anand Moon

Re: [PATCH] ARM: exynos_defconfig: Disable big.LITTLE switcher

config > @@ -13,8 +13,6 @@ CONFIG_ARCH_EXYNOS3=y > CONFIG_EXYNOS5420_MCPM=y > CONFIG_SMP=y > CONFIG_BIG_LITTLE=y > -CONFIG_BL_SWITCHER=y > -CONFIG_BL_SWITCHER_DUMMY_IF=y > CONFIG_NR_CPUS=8 > CONFIG_PREEMPT=y > CONFIG_AEABI=y > -- > 1.9.1 > Tested On Odroid XU4. Re

Re: [PATCH] ARM: exynos_defconfig: Disable big.LITTLE switcher

20_MCPM=y > CONFIG_SMP=y > CONFIG_BIG_LITTLE=y > -CONFIG_BL_SWITCHER=y > -CONFIG_BL_SWITCHER_DUMMY_IF=y > CONFIG_NR_CPUS=8 > CONFIG_PREEMPT=y > CONFIG_AEABI=y > -- > 1.9.1 > Tested On Odroid XU4. Reviewed-by: Anand Moon Tested-by: Anand Moon Best Regar

Re: [PATCH] i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared

b6 ("i2c: s3c2410: fix ABBA > deadlock by keeping clock prepared") that fixes the same bug in other > driver for an I2C controller found in Samsung SoCs. > > Reported-by: Anand Moon <linux.am...@gmail.com> > Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.c

Re: [PATCH] i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared

gt; deadlock by keeping clock prepared") that fixes the same bug in other > driver for an I2C controller found in Samsung SoCs. > > Reported-by: Anand Moon > Signed-off-by: Javier Martinez Canillas > > --- > > drivers/i2c/busses/i2c-exynos5.c | 20 +++-

Re: Odroid XU4 deadlock

Hi Krzysztof, On 9 April 2016 at 16:30, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: > On Fri, Apr 8, 2016 at 5:36 PM, Anand Moon <linux.am...@gmail.com> wrote: >> hi Javier, >> >> On 8 April 2016 at 20:25, Javier Martinez Canillas >> <jav.

Re: Odroid XU4 deadlock

Hi Krzysztof, On 9 April 2016 at 16:30, Krzysztof Kozlowski wrote: > On Fri, Apr 8, 2016 at 5:36 PM, Anand Moon wrote: >> hi Javier, >> >> On 8 April 2016 at 20:25, Javier Martinez Canillas >> wrote: >>> Hello Anand, >>> >>> On 04/08/2016 0

Re: [PATCH 0/7] PM / devfreq: Add NoCP devfreq-event and support busfreq on exyno5422-odroidxu3

Hi Chanwoo, On 11 April 2016 at 07:46, Chanwoo Choi <cw00.c...@samsung.com> wrote: > Hi Anand, > > On 2016년 04월 09일 03:24, Chanwoo Choi wrote: >> Hi Anand, >> >> On Sat, Apr 9, 2016 at 3:11 AM, Anand Moon <linux.am...@gmail.com> wrote: >>> Hi Chanw

Re: [PATCH 0/7] PM / devfreq: Add NoCP devfreq-event and support busfreq on exyno5422-odroidxu3

Hi Chanwoo, On 11 April 2016 at 07:46, Chanwoo Choi wrote: > Hi Anand, > > On 2016년 04월 09일 03:24, Chanwoo Choi wrote: >> Hi Anand, >> >> On Sat, Apr 9, 2016 at 3:11 AM, Anand Moon wrote: >>> Hi Chanwoo, >>> > > [snip] > >>>

Re: [PATCH 0/7] PM / devfreq: Add NoCP devfreq-event and support busfreq on exyno5422-odroidxu3

r_call_chain+0x18/0x20) [7.976783] [] (srcu_notifier_call_chain) from [] (update_devfreq+0xe4/0x18c) [7.985622] [] (update_devfreq) from [] (devfreq_monitor+0x24/0x78) [7.993595] [] (devfreq_monitor) from [] (process_one_work+0x1ac/0x454) [ 8.001913] [] (process_one_work) from [] (worker_thread+0x50/0x508) [8.009976] [] (worker_thread) from [] (kthread+0xf8/0x110) [8.017254] [] (kthread) from [] (ret_from_fork+0x14/0x24) Best Regards -Anand Moon

Re: [PATCH 0/7] PM / devfreq: Add NoCP devfreq-event and support busfreq on exyno5422-odroidxu3

+0x18/0x20) [7.976783] [] (srcu_notifier_call_chain) from [] (update_devfreq+0xe4/0x18c) [7.985622] [] (update_devfreq) from [] (devfreq_monitor+0x24/0x78) [7.993595] [] (devfreq_monitor) from [] (process_one_work+0x1ac/0x454) [8.001913] [] (process_one_work) from [] (worker_thread+0x50/0x508) [8.009976] [] (worker_thread) from [] (kthread+0xf8/0x110) [8.017254] [] (kthread) from [] (ret_from_fork+0x14/0x24) Best Regards -Anand Moon

Re: Odroid XU4 deadlock

hi Javier, On 8 April 2016 at 20:25, Javier Martinez Canillas <jav...@osg.samsung.com> wrote: > Hello Anand, > > On 04/08/2016 09:51 AM, Anand Moon wrote: >> Hi All, >> >> I am observing this deadlock or warning on my Odroid XU4. >> I thinks the

Re: Odroid XU4 deadlock

hi Javier, On 8 April 2016 at 20:25, Javier Martinez Canillas wrote: > Hello Anand, > > On 04/08/2016 09:51 AM, Anand Moon wrote: >> Hi All, >> >> I am observing this deadlock or warning on my Odroid XU4. >> I thinks the is related to clk from exynos5_i2c_xfer ..

Odroid XU4 deadlock

) [ 11.865118] [] (worker_thread) from [] (kthread+0xf4/0x10c) [ 11.865156] [] (kthread) from [] (ret_from_fork+0x14/0x24) Best Regards -Anand Moon

Odroid XU4 deadlock

) [ 11.865118] [] (worker_thread) from [] (kthread+0xf4/0x10c) [ 11.865156] [] (kthread) from [] (ret_from_fork+0x14/0x24) Best Regards -Anand Moon

Re: [PATCH V3] mmc: sdhci: Fix regression setting power on Trats2 board

/host/sdhci.h > index 0115e9907bf8..033d72b5bbd5 100644 > --- a/drivers/mmc/host/sdhci.h > +++ b/drivers/mmc/host/sdhci.h > @@ -529,6 +529,8 @@ struct sdhci_ops { > #endif > > void(*set_clock)(struct sdhci_host *host, unsigned int clock); > + void(*set_power)(str

Re: [PATCH V3] mmc: sdhci: Fix regression setting power on Trats2 board

i_ops { > #endif > > void(*set_clock)(struct sdhci_host *host, unsigned int clock); > + void(*set_power)(struct sdhci_host *host, unsigned char mode, > +unsigned short vdd); > > int (*enable_dma)(struct sdhci_host

Re: Warnings for invalid VDD (sdhci-s3c)

Hi Adrian Hunter, On 29 March 2016 at 13:29, Adrian Hunter <adrian.hun...@intel.com> wrote: > On 28/03/16 14:39, Anand Moon wrote: >> Hi Krzysztof, >> >> On 28 March 2016 at 11:03, Krzysztof Kozlowski <k.kozlow...@samsung.com> >> wrote: >>> On 27.

Re: Warnings for invalid VDD (sdhci-s3c)

Hi Adrian Hunter, On 29 March 2016 at 13:29, Adrian Hunter wrote: > On 28/03/16 14:39, Anand Moon wrote: >> Hi Krzysztof, >> >> On 28 March 2016 at 11:03, Krzysztof Kozlowski >> wrote: >>> On 27.03.2016 16:41, Anand Moon wrote: >>>> >>>

Re: Warnings for invalid VDD (sdhci-s3c)

Hi Krzysztof, On 28 March 2016 at 11:03, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: > On 27.03.2016 16:41, Anand Moon wrote: >> >> On My Odroid U3 with debug flags enable I am observing bellow deadlock. > > There is a sleep in atomic context and possible deadl

Re: Warnings for invalid VDD (sdhci-s3c)

Hi Krzysztof, On 28 March 2016 at 11:03, Krzysztof Kozlowski wrote: > On 27.03.2016 16:41, Anand Moon wrote: >> >> On My Odroid U3 with debug flags enable I am observing bellow deadlock. > > There is a sleep in atomic context and possible deadlock, but: > 1. Are you

Re: [PATCH] regulator: s2mps11: Fix invalid minimal selector for buck9 supplying SD card

ic const struct regulator_desc s2mps11_regulators[] >>> = { >>> regulator_desc_s2mps11_buck6_10(6, MIN_600_MV, STEP_6_25_MV), >>> regulator_desc_s2mps11_buck6_10(7, MIN_600_MV, STEP_6_25_MV), >>> regulator_desc_s2mps11_buck6_10(8, MIN_600_MV, S

Re: [PATCH] regulator: s2mps11: Fix invalid minimal selector for buck9 supplying SD card

regulator_desc_s2mps11_buck6_10(6, MIN_600_MV, STEP_6_25_MV), >>> regulator_desc_s2mps11_buck6_10(7, MIN_600_MV, STEP_6_25_MV), >>> regulator_desc_s2mps11_buck6_10(8, MIN_600_MV, STEP_6_25_MV), >>> -regulator_desc_s2mps11_buck6_10(9, MIN_3000_MV, STEP_25_M

Re: [PATCH v5 00/21] PM / devferq: Add generic exynos bus frequency driver and new passive governor

add my Tested tag if needed Tested-by: Anand Moon <linux.am...@gmail.com> Best Regards -Anand Moon > To Tobias, > I fixed the following issues reported by you. Thanks your test and report. > - RCU locking issue > - debugfs error during kernel booting > > Best Regards, &

Re: [PATCH v5 00/21] PM / devferq: Add generic exynos bus frequency driver and new passive governor

RANSITION_NOTIFIER > notifier. > I think that this patch-set need to test with this patchset. > If you possible, could you please test this patch-set? Thanks in advance. > I have being following this series, I have tested this series on Odroid U3. Please feel free to add my Tested tag if needed

Re: Warnings for invalid VDD (sdhci-s3c)

set_clock+0x18c/0x1b0) [ 203.982551] [] (sdhci_s3c_set_clock) from [] (sdhci_cmu_set_clock+0x24/0x17c) [ 203.991403] [] (sdhci_cmu_set_clock) from [] (sdhci_do_set_ios+0x78/0x484) [ 203.93] [] (sdhci_do_set_ios) from [] (sdhci_runtime_resume_host+0x60/0x114) [ 204.009094] [] (sdhci_runtime_resume_host) from [] (__rpm_callback+0x2c/0x60) [ 204.017938] [] (__rpm_callback) from [] (rpm_callback+0x54/0x80) [ 204.025661] [] (rpm_callback) from [] (rpm_resume+0x364/0x558) [ 204.033214] [] (rpm_resume) from [] (__pm_runtime_resume+0x60/0x8c) [ 204.041201] [] (__pm_runtime_resume) from [] (__mmc_claim_host+0x1b4/0x1f8) [ 204.049885] [] (__mmc_claim_host) from [] (mmc_sd_runtime_resume+0x20/0xac) [ 204.058563] [] (mmc_sd_runtime_resume) from [] (__rpm_callback+0x2c/0x60) [ 204.067063] [] (__rpm_callback) from [] (rpm_callback+0x54/0x80) [ 204.074788] [] (rpm_callback) from [] (rpm_resume+0x364/0x558) [ 204.082340] [] (rpm_resume) from [] (__pm_runtime_resume+0x60/0x8c) [ 204.090326] [] (__pm_runtime_resume) from [] (mmc_get_card+0x14/0x24) [ 204.098487] [] (mmc_get_card) from [] (mmc_blk_issue_rq+0x258/0x4f0) [ 204.106559] [] (mmc_blk_issue_rq) from [] (mmc_queue_thread+0xd0/0x1d8) [ 204.114903] [] (mmc_queue_thread) from [] (kthread+0xf4/0x10c) [ 204.122452] [] (kthread) from [] (ret_from_fork+0x14/0x24) - Best Regards -Anand Moon > -- > 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 at http://vger.kernel.org/majordomo-info.html

Re: Warnings for invalid VDD (sdhci-s3c)

18c/0x1b0) [ 203.982551] [] (sdhci_s3c_set_clock) from [] (sdhci_cmu_set_clock+0x24/0x17c) [ 203.991403] [] (sdhci_cmu_set_clock) from [] (sdhci_do_set_ios+0x78/0x484) [ 203.93] [] (sdhci_do_set_ios) from [] (sdhci_runtime_resume_host+0x60/0x114) [ 204.009094] [] (sdhci_runtime_resume_host) from [] (__rpm_callback+0x2c/0x60) [ 204.017938] [] (__rpm_callback) from [] (rpm_callback+0x54/0x80) [ 204.025661] [] (rpm_callback) from [] (rpm_resume+0x364/0x558) [ 204.033214] [] (rpm_resume) from [] (__pm_runtime_resume+0x60/0x8c) [ 204.041201] [] (__pm_runtime_resume) from [] (__mmc_claim_host+0x1b4/0x1f8) [ 204.049885] [] (__mmc_claim_host) from [] (mmc_sd_runtime_resume+0x20/0xac) [ 204.058563] [] (mmc_sd_runtime_resume) from [] (__rpm_callback+0x2c/0x60) [ 204.067063] [] (__rpm_callback) from [] (rpm_callback+0x54/0x80) [ 204.074788] [] (rpm_callback) from [] (rpm_resume+0x364/0x558) [ 204.082340] [] (rpm_resume) from [] (__pm_runtime_resume+0x60/0x8c) [ 204.090326] [] (__pm_runtime_resume) from [] (mmc_get_card+0x14/0x24) [ 204.098487] [] (mmc_get_card) from [] (mmc_blk_issue_rq+0x258/0x4f0) [ 204.106559] [] (mmc_blk_issue_rq) from [] (mmc_queue_thread+0xd0/0x1d8) [ 204.114903] [] (mmc_queue_thread) from [] (kthread+0xf4/0x10c) [ 204.122452] [] (kthread) from [] (ret_from_fork+0x14/0x24) - Best Regards -Anand Moon > -- > 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 at http://vger.kernel.org/majordomo-info.html

Re: [PATCH] ARM: dts: add support for gpio buttons for exynos5422-odroidxu3

Hi Krzysztof, On 23 February 2016 at 17:32, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: > 2016-02-23 18:17 GMT+09:00 Anand Moon <linux.am...@gmail.com>: >> Hi Krzysztof, >> >> On 23 February 2016 at 14:03, Krzysztof Kozlowski >>&

Re: [PATCH] ARM: dts: add support for gpio buttons for exynos5422-odroidxu3

Hi Krzysztof, On 23 February 2016 at 17:32, Krzysztof Kozlowski wrote: > 2016-02-23 18:17 GMT+09:00 Anand Moon : >> Hi Krzysztof, >> >> On 23 February 2016 at 14:03, Krzysztof Kozlowski >>>>> }; >>>>> + >>>&g

Re: [PATCH] ARM: dts: add support for gpio buttons for exynos5422-odroidxu3

Hi Krzysztof, On 23 February 2016 at 14:03, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: > On 23.02.2016 17:21, Krzysztof Kozlowski wrote: >> On 23.02.2016 17:01, Anand Moon wrote: >>> Add support for gpio-based button on Odroid-XU3 boards >>> for reboot

Re: [PATCH] ARM: dts: add support for gpio buttons for exynos5422-odroidxu3

Hi Krzysztof, On 23 February 2016 at 14:03, Krzysztof Kozlowski wrote: > On 23.02.2016 17:21, Krzysztof Kozlowski wrote: >> On 23.02.2016 17:01, Anand Moon wrote: >>> Add support for gpio-based button on Odroid-XU3 boards >>> for reboot/poweroff feature. >&g

[PATCH] ARM: dts: add support for gpio buttons for exynos5422-odroidxu3

Add support for gpio-based button on Odroid-XU3 boards for reboot/poweroff feature. Signed-off-by: Anand Moon <linux.am...@gmail.com> --- changes rebase based on linux next-20160222. Tested on Odroid-XU4 dmesg output. [3.286068] of_get_named_gpiod_flags: parsed 'gpios' property o

[PATCH] ARM: dts: add support for gpio buttons for exynos5422-odroidxu3

Add support for gpio-based button on Odroid-XU3 boards for reboot/poweroff feature. Signed-off-by: Anand Moon --- changes rebase based on linux next-20160222. Tested on Odroid-XU4 dmesg output. [3.286068] of_get_named_gpiod_flags: parsed 'gpios' property of node '/gpio_keys/power_key[0

Re: [PATCHv2] serial: samsung: drop the spinlock around uart_write_wakeup

Hi Krzysztof, On 22 February 2016 at 05:38, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: > On 21.02.2016 11:59, Anand Moon wrote: >> Hi Krzysztof, >> >> On 21 February 2016 at 07:07, Krzysztof Kozlowski >> <k.kozlow...@samsung.com> wrote: >>

Re: [PATCHv2] serial: samsung: drop the spinlock around uart_write_wakeup

Hi Krzysztof, On 22 February 2016 at 05:38, Krzysztof Kozlowski wrote: > On 21.02.2016 11:59, Anand Moon wrote: >> Hi Krzysztof, >> >> On 21 February 2016 at 07:07, Krzysztof Kozlowski >> wrote: >>> 2016-02-20 4:30 GMT+09:00 Peter Hurley : >>>>

Re: [PATCH] dmaengine: pl330: initialize tasklet after spin_unlock_irqrestore

Hi Krzysztof, On 19 February 2016 at 13:45, Lars-Peter Clausen <l...@metafoo.de> wrote: > On 02/19/2016 09:10 AM, Anand Moon wrote: >> Hi Krzysztof, >> >> On 19 February 2016 at 12:50, Krzysztof Kozlowski >> <k.kozlow...@samsung.com> wrote: >>>

Re: [PATCH] dmaengine: pl330: initialize tasklet after spin_unlock_irqrestore

Hi Krzysztof, On 19 February 2016 at 13:45, Lars-Peter Clausen wrote: > On 02/19/2016 09:10 AM, Anand Moon wrote: >> Hi Krzysztof, >> >> On 19 February 2016 at 12:50, Krzysztof Kozlowski >> wrote: >>> On 19.02.2016 15:39, Anand Moon wrote: >>>> H

Re: [PATCHv2] serial: samsung: drop the spinlock around uart_write_wakeup

Hi Krzysztof, On 21 February 2016 at 07:07, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: > 2016-02-20 4:30 GMT+09:00 Peter Hurley <pe...@hurleysoftware.com>: >> [ +cc Krzysztof Kozlowski ] >> >> On 02/18/2016 09:15 PM, Anand Moon wrote: >>&g

Re: [PATCHv2] serial: samsung: drop the spinlock around uart_write_wakeup

Hi Krzysztof, On 21 February 2016 at 07:07, Krzysztof Kozlowski wrote: > 2016-02-20 4:30 GMT+09:00 Peter Hurley : >> [ +cc Krzysztof Kozlowski ] >> >> On 02/18/2016 09:15 PM, Anand Moon wrote: >>> From: Anand Moon >>> >>> drop the spin_unlock/lo

Re: [PATCHv2] serial: samsung: drop the spinlock around uart_write_wakeup

Hi Peter, On 20 February 2016 at 01:00, Peter Hurley <pe...@hurleysoftware.com> wrote: > [ +cc Krzysztof Kozlowski ] > > On 02/18/2016 09:15 PM, Anand Moon wrote: >> From: Anand Moon <linux.am...@gmail.com> >> >> drop the spin_unlock/lock around uart_

Re: [PATCHv2] serial: samsung: drop the spinlock around uart_write_wakeup

Hi Peter, On 20 February 2016 at 01:00, Peter Hurley wrote: > [ +cc Krzysztof Kozlowski ] > > On 02/18/2016 09:15 PM, Anand Moon wrote: >> From: Anand Moon >> >> drop the spin_unlock/lock around uart_write_wakeup to protect >> write wakeup for uart port. >

Re: [PATCH] dmaengine: pl330: initialize tasklet after spin_unlock_irqrestore

hi Lars-Peter, On 19 February 2016 at 13:45, Lars-Peter Clausen <l...@metafoo.de> wrote: > On 02/19/2016 09:10 AM, Anand Moon wrote: >> Hi Krzysztof, >> >> On 19 February 2016 at 12:50, Krzysztof Kozlowski >> <k.kozlow...@samsung.com> wrote: >>>

Re: [PATCH] dmaengine: pl330: initialize tasklet after spin_unlock_irqrestore

hi Lars-Peter, On 19 February 2016 at 13:45, Lars-Peter Clausen wrote: > On 02/19/2016 09:10 AM, Anand Moon wrote: >> Hi Krzysztof, >> >> On 19 February 2016 at 12:50, Krzysztof Kozlowski >> wrote: >>> On 19.02.2016 15:39, Anand Moon wrote: >>>> H

Re: [PATCH] serial: samsung: fix the inconsistency in spinlock

Hi Krzysztof, On 19 February 2016 at 13:57, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: > On 19.02.2016 17:23, Anand Moon wrote: >> Hi Krzysztof, >> >> On 19 February 2016 at 13:14, Krzysztof Kozlowski >> <k.kozlow...@samsung.com> wrote: >>>

Re: [PATCH] serial: samsung: fix the inconsistency in spinlock

Hi Krzysztof, On 19 February 2016 at 13:57, Krzysztof Kozlowski wrote: > On 19.02.2016 17:23, Anand Moon wrote: >> Hi Krzysztof, >> >> On 19 February 2016 at 13:14, Krzysztof Kozlowski >> wrote: >>> On 19.02.2016 15:51, Anand Moon wrote: >>>> Hi K

Re: [PATCH] serial: samsung: fix the inconsistency in spinlock

Hi Krzysztof, On 19 February 2016 at 13:14, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: > On 19.02.2016 15:51, Anand Moon wrote: >> Hi Krzysztof, >> >> On 19 February 2016 at 11:39, Krzysztof Kozlowski >> <k.kozlow...@samsung.com> wrote: >>>

Re: [PATCH] serial: samsung: fix the inconsistency in spinlock

Hi Krzysztof, On 19 February 2016 at 13:14, Krzysztof Kozlowski wrote: > On 19.02.2016 15:51, Anand Moon wrote: >> Hi Krzysztof, >> >> On 19 February 2016 at 11:39, Krzysztof Kozlowski >> wrote: >>> 2016-02-19 4:14 GMT+09:00 Anand Moon : >>>>

Re: [PATCH] dmaengine: pl330: initialize tasklet after spin_unlock_irqrestore

Hi Krzysztof, On 19 February 2016 at 12:50, Krzysztof Kozlowski <k.kozlow...@samsung.com> wrote: > On 19.02.2016 15:39, Anand Moon wrote: >> Hi Krzysztof, >> >> On 19 February 2016 at 11:36, Krzysztof Kozlowski >> <k.kozlow...@samsung.com> wrote: >>>

Re: [PATCH] dmaengine: pl330: initialize tasklet after spin_unlock_irqrestore

Hi Krzysztof, On 19 February 2016 at 12:50, Krzysztof Kozlowski wrote: > On 19.02.2016 15:39, Anand Moon wrote: >> Hi Krzysztof, >> >> On 19 February 2016 at 11:36, Krzysztof Kozlowski >> wrote: >>> 2016-02-19 2:21 GMT+09:00 Anand Moon : >>>> F

<    1   2   3   4   5   6   7   >