Re: [PATCH 1/2] MAINTAINERS: Move Kukjin Kim to credits

[Kukjin Kim]

> 10/16/20 PM 3:19, Krzysztof Kozlowski  wrote:

Hi Krzysztof,

Thanks for your maintaining :)
I’m fine on this change.

> Kukjin Kim has been maintaining the Samsung ARM architectures since 2010
> up to 2016.  He contributed many patches for the S3C, S5P and Exynos
> support.  However since 2016 there is little activity from him on the
> LKML [1] so move his name to the CREDITS.
> 
> Dear Kukjin, thank you for all the effort you put in to the upstream
> Samsung support.
> 
> [1] https://lore.kernel.org/lkml/?q=f%3A%22Kukjin+Kim%22
> 
> Cc: Kukjin Kim 
Acked-by: Kukjin Kim 

> Cc: Arnd Bergmann 
> Cc: Olof Johansson 
> Signed-off-by: Krzysztof Kozlowski 
> ---
> CREDITS | 4 
> MAINTAINERS | 2 --
> 2 files changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/CREDITS b/CREDITS
> index cb02b9923a52..5df027e12ff7 100644
> --- a/CREDITS
> +++ b/CREDITS
> @@ -1910,6 +1910,10 @@ S: 660 Harvard Ave. #7
> S: Santa Clara, CA 95051
> S: USA
> 
> +N: Kukjin Kim
> +E: kg...@kernel.org
> +D: Samsung S3C, S5P and Exynos ARM architectures
> +
> N: Russell King
> E: r...@arm.linux.org.uk
> D: Linux/arm integrator, maintainer & hacker
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4538378de6f5..c3976803057c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2375,7 +2375,6 @@ F:sound/soc/rockchip/
> N:rockchip
> 
> ARM/SAMSUNG EXYNOS ARM ARCHITECTURES
> -M:Kukjin Kim 
> M:Krzysztof Kozlowski 
> L:linux-arm-ker...@lists.infradead.org (moderated for non-subscribers)
> L:linux-samsung-...@vger.kernel.org
> @@ -15497,7 +15496,6 @@ F:include/linux/clk/samsung.h
> F:include/linux/platform_data/clk-s3c2410.h
> 
> SAMSUNG SPI DRIVERS
> -M:Kukjin Kim 
> M:Krzysztof Kozlowski 
> M:Andi Shyti 
> L:linux-...@vger.kernel.org
> -- 
> 2.25.1
> 

Re: [PATCH 0/4] Drop drivers for Exynos4415

[Kukjin Kim]

Hi Krzk,

2017. 1. 14. PM 8:36 Krzysztof Kozlowski <k...@kernel.org> wrote:

> Hi,
> 
> Support for Exynos4415 is being removed because:
> 1. There are no upstream users,
> 2. There are no known downstream users,
> 3. Except compile testing, you cannot build working kernel
>   for Exynos4415 anymore.
> 
> Patches are rebased on current next and are independent.
> Please pick up as you wish.
> 
> Best regards,
> Krzysztof

Agreed,

Acked-by: Kukjin Kim <kg...@kernel.org>

k-gene
> 
> Krzysztof Kozlowski (4):
>  ARM: EXYNOS: Remove Exynos4415 driver (SoC not supported anymore)
>  clk: samsung: Remove Exynos4415 driver (SoC not supported anymore)
>  pinctrl: samsung: Remove support for Exynos4415 (SoC not supported
>anymore)
>  drm: exynos: Remove support for Exynos4415 (SoC not supported anymore)
> 
> .../devicetree/bindings/clock/exynos4415-clock.txt |   38 -
> .../bindings/display/exynos/exynos_dsim.txt|1 -
> .../bindings/display/exynos/samsung-fimd.txt   |1 -
> arch/arm/mach-exynos/Kconfig   |5 -
> arch/arm/mach-exynos/exynos.c  |1 -
> arch/arm/mach-exynos/suspend.c |1 -
> drivers/clk/samsung/Makefile   |1 -
> drivers/clk/samsung/clk-exynos4415.c   | 1022 
> drivers/gpu/drm/exynos/exynos_drm_dsi.c|   15 +-
> drivers/gpu/drm/exynos/exynos_drm_fimd.c   |   18 +-
> drivers/pinctrl/samsung/pinctrl-exynos.c   |   75 --
> drivers/pinctrl/samsung/pinctrl-samsung.c  |2 -
> drivers/pinctrl/samsung/pinctrl-samsung.h  |1 -
> include/dt-bindings/clock/exynos4415.h |  360 ---
> 14 files changed, 3 insertions(+), 1538 deletions(-)
> delete mode 100644 
> Documentation/devicetree/bindings/clock/exynos4415-clock.txt
> delete mode 100644 drivers/clk/samsung/clk-exynos4415.c
> delete mode 100644 include/dt-bindings/clock/exynos4415.h
> 
> -- 
> 2.9.3
> 

Re: [PATCH 0/4] Drop drivers for Exynos4415

[Kukjin Kim]

Hi Krzk,

2017. 1. 14. PM 8:36 Krzysztof Kozlowski  wrote:

> Hi,
> 
> Support for Exynos4415 is being removed because:
> 1. There are no upstream users,
> 2. There are no known downstream users,
> 3. Except compile testing, you cannot build working kernel
>   for Exynos4415 anymore.
> 
> Patches are rebased on current next and are independent.
> Please pick up as you wish.
> 
> Best regards,
> Krzysztof

Agreed,

Acked-by: Kukjin Kim 

k-gene
> 
> Krzysztof Kozlowski (4):
>  ARM: EXYNOS: Remove Exynos4415 driver (SoC not supported anymore)
>  clk: samsung: Remove Exynos4415 driver (SoC not supported anymore)
>  pinctrl: samsung: Remove support for Exynos4415 (SoC not supported
>anymore)
>  drm: exynos: Remove support for Exynos4415 (SoC not supported anymore)
> 
> .../devicetree/bindings/clock/exynos4415-clock.txt |   38 -
> .../bindings/display/exynos/exynos_dsim.txt|1 -
> .../bindings/display/exynos/samsung-fimd.txt   |1 -
> arch/arm/mach-exynos/Kconfig   |5 -
> arch/arm/mach-exynos/exynos.c  |1 -
> arch/arm/mach-exynos/suspend.c |1 -
> drivers/clk/samsung/Makefile   |1 -
> drivers/clk/samsung/clk-exynos4415.c   | 1022 
> drivers/gpu/drm/exynos/exynos_drm_dsi.c|   15 +-
> drivers/gpu/drm/exynos/exynos_drm_fimd.c   |   18 +-
> drivers/pinctrl/samsung/pinctrl-exynos.c   |   75 --
> drivers/pinctrl/samsung/pinctrl-samsung.c  |2 -
> drivers/pinctrl/samsung/pinctrl-samsung.h  |1 -
> include/dt-bindings/clock/exynos4415.h |  360 ---
> 14 files changed, 3 insertions(+), 1538 deletions(-)
> delete mode 100644 
> Documentation/devicetree/bindings/clock/exynos4415-clock.txt
> delete mode 100644 drivers/clk/samsung/clk-exynos4415.c
> delete mode 100644 include/dt-bindings/clock/exynos4415.h
> 
> -- 
> 2.9.3
> 

Re: [PATCH] MAINTAINERS: Add Patchwork URL to Samsung Exynos entry

[Kukjin Kim]

2016. 12. 8. 02:18 Krzysztof Kozlowski <k...@kernel.org> wrote:

> I use Patchwork for handling incoming patches. Put its address here so
> submitters could know what is in the queue.

> Signed-off-by: Krzysztof Kozlowski <k...@kernel.org>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 191887bdc49b..ec5137c39572 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1689,6 +1689,7 @@ M:Krzysztof Kozlowski <k...@kernel.org>
> R:Javier Martinez Canillas <jav...@osg.samsung.com>
> L:linux-arm-ker...@lists.infradead.org (moderated for non-subscribers)
> L:linux-samsung-...@vger.kernel.org (moderated for non-subscribers)
> +Q:https://patchwork.kernel.org/project/linux-samsung-soc/list/

to use http would be better instead of https?

then,

Acked-by: Kukjin Kim <kg...@kernel.org>

> S:Maintained
> F:arch/arm/boot/dts/s3c*
> F:arch/arm/boot/dts/s5p*
> -- 
> 2.7.4
> 

Re: [PATCH] MAINTAINERS: Add Patchwork URL to Samsung Exynos entry

[Kukjin Kim]

2016. 12. 8. 02:18 Krzysztof Kozlowski  wrote:

> I use Patchwork for handling incoming patches. Put its address here so
> submitters could know what is in the queue.

> Signed-off-by: Krzysztof Kozlowski 
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 191887bdc49b..ec5137c39572 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1689,6 +1689,7 @@ M:Krzysztof Kozlowski 
> R:Javier Martinez Canillas 
> L:linux-arm-ker...@lists.infradead.org (moderated for non-subscribers)
> L:linux-samsung-...@vger.kernel.org (moderated for non-subscribers)
> +Q:https://patchwork.kernel.org/project/linux-samsung-soc/list/

to use http would be better instead of https?

then,

Acked-by: Kukjin Kim 

> S:Maintained
> F:arch/arm/boot/dts/s3c*
> F:arch/arm/boot/dts/s5p*
> -- 
> 2.7.4
> 

Re: [PATCH v2] ARM: Drop fixed 200 Hz timer requirement from Samsung platforms

[Kukjin Kim]

2016. 11. 18. 16:16 Krzysztof Kozlowski <k...@kernel.org> wrote:

> All Samsung platforms, including the Exynos, are selecting HZ_FIXED with
> 200 Hz.  Unfortunately in case of multiplatform image this affects also
> other platforms when Exynos is enabled.
> 
> This looks like an very old legacy code, dating back to initial
> upstreaming of S3C24xx.  Probably it was required for s3c24xx timer
> driver, which was removed in commit ad38bdd15d5b ("ARM: SAMSUNG: Remove
> unused plat-samsung/time.c").
> 
> Since then, this fixed 200 Hz spread everywhere, including out-of-tree
> Samsung kernels (SoC vendor's and Tizen's).  I believe this choice
> was rather an effect of coincidence instead of conscious choice.
> 
> Exynos uses its own MCT or arch timer and can work with all HZ values.
> Older platforms use newer Samsung PWM timer driver which should handle
> down to 100 Hz.
> 
> Few perf mem and sched tests on Odroid XU3 board (Exynos5422, 4x Cortex
> A7, 4x Cortex A15) show no regressions when switching from 200 Hz to
> other values.
> 
> Reported-by: Lee Jones <lee.jo...@linaro.org>
> [Dropping 200_HZ from S3C/S5P suggested by Arnd]
> Reported-by: Arnd Bergmann <a...@arndb.de>
> Signed-off-by: Krzysztof Kozlowski <k...@kernel.org>
> Cc: Kukjin Kim <kg...@kernel.org>

Acked-by: Kukjin Kim <kg...@kernel.org>

> Tested-by: Javier Martinez Canillas <jav...@osg.samsung.com>
> 
> ---
> 
> Tested on Exynos5422 and Exynos5800 (by Javier). It would be
> appreciated if anyone could test it on S3C24xx or S5PV210.
> 
> Changes since v1:
> 1. Add Javier's tested-by.
> 2. Drop HZ_FIXED also from ARCH_S5PV210 and ARCH_S3C24XX after Arnd
>   suggestions and analysis.
> ---
> arch/arm/Kconfig | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index b5d529fdffab..ced2e08a9d08 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -1496,8 +1496,7 @@ source kernel/Kconfig.preempt
> 
> config HZ_FIXED
>int
> -default 200 if ARCH_EBSA110 || ARCH_S3C24XX || \
> -ARCH_S5PV210 || ARCH_EXYNOS4
> +default 200 if ARCH_EBSA110
>default 128 if SOC_AT91RM9200
>default 0
> 
> -- 
> 2.7.4
> 

Re: [PATCH v2] ARM: Drop fixed 200 Hz timer requirement from Samsung platforms

[Kukjin Kim]

2016. 11. 18. 16:16 Krzysztof Kozlowski  wrote:

> All Samsung platforms, including the Exynos, are selecting HZ_FIXED with
> 200 Hz.  Unfortunately in case of multiplatform image this affects also
> other platforms when Exynos is enabled.
> 
> This looks like an very old legacy code, dating back to initial
> upstreaming of S3C24xx.  Probably it was required for s3c24xx timer
> driver, which was removed in commit ad38bdd15d5b ("ARM: SAMSUNG: Remove
> unused plat-samsung/time.c").
> 
> Since then, this fixed 200 Hz spread everywhere, including out-of-tree
> Samsung kernels (SoC vendor's and Tizen's).  I believe this choice
> was rather an effect of coincidence instead of conscious choice.
> 
> Exynos uses its own MCT or arch timer and can work with all HZ values.
> Older platforms use newer Samsung PWM timer driver which should handle
> down to 100 Hz.
> 
> Few perf mem and sched tests on Odroid XU3 board (Exynos5422, 4x Cortex
> A7, 4x Cortex A15) show no regressions when switching from 200 Hz to
> other values.
> 
> Reported-by: Lee Jones 
> [Dropping 200_HZ from S3C/S5P suggested by Arnd]
> Reported-by: Arnd Bergmann 
> Signed-off-by: Krzysztof Kozlowski 
> Cc: Kukjin Kim 

Acked-by: Kukjin Kim 

> Tested-by: Javier Martinez Canillas 
> 
> ---
> 
> Tested on Exynos5422 and Exynos5800 (by Javier). It would be
> appreciated if anyone could test it on S3C24xx or S5PV210.
> 
> Changes since v1:
> 1. Add Javier's tested-by.
> 2. Drop HZ_FIXED also from ARCH_S5PV210 and ARCH_S3C24XX after Arnd
>   suggestions and analysis.
> ---
> arch/arm/Kconfig | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index b5d529fdffab..ced2e08a9d08 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -1496,8 +1496,7 @@ source kernel/Kconfig.preempt
> 
> config HZ_FIXED
>int
> -default 200 if ARCH_EBSA110 || ARCH_S3C24XX || \
> -ARCH_S5PV210 || ARCH_EXYNOS4
> +default 200 if ARCH_EBSA110
>default 128 if SOC_AT91RM9200
>default 0
> 
> -- 
> 2.7.4
> 

RE: [GIT PULL 1/3] ARM: soc: exynos: Drivers for v4.9

[Kukjin Kim]

Kukjin Kim wrote:

- Krzysztof's samsung email because he is not using now

> 
> 2016. 10. 3. 21:19 Kukjin Kim <kgene@gmail.com> wrote:
> 
> + my samsung email
> 
> > 2016. 10. 3. 15:48 Krzysztof Kozlowski <k...@kernel.org> wrote:
> >
> >>>> On Sun, Oct 02, 2016 at 05:25:07PM -0700, Olof Johansson wrote:
> >>>>> On Mon, Sep 19, 2016 at 8:53 AM, Krzysztof Kozlowski <k...@kernel.org> 
> >>>>> wrote:
> >>>>>> On Mon, Sep 19, 2016 at 05:02:40PM +0200, Arnd Bergmann wrote:
> >>>>>> On Sunday, September 18, 2016 6:39:46 PM CEST Krzysztof Kozlowski 
> >>>>>> wrote:
> >>>>>> Samsung drivers/soc update for v4.9:
> >>>>>> 1. Allow compile testing of exynos-mct clocksource driver on ARM64.
> >>>>>> 2. Document Exynos5433 PMU compatible (already used by clkout
> >>>>>> driver and more  will be coming soon).
> >>>>>
> >>>>> Pulled into next/drivers, thanks
> >>>>>
> >>>>> Just for my understanding: why do we need the exynos-mct driver on
> >>>>> ARM64 but not the delay-timer portion of it?
> >>>>
> >>>> I think we want all of it but Doug's optimization 3252a646aa2c
> >>>> ("clocksource: exynos_mct: Only use 32-bits where possible") is not
> >>>> ARM64 friendly. One way of dealing with it would be to prepare two
> >>>> versions of exynos4_read_current_timer(). One reading only lower
> >>>> 32-bit value for ARMv7 and second (slow) reading lower and upper for 
> >>>> ARMv8.
> >>>>
> >>>>>
> >>>>> Is there an advantage in using MCT over the architected timer on
> >>>>> these chips? If so, should we also have a way to use it as the delay 
> >>>>> timer?
> >>>>
> >>>> No, there is no real advantage... except that the SoC has some
> >>>> interesting "characteristics"... The timers are tightly coupled.
> >>>> Very tightly. I spent a lot of time and failed to boot my ARMv8
> >>>> board without some MCT magic.
> >>>
> >>> What kind of magic is that?
> >>
> >> Most notably: the arch timer starts when MCT forward running counter
> >> starts. Without kicking MCT, the arch timer seems to be frozen.
> >>
> >>> I can understand that needing the MCT for some system-level timer
> >>> functionality might be true (wakeups, etc),

Yes correct, the MCT is designed for the power consumption related
functionalities such as cluster power down

> >>> but for system
> >>> timesource avoiding the MMIO timer and using the arch ones is a
> >>> substantial performance improvement for gettimeofday() and friends.
> >>>

At this moment, we can use the ARM arch timers as clocksource so I think
no performance degradation (some latency?) with using the CP15 access for
the gettimeofday() and friends

> >>> There was extensive discussion last year over using arch timers on
> >>> 5420/5422, and it fizzled out with vague comments about something
> >>> not working right between A15/A7 on b.L. hardware.

Current Exynos SoCs including ARMv8 architecture based have no hardware
something which means 'not working right'

> >>> I'm presuming
> >>> whatever implementation details of that SoC has since been fixed on
> >>> later chips (including v8). Any chance you can confirm? It'd be very
> >>> nice to leave MCT behind on v8 as a system time source.

It is depending on system level design architecture. If we don't need to
support some power mode such as cluster power down, we can use arch timers
without the MCT but actual product needed to support it for power consumption.

Let me add some comments.
According to the ARM architecture design, the ARM arch timers require toggle
from outside of the core as timer source and we're using the MCT for it. And
we can use the ARM arch timers as clocksource not the MCT on current Exynos.

> >> Unfortunately, I cannot confirm this, at least on Exynos5433 (ARMv8).
> >> I played with arch and MCT timers on it and failed to get the
> >> arch-timer-only setup working. I did not have access to newer Exynos
> >> designs (Exynos 7) so I do not know how it works there.
> >
> > Hi guys,
> >
> > I know what Olof want to know and actually several days ago someone asked 
> > me about that. As you guys
> talked, a couple of years ago there were some discussions...BTW I need to 
> contact to hardware designer
> before let you guys know because something needs to be confirmed by them even 
> I know roughly.
> >
> > Note I'm in vacation with my family. Will be back on this in several days 
> > with exact information.
> >
> > BRs,
> > Kukjin

k-gene

RE: [GIT PULL 1/3] ARM: soc: exynos: Drivers for v4.9

[Kukjin Kim]

Kukjin Kim wrote:

- Krzysztof's samsung email because he is not using now

> 
> 2016. 10. 3. 21:19 Kukjin Kim  wrote:
> 
> + my samsung email
> 
> > 2016. 10. 3. 15:48 Krzysztof Kozlowski  wrote:
> >
> >>>> On Sun, Oct 02, 2016 at 05:25:07PM -0700, Olof Johansson wrote:
> >>>>> On Mon, Sep 19, 2016 at 8:53 AM, Krzysztof Kozlowski  
> >>>>> wrote:
> >>>>>> On Mon, Sep 19, 2016 at 05:02:40PM +0200, Arnd Bergmann wrote:
> >>>>>> On Sunday, September 18, 2016 6:39:46 PM CEST Krzysztof Kozlowski 
> >>>>>> wrote:
> >>>>>> Samsung drivers/soc update for v4.9:
> >>>>>> 1. Allow compile testing of exynos-mct clocksource driver on ARM64.
> >>>>>> 2. Document Exynos5433 PMU compatible (already used by clkout
> >>>>>> driver and more  will be coming soon).
> >>>>>
> >>>>> Pulled into next/drivers, thanks
> >>>>>
> >>>>> Just for my understanding: why do we need the exynos-mct driver on
> >>>>> ARM64 but not the delay-timer portion of it?
> >>>>
> >>>> I think we want all of it but Doug's optimization 3252a646aa2c
> >>>> ("clocksource: exynos_mct: Only use 32-bits where possible") is not
> >>>> ARM64 friendly. One way of dealing with it would be to prepare two
> >>>> versions of exynos4_read_current_timer(). One reading only lower
> >>>> 32-bit value for ARMv7 and second (slow) reading lower and upper for 
> >>>> ARMv8.
> >>>>
> >>>>>
> >>>>> Is there an advantage in using MCT over the architected timer on
> >>>>> these chips? If so, should we also have a way to use it as the delay 
> >>>>> timer?
> >>>>
> >>>> No, there is no real advantage... except that the SoC has some
> >>>> interesting "characteristics"... The timers are tightly coupled.
> >>>> Very tightly. I spent a lot of time and failed to boot my ARMv8
> >>>> board without some MCT magic.
> >>>
> >>> What kind of magic is that?
> >>
> >> Most notably: the arch timer starts when MCT forward running counter
> >> starts. Without kicking MCT, the arch timer seems to be frozen.
> >>
> >>> I can understand that needing the MCT for some system-level timer
> >>> functionality might be true (wakeups, etc),

Yes correct, the MCT is designed for the power consumption related
functionalities such as cluster power down

> >>> but for system
> >>> timesource avoiding the MMIO timer and using the arch ones is a
> >>> substantial performance improvement for gettimeofday() and friends.
> >>>

At this moment, we can use the ARM arch timers as clocksource so I think
no performance degradation (some latency?) with using the CP15 access for
the gettimeofday() and friends

> >>> There was extensive discussion last year over using arch timers on
> >>> 5420/5422, and it fizzled out with vague comments about something
> >>> not working right between A15/A7 on b.L. hardware.

Current Exynos SoCs including ARMv8 architecture based have no hardware
something which means 'not working right'

> >>> I'm presuming
> >>> whatever implementation details of that SoC has since been fixed on
> >>> later chips (including v8). Any chance you can confirm? It'd be very
> >>> nice to leave MCT behind on v8 as a system time source.

It is depending on system level design architecture. If we don't need to
support some power mode such as cluster power down, we can use arch timers
without the MCT but actual product needed to support it for power consumption.

Let me add some comments.
According to the ARM architecture design, the ARM arch timers require toggle
from outside of the core as timer source and we're using the MCT for it. And
we can use the ARM arch timers as clocksource not the MCT on current Exynos.

> >> Unfortunately, I cannot confirm this, at least on Exynos5433 (ARMv8).
> >> I played with arch and MCT timers on it and failed to get the
> >> arch-timer-only setup working. I did not have access to newer Exynos
> >> designs (Exynos 7) so I do not know how it works there.
> >
> > Hi guys,
> >
> > I know what Olof want to know and actually several days ago someone asked 
> > me about that. As you guys
> talked, a couple of years ago there were some discussions...BTW I need to 
> contact to hardware designer
> before let you guys know because something needs to be confirmed by them even 
> I know roughly.
> >
> > Note I'm in vacation with my family. Will be back on this in several days 
> > with exact information.
> >
> > BRs,
> > Kukjin

k-gene

Re: [GIT PULL 1/3] ARM: soc: exynos: Drivers for v4.9

[Kukjin Kim]

2016. 10. 3. 21:19 Kukjin Kim <kgene@gmail.com> wrote:

+ my samsung email

> 2016. 10. 3. 15:48 Krzysztof Kozlowski <k...@kernel.org> wrote:
> 
>>>> On Sun, Oct 02, 2016 at 05:25:07PM -0700, Olof Johansson wrote:
>>>>> On Mon, Sep 19, 2016 at 8:53 AM, Krzysztof Kozlowski <k...@kernel.org> 
>>>>> wrote:
>>>>>> On Mon, Sep 19, 2016 at 05:02:40PM +0200, Arnd Bergmann wrote:
>>>>>> On Sunday, September 18, 2016 6:39:46 PM CEST Krzysztof Kozlowski wrote:
>>>>>> Samsung drivers/soc update for v4.9:
>>>>>> 1. Allow compile testing of exynos-mct clocksource driver on ARM64.
>>>>>> 2. Document Exynos5433 PMU compatible (already used by clkout driver and 
>>>>>> more
>>>>>>  will be coming soon).
>>>>> 
>>>>> Pulled into next/drivers, thanks
>>>>> 
>>>>> Just for my understanding: why do we need the exynos-mct driver on ARM64
>>>>> but not the delay-timer portion of it?
>>>> 
>>>> I think we want all of it but Doug's optimization 3252a646aa2c
>>>> ("clocksource: exynos_mct: Only use 32-bits where possible") is not
>>>> ARM64 friendly. One way of dealing with it would be to prepare two
>>>> versions of exynos4_read_current_timer(). One reading only lower 32-bit
>>>> value for ARMv7 and second (slow) reading lower and upper for ARMv8.
>>>> 
>>>>> 
>>>>> Is there an advantage in using MCT over the architected timer on these
>>>>> chips? If so, should we also have a way to use it as the delay timer?
>>>> 
>>>> No, there is no real advantage... except that the SoC has some
>>>> interesting "characteristics"... The timers are tightly coupled. Very
>>>> tightly. I spent a lot of time and failed to boot my ARMv8 board without
>>>> some MCT magic.
>>> 
>>> What kind of magic is that?
>> 
>> Most notably: the arch timer starts when MCT forward running counter
>> starts. Without kicking MCT, the arch timer seems to be frozen.
>> 
>>> I can understand that needing the MCT for
>>> some system-level timer functionality might be true (wakeups, etc),
>>> but for system timesource avoiding the MMIO timer and using the arch
>>> ones is a substantial performance improvement for gettimeofday() and
>>> friends.
>>> 
>>> There was extensive discussion last year over using arch timers on
>>> 5420/5422, and it fizzled out with vague comments about something not
>>> working right between A15/A7 on b.L. hardware. I'm presuming whatever
>>> implementation details of that SoC has since been fixed on later chips
>>> (including v8). Any chance you can confirm? It'd be very nice to leave
>>> MCT behind on v8 as a system time source.
>> 
>> Unfortunately, I cannot confirm this, at least on Exynos5433 (ARMv8). I
>> played with arch and MCT timers on it and failed to get the
>> arch-timer-only setup working. I did not have access to newer Exynos
>> designs (Exynos 7) so I do not know how it works there.
> 
> Hi guys,
> 
> I know what Olof want to know and actually several days ago someone asked me 
> about that. As you guys talked, a couple of years ago there were some 
> discussions...BTW I need to contact to hardware designer before let you guys 
> know because something needs to be confirmed by them even I know roughly.
> 
> Note I'm in vacation with my family. Will be back on this in several days 
> with exact information.
> 
> BRs,
> Kukjin

Re: [GIT PULL 1/3] ARM: soc: exynos: Drivers for v4.9

[Kukjin Kim]

2016. 10. 3. 21:19 Kukjin Kim  wrote:

+ my samsung email

> 2016. 10. 3. 15:48 Krzysztof Kozlowski  wrote:
> 
>>>> On Sun, Oct 02, 2016 at 05:25:07PM -0700, Olof Johansson wrote:
>>>>> On Mon, Sep 19, 2016 at 8:53 AM, Krzysztof Kozlowski  
>>>>> wrote:
>>>>>> On Mon, Sep 19, 2016 at 05:02:40PM +0200, Arnd Bergmann wrote:
>>>>>> On Sunday, September 18, 2016 6:39:46 PM CEST Krzysztof Kozlowski wrote:
>>>>>> Samsung drivers/soc update for v4.9:
>>>>>> 1. Allow compile testing of exynos-mct clocksource driver on ARM64.
>>>>>> 2. Document Exynos5433 PMU compatible (already used by clkout driver and 
>>>>>> more
>>>>>>  will be coming soon).
>>>>> 
>>>>> Pulled into next/drivers, thanks
>>>>> 
>>>>> Just for my understanding: why do we need the exynos-mct driver on ARM64
>>>>> but not the delay-timer portion of it?
>>>> 
>>>> I think we want all of it but Doug's optimization 3252a646aa2c
>>>> ("clocksource: exynos_mct: Only use 32-bits where possible") is not
>>>> ARM64 friendly. One way of dealing with it would be to prepare two
>>>> versions of exynos4_read_current_timer(). One reading only lower 32-bit
>>>> value for ARMv7 and second (slow) reading lower and upper for ARMv8.
>>>> 
>>>>> 
>>>>> Is there an advantage in using MCT over the architected timer on these
>>>>> chips? If so, should we also have a way to use it as the delay timer?
>>>> 
>>>> No, there is no real advantage... except that the SoC has some
>>>> interesting "characteristics"... The timers are tightly coupled. Very
>>>> tightly. I spent a lot of time and failed to boot my ARMv8 board without
>>>> some MCT magic.
>>> 
>>> What kind of magic is that?
>> 
>> Most notably: the arch timer starts when MCT forward running counter
>> starts. Without kicking MCT, the arch timer seems to be frozen.
>> 
>>> I can understand that needing the MCT for
>>> some system-level timer functionality might be true (wakeups, etc),
>>> but for system timesource avoiding the MMIO timer and using the arch
>>> ones is a substantial performance improvement for gettimeofday() and
>>> friends.
>>> 
>>> There was extensive discussion last year over using arch timers on
>>> 5420/5422, and it fizzled out with vague comments about something not
>>> working right between A15/A7 on b.L. hardware. I'm presuming whatever
>>> implementation details of that SoC has since been fixed on later chips
>>> (including v8). Any chance you can confirm? It'd be very nice to leave
>>> MCT behind on v8 as a system time source.
>> 
>> Unfortunately, I cannot confirm this, at least on Exynos5433 (ARMv8). I
>> played with arch and MCT timers on it and failed to get the
>> arch-timer-only setup working. I did not have access to newer Exynos
>> designs (Exynos 7) so I do not know how it works there.
> 
> Hi guys,
> 
> I know what Olof want to know and actually several days ago someone asked me 
> about that. As you guys talked, a couple of years ago there were some 
> discussions...BTW I need to contact to hardware designer before let you guys 
> know because something needs to be confirmed by them even I know roughly.
> 
> Note I'm in vacation with my family. Will be back on this in several days 
> with exact information.
> 
> BRs,
> Kukjin

Re: [GIT PULL 1/3] ARM: soc: exynos: Drivers for v4.9

[Kukjin Kim]

2016. 10. 3. 15:48 Krzysztof Kozlowski  wrote:

>> On Sun, Oct 02, 2016 at 05:25:07PM -0700, Olof Johansson wrote:
>>> On Mon, Sep 19, 2016 at 8:53 AM, Krzysztof Kozlowski  
>>> wrote:
 On Mon, Sep 19, 2016 at 05:02:40PM +0200, Arnd Bergmann wrote:
> On Sunday, September 18, 2016 6:39:46 PM CEST Krzysztof Kozlowski wrote:
> Samsung drivers/soc update for v4.9:
> 1. Allow compile testing of exynos-mct clocksource driver on ARM64.
> 2. Document Exynos5433 PMU compatible (already used by clkout driver and 
> more
>   will be coming soon).
 
 Pulled into next/drivers, thanks
 
 Just for my understanding: why do we need the exynos-mct driver on ARM64
 but not the delay-timer portion of it?
>>> 
>>> I think we want all of it but Doug's optimization 3252a646aa2c
>>> ("clocksource: exynos_mct: Only use 32-bits where possible") is not
>>> ARM64 friendly. One way of dealing with it would be to prepare two
>>> versions of exynos4_read_current_timer(). One reading only lower 32-bit
>>> value for ARMv7 and second (slow) reading lower and upper for ARMv8.
>>> 
 
 Is there an advantage in using MCT over the architected timer on these
 chips? If so, should we also have a way to use it as the delay timer?
>>> 
>>> No, there is no real advantage... except that the SoC has some
>>> interesting "characteristics"... The timers are tightly coupled. Very
>>> tightly. I spent a lot of time and failed to boot my ARMv8 board without
>>> some MCT magic.
>> 
>> What kind of magic is that?
> 
> Most notably: the arch timer starts when MCT forward running counter
> starts. Without kicking MCT, the arch timer seems to be frozen.
> 
>> I can understand that needing the MCT for
>> some system-level timer functionality might be true (wakeups, etc),
>> but for system timesource avoiding the MMIO timer and using the arch
>> ones is a substantial performance improvement for gettimeofday() and
>> friends.
>> 
>> There was extensive discussion last year over using arch timers on
>> 5420/5422, and it fizzled out with vague comments about something not
>> working right between A15/A7 on b.L. hardware. I'm presuming whatever
>> implementation details of that SoC has since been fixed on later chips
>> (including v8). Any chance you can confirm? It'd be very nice to leave
>> MCT behind on v8 as a system time source.
> 
> Unfortunately, I cannot confirm this, at least on Exynos5433 (ARMv8). I
> played with arch and MCT timers on it and failed to get the
> arch-timer-only setup working. I did not have access to newer Exynos
> designs (Exynos 7) so I do not know how it works there.

Hi guys,

I know what Olof want to know and actually several days ago someone asked me 
about that. As you guys talked, a couple of years ago there were some 
discussions...BTW I need to contact to hardware designer before let you guys 
know because something needs to be confirmed by them even I know roughly.

Note I'm in vacation with my family. Will be back on this in several days with 
exact information.

BRs,
Kukjin

Re: [GIT PULL 1/3] ARM: soc: exynos: Drivers for v4.9

[Kukjin Kim]

2016. 10. 3. 15:48 Krzysztof Kozlowski  wrote:

>> On Sun, Oct 02, 2016 at 05:25:07PM -0700, Olof Johansson wrote:
>>> On Mon, Sep 19, 2016 at 8:53 AM, Krzysztof Kozlowski  
>>> wrote:
 On Mon, Sep 19, 2016 at 05:02:40PM +0200, Arnd Bergmann wrote:
> On Sunday, September 18, 2016 6:39:46 PM CEST Krzysztof Kozlowski wrote:
> Samsung drivers/soc update for v4.9:
> 1. Allow compile testing of exynos-mct clocksource driver on ARM64.
> 2. Document Exynos5433 PMU compatible (already used by clkout driver and 
> more
>   will be coming soon).
 
 Pulled into next/drivers, thanks
 
 Just for my understanding: why do we need the exynos-mct driver on ARM64
 but not the delay-timer portion of it?
>>> 
>>> I think we want all of it but Doug's optimization 3252a646aa2c
>>> ("clocksource: exynos_mct: Only use 32-bits where possible") is not
>>> ARM64 friendly. One way of dealing with it would be to prepare two
>>> versions of exynos4_read_current_timer(). One reading only lower 32-bit
>>> value for ARMv7 and second (slow) reading lower and upper for ARMv8.
>>> 
 
 Is there an advantage in using MCT over the architected timer on these
 chips? If so, should we also have a way to use it as the delay timer?
>>> 
>>> No, there is no real advantage... except that the SoC has some
>>> interesting "characteristics"... The timers are tightly coupled. Very
>>> tightly. I spent a lot of time and failed to boot my ARMv8 board without
>>> some MCT magic.
>> 
>> What kind of magic is that?
> 
> Most notably: the arch timer starts when MCT forward running counter
> starts. Without kicking MCT, the arch timer seems to be frozen.
> 
>> I can understand that needing the MCT for
>> some system-level timer functionality might be true (wakeups, etc),
>> but for system timesource avoiding the MMIO timer and using the arch
>> ones is a substantial performance improvement for gettimeofday() and
>> friends.
>> 
>> There was extensive discussion last year over using arch timers on
>> 5420/5422, and it fizzled out with vague comments about something not
>> working right between A15/A7 on b.L. hardware. I'm presuming whatever
>> implementation details of that SoC has since been fixed on later chips
>> (including v8). Any chance you can confirm? It'd be very nice to leave
>> MCT behind on v8 as a system time source.
> 
> Unfortunately, I cannot confirm this, at least on Exynos5433 (ARMv8). I
> played with arch and MCT timers on it and failed to get the
> arch-timer-only setup working. I did not have access to newer Exynos
> designs (Exynos 7) so I do not know how it works there.

Hi guys,

I know what Olof want to know and actually several days ago someone asked me 
about that. As you guys talked, a couple of years ago there were some 
discussions...BTW I need to contact to hardware designer before let you guys 
know because something needs to be confirmed by them even I know roughly.

Note I'm in vacation with my family. Will be back on this in several days with 
exact information.

BRs,
Kukjin

Re: [PATCH] MAINTAINERS: Add myself as reviewer for Samsung Exynos support

[Kukjin Kim]

Javier Martinez Canillas <jav...@osg.samsung.com> wrote:
> I've been helping reviewing and testing Exynos SoC support patches
> for the last couple of years. But it would be easier for me if I'm
> cc'ed for patches, so I'm adding myself as reviewer for this entry.

Hi Javier,

Thanks for your review and support :)

Acked-by: Kukjin Kim <kg...@kernel.org>

BRs,
k-gene

> Signed-off-by: Javier Martinez Canillas <jav...@osg.samsung.com>
> 
> ---
> 
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d8e81b1dde30..27ffdb2a98e0 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1635,6 +1635,7 @@ N:    rockchip
> ARM/SAMSUNG EXYNOS ARM ARCHITECTURES
> M:Kukjin Kim <kg...@kernel.org>
> M:Krzysztof Kozlowski <k...@kernel.org>
> +R:Javier Martinez Canillas <jav...@osg.samsung.com>
> L:linux-arm-ker...@lists.infradead.org (moderated for non-subscribers)
> L:linux-samsung-...@vger.kernel.org (moderated for non-subscribers)
> S:Maintained
> -- 
> 2.5.5

Re: [PATCH] MAINTAINERS: Add myself as reviewer for Samsung Exynos support

[Kukjin Kim]

Javier Martinez Canillas  wrote:
> I've been helping reviewing and testing Exynos SoC support patches
> for the last couple of years. But it would be easier for me if I'm
> cc'ed for patches, so I'm adding myself as reviewer for this entry.

Hi Javier,

Thanks for your review and support :)

Acked-by: Kukjin Kim 

BRs,
k-gene

> Signed-off-by: Javier Martinez Canillas 
> 
> ---
> 
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d8e81b1dde30..27ffdb2a98e0 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1635,6 +1635,7 @@ N:rockchip
> ARM/SAMSUNG EXYNOS ARM ARCHITECTURES
> M:Kukjin Kim 
> M:Krzysztof Kozlowski 
> +R:Javier Martinez Canillas 
> L:linux-arm-ker...@lists.infradead.org (moderated for non-subscribers)
> L:linux-samsung-...@vger.kernel.org (moderated for non-subscribers)
> S:Maintained
> -- 
> 2.5.5

Re: [PATCH v3] MAINTAINERS: Switch to kernel.org account for Krzysztof Kozlowski

[Kukjin Kim]

Krzysztof Kozlowski wrote:
> Change my email address to kernel.org account instead of Samsung one.
> 
> Add Bartlomiej Zolnierkiewicz as a co-maintainer of Maxim and Samsung
> PMIC drivers.  These are used on many of our boards along with Exynos
> SoCs and Samsung R Institute Poland can still take care of them.
> 
> Signed-off-by: Krzysztof Kozlowski <k...@kernel.org>
> Cc: Kukjin Kim <kg...@kernel.org>

Acked-by: Kukjin Kim <kg...@kernel.org>

> Cc: linux-samsung-...@vger.kernel.org
> Cc: Bartlomiej Zolnierkiewicz <b.zolnier...@samsung.com>
> 
> ---
> 
> Third revision for simple maintainers update. Nice! :)
> 
> Changes since v2:
> 1. Add Bartlomiej, leave MUIC charger drivers as "Supported".
> 
> Changes since v1:
> 1. Update also mailmap after Joe Perches suggestion.
> 
> Affected drivers/subsystems:
> 1. arch/arm,
> 2. mfd,
> 3. power,
> 4. regulator,
> 5. clk,
> 6. rtc,
> 7. extcon,
> 8. pinctrl,
> 9. sound/soc,
> 
> However if there are no objections, I can push it through my tree (to
> arm-soc folks).
> ---
> .mailmap|  1 +
> MAINTAINERS | 15 +--
> 2 files changed, 10 insertions(+), 6 deletions(-)
> 
> diff --git a/.mailmap b/.mailmap
> index 2a91c14c80bf..b18912c5121e 100644
> --- a/.mailmap
> +++ b/.mailmap
> @@ -88,6 +88,7 @@ Kay Sievers <kay.siev...@vrfy.org>
> Kenneth W Chen <kenneth.w.c...@intel.com>
> Konstantin Khlebnikov <koc...@gmail.com> <k.khlebni...@samsung.com>
> Koushik <raghavendra.kous...@neterion.com>
> +Krzysztof Kozlowski <k...@kernel.org> <k.kozlow...@samsung.com>
> Krzysztof Kozlowski <k...@kernel.org> <k.kozlowsk...@gmail.com>
> Kuninori Morimoto <kuninori.morimoto...@renesas.com>
> Leonid I Ananiev <leonid.i.anan...@intel.com>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 45c98485c3f0..f77df673d097 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1623,7 +1623,7 @@ N:rockchip
> 
> ARM/SAMSUNG EXYNOS ARM ARCHITECTURES
> M:Kukjin Kim <kg...@kernel.org>
> -M:Krzysztof Kozlowski <k.kozlow...@samsung.com>
> +M:Krzysztof Kozlowski <k...@kernel.org>
> L:linux-arm-ker...@lists.infradead.org (moderated for non-subscribers)
> L:linux-samsung-...@vger.kernel.org (moderated for non-subscribers)
> S:Maintained
> @@ -7465,7 +7465,8 @@ F:
> Documentation/devicetree/bindings/sound/max9860.txt
> F:sound/soc/codecs/max9860.*
> 
> MAXIM MUIC CHARGER DRIVERS FOR EXYNOS BASED BOARDS
> -M:Krzysztof Kozlowski <k.kozlow...@samsung.com>
> +M:Krzysztof Kozlowski <k...@kernel.org>
> +M:Bartlomiej Zolnierkiewicz <b.zolnier...@samsung.com>
> L:linux...@vger.kernel.org
> S:Supported
> F:drivers/power/supply/max14577_charger.c
> @@ -7481,7 +7482,8 @@ F:include/dt-bindings/*/*max77802.h
> 
> MAXIM PMIC AND MUIC DRIVERS FOR EXYNOS BASED BOARDS
> M:Chanwoo Choi <cw00.c...@samsung.com>
> -M:Krzysztof Kozlowski <k.kozlow...@samsung.com>
> +M:Krzysztof Kozlowski <k...@kernel.org>
> +M:Bartlomiej Zolnierkiewicz <b.zolnier...@samsung.com>
> L:linux-kernel@vger.kernel.org
> S:Supported
> F:drivers/*/max14577*.c
> @@ -9258,7 +9260,7 @@ F:drivers/pinctrl/sh-pfc/
> 
> PIN CONTROLLER - SAMSUNG
> M:Tomasz Figa <tomasz.f...@gmail.com>
> -M:Krzysztof Kozlowski <k.kozlow...@samsung.com>
> +M:Krzysztof Kozlowski <k...@kernel.org>
> M:Sylwester Nawrocki <s.nawro...@samsung.com>
> L:linux-arm-ker...@lists.infradead.org (moderated for non-subscribers)
> L:linux-samsung-...@vger.kernel.org (moderated for non-subscribers)
> @@ -10189,7 +10191,7 @@ S:Maintained
> F:drivers/platform/x86/samsung-laptop.c
> 
> SAMSUNG AUDIO (ASoC) DRIVERS
> -M:Krzysztof Kozlowski <k.kozlow...@samsung.com>
> +M:Krzysztof Kozlowski <k...@kernel.org>
> M:Sangbeom Kim <sbki...@samsung.com>
> M:Sylwester Nawrocki <s.nawro...@samsung.com>
> L:alsa-de...@alsa-project.org (moderated for non-subscribers)
> @@ -10204,7 +10206,8 @@ F:drivers/video/fbdev/s3c-fb.c
> 
> SAMSUNG MULTIFUNCTION PMIC DEVICE DRIVERS
> M:Sangbeom Kim <sbki...@samsung.com>
> -M:Krzysztof Kozlowski <k.kozlow...@samsung.com>
> +M:Krzysztof Kozlowski <k...@kernel.org>
> +M:Bartlomiej Zolnierkiewicz <b.zolnier...@samsung.com>
> L:linux-kernel@vger.kernel.org
> L:linux-samsung-...@vger.kernel.org
> S:Supported
> -- 
> 2.7.4
> 

Re: [PATCH v3] MAINTAINERS: Switch to kernel.org account for Krzysztof Kozlowski

[Kukjin Kim]

Krzysztof Kozlowski wrote:
> Change my email address to kernel.org account instead of Samsung one.
> 
> Add Bartlomiej Zolnierkiewicz as a co-maintainer of Maxim and Samsung
> PMIC drivers.  These are used on many of our boards along with Exynos
> SoCs and Samsung R Institute Poland can still take care of them.
> 
> Signed-off-by: Krzysztof Kozlowski 
> Cc: Kukjin Kim 

Acked-by: Kukjin Kim 

> Cc: linux-samsung-...@vger.kernel.org
> Cc: Bartlomiej Zolnierkiewicz 
> 
> ---
> 
> Third revision for simple maintainers update. Nice! :)
> 
> Changes since v2:
> 1. Add Bartlomiej, leave MUIC charger drivers as "Supported".
> 
> Changes since v1:
> 1. Update also mailmap after Joe Perches suggestion.
> 
> Affected drivers/subsystems:
> 1. arch/arm,
> 2. mfd,
> 3. power,
> 4. regulator,
> 5. clk,
> 6. rtc,
> 7. extcon,
> 8. pinctrl,
> 9. sound/soc,
> 
> However if there are no objections, I can push it through my tree (to
> arm-soc folks).
> ---
> .mailmap|  1 +
> MAINTAINERS | 15 +--
> 2 files changed, 10 insertions(+), 6 deletions(-)
> 
> diff --git a/.mailmap b/.mailmap
> index 2a91c14c80bf..b18912c5121e 100644
> --- a/.mailmap
> +++ b/.mailmap
> @@ -88,6 +88,7 @@ Kay Sievers 
> Kenneth W Chen 
> Konstantin Khlebnikov  
> Koushik 
> +Krzysztof Kozlowski  
> Krzysztof Kozlowski  
> Kuninori Morimoto 
> Leonid I Ananiev 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 45c98485c3f0..f77df673d097 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1623,7 +1623,7 @@ N:rockchip
> 
> ARM/SAMSUNG EXYNOS ARM ARCHITECTURES
> M:Kukjin Kim 
> -M:Krzysztof Kozlowski 
> +M:Krzysztof Kozlowski 
> L:linux-arm-ker...@lists.infradead.org (moderated for non-subscribers)
> L:linux-samsung-...@vger.kernel.org (moderated for non-subscribers)
> S:Maintained
> @@ -7465,7 +7465,8 @@ F:
> Documentation/devicetree/bindings/sound/max9860.txt
> F:sound/soc/codecs/max9860.*
> 
> MAXIM MUIC CHARGER DRIVERS FOR EXYNOS BASED BOARDS
> -M:Krzysztof Kozlowski 
> +M:Krzysztof Kozlowski 
> +M:Bartlomiej Zolnierkiewicz 
> L:linux...@vger.kernel.org
> S:Supported
> F:drivers/power/supply/max14577_charger.c
> @@ -7481,7 +7482,8 @@ F:include/dt-bindings/*/*max77802.h
> 
> MAXIM PMIC AND MUIC DRIVERS FOR EXYNOS BASED BOARDS
> M:Chanwoo Choi 
> -M:Krzysztof Kozlowski 
> +M:Krzysztof Kozlowski 
> +M:Bartlomiej Zolnierkiewicz 
> L:linux-kernel@vger.kernel.org
> S:Supported
> F:drivers/*/max14577*.c
> @@ -9258,7 +9260,7 @@ F:drivers/pinctrl/sh-pfc/
> 
> PIN CONTROLLER - SAMSUNG
> M:Tomasz Figa 
> -M:Krzysztof Kozlowski 
> +M:Krzysztof Kozlowski 
> M:Sylwester Nawrocki 
> L:linux-arm-ker...@lists.infradead.org (moderated for non-subscribers)
> L:linux-samsung-...@vger.kernel.org (moderated for non-subscribers)
> @@ -10189,7 +10191,7 @@ S:Maintained
> F:drivers/platform/x86/samsung-laptop.c
> 
> SAMSUNG AUDIO (ASoC) DRIVERS
> -M:Krzysztof Kozlowski 
> +M:Krzysztof Kozlowski 
> M:Sangbeom Kim 
> M:Sylwester Nawrocki 
> L:alsa-de...@alsa-project.org (moderated for non-subscribers)
> @@ -10204,7 +10206,8 @@ F:drivers/video/fbdev/s3c-fb.c
> 
> SAMSUNG MULTIFUNCTION PMIC DEVICE DRIVERS
> M:Sangbeom Kim 
> -M:Krzysztof Kozlowski 
> +M:Krzysztof Kozlowski 
> +M:Bartlomiej Zolnierkiewicz 
> L:linux-kernel@vger.kernel.org
> L:linux-samsung-...@vger.kernel.org
> S:Supported
> -- 
> 2.7.4
> 

Re: [PATCH] ARM: exynos_defconfig: Enable PM_DEBUG

[Kukjin Kim]

On 07/19/16 23:49, Javier Martinez Canillas wrote:
> Hello Krzysztof,
> 
> On 07/19/2016 07:09 AM, Krzysztof Kozlowski wrote:
>> PM_DEBUG and PM_ADVANCED_DEBUG bring some information useful for
>> development and they should not cause any significant overhead.  Enable
>> them in default configuration so debugging would be slightly easier.
>>
>> Signed-off-by: Krzysztof Kozlowski <k.kozlow...@samsung.com>
>> ---
> 
> I agree that it's good to have these enabled to make debugging easier.
> 
I'm back ;-)

I agreed...so,
Acked-by: Kukjin Kim <kg...@kernel.org>

BTW, I have not seen the kernel log with PM_ADVANCED_DEBUG. Can anyone
show me the log?...to be honest I need to setup the dev. environment on
my desk at this moment...

Thanks,
Kukjin

> Reviewed-by: Javier Martinez Canillas <jav...@osg.samsung.com>
> 
> Best regards,

Re: [PATCH] ARM: exynos_defconfig: Enable PM_DEBUG

[Kukjin Kim]

On 07/19/16 23:49, Javier Martinez Canillas wrote:
> Hello Krzysztof,
> 
> On 07/19/2016 07:09 AM, Krzysztof Kozlowski wrote:
>> PM_DEBUG and PM_ADVANCED_DEBUG bring some information useful for
>> development and they should not cause any significant overhead.  Enable
>> them in default configuration so debugging would be slightly easier.
>>
>> Signed-off-by: Krzysztof Kozlowski 
>> ---
> 
> I agree that it's good to have these enabled to make debugging easier.
> 
I'm back ;-)

I agreed...so,
Acked-by: Kukjin Kim 

BTW, I have not seen the kernel log with PM_ADVANCED_DEBUG. Can anyone
show me the log?...to be honest I need to setup the dev. environment on
my desk at this moment...

Thanks,
Kukjin

> Reviewed-by: Javier Martinez Canillas 
> 
> Best regards,

Re: [GIT PULL] ARM: Exynos fixes for v4.4

[Kukjin Kim]

Krzysztof Kozlowski wrote:
> 
Hi Krzysztof,

Looks good to me, but I have no other fixes in my tree so this would be sent to
out arm-soc directly :-)

Hi Arnd, Olof, Kevin,
Please pull this for v4.4.

Thanks,
Kukjin

> Hi Kukjin,
> 
> Two fixes for v4.4 cycle. Rafael wanted the cpufreq fix to go through arm-soc 
> tree.
> 
> Please note that location of repository has changed to kernel.org.
> 
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> 
>   Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> 
> are available in the git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git 
> tags/samsung-fixes-4.4
> 
> for you to fetch changes up to 62f49ee26f14753bd7fa634f51d537a79061bf0f:
> 
>   cpufreq: s3c24xx: Do not mark s3c2410_plls_add as __init (2015-11-27 
> 10:10:32 +0900)
> 
> 
> Fixes for Exynos:
> 1. Fix potential NULL pointer dereference in Exynos PMU driver.
> 2. Remove incorrect __init annotation from s3c24xx cpufreq driver
>structures.
> 
> 
> Arnd Bergmann (1):
>   cpufreq: s3c24xx: Do not mark s3c2410_plls_add as __init
> 
> Pankaj Dubey (1):
>   ARM: EXYNOS: Fix potential NULL pointer access in 
> exynos_sys_powerdown_conf
> 
>  arch/arm/mach-exynos/pmu.c   | 6 +-
>  arch/arm/mach-s3c24xx/pll-s3c2440-1200.c | 2 +-  
> arch/arm/mach-s3c24xx/pll-s3c2440-16934400.c | 2
> +-
>  drivers/cpufreq/s3c24xx-cpufreq.c| 2 +-
>  4 files changed, 8 insertions(+), 4 deletions(-)
> --

Re: [GIT PULL] ARM: Exynos fixes for v4.4

[Kukjin Kim]

Krzysztof Kozlowski wrote:
> 
Hi Krzysztof,

Looks good to me, but I have no other fixes in my tree so this would be sent to
out arm-soc directly :-)

Hi Arnd, Olof, Kevin,
Please pull this for v4.4.

Thanks,
Kukjin

> Hi Kukjin,
> 
> Two fixes for v4.4 cycle. Rafael wanted the cpufreq fix to go through arm-soc 
> tree.
> 
> Please note that location of repository has changed to kernel.org.
> 
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> 
>   Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> 
> are available in the git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git 
> tags/samsung-fixes-4.4
> 
> for you to fetch changes up to 62f49ee26f14753bd7fa634f51d537a79061bf0f:
> 
>   cpufreq: s3c24xx: Do not mark s3c2410_plls_add as __init (2015-11-27 
> 10:10:32 +0900)
> 
> 
> Fixes for Exynos:
> 1. Fix potential NULL pointer dereference in Exynos PMU driver.
> 2. Remove incorrect __init annotation from s3c24xx cpufreq driver
>structures.
> 
> 
> Arnd Bergmann (1):
>   cpufreq: s3c24xx: Do not mark s3c2410_plls_add as __init
> 
> Pankaj Dubey (1):
>   ARM: EXYNOS: Fix potential NULL pointer access in 
> exynos_sys_powerdown_conf
> 
>  arch/arm/mach-exynos/pmu.c   | 6 +-
>  arch/arm/mach-s3c24xx/pll-s3c2440-1200.c | 2 +-  
> arch/arm/mach-s3c24xx/pll-s3c2440-16934400.c | 2
> +-
>  drivers/cpufreq/s3c24xx-cpufreq.c| 2 +-
>  4 files changed, 8 insertions(+), 4 deletions(-)
> --

Re: [PATCH v5 0/8] Add support for Exynos SROM Controller driver

[Kukjin Kim]

On 10/26/15 15:45, Pavel Fedin wrote:
>  Hello!
> 
Hi,

>> Applied, this whole series.
> 
>  Where can i find the recent code to base my series on? I looked at 
> linux-samsung.git but was unable to find it there.
> 
You may need to fetch again?
Anyway the branch is v4.4-next/driver-samsung or tags/samsung-driver...
Or just for-next should be fine I think.

See below:
https://git.kernel.org/cgit/linux/kernel/git/kgene/linux-samsung.git/log/?h=v4.4-next/driver-samsung

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v5 0/8] Add support for Exynos SROM Controller driver

[Kukjin Kim]

On 10/26/15 15:45, Pavel Fedin wrote:
>  Hello!
> 
Hi,

>> Applied, this whole series.
> 
>  Where can i find the recent code to base my series on? I looked at 
> linux-samsung.git but was unable to find it there.
> 
You may need to fetch again?
Anyway the branch is v4.4-next/driver-samsung or tags/samsung-driver...
Or just for-next should be fine I think.

See below:
https://git.kernel.org/cgit/linux/kernel/git/kgene/linux-samsung.git/log/?h=v4.4-next/driver-samsung

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v3 2/3] dt-bindings: Consolidate Exynos SoC bindings

[Kukjin Kim]

On 10/23/15 10:39, Krzysztof Kozlowski wrote:
> Exynos SoC Device Tree bindings are spread over arm/exynos/ and
> arm/samsung/ directories. There is no need for that separation and it
> actually confuses. Put power domain bindings under power/ and
> remaining samsung-boards.txt under arm/samsung/.
> 
> Signed-off-by: Krzysztof Kozlowski 
> Cc: Kukjin Kim 
> Reviewed-by: Javier Martinez Canillas 
> 
> ---
> 
> Changes since v2:
> 1. Update path pointing to pd-samsung.txt in samsung,sysmmu.txt.
> 
> Changes since v1:
> 1. Move power_domain.txt to power/pd-samsung.txt.
> 2. The smp-sysram.txt is moved in previous patch to sram/ directory
>(Suggested by Rob Herring).
> 3. Added Javier's reviewed-by. Although there are some differences since
>v1 but this is merely re-organization. Please let me know if the
>review tag is no longer valid.
> ---
>  Documentation/devicetree/bindings/arm/{ => samsung}/samsung-boards.txt  | 0
>  Documentation/devicetree/bindings/iommu/samsung,sysmmu.txt  | 2 
> +-
>  .../bindings/{arm/exynos/power_domain.txt => power/pd-samsung.txt}  | 0
>  3 files changed, 1 insertion(+), 1 deletion(-)
>  rename Documentation/devicetree/bindings/arm/{ => 
> samsung}/samsung-boards.txt (100%)
>  rename Documentation/devicetree/bindings/{arm/exynos/power_domain.txt => 
> power/pd-samsung.txt} (100%)
> 
> diff --git a/Documentation/devicetree/bindings/arm/samsung-boards.txt 
> b/Documentation/devicetree/bindings/arm/samsung/samsung-boards.txt
> similarity index 100%
> rename from Documentation/devicetree/bindings/arm/samsung-boards.txt
> rename to Documentation/devicetree/bindings/arm/samsung/samsung-boards.txt
> diff --git a/Documentation/devicetree/bindings/iommu/samsung,sysmmu.txt 
> b/Documentation/devicetree/bindings/iommu/samsung,sysmmu.txt
> index 729543c47046..bc620fe32a70 100644
> --- a/Documentation/devicetree/bindings/iommu/samsung,sysmmu.txt
> +++ b/Documentation/devicetree/bindings/iommu/samsung,sysmmu.txt
> @@ -47,7 +47,7 @@ Required properties:
>  - clocks: Required if the System MMU is needed to gate its clock.
>  - power-domains: Required if the System MMU is needed to gate its power.
> Please refer to the following document:
> -   Documentation/devicetree/bindings/arm/exynos/power_domain.txt
> +   Documentation/devicetree/bindings/power/pd-samsung.txt
>  
>  Examples:
>   gsc_0: gsc@13e0 {
> diff --git a/Documentation/devicetree/bindings/arm/exynos/power_domain.txt 
> b/Documentation/devicetree/bindings/power/pd-samsung.txt
> similarity index 100%
> rename from Documentation/devicetree/bindings/arm/exynos/power_domain.txt
> rename to Documentation/devicetree/bindings/power/pd-samsung.txt

Applied 2/3 and 3/3.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v3 1/3] dt-bindings: Consolidate SRAM bindings from all vendors

[Kukjin Kim]

On 10/24/15 04:47, Kukjin Kim wrote:
> On 10/23/15 10:39, Krzysztof Kozlowski wrote:
>> SRAM bindings for various SoCs, using the mmio-sram genalloc
>> API, are spread over different places - per SoC vendor. Since all of
>> these are quite similar (they depend on mmio-sram) move them to a common
>> place.
>>
>> Signed-off-by: Krzysztof Kozlowski 
>> Cc: Heiko Stuebner 
>> Cc: Maxime Ripard 
>> Cc: Chen-Yu Tsai 
>> Cc: Kukjin Kim 

Acked-by: Kukjin Kim 

>> Suggested-by: Rob Herring 
>>
> Applied with Heiko and Maxime's ack.
> 
+ Sudeep

Oops, I can't because of ..bindings/arm/arm,scpi.txt, this series should
be handled with "DT binding for ARM System Control and Power
Interface(SCPI) protocol"

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v3 1/3] dt-bindings: Consolidate SRAM bindings from all vendors

[Kukjin Kim]

On 10/23/15 10:39, Krzysztof Kozlowski wrote:
> SRAM bindings for various SoCs, using the mmio-sram genalloc
> API, are spread over different places - per SoC vendor. Since all of
> these are quite similar (they depend on mmio-sram) move them to a common
> place.
> 
> Signed-off-by: Krzysztof Kozlowski 
> Cc: Heiko Stuebner 
> Cc: Maxime Ripard 
> Cc: Chen-Yu Tsai 
> Cc: Kukjin Kim 
> Suggested-by: Rob Herring 
> 
Applied with Heiko and Maxime's ack.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2] MAINTAINERS: ARM: EXYNOS: Add documentation and dt-bindings

[Kukjin Kim]

On 10/22/15 10:28, Krzysztof Kozlowski wrote:
> Extend the Samsung Exynos maintainer entry to match SoC documentation
> and SoC dt-bindings directories. Without that some files, like
> bindings/arm/samsung/pmu.txt, are not matched by existing patterns.
> 
> This also may serve as a hint where new documentation and bindings (not
> matching specific subsystem) should be put.
> 
> Signed-off-by: Krzysztof Kozlowski 
> Cc: Kukjin Kim 
> Reviewed-by: Javier Martinez Canillas 
> 
> ---
> 
> Changes since v1:
> 1. Added Javier's reviewed-by
> 2. Cover also power domain and sram bindings located now in separate
>directory.
> ---
>  MAINTAINERS | 4 
>  1 file changed, 4 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index b556aad90930..6339926c77d6 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1459,6 +1459,10 @@ F: drivers/*/*s3c2410*
>  F:   drivers/*/*/*s3c2410*
>  F:   drivers/spi/spi-s3c*
>  F:   sound/soc/samsung/*
> +F:   Documentation/arm/Samsung/
> +F:   Documentation/devicetree/bindings/arm/samsung/
> +F:   Documentation/devicetree/bindings/sram/samsung-sram.txt
> +F:   Documentation/devicetree/bindings/power/pd-samsung.txt
>  N:   exynos
>  
>  ARM/SAMSUNG MOBILE MACHINE SUPPORT

Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: ARM: EXYNOS: Update bootloader interface on Exynos542x

[Kukjin Kim]

On 10/23/15 13:19, Krzysztof Kozlowski wrote:
> Update the documentation about:
> 1. Usage of PMU_SPARE2 register.
>Bootloaders on Exynos542x-based boards often use the register
>PMU_SPARE2 (0x908) in the same way as on Exynos3250: as a indicator
>the secondary CPU was booted on. The bootloader will set this value
>to non-zero, after sucessfull power up of secondary CPU. In the same
>time this booted CPU will stuck (spin) waiting for software reset.
> 2. Exynos542x entry address for secondary CPU boot up after system
>suspend (with MCPM enabled and in non-secure mode).
> 
> See arch/arm/mach-exynos/mcpm-exynos.c for source code.
> 
> Signed-off-by: Krzysztof Kozlowski 
> ---
>  Documentation/arm/Samsung/Bootloader-interface.txt | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/arm/Samsung/Bootloader-interface.txt 
> b/Documentation/arm/Samsung/Bootloader-interface.txt
> index df8d4fb85939..ed494ac0beb2 100644
> --- a/Documentation/arm/Samsung/Bootloader-interface.txt
> +++ b/Documentation/arm/Samsung/Bootloader-interface.txt
> @@ -19,7 +19,7 @@ executing kernel.
>  Address:  sysram_ns_base_addr
>  OffsetValuePurpose
>  =
> -0x08  exynos_cpu_resume_ns System suspend
> +0x08  exynos_cpu_resume_ns, mcpm_entry_point   System suspend
>  0x0c  0x0bad (Magic cookie)System suspend
>  0x1c  exynos4_secondary_startupSecondary CPU boot
>  0x1c + 4*cpu  exynos4_secondary_startup (Exynos4412)   Secondary CPU boot
> @@ -56,7 +56,8 @@ OffsetValue
> Purpose
>  Address:  pmu_base_addr
>  OffsetValue   Purpose
>  =
> -0x0908Non-zero (only Exynos3250)  Secondary CPU boot up indicator
> +0x0908Non-zeroSecondary CPU boot up indicator
> +  on Exynos3250 and Exynos542x
>  
>  
>  4. Glossary

Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [GIT PULL] ARM: dts: Exynos for v4.4 (3rd)

[Kukjin Kim]

On 10/16/15 14:42, Krzysztof Kozlowski wrote:
> Dear Kukjin,
> 
> Last batch of changes to DT for Exynos for v4.4.
> Includes dependency - clock driver changes.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 9aaf43d9b59d6b5d8daeb3a4b9d894ea88fc34c5:
> 
>   clk: samsung: exynos5250: Add DISP1 clocks (2015-10-16 08:49:53 +0900)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-dt-4.4-3
> 
> for you to fetch changes up to 1967da5699e660957737ec6c4015cfd8e428f0ff:
> 
>   ARM: dts: Add clocks to DISP1 domain in exynos5250 (2015-10-16 14:20:03 
> +0900)
> 
> 
> Last round (from my side) of v4.4 Device Tree improvements for Exynos
> based boards:
> 1. Fix USB OTG on Exynos3250 (Monk and Rinato), Exynos4210 (Trats
>and Universal) and Exynos4412 (Trats2).
> 2. Fix HDMI and LVDS display on Snow (Exynos5250) after second Suspend to RAM.
> 3. Minor cleanups and fixes.
> 
> 
> Krzysztof Kozlowski (2):
>   Merge tag 'samsung-clk-exynos5250-4.4' into dt-for-next

Since there is no the branch(tags/samsung-clk-exynos5250-4.4) in clk
tree, I think we don't need to keep the branch as a topic and we can
just take the patch with Stephen's ack...

>   dt-bindings: Correct the example for Exynos power domain clocks
> 
> Laurent Pinchart (2):
>   ARM: dts: Fix typo in regulator enable GPIO property in s5pv210-aquila
>   ARM: dts: Fix typo in regulator enable GPIO property in s5pv210-goni
> 
> Marek Szyprowski (1):
>   ARM: dts: Add vbus regulator to USB2 phy nodes on exynos3250, 
> exynos4210 and exynos4412 boards
> 
> Tomeu Vizoso (1):
>   ARM: dts: Add clocks to DISP1 domain in exynos5250
> 
>  Documentation/devicetree/bindings/arm/exynos/power_domain.txt | 5 ++---
>  arch/arm/boot/dts/exynos3250-monk.dts | 1 +
>  arch/arm/boot/dts/exynos3250-rinato.dts   | 1 +
>  arch/arm/boot/dts/exynos4210-trats.dts| 2 +-
>  arch/arm/boot/dts/exynos4210-universal_c210.dts   | 2 +-
>  arch/arm/boot/dts/exynos4412-trats2.dts   | 1 +
>  arch/arm/boot/dts/exynos5250.dtsi | 4 
>  arch/arm/boot/dts/s5pv210-aquila.dts  | 2 +-
>  arch/arm/boot/dts/s5pv210-goni.dts| 4 ++--
>  9 files changed, 14 insertions(+), 8 deletions(-)

In this case, please show all of diff status including merge branch ;-)

Applied all of your tags/samsung-dt-4.4-3.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [GIT PULL] ARM: defconfig: Exynos improvements for 4.4, 2nd pull

[Kukjin Kim]

On 10/13/15 09:38, Krzysztof Kozlowski wrote:
> Dear Kukjin,
> 
> This is another round of defconfig related changes for 4.4.
> 
> Description along with a tag.
> You can find them also on the lists with my reviewed-by.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 7fa5ce4e6fcb4596761c17e124e7d1f8cf64fe96:
> 
>   ARM: exynos_defconfig: Disable simplefb support (2015-09-13 19:25:39 +0900)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-defconfig-4.4-2
> 
> for you to fetch changes up to 89a0112100e74f50407d269570a02a82fd28ccb8:
> 
>   ARM: multi_v7_defconfig: Enable rtl8152 ethernet driver for Odroid-XU4 
> (2015-10-12 12:59:50 +0900)
> 
> 
> Defconfig changes around Exynos based boards:
> 1. Change WiFi-Ex from built-in to module to fix issue with probing
>the driver before root filesystem is available (driver needs
>firmware).
> 2. Enable Realtek RTL81t3 ethernet adapter present on Odroid-XU4
>board.
> 
> 
> Anand Moon (2):
>   ARM: exynos_defconfig: Enable rtl8152 ethernet driver for Odroid-XU4
>   ARM: multi_v7_defconfig: Enable rtl8152 ethernet driver for Odroid-XU4
> 
> Javier Martinez Canillas (1):
>   ARM: exynos_defconfig: Enable WiFi-Ex as a module instead built-in
> 
>  arch/arm/configs/exynos_defconfig   | 5 +++--
>  arch/arm/configs/multi_v7_defconfig | 1 +
>  2 files changed, 4 insertions(+), 2 deletions(-)

Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v5 8/8] ARM: EXYNOS: Remove SROM related register settings from mach-exynos

[Kukjin Kim]

On 10/20/15 18:15, Pankaj Dubey wrote:
> As now we have dedicated driver for SROM controller, it will take care
> of saving register banks during S2R so we can safely remove these
> settings from mach-exynos.
> 
> Signed-off-by: Pankaj Dubey 
> Reviewed-by: Krzysztof Kozlowski 
> ---
>  arch/arm/mach-exynos/Kconfig |  2 ++
>  arch/arm/mach-exynos/exynos.c| 17 -
>  arch/arm/mach-exynos/include/mach/map.h  |  3 --
>  arch/arm/mach-exynos/regs-srom.h | 53 
> 
>  arch/arm/mach-exynos/suspend.c   | 20 ++-
>  arch/arm/plat-samsung/include/plat/map-s5p.h |  1 -
>  6 files changed, 4 insertions(+), 92 deletions(-)
>  delete mode 100644 arch/arm/mach-exynos/regs-srom.h
> 
> diff --git a/arch/arm/mach-exynos/Kconfig b/arch/arm/mach-exynos/Kconfig
> index 3a10f1a..62c3139 100644
> --- a/arch/arm/mach-exynos/Kconfig
> +++ b/arch/arm/mach-exynos/Kconfig
> @@ -27,6 +27,8 @@ menuconfig ARCH_EXYNOS
>   select SRAM
>   select THERMAL
>   select MFD_SYSCON
> + select SOC_SAMSUNG
> + select EXYNOS_SROM if PM

Please add them in alphabetical next time...I've changed the order in
this time.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v5 0/8] Add support for Exynos SROM Controller driver

[Kukjin Kim]

On 10/23/15 18:49, Pavel Fedin wrote:
>  Hello!
> 
>>> This patchset, I have tested on Peach-Pi (Exynos5880) based chromebook for 
>>> boot
>>> and S2R functionality.
>>>
>>
>> Entire patchset tested on Trats2 (Exynos4412) board. Unless Kukjin picks
>> it also, I plan to take it for v4.5.
> 
>  Tested on SMDK5410. By the way, what is current status? If this is final 
> revision, can i post my Ethernet support patchset on top
> of it?
> 
>  Tested-by: Pavel Fedin 
> 
Applied, this whole series.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v5 0/8] Add support for Exynos SROM Controller driver

[Kukjin Kim]

On 10/23/15 18:49, Pavel Fedin wrote:
>  Hello!
> 
>>> This patchset, I have tested on Peach-Pi (Exynos5880) based chromebook for 
>>> boot
>>> and S2R functionality.
>>>
>>
>> Entire patchset tested on Trats2 (Exynos4412) board. Unless Kukjin picks
>> it also, I plan to take it for v4.5.
> 
>  Tested on SMDK5410. By the way, what is current status? If this is final 
> revision, can i post my Ethernet support patchset on top
> of it?
> 
>  Tested-by: Pavel Fedin 
> 
Applied, this whole series.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v3 2/3] dt-bindings: Consolidate Exynos SoC bindings

[Kukjin Kim]

On 10/23/15 10:39, Krzysztof Kozlowski wrote:
> Exynos SoC Device Tree bindings are spread over arm/exynos/ and
> arm/samsung/ directories. There is no need for that separation and it
> actually confuses. Put power domain bindings under power/ and
> remaining samsung-boards.txt under arm/samsung/.
> 
> Signed-off-by: Krzysztof Kozlowski <k.kozlow...@samsung.com>
> Cc: Kukjin Kim <kg...@kernel.org>
> Reviewed-by: Javier Martinez Canillas <jav...@osg.samsung.com>
> 
> ---
> 
> Changes since v2:
> 1. Update path pointing to pd-samsung.txt in samsung,sysmmu.txt.
> 
> Changes since v1:
> 1. Move power_domain.txt to power/pd-samsung.txt.
> 2. The smp-sysram.txt is moved in previous patch to sram/ directory
>(Suggested by Rob Herring).
> 3. Added Javier's reviewed-by. Although there are some differences since
>v1 but this is merely re-organization. Please let me know if the
>review tag is no longer valid.
> ---
>  Documentation/devicetree/bindings/arm/{ => samsung}/samsung-boards.txt  | 0
>  Documentation/devicetree/bindings/iommu/samsung,sysmmu.txt  | 2 
> +-
>  .../bindings/{arm/exynos/power_domain.txt => power/pd-samsung.txt}  | 0
>  3 files changed, 1 insertion(+), 1 deletion(-)
>  rename Documentation/devicetree/bindings/arm/{ => 
> samsung}/samsung-boards.txt (100%)
>  rename Documentation/devicetree/bindings/{arm/exynos/power_domain.txt => 
> power/pd-samsung.txt} (100%)
> 
> diff --git a/Documentation/devicetree/bindings/arm/samsung-boards.txt 
> b/Documentation/devicetree/bindings/arm/samsung/samsung-boards.txt
> similarity index 100%
> rename from Documentation/devicetree/bindings/arm/samsung-boards.txt
> rename to Documentation/devicetree/bindings/arm/samsung/samsung-boards.txt
> diff --git a/Documentation/devicetree/bindings/iommu/samsung,sysmmu.txt 
> b/Documentation/devicetree/bindings/iommu/samsung,sysmmu.txt
> index 729543c47046..bc620fe32a70 100644
> --- a/Documentation/devicetree/bindings/iommu/samsung,sysmmu.txt
> +++ b/Documentation/devicetree/bindings/iommu/samsung,sysmmu.txt
> @@ -47,7 +47,7 @@ Required properties:
>  - clocks: Required if the System MMU is needed to gate its clock.
>  - power-domains: Required if the System MMU is needed to gate its power.
> Please refer to the following document:
> -   Documentation/devicetree/bindings/arm/exynos/power_domain.txt
> +   Documentation/devicetree/bindings/power/pd-samsung.txt
>  
>  Examples:
>   gsc_0: gsc@13e0 {
> diff --git a/Documentation/devicetree/bindings/arm/exynos/power_domain.txt 
> b/Documentation/devicetree/bindings/power/pd-samsung.txt
> similarity index 100%
> rename from Documentation/devicetree/bindings/arm/exynos/power_domain.txt
> rename to Documentation/devicetree/bindings/power/pd-samsung.txt

Applied 2/3 and 3/3.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v3 1/3] dt-bindings: Consolidate SRAM bindings from all vendors

[Kukjin Kim]

On 10/24/15 04:47, Kukjin Kim wrote:
> On 10/23/15 10:39, Krzysztof Kozlowski wrote:
>> SRAM bindings for various SoCs, using the mmio-sram genalloc
>> API, are spread over different places - per SoC vendor. Since all of
>> these are quite similar (they depend on mmio-sram) move them to a common
>> place.
>>
>> Signed-off-by: Krzysztof Kozlowski <k.kozlow...@samsung.com>
>> Cc: Heiko Stuebner <he...@sntech.de>
>> Cc: Maxime Ripard <maxime.rip...@free-electrons.com>
>> Cc: Chen-Yu Tsai <w...@csie.org>
>> Cc: Kukjin Kim <kg...@kernel.org>

Acked-by: Kukjin Kim <kg...@kernel.org>

>> Suggested-by: Rob Herring <robh...@kernel.org>
>>
> Applied with Heiko and Maxime's ack.
> 
+ Sudeep

Oops, I can't because of ..bindings/arm/arm,scpi.txt, this series should
be handled with "DT binding for ARM System Control and Power
Interface(SCPI) protocol"

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Documentation: ARM: EXYNOS: Update bootloader interface on Exynos542x

[Kukjin Kim]

On 10/23/15 13:19, Krzysztof Kozlowski wrote:
> Update the documentation about:
> 1. Usage of PMU_SPARE2 register.
>Bootloaders on Exynos542x-based boards often use the register
>PMU_SPARE2 (0x908) in the same way as on Exynos3250: as a indicator
>the secondary CPU was booted on. The bootloader will set this value
>to non-zero, after sucessfull power up of secondary CPU. In the same
>time this booted CPU will stuck (spin) waiting for software reset.
> 2. Exynos542x entry address for secondary CPU boot up after system
>suspend (with MCPM enabled and in non-secure mode).
> 
> See arch/arm/mach-exynos/mcpm-exynos.c for source code.
> 
> Signed-off-by: Krzysztof Kozlowski 
> ---
>  Documentation/arm/Samsung/Bootloader-interface.txt | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/arm/Samsung/Bootloader-interface.txt 
> b/Documentation/arm/Samsung/Bootloader-interface.txt
> index df8d4fb85939..ed494ac0beb2 100644
> --- a/Documentation/arm/Samsung/Bootloader-interface.txt
> +++ b/Documentation/arm/Samsung/Bootloader-interface.txt
> @@ -19,7 +19,7 @@ executing kernel.
>  Address:  sysram_ns_base_addr
>  OffsetValuePurpose
>  =
> -0x08  exynos_cpu_resume_ns System suspend
> +0x08  exynos_cpu_resume_ns, mcpm_entry_point   System suspend
>  0x0c  0x0bad (Magic cookie)System suspend
>  0x1c  exynos4_secondary_startupSecondary CPU boot
>  0x1c + 4*cpu  exynos4_secondary_startup (Exynos4412)   Secondary CPU boot
> @@ -56,7 +56,8 @@ OffsetValue
> Purpose
>  Address:  pmu_base_addr
>  OffsetValue   Purpose
>  =
> -0x0908Non-zero (only Exynos3250)  Secondary CPU boot up indicator
> +0x0908Non-zeroSecondary CPU boot up indicator
> +  on Exynos3250 and Exynos542x
>  
>  
>  4. Glossary

Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2] MAINTAINERS: ARM: EXYNOS: Add documentation and dt-bindings

[Kukjin Kim]

On 10/22/15 10:28, Krzysztof Kozlowski wrote:
> Extend the Samsung Exynos maintainer entry to match SoC documentation
> and SoC dt-bindings directories. Without that some files, like
> bindings/arm/samsung/pmu.txt, are not matched by existing patterns.
> 
> This also may serve as a hint where new documentation and bindings (not
> matching specific subsystem) should be put.
> 
> Signed-off-by: Krzysztof Kozlowski <k.kozlow...@samsung.com>
> Cc: Kukjin Kim <kg...@kernel.org>
> Reviewed-by: Javier Martinez Canillas <jav...@osg.samsung.com>
> 
> ---
> 
> Changes since v1:
> 1. Added Javier's reviewed-by
> 2. Cover also power domain and sram bindings located now in separate
>directory.
> ---
>  MAINTAINERS | 4 
>  1 file changed, 4 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index b556aad90930..6339926c77d6 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1459,6 +1459,10 @@ F: drivers/*/*s3c2410*
>  F:   drivers/*/*/*s3c2410*
>  F:   drivers/spi/spi-s3c*
>  F:   sound/soc/samsung/*
> +F:   Documentation/arm/Samsung/
> +F:   Documentation/devicetree/bindings/arm/samsung/
> +F:   Documentation/devicetree/bindings/sram/samsung-sram.txt
> +F:   Documentation/devicetree/bindings/power/pd-samsung.txt
>  N:   exynos
>  
>  ARM/SAMSUNG MOBILE MACHINE SUPPORT

Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v3 1/3] dt-bindings: Consolidate SRAM bindings from all vendors

[Kukjin Kim]

On 10/23/15 10:39, Krzysztof Kozlowski wrote:
> SRAM bindings for various SoCs, using the mmio-sram genalloc
> API, are spread over different places - per SoC vendor. Since all of
> these are quite similar (they depend on mmio-sram) move them to a common
> place.
> 
> Signed-off-by: Krzysztof Kozlowski <k.kozlow...@samsung.com>
> Cc: Heiko Stuebner <he...@sntech.de>
> Cc: Maxime Ripard <maxime.rip...@free-electrons.com>
> Cc: Chen-Yu Tsai <w...@csie.org>
> Cc: Kukjin Kim <kg...@kernel.org>
> Suggested-by: Rob Herring <robh...@kernel.org>
> 
Applied with Heiko and Maxime's ack.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [GIT PULL] ARM: defconfig: Exynos improvements for 4.4, 2nd pull

[Kukjin Kim]

On 10/13/15 09:38, Krzysztof Kozlowski wrote:
> Dear Kukjin,
> 
> This is another round of defconfig related changes for 4.4.
> 
> Description along with a tag.
> You can find them also on the lists with my reviewed-by.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 7fa5ce4e6fcb4596761c17e124e7d1f8cf64fe96:
> 
>   ARM: exynos_defconfig: Disable simplefb support (2015-09-13 19:25:39 +0900)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-defconfig-4.4-2
> 
> for you to fetch changes up to 89a0112100e74f50407d269570a02a82fd28ccb8:
> 
>   ARM: multi_v7_defconfig: Enable rtl8152 ethernet driver for Odroid-XU4 
> (2015-10-12 12:59:50 +0900)
> 
> 
> Defconfig changes around Exynos based boards:
> 1. Change WiFi-Ex from built-in to module to fix issue with probing
>the driver before root filesystem is available (driver needs
>firmware).
> 2. Enable Realtek RTL81t3 ethernet adapter present on Odroid-XU4
>board.
> 
> 
> Anand Moon (2):
>   ARM: exynos_defconfig: Enable rtl8152 ethernet driver for Odroid-XU4
>   ARM: multi_v7_defconfig: Enable rtl8152 ethernet driver for Odroid-XU4
> 
> Javier Martinez Canillas (1):
>   ARM: exynos_defconfig: Enable WiFi-Ex as a module instead built-in
> 
>  arch/arm/configs/exynos_defconfig   | 5 +++--
>  arch/arm/configs/multi_v7_defconfig | 1 +
>  2 files changed, 4 insertions(+), 2 deletions(-)

Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [GIT PULL] ARM: dts: Exynos for v4.4 (3rd)

[Kukjin Kim]

On 10/16/15 14:42, Krzysztof Kozlowski wrote:
> Dear Kukjin,
> 
> Last batch of changes to DT for Exynos for v4.4.
> Includes dependency - clock driver changes.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 9aaf43d9b59d6b5d8daeb3a4b9d894ea88fc34c5:
> 
>   clk: samsung: exynos5250: Add DISP1 clocks (2015-10-16 08:49:53 +0900)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-dt-4.4-3
> 
> for you to fetch changes up to 1967da5699e660957737ec6c4015cfd8e428f0ff:
> 
>   ARM: dts: Add clocks to DISP1 domain in exynos5250 (2015-10-16 14:20:03 
> +0900)
> 
> 
> Last round (from my side) of v4.4 Device Tree improvements for Exynos
> based boards:
> 1. Fix USB OTG on Exynos3250 (Monk and Rinato), Exynos4210 (Trats
>and Universal) and Exynos4412 (Trats2).
> 2. Fix HDMI and LVDS display on Snow (Exynos5250) after second Suspend to RAM.
> 3. Minor cleanups and fixes.
> 
> 
> Krzysztof Kozlowski (2):
>   Merge tag 'samsung-clk-exynos5250-4.4' into dt-for-next

Since there is no the branch(tags/samsung-clk-exynos5250-4.4) in clk
tree, I think we don't need to keep the branch as a topic and we can
just take the patch with Stephen's ack...

>   dt-bindings: Correct the example for Exynos power domain clocks
> 
> Laurent Pinchart (2):
>   ARM: dts: Fix typo in regulator enable GPIO property in s5pv210-aquila
>   ARM: dts: Fix typo in regulator enable GPIO property in s5pv210-goni
> 
> Marek Szyprowski (1):
>   ARM: dts: Add vbus regulator to USB2 phy nodes on exynos3250, 
> exynos4210 and exynos4412 boards
> 
> Tomeu Vizoso (1):
>   ARM: dts: Add clocks to DISP1 domain in exynos5250
> 
>  Documentation/devicetree/bindings/arm/exynos/power_domain.txt | 5 ++---
>  arch/arm/boot/dts/exynos3250-monk.dts | 1 +
>  arch/arm/boot/dts/exynos3250-rinato.dts   | 1 +
>  arch/arm/boot/dts/exynos4210-trats.dts| 2 +-
>  arch/arm/boot/dts/exynos4210-universal_c210.dts   | 2 +-
>  arch/arm/boot/dts/exynos4412-trats2.dts   | 1 +
>  arch/arm/boot/dts/exynos5250.dtsi | 4 
>  arch/arm/boot/dts/s5pv210-aquila.dts  | 2 +-
>  arch/arm/boot/dts/s5pv210-goni.dts| 4 ++--
>  9 files changed, 14 insertions(+), 8 deletions(-)

In this case, please show all of diff status including merge branch ;-)

Applied all of your tags/samsung-dt-4.4-3.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v5 8/8] ARM: EXYNOS: Remove SROM related register settings from mach-exynos

[Kukjin Kim]

On 10/20/15 18:15, Pankaj Dubey wrote:
> As now we have dedicated driver for SROM controller, it will take care
> of saving register banks during S2R so we can safely remove these
> settings from mach-exynos.
> 
> Signed-off-by: Pankaj Dubey 
> Reviewed-by: Krzysztof Kozlowski 
> ---
>  arch/arm/mach-exynos/Kconfig |  2 ++
>  arch/arm/mach-exynos/exynos.c| 17 -
>  arch/arm/mach-exynos/include/mach/map.h  |  3 --
>  arch/arm/mach-exynos/regs-srom.h | 53 
> 
>  arch/arm/mach-exynos/suspend.c   | 20 ++-
>  arch/arm/plat-samsung/include/plat/map-s5p.h |  1 -
>  6 files changed, 4 insertions(+), 92 deletions(-)
>  delete mode 100644 arch/arm/mach-exynos/regs-srom.h
> 
> diff --git a/arch/arm/mach-exynos/Kconfig b/arch/arm/mach-exynos/Kconfig
> index 3a10f1a..62c3139 100644
> --- a/arch/arm/mach-exynos/Kconfig
> +++ b/arch/arm/mach-exynos/Kconfig
> @@ -27,6 +27,8 @@ menuconfig ARCH_EXYNOS
>   select SRAM
>   select THERMAL
>   select MFD_SYSCON
> + select SOC_SAMSUNG
> + select EXYNOS_SROM if PM

Please add them in alphabetical next time...I've changed the order in
this time.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2 0/6] ARM: dts: Use correct CD properties for SDIO and eMMC in Snow and Peach

[Kukjin Kim]

On 10/16/15 22:48, Javier Martinez Canillas wrote:
> Hello Alim,
> 
> On 10/16/2015 01:37 PM, Alim Akhtar wrote:
>> Hi Javier,
>>
>> On 10/15/2015 10:21 PM, Javier Martinez Canillas wrote:
>>> Hello,
>>>
>>> The Exynos Chromebooks DTS don't use the correct card detection properties
>>> since these were carried from the vendor tree that had a reason to do so.
>>>
>>> There are two things that I noticed:
>>>
>>> 1) The Marvell WiFi SDIO is marked as broken-cd instead of non-removable:
>>>
>>> This causes the device to be removed when the system enters into a suspend
>>> state which leads to the following warning when the system is resumed:
>>>
>>> [  181.944636] mmc2: error -2 during resume (card was removed?)
>>>
>>> The rationale for using broken-cd is explained in downstream commit [0] and
>>> was that using the non-removable property caused issues with the mwifiex
>>> driver since the reset logic called the mmc_{remove,add}_host() functions.
>>>
>>> But the reset logic in the mwifiex mainline driver has changed and this is
>>> no longer the case so it's safe to use the non-removable property AFAICT.
>>>
>> Good to know it is fixed now. This is fixed in firmware or in the driver?
>>
> 
> The fix is only in the driver. In fact, I'm using the same firmware from
> the ChromeOS rootfs for both the v3.8 vendor tree and mainline.
> 
> So IIUC, the problem with the vendor tree was that the mwifiex SDIO driver
> mwifiex_sdio_reset_work() function did a card reset by calling the functions
> mmc_remove_host() and then mmc_add_host().
> 
> But this didn't play nice with MMC_CAP_NONREMOVABLE since mmc_rescan() just
> returns if the flag is set so the card wouldn't be tried to be detected again.
> 
> After commit ("b4336a282db8 mwifiex: sdio: reset adapter using mmc_hw_reset"),
> the card is reset by doing a power cycle so that's why "non-removable" can be
> used now instead of "broken-cd".
> 
>>> 2) The eMMC node has both broken-cd and non-removable but the MMC DT binding
>>> doc (Documentation/devicetree/bindings/mmc/mmc.txt) mentions that only one
>>> of these card detection properties should be used.
>>>
>> This change looks ok, will take a closer look once I am back to my work 
>> station.
>>
Actually, looks good to me +1.
Let me take this series once get the feedback from Alim.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2 1/2] clk: samsung: exynos5250: Add DISP1 clocks

[Kukjin Kim]

On 10/17/15 03:56, Tomeu Vizoso wrote:
> On 16 October 2015 at 19:26, Stephen Boyd  wrote:
>> On 10/16, Michael Turquette wrote:
>>> Quoting Krzysztof Kozlowski (2015-10-15 16:46:27)
 On 15.10.2015 19:31, Tomeu Vizoso wrote:
> When the DISP1 power domain is powered off, there's two clocks that need
> to be temporarily reparented to OSC, and back to their original parents
> when the domain is powered on again.
>
> We expose these two clocks in the DT bindings so that the DT node of the
> power domain can reference them.
>
> Signed-off-by: Tomeu Vizoso 
> Acked-by: Stephen Boyd 
> ---
>
> Changes in v2:
> - Reuse mout_aclk200_p
> - Rename div_aclk300 as div_aclk300_disp
>
>  drivers/clk/samsung/clk-exynos5250.c   | 14 +-
>  include/dt-bindings/clock/exynos5250.h |  4 +++-
>  2 files changed, 16 insertions(+), 2 deletions(-)
>

 Reviewed-by: Krzysztof Kozlowski 
>>>
>>> Applied to clk-next.
>>>
>>
>> I think Tomeu wanted to take this through arm-soc? Otherwise
>> we'll need to provide a stable branch for the dt header.
> 
> Hi, Stephen is right, the second patch depends on this one.
> 
So...how can I take 2nd patch of this series in samsung(arm-soc) tree?
And this series shouldn't be for fixes for 4.3?...Mike how do you think?

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2 0/6] ARM: dts: Use correct CD properties for SDIO and eMMC in Snow and Peach

[Kukjin Kim]

On 10/16/15 22:48, Javier Martinez Canillas wrote:
> Hello Alim,
> 
> On 10/16/2015 01:37 PM, Alim Akhtar wrote:
>> Hi Javier,
>>
>> On 10/15/2015 10:21 PM, Javier Martinez Canillas wrote:
>>> Hello,
>>>
>>> The Exynos Chromebooks DTS don't use the correct card detection properties
>>> since these were carried from the vendor tree that had a reason to do so.
>>>
>>> There are two things that I noticed:
>>>
>>> 1) The Marvell WiFi SDIO is marked as broken-cd instead of non-removable:
>>>
>>> This causes the device to be removed when the system enters into a suspend
>>> state which leads to the following warning when the system is resumed:
>>>
>>> [  181.944636] mmc2: error -2 during resume (card was removed?)
>>>
>>> The rationale for using broken-cd is explained in downstream commit [0] and
>>> was that using the non-removable property caused issues with the mwifiex
>>> driver since the reset logic called the mmc_{remove,add}_host() functions.
>>>
>>> But the reset logic in the mwifiex mainline driver has changed and this is
>>> no longer the case so it's safe to use the non-removable property AFAICT.
>>>
>> Good to know it is fixed now. This is fixed in firmware or in the driver?
>>
> 
> The fix is only in the driver. In fact, I'm using the same firmware from
> the ChromeOS rootfs for both the v3.8 vendor tree and mainline.
> 
> So IIUC, the problem with the vendor tree was that the mwifiex SDIO driver
> mwifiex_sdio_reset_work() function did a card reset by calling the functions
> mmc_remove_host() and then mmc_add_host().
> 
> But this didn't play nice with MMC_CAP_NONREMOVABLE since mmc_rescan() just
> returns if the flag is set so the card wouldn't be tried to be detected again.
> 
> After commit ("b4336a282db8 mwifiex: sdio: reset adapter using mmc_hw_reset"),
> the card is reset by doing a power cycle so that's why "non-removable" can be
> used now instead of "broken-cd".
> 
>>> 2) The eMMC node has both broken-cd and non-removable but the MMC DT binding
>>> doc (Documentation/devicetree/bindings/mmc/mmc.txt) mentions that only one
>>> of these card detection properties should be used.
>>>
>> This change looks ok, will take a closer look once I am back to my work 
>> station.
>>
Actually, looks good to me +1.
Let me take this series once get the feedback from Alim.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2 1/2] clk: samsung: exynos5250: Add DISP1 clocks

[Kukjin Kim]

On 10/17/15 03:56, Tomeu Vizoso wrote:
> On 16 October 2015 at 19:26, Stephen Boyd  wrote:
>> On 10/16, Michael Turquette wrote:
>>> Quoting Krzysztof Kozlowski (2015-10-15 16:46:27)
 On 15.10.2015 19:31, Tomeu Vizoso wrote:
> When the DISP1 power domain is powered off, there's two clocks that need
> to be temporarily reparented to OSC, and back to their original parents
> when the domain is powered on again.
>
> We expose these two clocks in the DT bindings so that the DT node of the
> power domain can reference them.
>
> Signed-off-by: Tomeu Vizoso 
> Acked-by: Stephen Boyd 
> ---
>
> Changes in v2:
> - Reuse mout_aclk200_p
> - Rename div_aclk300 as div_aclk300_disp
>
>  drivers/clk/samsung/clk-exynos5250.c   | 14 +-
>  include/dt-bindings/clock/exynos5250.h |  4 +++-
>  2 files changed, 16 insertions(+), 2 deletions(-)
>

 Reviewed-by: Krzysztof Kozlowski 
>>>
>>> Applied to clk-next.
>>>
>>
>> I think Tomeu wanted to take this through arm-soc? Otherwise
>> we'll need to provide a stable branch for the dt header.
> 
> Hi, Stephen is right, the second patch depends on this one.
> 
So...how can I take 2nd patch of this series in samsung(arm-soc) tree?
And this series shouldn't be for fixes for 4.3?...Mike how do you think?

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [GIT PULL] ARM: defconfig: Exynos improvements for 4.4

[Kukjin Kim]

On 09/30/15 11:22, Krzysztof Kozlowski wrote:
> Dear Kukjin,
> 
> Few defconfig related changes for 4.4.
> 
> Description along with a tag.
> You can find them also on the lists with my reviewed-by.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> 
>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-defconfig-4.4
> 
> for you to fetch changes up to 7fa5ce4e6fcb4596761c17e124e7d1f8cf64fe96:
> 
>   ARM: exynos_defconfig: Disable simplefb support (2015-09-13 19:25:39 +0900)
> 
> 
> Defconfig changes around Exynos based boards:
> 1. Enable DWC2 USB driver for exynos and multi_v7 defconfigs.
>The driver is present on Exynos and Rockhip boards. Enabling also
>ethernet gadget allows betwork communication with the device.
> 2. Enable LEDS for Odroid XU3/XU4 family boards (provides simple
>monitoring of the board).
> 3. Disable the simplefb driver because in certain situations (when
>U-boot injects simplefb bindings into DTB) it may break display.
> 
> 
> Anand Moon (1):
>   ARM: exynos_defconfig: Enable LEDS for Odroid-XU3/XU4
> 
> Javier Martinez Canillas (1):
>   ARM: exynos_defconfig: Disable simplefb support
> 
> Marek Szyprowski (2):
>   ARM: exynos_defconfig: Enable DWC2 USB driver and USB ethernet gadget
>   ARM: multi_v7_defconfig: Enable DWC2 USB driver and USB ethernet gadget
> 
>  arch/arm/configs/exynos_defconfig   | 9 -
>  arch/arm/configs/multi_v7_defconfig | 2 ++
>  2 files changed, 10 insertions(+), 1 deletion(-)

Pulled, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v3] i2c: s3c2410: enable RuntimePM before registering to the core

[Kukjin Kim]

On 10/10/15 16:24, Wolfram Sang wrote:
> From: Wolfram Sang 
> 
> The core may register clients attached to this master which may use
> funtionality from the master. So, RuntimePM must be enabled before, otherwise
> this will fail. While here, move drvdata, too.
> 
> Signed-off-by: Wolfram Sang 

Looks good to me,

Acked-by: Kukjin Kim 

Thanks,
Kukjin

> ---
> 
> Changes since v2: don't call runtime pm on adaper if it wasn't registered
> 
> Thanks to Krzysztof for testing!
> 
>  drivers/i2c/busses/i2c-s3c2410.c | 8 +---
>  1 file changed, 5 insertions(+), 3 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] ARM: EXYNOS: Fix double of_node_put() when parsing child power domains

[Kukjin Kim]

On 10/12/15 10:26, Krzysztof Kozlowski wrote:
> On each next iteration of for_each_compatible_node() the reference
> counter for current device node is already decreased by the loop
> iterator. The manual call to of_node_get() is required only on loop
> break which is not happening here.
> 
> The double of_node_get() (with enabled CONFIG_OF_DYNAMIC) lead to
> decreasing the counter below expected, initial value.
> 
> Signed-off-by: Krzysztof Kozlowski 
> Fixes: fe4034a3fad7 ("ARM: EXYNOS: Add missing of_node_put() when parsing 
> power domains")
> ---
>  arch/arm/mach-exynos/pm_domains.c | 8 +++-
>  1 file changed, 3 insertions(+), 5 deletions(-)
> 
> diff --git a/arch/arm/mach-exynos/pm_domains.c 
> b/arch/arm/mach-exynos/pm_domains.c
> index 4a87e86dec45..7c21760f590f 100644
> --- a/arch/arm/mach-exynos/pm_domains.c
> +++ b/arch/arm/mach-exynos/pm_domains.c
> @@ -200,15 +200,15 @@ no_clk:
>   args.args_count = 0;
>   child_domain = of_genpd_get_from_provider();
>   if (IS_ERR(child_domain))
> - goto next_pd;
> + continue;
>  
>   if (of_parse_phandle_with_args(np, "power-domains",
>"#power-domain-cells", 0, ) != 0)
> - goto next_pd;
> + continue;
>  
>   parent_domain = of_genpd_get_from_provider();
>   if (IS_ERR(parent_domain))
> - goto next_pd;
> + continue;
>  
>   if (pm_genpd_add_subdomain(parent_domain, child_domain))
>   pr_warn("%s failed to add subdomain: %s\n",
> @@ -216,8 +216,6 @@ no_clk:
>   else
>   pr_info("%s has as child subdomain: %s.\n",
>   parent_domain->name, child_domain->name);
> -next_pd:
> - of_node_put(np);
>   }
>  
>   return 0;

Looks good to me, applied.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2] arm: dts: Fix audio card detection on peach boards

[Kukjin Kim]

On 10/12/15 22:04, Krzysztof Kozlowski wrote:
> W dniu 12.10.2015 o 21:37, Alim Akhtar pisze:
>> Since commit 2fad972d45c4 ("ARM: dts: Add mclk entry for Peach boards"),
>> sound card detection is broken on peach boards and gives below errors:
>>
>> [3.630457] max98090 7-0010: MAX98091 REVID=0x51
>> [3.634233] max98090 7-0010: use default 2.8v micbias
>> [3.640985] snow-audio sound: HiFi <-> 383.i2s mapping ok
>> [3.645307] max98090 7-0010: Invalid master clock frequency
>> [3.650824] snow-audio sound: ASoC: Peach-Pi-I2S-MAX98091 late_probe() 
>> failed: -22
>> [3.658914] snow-audio sound: snd_soc_register_card failed (-22)
>> [3.664366] snow-audio: probe of sound failed with error -22
>>
>> This patch adds missing assigned-clocks and assigned-clock-parents for
>> pmu_system_controller node which is used as "mclk" for audio codec.
>>
>> Signed-off-by: Alim Akhtar 
>> Fixes: 2fad972d45c4 ("ARM: dts: Add mclk entry for Peach boards")
>> Cc: 
>> ---
>> Changes since v1:
>> Addressed Krzysztof's review comments.
> 
> Looks good, thanks!
> 
> Reviewed-by: Krzysztof Kozlowski 
> 
Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2] arm: dts: Fix audio card detection on peach boards

[Kukjin Kim]

On 10/12/15 22:04, Krzysztof Kozlowski wrote:
> W dniu 12.10.2015 o 21:37, Alim Akhtar pisze:
>> Since commit 2fad972d45c4 ("ARM: dts: Add mclk entry for Peach boards"),
>> sound card detection is broken on peach boards and gives below errors:
>>
>> [3.630457] max98090 7-0010: MAX98091 REVID=0x51
>> [3.634233] max98090 7-0010: use default 2.8v micbias
>> [3.640985] snow-audio sound: HiFi <-> 383.i2s mapping ok
>> [3.645307] max98090 7-0010: Invalid master clock frequency
>> [3.650824] snow-audio sound: ASoC: Peach-Pi-I2S-MAX98091 late_probe() 
>> failed: -22
>> [3.658914] snow-audio sound: snd_soc_register_card failed (-22)
>> [3.664366] snow-audio: probe of sound failed with error -22
>>
>> This patch adds missing assigned-clocks and assigned-clock-parents for
>> pmu_system_controller node which is used as "mclk" for audio codec.
>>
>> Signed-off-by: Alim Akhtar 
>> Fixes: 2fad972d45c4 ("ARM: dts: Add mclk entry for Peach boards")
>> Cc: 
>> ---
>> Changes since v1:
>> Addressed Krzysztof's review comments.
> 
> Looks good, thanks!
> 
> Reviewed-by: Krzysztof Kozlowski 
> 
Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] ARM: EXYNOS: Fix double of_node_put() when parsing child power domains

[Kukjin Kim]

On 10/12/15 10:26, Krzysztof Kozlowski wrote:
> On each next iteration of for_each_compatible_node() the reference
> counter for current device node is already decreased by the loop
> iterator. The manual call to of_node_get() is required only on loop
> break which is not happening here.
> 
> The double of_node_get() (with enabled CONFIG_OF_DYNAMIC) lead to
> decreasing the counter below expected, initial value.
> 
> Signed-off-by: Krzysztof Kozlowski 
> Fixes: fe4034a3fad7 ("ARM: EXYNOS: Add missing of_node_put() when parsing 
> power domains")
> ---
>  arch/arm/mach-exynos/pm_domains.c | 8 +++-
>  1 file changed, 3 insertions(+), 5 deletions(-)
> 
> diff --git a/arch/arm/mach-exynos/pm_domains.c 
> b/arch/arm/mach-exynos/pm_domains.c
> index 4a87e86dec45..7c21760f590f 100644
> --- a/arch/arm/mach-exynos/pm_domains.c
> +++ b/arch/arm/mach-exynos/pm_domains.c
> @@ -200,15 +200,15 @@ no_clk:
>   args.args_count = 0;
>   child_domain = of_genpd_get_from_provider();
>   if (IS_ERR(child_domain))
> - goto next_pd;
> + continue;
>  
>   if (of_parse_phandle_with_args(np, "power-domains",
>"#power-domain-cells", 0, ) != 0)
> - goto next_pd;
> + continue;
>  
>   parent_domain = of_genpd_get_from_provider();
>   if (IS_ERR(parent_domain))
> - goto next_pd;
> + continue;
>  
>   if (pm_genpd_add_subdomain(parent_domain, child_domain))
>   pr_warn("%s failed to add subdomain: %s\n",
> @@ -216,8 +216,6 @@ no_clk:
>   else
>   pr_info("%s has as child subdomain: %s.\n",
>   parent_domain->name, child_domain->name);
> -next_pd:
> - of_node_put(np);
>   }
>  
>   return 0;

Looks good to me, applied.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v3] i2c: s3c2410: enable RuntimePM before registering to the core

[Kukjin Kim]

On 10/10/15 16:24, Wolfram Sang wrote:
> From: Wolfram Sang <wsa+rene...@sang-engineering.com>
> 
> The core may register clients attached to this master which may use
> funtionality from the master. So, RuntimePM must be enabled before, otherwise
> this will fail. While here, move drvdata, too.
> 
> Signed-off-by: Wolfram Sang <wsa+rene...@sang-engineering.com>

Looks good to me,

Acked-by: Kukjin Kim <kg...@kernel.org>

Thanks,
Kukjin

> ---
> 
> Changes since v2: don't call runtime pm on adaper if it wasn't registered
> 
> Thanks to Krzysztof for testing!
> 
>  drivers/i2c/busses/i2c-s3c2410.c | 8 +---
>  1 file changed, 5 insertions(+), 3 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [GIT PULL] ARM: defconfig: Exynos improvements for 4.4

[Kukjin Kim]

On 09/30/15 11:22, Krzysztof Kozlowski wrote:
> Dear Kukjin,
> 
> Few defconfig related changes for 4.4.
> 
> Description along with a tag.
> You can find them also on the lists with my reviewed-by.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> 
>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-defconfig-4.4
> 
> for you to fetch changes up to 7fa5ce4e6fcb4596761c17e124e7d1f8cf64fe96:
> 
>   ARM: exynos_defconfig: Disable simplefb support (2015-09-13 19:25:39 +0900)
> 
> 
> Defconfig changes around Exynos based boards:
> 1. Enable DWC2 USB driver for exynos and multi_v7 defconfigs.
>The driver is present on Exynos and Rockhip boards. Enabling also
>ethernet gadget allows betwork communication with the device.
> 2. Enable LEDS for Odroid XU3/XU4 family boards (provides simple
>monitoring of the board).
> 3. Disable the simplefb driver because in certain situations (when
>U-boot injects simplefb bindings into DTB) it may break display.
> 
> 
> Anand Moon (1):
>   ARM: exynos_defconfig: Enable LEDS for Odroid-XU3/XU4
> 
> Javier Martinez Canillas (1):
>   ARM: exynos_defconfig: Disable simplefb support
> 
> Marek Szyprowski (2):
>   ARM: exynos_defconfig: Enable DWC2 USB driver and USB ethernet gadget
>   ARM: multi_v7_defconfig: Enable DWC2 USB driver and USB ethernet gadget
> 
>  arch/arm/configs/exynos_defconfig   | 9 -
>  arch/arm/configs/multi_v7_defconfig | 2 ++
>  2 files changed, 10 insertions(+), 1 deletion(-)

Pulled, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH 0/5] ARM: dts: Use GPIO constants for flags cells in exynos boards

[Kukjin Kim]

On 10/07/15 22:14, Javier Martinez Canillas wrote:
> Hello,
> 
> This series contains trivial patches that use the GPIO constants
> defined in include/dt-bindings/gpio/gpio.h to express GPIO polarity
> instead of numeric values.
> 
> There is no functional change and the compiled dtbs are unchanged but
> is a good practice to use the defined macros instead of magic numbers
> since that makes the DTS more readable.
> 
> Since the changes are trivial, I thought that split the changes per
> board DTS would create an unnecessary churn but a single patch would
> maybe be harder to review so I decided that split it by SoC family
> would be a good trade off.
> 
> Please let me know if you prefer another approach.
> 
> Best regards,
> Javier
> 
> 
> Javier Martinez Canillas (5):
>   ARM: dts: Use GPIO constants for flags cells in exynos3250 boards
>   ARM: dts: Use GPIO constants for flags cells in exynos4120 boards
>   ARM: dts: Use GPIO constants for flags cells in exynos4412 boards
>   ARM: dts: Use GPIO constants for flags cells in exynos5420/5422/5800
> boards
>   ARM: dts: Use GPIO constants for flags cells in exynos5440 boards
> 
>  arch/arm/boot/dts/exynos3250-monk.dts  |  8 ++---
>  arch/arm/boot/dts/exynos3250-rinato.dts| 10 +++---
>  arch/arm/boot/dts/exynos4210-origen.dts| 15 
>  arch/arm/boot/dts/exynos4210-smdkv310.dts  |  3 +-
>  arch/arm/boot/dts/exynos4210-trats.dts | 29 +++
>  arch/arm/boot/dts/exynos4210-universal_c210.dts| 42 
> +++---
>  arch/arm/boot/dts/exynos4412-odroid-common.dtsi| 15 
>  arch/arm/boot/dts/exynos4412-odroidu3.dts  |  2 +-
>  arch/arm/boot/dts/exynos4412-odroidx.dts   |  8 ++---
>  arch/arm/boot/dts/exynos4412-origen.dts| 15 
>  arch/arm/boot/dts/exynos4412-tiny4412.dts  |  9 ++---
>  arch/arm/boot/dts/exynos4412-trats2.dts| 34 +-
>  arch/arm/boot/dts/exynos5420-arndale-octa.dts  |  3 +-
>  arch/arm/boot/dts/exynos5420-peach-pit.dts |  8 ++---
>  arch/arm/boot/dts/exynos5420-smdk5420.dts  |  7 ++--
>  arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi |  4 +--
>  arch/arm/boot/dts/exynos5440-ssdk5440.dts  |  5 +--
>  arch/arm/boot/dts/exynos5800-peach-pi.dts  |  8 ++---
>  18 files changed, 118 insertions(+), 107 deletions(-)
> 
Applied this whole series, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v3 4/4] ARM: dts: Enable EC vboot context support on Peach boards

[Kukjin Kim]

On 09/21/15 22:38, Emilio López wrote:
> The Peach boards use the EC to store the vboot context information,
> so add the corresponding properties on the EC node to indicate so.
> 
> Reviewed-by: Krzysztof Kozlowski 
> Acked-by: Javier Martinez Canillas 
> Signed-off-by: Emilio López 
> ---
> 
> Changes from v1:
>  - none
> 
> Changes from v2:
>  - collect tags from Krzysztof & Javier
> 
>  arch/arm/boot/dts/exynos5420-peach-pit.dts | 1 +
>  arch/arm/boot/dts/exynos5800-peach-pi.dts  | 1 +
>  2 files changed, 2 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/exynos5420-peach-pit.dts 
> b/arch/arm/boot/dts/exynos5420-peach-pit.dts
> index 8f4d76c..ac02fb4 100644
> --- a/arch/arm/boot/dts/exynos5420-peach-pit.dts
> +++ b/arch/arm/boot/dts/exynos5420-peach-pit.dts
> @@ -935,6 +935,7 @@
>   pinctrl-0 = <_spi_cs _irq>;
>   reg = <0>;
>   spi-max-frequency = <3125000>;
> + google,has-vbc-nvram;
>  
>   controller-data {
>   samsung,spi-feedback-delay = <1>;
> diff --git a/arch/arm/boot/dts/exynos5800-peach-pi.dts 
> b/arch/arm/boot/dts/exynos5800-peach-pi.dts
> index 7d5b386..b60dec0 100644
> --- a/arch/arm/boot/dts/exynos5800-peach-pi.dts
> +++ b/arch/arm/boot/dts/exynos5800-peach-pi.dts
> @@ -898,6 +898,7 @@
>   pinctrl-0 = <_spi_cs _irq>;
>   reg = <0>;
>   spi-max-frequency = <3125000>;
> + google,has-vbc-nvram;
>  
>   controller-data {
>   samsung,spi-feedback-delay = <1>;

Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [GIT PULL] ARM: dts: Exynos improvements for 4.4-2

[Kukjin Kim]

On 10/06/15 10:54, Krzysztof Kozlowski wrote:
> Dear Kukjin,
> 
> This is an updated pull request with DTS related changes for 4.4.
> 
> Description along with a tag.
> You can find them also on the lists with my reviewed-by.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> 
>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-dt-4.4-2
> 
> for you to fetch changes up to c21dbcfefc9dc9abc42971dc1f2681b6a8677c3c:
> 
>   ARM: dts: Remove regulator-compatible usage in exynos4412-trats2 
> (2015-10-06 10:47:13 +0900)
> 
> 
> Device Tree improvements for Exynos based boards (updated pull request):
> 1. Enable DMA on Exynos4 serial ports. This old patch uncovered
>a number of other issues in dmaengine and samsung serial driver.
>All of known issues are resolved so finally enable the DMA for UART.
> 2. Fix incorrect location of display-timings node (FIMD->DP node)
>on Arndale, SMDK5250 and SMDK5240 boards.
> 3. Minor cleanups.
> 
> 
> Javier Martinez Canillas (1):
>   ARM: dts: Remove regulator-compatible usage in exynos4412-trats2
> 
> Robert Baldyga (1):
>   ARM: dts: Add DMA support for serial ports in exynos4
> 
> Sean Paul (1):
>   ARM: dts: Move display-timings node from fimd to dp in 
> exynos5250-arndale, smdk5250 and smdk5420
> 
> Tobias Jakobi (2):
>   ARM: dts: Remove redundant pinctrl settings in exynos4412-odroid
>   ARM: dts: Unify voltage regulator style in exynos4412-odroid
> 
> Vladimir Zapolskiy (1):
>   ARM: dts: Fix cpu compatible value for s3c2416
> 
>  arch/arm/boot/dts/exynos4.dtsi  |   8 ++
>  arch/arm/boot/dts/exynos4412-odroid-common.dtsi |  12 +--
>  arch/arm/boot/dts/exynos4412-trats2.dts | 105 
> 
>  arch/arm/boot/dts/exynos5250-arndale.dts|   8 +-
>  arch/arm/boot/dts/exynos5250-smdk5250.dts   |  16 ++--
>  arch/arm/boot/dts/exynos5420-smdk5420.dts   |   7 +-
>  arch/arm/boot/dts/s3c2416.dtsi  |   2 +-
>  7 files changed, 62 insertions(+), 96 deletions(-)

Pulled, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [GIT PULL] ARM: dts: Exynos improvements for 4.4-2

[Kukjin Kim]

On 10/06/15 10:54, Krzysztof Kozlowski wrote:
> Dear Kukjin,
> 
> This is an updated pull request with DTS related changes for 4.4.
> 
> Description along with a tag.
> You can find them also on the lists with my reviewed-by.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> 
>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-dt-4.4-2
> 
> for you to fetch changes up to c21dbcfefc9dc9abc42971dc1f2681b6a8677c3c:
> 
>   ARM: dts: Remove regulator-compatible usage in exynos4412-trats2 
> (2015-10-06 10:47:13 +0900)
> 
> 
> Device Tree improvements for Exynos based boards (updated pull request):
> 1. Enable DMA on Exynos4 serial ports. This old patch uncovered
>a number of other issues in dmaengine and samsung serial driver.
>All of known issues are resolved so finally enable the DMA for UART.
> 2. Fix incorrect location of display-timings node (FIMD->DP node)
>on Arndale, SMDK5250 and SMDK5240 boards.
> 3. Minor cleanups.
> 
> 
> Javier Martinez Canillas (1):
>   ARM: dts: Remove regulator-compatible usage in exynos4412-trats2
> 
> Robert Baldyga (1):
>   ARM: dts: Add DMA support for serial ports in exynos4
> 
> Sean Paul (1):
>   ARM: dts: Move display-timings node from fimd to dp in 
> exynos5250-arndale, smdk5250 and smdk5420
> 
> Tobias Jakobi (2):
>   ARM: dts: Remove redundant pinctrl settings in exynos4412-odroid
>   ARM: dts: Unify voltage regulator style in exynos4412-odroid
> 
> Vladimir Zapolskiy (1):
>   ARM: dts: Fix cpu compatible value for s3c2416
> 
>  arch/arm/boot/dts/exynos4.dtsi  |   8 ++
>  arch/arm/boot/dts/exynos4412-odroid-common.dtsi |  12 +--
>  arch/arm/boot/dts/exynos4412-trats2.dts | 105 
> 
>  arch/arm/boot/dts/exynos5250-arndale.dts|   8 +-
>  arch/arm/boot/dts/exynos5250-smdk5250.dts   |  16 ++--
>  arch/arm/boot/dts/exynos5420-smdk5420.dts   |   7 +-
>  arch/arm/boot/dts/s3c2416.dtsi  |   2 +-
>  7 files changed, 62 insertions(+), 96 deletions(-)

Pulled, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v3 4/4] ARM: dts: Enable EC vboot context support on Peach boards

[Kukjin Kim]

On 09/21/15 22:38, Emilio López wrote:
> The Peach boards use the EC to store the vboot context information,
> so add the corresponding properties on the EC node to indicate so.
> 
> Reviewed-by: Krzysztof Kozlowski 
> Acked-by: Javier Martinez Canillas 
> Signed-off-by: Emilio López 
> ---
> 
> Changes from v1:
>  - none
> 
> Changes from v2:
>  - collect tags from Krzysztof & Javier
> 
>  arch/arm/boot/dts/exynos5420-peach-pit.dts | 1 +
>  arch/arm/boot/dts/exynos5800-peach-pi.dts  | 1 +
>  2 files changed, 2 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/exynos5420-peach-pit.dts 
> b/arch/arm/boot/dts/exynos5420-peach-pit.dts
> index 8f4d76c..ac02fb4 100644
> --- a/arch/arm/boot/dts/exynos5420-peach-pit.dts
> +++ b/arch/arm/boot/dts/exynos5420-peach-pit.dts
> @@ -935,6 +935,7 @@
>   pinctrl-0 = <_spi_cs _irq>;
>   reg = <0>;
>   spi-max-frequency = <3125000>;
> + google,has-vbc-nvram;
>  
>   controller-data {
>   samsung,spi-feedback-delay = <1>;
> diff --git a/arch/arm/boot/dts/exynos5800-peach-pi.dts 
> b/arch/arm/boot/dts/exynos5800-peach-pi.dts
> index 7d5b386..b60dec0 100644
> --- a/arch/arm/boot/dts/exynos5800-peach-pi.dts
> +++ b/arch/arm/boot/dts/exynos5800-peach-pi.dts
> @@ -898,6 +898,7 @@
>   pinctrl-0 = <_spi_cs _irq>;
>   reg = <0>;
>   spi-max-frequency = <3125000>;
> + google,has-vbc-nvram;
>  
>   controller-data {
>   samsung,spi-feedback-delay = <1>;

Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH 0/5] ARM: dts: Use GPIO constants for flags cells in exynos boards

[Kukjin Kim]

On 10/07/15 22:14, Javier Martinez Canillas wrote:
> Hello,
> 
> This series contains trivial patches that use the GPIO constants
> defined in include/dt-bindings/gpio/gpio.h to express GPIO polarity
> instead of numeric values.
> 
> There is no functional change and the compiled dtbs are unchanged but
> is a good practice to use the defined macros instead of magic numbers
> since that makes the DTS more readable.
> 
> Since the changes are trivial, I thought that split the changes per
> board DTS would create an unnecessary churn but a single patch would
> maybe be harder to review so I decided that split it by SoC family
> would be a good trade off.
> 
> Please let me know if you prefer another approach.
> 
> Best regards,
> Javier
> 
> 
> Javier Martinez Canillas (5):
>   ARM: dts: Use GPIO constants for flags cells in exynos3250 boards
>   ARM: dts: Use GPIO constants for flags cells in exynos4120 boards
>   ARM: dts: Use GPIO constants for flags cells in exynos4412 boards
>   ARM: dts: Use GPIO constants for flags cells in exynos5420/5422/5800
> boards
>   ARM: dts: Use GPIO constants for flags cells in exynos5440 boards
> 
>  arch/arm/boot/dts/exynos3250-monk.dts  |  8 ++---
>  arch/arm/boot/dts/exynos3250-rinato.dts| 10 +++---
>  arch/arm/boot/dts/exynos4210-origen.dts| 15 
>  arch/arm/boot/dts/exynos4210-smdkv310.dts  |  3 +-
>  arch/arm/boot/dts/exynos4210-trats.dts | 29 +++
>  arch/arm/boot/dts/exynos4210-universal_c210.dts| 42 
> +++---
>  arch/arm/boot/dts/exynos4412-odroid-common.dtsi| 15 
>  arch/arm/boot/dts/exynos4412-odroidu3.dts  |  2 +-
>  arch/arm/boot/dts/exynos4412-odroidx.dts   |  8 ++---
>  arch/arm/boot/dts/exynos4412-origen.dts| 15 
>  arch/arm/boot/dts/exynos4412-tiny4412.dts  |  9 ++---
>  arch/arm/boot/dts/exynos4412-trats2.dts| 34 +-
>  arch/arm/boot/dts/exynos5420-arndale-octa.dts  |  3 +-
>  arch/arm/boot/dts/exynos5420-peach-pit.dts |  8 ++---
>  arch/arm/boot/dts/exynos5420-smdk5420.dts  |  7 ++--
>  arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi |  4 +--
>  arch/arm/boot/dts/exynos5440-ssdk5440.dts  |  5 +--
>  arch/arm/boot/dts/exynos5800-peach-pi.dts  |  8 ++---
>  18 files changed, 118 insertions(+), 107 deletions(-)
> 
Applied this whole series, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [GIT PULL] arm64: dts: Exynos ARMv8 improvements for 4.4

[Kukjin Kim]

Krzysztof Kozlowski wrote:
> 
> Dear Kukjin,
> 
> One ARMv8 DTS change for 4.4.
> 
> Best regards,
> Krzysztof
> 
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> 
>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-dt64-4.4
> 
> for you to fetch changes up to 235c8e96f54a76bee201a7c86620c351a30b1ac6:
> 
>   arm64: dts: Add BUS1 instance pinctrl support for exynos7 (2015-09-16 
> 09:03:09 +0900)
> 
> 
> Device Tree improvements for Exynos ARMv8 based boards:
> 1. Add a BUS1 instance pinctrl for Exynos7 SoC.
> 
> 
> Alim Akhtar (1):
>   arm64: dts: Add BUS1 instance pinctrl support for exynos7
> 
>  arch/arm64/boot/dts/exynos/exynos7-pinctrl.dtsi | 103 
> 
>  arch/arm64/boot/dts/exynos/exynos7.dtsi |   7 ++
>  2 files changed, 110 insertions(+)

Looks good to me. Since just one patch in this pull-request if you don't mind,
let me take the patch directly with your signed-off.

- Kukjin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [GIT PULL] ARM: dts: Exynos improvements for 4.4

[Kukjin Kim]

Krzysztof Kozlowski wrote:
> 
> Dear Kukjin,
> 
Hi,

> DTS related changes for 4.4.
> 
> Description along with a tag.
> You can find them also on the lists with my reviewed-by.
> 
I have small comments. Then I could just pull your branch...

> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> 
>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-dt-4.4
> 
> for you to fetch changes up to 01dd011b7a0230a426a79475ae452298421a16e4:
> 
>   ARM: dts: exynos4412-trats2: remove regulator-compatible usage (2015-09-30 
> 09:03:03 +0900)
> 
> 
> Device Tree improvements for Exynos based boards:
> 1. Enable DMA on Exynos4 serial ports. This old patch uncovered
>a number of other issues in dmaengine and samsung serial driver.
>All of known issues are resolved so finally enable the DMA for UART.
> 2. Fix incorrect location of display-timings node (FIMD->DP node).
> 3. Minor cleanups.
> 
> 
> Javier Martinez Canillas (1):
>   ARM: dts: exynos4412-trats2: remove regulator-compatible usage

Can you please move the dt name at the end of subject like others?

> 
> Robert Baldyga (1):
>   ARM: dts: Add DMA support for serial ports in exynos4
> 
> Sean Paul (1):
>   ARM: dts: Move display-timings node from fimd to dp on Exynos

For all of exynos? If not, please specify the dt file in subject so that we
could realize what has been updated.

> 
> Tobias Jakobi (2):
>   ARM: dts: Remove redundant pinctrl settings in exynos4412-odroid
>   ARM: dts: Unify voltage regulator style in exynos4412-odroid
> 
> Vladimir Zapolskiy (1):
>   ARM: dts: Fix cpu compatible value for s3c2416
> 
>  arch/arm/boot/dts/exynos4.dtsi  |   8 ++
>  arch/arm/boot/dts/exynos4412-odroid-common.dtsi |  12 +--
>  arch/arm/boot/dts/exynos4412-trats2.dts | 105 
> 
>  arch/arm/boot/dts/exynos5250-arndale.dts|   8 +-
>  arch/arm/boot/dts/exynos5250-smdk5250.dts   |  16 ++--
>  arch/arm/boot/dts/exynos5420-smdk5420.dts   |   7 +-
>  arch/arm/boot/dts/s3c2416.dtsi  |   2 +-
>  7 files changed, 62 insertions(+), 96 deletions(-)

- Kukjin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [GIT PULL] ARM: dts: Exynos improvements for 4.4

[Kukjin Kim]

Krzysztof Kozlowski wrote:
> 
> Dear Kukjin,
> 
Hi,

> DTS related changes for 4.4.
> 
> Description along with a tag.
> You can find them also on the lists with my reviewed-by.
> 
I have small comments. Then I could just pull your branch...

> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> 
>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-dt-4.4
> 
> for you to fetch changes up to 01dd011b7a0230a426a79475ae452298421a16e4:
> 
>   ARM: dts: exynos4412-trats2: remove regulator-compatible usage (2015-09-30 
> 09:03:03 +0900)
> 
> 
> Device Tree improvements for Exynos based boards:
> 1. Enable DMA on Exynos4 serial ports. This old patch uncovered
>a number of other issues in dmaengine and samsung serial driver.
>All of known issues are resolved so finally enable the DMA for UART.
> 2. Fix incorrect location of display-timings node (FIMD->DP node).
> 3. Minor cleanups.
> 
> 
> Javier Martinez Canillas (1):
>   ARM: dts: exynos4412-trats2: remove regulator-compatible usage

Can you please move the dt name at the end of subject like others?

> 
> Robert Baldyga (1):
>   ARM: dts: Add DMA support for serial ports in exynos4
> 
> Sean Paul (1):
>   ARM: dts: Move display-timings node from fimd to dp on Exynos

For all of exynos? If not, please specify the dt file in subject so that we
could realize what has been updated.

> 
> Tobias Jakobi (2):
>   ARM: dts: Remove redundant pinctrl settings in exynos4412-odroid
>   ARM: dts: Unify voltage regulator style in exynos4412-odroid
> 
> Vladimir Zapolskiy (1):
>   ARM: dts: Fix cpu compatible value for s3c2416
> 
>  arch/arm/boot/dts/exynos4.dtsi  |   8 ++
>  arch/arm/boot/dts/exynos4412-odroid-common.dtsi |  12 +--
>  arch/arm/boot/dts/exynos4412-trats2.dts | 105 
> 
>  arch/arm/boot/dts/exynos5250-arndale.dts|   8 +-
>  arch/arm/boot/dts/exynos5250-smdk5250.dts   |  16 ++--
>  arch/arm/boot/dts/exynos5420-smdk5420.dts   |   7 +-
>  arch/arm/boot/dts/s3c2416.dtsi  |   2 +-
>  7 files changed, 62 insertions(+), 96 deletions(-)

- Kukjin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [GIT PULL] arm64: dts: Exynos ARMv8 improvements for 4.4

[Kukjin Kim]

Krzysztof Kozlowski wrote:
> 
> Dear Kukjin,
> 
> One ARMv8 DTS change for 4.4.
> 
> Best regards,
> Krzysztof
> 
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> 
>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-dt64-4.4
> 
> for you to fetch changes up to 235c8e96f54a76bee201a7c86620c351a30b1ac6:
> 
>   arm64: dts: Add BUS1 instance pinctrl support for exynos7 (2015-09-16 
> 09:03:09 +0900)
> 
> 
> Device Tree improvements for Exynos ARMv8 based boards:
> 1. Add a BUS1 instance pinctrl for Exynos7 SoC.
> 
> 
> Alim Akhtar (1):
>   arm64: dts: Add BUS1 instance pinctrl support for exynos7
> 
>  arch/arm64/boot/dts/exynos/exynos7-pinctrl.dtsi | 103 
> 
>  arch/arm64/boot/dts/exynos/exynos7.dtsi |   7 ++
>  2 files changed, 110 insertions(+)

Looks good to me. Since just one patch in this pull-request if you don't mind,
let me take the patch directly with your signed-off.

- Kukjin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [GIT PULL] Samsung fixes for v4.3

[Kukjin Kim]

Krzysztof Kozlowski wrote:
> 
> On 30.09.2015 15:50, Kukjin Kim wrote:
> > On 09/30/15 08:59, Krzysztof Kozlowski wrote:
> >> Dear Kukjin,
> >>
> >> Below you will find fixes for current release cycle which are not
> >> present yet in your tree.
> >>
> >> Best regards,
> >> Krzysztof
> >>
> >>
> >> The following changes since commit 
> >> 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> >>
> >>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> >>
> >> are available in the git repository at:
> >>
> >>   https://github.com/krzk/linux.git tags/samsung-fixes-4.3
> >>
> >> for you to fetch changes up to c7d2ecd9f64c351cb4d551f1f472d0fc09c3cae8:
> >>
> >>   ARM: dts: Fix wrong clock binding for sysmmu_fimd1_1 on exynos5420 
> >> (2015-09-29 15:39:58 +0900)
> >>
> >> 
> >> Fixes for Exynos (DT and mach code):
> >> 1. Finally fix booting of all 8 cores on Exynos Octa (Exynos542x): all
> >>8 cores are booting and can be used. The fix, based on vendor
> >>code and bootloader behavior, is as for time being only
> >>for MCPM enabled path.
> >> 2. Fix thermal boot issue on SMDK5250.
> >> 3. Fix invalid clock used for FIMD IOMMU.
> >>
> > Pulled, thanks.
> >
> > Note it will be sent to upstream in a day.
> 
> A day extended to a week. Please do not hold the fixes but send them. If
> they reached Linus tree late and they required any further fix, then we
> would have less time for any updates.
> 
Sorry for the delay and it's my fault. I'll handle it tonight...

> The same applies for regular pull request for 4.4. For previous v4.3
> release many changes were too late (so they could even slip from 4.3 to
> 4.4). Can we just avoid such issues and send pull requests earlier?
> 
Krzysztof, I sent a pull request lately because of handling of cross-tree but I
don't think so it causes some missing because it was due to cross tree not only
mine. Please don't worry about that I'll handle it.

Anyway thanks for your gentle reminder.

- Kukjin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [GIT PULL] Samsung fixes for v4.3

[Kukjin Kim]

Krzysztof Kozlowski wrote:
> 
> On 30.09.2015 15:50, Kukjin Kim wrote:
> > On 09/30/15 08:59, Krzysztof Kozlowski wrote:
> >> Dear Kukjin,
> >>
> >> Below you will find fixes for current release cycle which are not
> >> present yet in your tree.
> >>
> >> Best regards,
> >> Krzysztof
> >>
> >>
> >> The following changes since commit 
> >> 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> >>
> >>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> >>
> >> are available in the git repository at:
> >>
> >>   https://github.com/krzk/linux.git tags/samsung-fixes-4.3
> >>
> >> for you to fetch changes up to c7d2ecd9f64c351cb4d551f1f472d0fc09c3cae8:
> >>
> >>   ARM: dts: Fix wrong clock binding for sysmmu_fimd1_1 on exynos5420 
> >> (2015-09-29 15:39:58 +0900)
> >>
> >> 
> >> Fixes for Exynos (DT and mach code):
> >> 1. Finally fix booting of all 8 cores on Exynos Octa (Exynos542x): all
> >>8 cores are booting and can be used. The fix, based on vendor
> >>code and bootloader behavior, is as for time being only
> >>for MCPM enabled path.
> >> 2. Fix thermal boot issue on SMDK5250.
> >> 3. Fix invalid clock used for FIMD IOMMU.
> >>
> > Pulled, thanks.
> >
> > Note it will be sent to upstream in a day.
> 
> A day extended to a week. Please do not hold the fixes but send them. If
> they reached Linus tree late and they required any further fix, then we
> would have less time for any updates.
> 
Sorry for the delay and it's my fault. I'll handle it tonight...

> The same applies for regular pull request for 4.4. For previous v4.3
> release many changes were too late (so they could even slip from 4.3 to
> 4.4). Can we just avoid such issues and send pull requests earlier?
> 
Krzysztof, I sent a pull request lately because of handling of cross-tree but I
don't think so it causes some missing because it was due to cross tree not only
mine. Please don't worry about that I'll handle it.

Anyway thanks for your gentle reminder.

- Kukjin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] ARM: dts: Add Exynos5250 Snow Rev5+ support

[Kukjin Kim]

On 09/30/15 09:30, Krzysztof Kozlowski wrote:
> On 29.09.2015 20:57, Javier Martinez Canillas wrote:
>> There are 2 revisions of the Exynos5250 Snow Chromebook that were shipped:
>> Rev4 and Rev5. The only difference between these 2 revisions is the codec,
>> Rev4 has a max98095 codec while Rev5 has a max98090.
>>
>> Mainline only supports Rev4 so this patch moves the common device nodes to
>> a DTSI file and adds a DTS for the Exynos5250 Snow Rev5.
>>
>> The Snow Rev5 DTS is based on the DTS found in the ChromiumOS 3.8 tree.
>>
>> Signed-off-by: Javier Martinez Canillas 
>>
>> ---
>>
>> The DTS in the vendor ChromeOS tree are called exynos5250-snow-rev{4,5}.dtb
>> but I decided to leave Rev4 as exynos5250-snow.dtb to avoid breaking u-boot
>> that has CONFIG_DEFAULT_DEVICE_TREE="exynos5250-snow" in snow_defconfig.
>>
>> Also, ChromiumOS Rev4 DTS has "google,snow-rev4" in its compatible string
>> but was not added in mainline since Rev4 firmware fallbacks to "google,snow"
>> and Rev5 searches for "google,snow-rev5". That way the compatible string
>> could be consistent with the DTS naming and still be able to pack both Rev4
>> and Rev5 FDT in the same FIT image and let the firmware pick the correct FDT.
>>
>>  arch/arm/boot/dts/Makefile|   1 +
>>  arch/arm/boot/dts/exynos5250-snow-common.dtsi | 684 
>> ++
>>  arch/arm/boot/dts/exynos5250-snow-rev5.dts|  47 ++
>>  arch/arm/boot/dts/exynos5250-snow.dts | 666 
>> +
>>  4 files changed, 733 insertions(+), 665 deletions(-)
>>  create mode 100644 arch/arm/boot/dts/exynos5250-snow-common.dtsi
>>  create mode 100644 arch/arm/boot/dts/exynos5250-snow-rev5.dts
> 
> Now the exynos5250-snow.dts means in fact Rev4... but there is no
> information in DTS about it. I think adding compatible
> "google,snow-rev4" makes sense:
> 1. For informational purposes (this could be also handled with a comment).
> 2. Later one could decide to switch the default meaning of "google,snow"
> to Rev5 and the real compatible (rev4) will be there already.
> 
> Could you add the new compatible and fix patch issues pointed by Doug?
> 
Documenting for the compatibles would be required even I already applied
its updated patch...

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2] ARM: dts: Add Exynos5250 Snow Rev5+ support

[Kukjin Kim]

On 09/30/15 15:44, Javier Martinez Canillas wrote:
> There are 2 revisions of the Exynos5250 Snow Chromebook that were shipped:
> Rev4 and Rev5. The only difference between these 2 revisions is the codec,
> Rev4 has a max98095 codec while Rev5 has a max98090.
> 
> Mainline only supports Rev4 so this patch moves the common device nodes to
> a DTSI file and adds a DTS for the Exynos5250 Snow Rev5.
> 
> The Snow Rev5 DTS is based on the DTS found in the ChromiumOS 3.8 tree.
> 
> Signed-off-by: Javier Martinez Canillas 
> Tested-by: Mauro Carvalho Chehab 
> Reviewed-by: Douglas Anderson 
> 
> ---
> 
> Changes in v2:
> - Add Mauro Carvalho Chehab's Tested-by tag.
> - Add Doug Anderson's Reviewed-by tag.
> - Remove warning about adding a whitespace error. Suggested by Doug Anderson.
> - Make Rev{4,5} codec pinctrl properties to match. Suggested by Doug Anderson.
> - Add "google,snow-rev4" to compatible string. Suggested by Krzysztof 
> Kozlowski.
> 
>  arch/arm/boot/dts/Makefile|   1 +
>  arch/arm/boot/dts/exynos5250-snow-common.dtsi | 684 
> ++
>  arch/arm/boot/dts/exynos5250-snow-rev5.dts|  47 ++
>  arch/arm/boot/dts/exynos5250-snow.dts | 671 +
>  4 files changed, 736 insertions(+), 667 deletions(-)
>  create mode 100644 arch/arm/boot/dts/exynos5250-snow-common.dtsi
>  create mode 100644 arch/arm/boot/dts/exynos5250-snow-rev5.dts
> 
Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [GIT PULL] Samsung fixes for v4.3

[Kukjin Kim]

On 09/30/15 08:59, Krzysztof Kozlowski wrote:
> Dear Kukjin,
> 
> Below you will find fixes for current release cycle which are not
> present yet in your tree.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> 
>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-fixes-4.3
> 
> for you to fetch changes up to c7d2ecd9f64c351cb4d551f1f472d0fc09c3cae8:
> 
>   ARM: dts: Fix wrong clock binding for sysmmu_fimd1_1 on exynos5420 
> (2015-09-29 15:39:58 +0900)
> 
> 
> Fixes for Exynos (DT and mach code):
> 1. Finally fix booting of all 8 cores on Exynos Octa (Exynos542x): all
>8 cores are booting and can be used. The fix, based on vendor
>code and bootloader behavior, is as for time being only
>for MCPM enabled path.
> 2. Fix thermal boot issue on SMDK5250.
> 3. Fix invalid clock used for FIMD IOMMU.
> 
Pulled, thanks.

Note it will be sent to upstream in a day.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [GIT PULL] Samsung fixes for v4.3

[Kukjin Kim]

On 09/30/15 08:59, Krzysztof Kozlowski wrote:
> Dear Kukjin,
> 
> Below you will find fixes for current release cycle which are not
> present yet in your tree.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
> 
>   Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-fixes-4.3
> 
> for you to fetch changes up to c7d2ecd9f64c351cb4d551f1f472d0fc09c3cae8:
> 
>   ARM: dts: Fix wrong clock binding for sysmmu_fimd1_1 on exynos5420 
> (2015-09-29 15:39:58 +0900)
> 
> 
> Fixes for Exynos (DT and mach code):
> 1. Finally fix booting of all 8 cores on Exynos Octa (Exynos542x): all
>8 cores are booting and can be used. The fix, based on vendor
>code and bootloader behavior, is as for time being only
>for MCPM enabled path.
> 2. Fix thermal boot issue on SMDK5250.
> 3. Fix invalid clock used for FIMD IOMMU.
> 
Pulled, thanks.

Note it will be sent to upstream in a day.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] ARM: dts: Add Exynos5250 Snow Rev5+ support

[Kukjin Kim]

On 09/30/15 09:30, Krzysztof Kozlowski wrote:
> On 29.09.2015 20:57, Javier Martinez Canillas wrote:
>> There are 2 revisions of the Exynos5250 Snow Chromebook that were shipped:
>> Rev4 and Rev5. The only difference between these 2 revisions is the codec,
>> Rev4 has a max98095 codec while Rev5 has a max98090.
>>
>> Mainline only supports Rev4 so this patch moves the common device nodes to
>> a DTSI file and adds a DTS for the Exynos5250 Snow Rev5.
>>
>> The Snow Rev5 DTS is based on the DTS found in the ChromiumOS 3.8 tree.
>>
>> Signed-off-by: Javier Martinez Canillas 
>>
>> ---
>>
>> The DTS in the vendor ChromeOS tree are called exynos5250-snow-rev{4,5}.dtb
>> but I decided to leave Rev4 as exynos5250-snow.dtb to avoid breaking u-boot
>> that has CONFIG_DEFAULT_DEVICE_TREE="exynos5250-snow" in snow_defconfig.
>>
>> Also, ChromiumOS Rev4 DTS has "google,snow-rev4" in its compatible string
>> but was not added in mainline since Rev4 firmware fallbacks to "google,snow"
>> and Rev5 searches for "google,snow-rev5". That way the compatible string
>> could be consistent with the DTS naming and still be able to pack both Rev4
>> and Rev5 FDT in the same FIT image and let the firmware pick the correct FDT.
>>
>>  arch/arm/boot/dts/Makefile|   1 +
>>  arch/arm/boot/dts/exynos5250-snow-common.dtsi | 684 
>> ++
>>  arch/arm/boot/dts/exynos5250-snow-rev5.dts|  47 ++
>>  arch/arm/boot/dts/exynos5250-snow.dts | 666 
>> +
>>  4 files changed, 733 insertions(+), 665 deletions(-)
>>  create mode 100644 arch/arm/boot/dts/exynos5250-snow-common.dtsi
>>  create mode 100644 arch/arm/boot/dts/exynos5250-snow-rev5.dts
> 
> Now the exynos5250-snow.dts means in fact Rev4... but there is no
> information in DTS about it. I think adding compatible
> "google,snow-rev4" makes sense:
> 1. For informational purposes (this could be also handled with a comment).
> 2. Later one could decide to switch the default meaning of "google,snow"
> to Rev5 and the real compatible (rev4) will be there already.
> 
> Could you add the new compatible and fix patch issues pointed by Doug?
> 
Documenting for the compatibles would be required even I already applied
its updated patch...

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2] ARM: dts: Add Exynos5250 Snow Rev5+ support

[Kukjin Kim]

On 09/30/15 15:44, Javier Martinez Canillas wrote:
> There are 2 revisions of the Exynos5250 Snow Chromebook that were shipped:
> Rev4 and Rev5. The only difference between these 2 revisions is the codec,
> Rev4 has a max98095 codec while Rev5 has a max98090.
> 
> Mainline only supports Rev4 so this patch moves the common device nodes to
> a DTSI file and adds a DTS for the Exynos5250 Snow Rev5.
> 
> The Snow Rev5 DTS is based on the DTS found in the ChromiumOS 3.8 tree.
> 
> Signed-off-by: Javier Martinez Canillas 
> Tested-by: Mauro Carvalho Chehab 
> Reviewed-by: Douglas Anderson 
> 
> ---
> 
> Changes in v2:
> - Add Mauro Carvalho Chehab's Tested-by tag.
> - Add Doug Anderson's Reviewed-by tag.
> - Remove warning about adding a whitespace error. Suggested by Doug Anderson.
> - Make Rev{4,5} codec pinctrl properties to match. Suggested by Doug Anderson.
> - Add "google,snow-rev4" to compatible string. Suggested by Krzysztof 
> Kozlowski.
> 
>  arch/arm/boot/dts/Makefile|   1 +
>  arch/arm/boot/dts/exynos5250-snow-common.dtsi | 684 
> ++
>  arch/arm/boot/dts/exynos5250-snow-rev5.dts|  47 ++
>  arch/arm/boot/dts/exynos5250-snow.dts | 671 +
>  4 files changed, 736 insertions(+), 667 deletions(-)
>  create mode 100644 arch/arm/boot/dts/exynos5250-snow-common.dtsi
>  create mode 100644 arch/arm/boot/dts/exynos5250-snow-rev5.dts
> 
Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2 0/7] Add support for Exynos SROM Controller driver

[Kukjin Kim]

On 08/24/15 17:02, Pankaj Dubey wrote:
> This patch set adds support for Exynos SROM controller DT based driver.
> Currently SROM register sets are used only during S2R, so driver
> basically added for taking care of S2R. It will help us in removing
> static mapping from exynos.c and other extra code handline during S2R.
> 
> This patch set also updated exynos4 and exynos5 dtsi files for with device
> node for srom, and added binding documentation for the same.
> 
> First two patches are some minor cleanup in mach-exynos.
> 
> Patchset v1 was posted here[1]
> [1]: https://lkml.org/lkml/2015/4/29/98
> 
> Changes since v1:
>  - Rebased to latest kgene tree.
>  - Addressed review comments from Krzysztof Kozlowski.
>  - Add two new patches for minor cleanup in exynos.c and map.h
> 
> Pankaj Dubey (7):
>   ARM: EXYNOS: remove unused static mapping of CMU for exynos5
>   ARM: EXYNOS: code cleanup in map.h
>   drivers: soc: add support for exynos SROM driver
>   ARM: EXYNOS: Remove SROM related register settings from mach-exynos
>   ARM: dts: add SROM device node for exynos4
>   ARM: dts: add SROM device node for exynos5
>   Documentation: dt-bindings: add exynos-srom binding information
> 
>  .../bindings/arm/samsung/exynos-srom.txt   |  12 ++
>  arch/arm/boot/dts/exynos4.dtsi |   5 +
>  arch/arm/boot/dts/exynos5.dtsi |   5 +
>  arch/arm/mach-exynos/Kconfig   |   2 +
>  arch/arm/mach-exynos/common.h  |   2 -
>  arch/arm/mach-exynos/exynos.c  |  22 
>  arch/arm/mach-exynos/include/mach/map.h|   8 --
>  arch/arm/mach-exynos/regs-srom.h   |  53 
>  arch/arm/mach-exynos/suspend.c |  20 +--
>  arch/arm/plat-samsung/include/plat/map-s5p.h   |   1 -
>  drivers/soc/Kconfig|   1 +
>  drivers/soc/Makefile   |   1 +
>  drivers/soc/samsung/Kconfig|  13 ++
>  drivers/soc/samsung/Makefile   |   1 +
>  drivers/soc/samsung/exynos-srom.c  | 143 
> +
>  drivers/soc/samsung/exynos-srom.h  |  51 
>  16 files changed, 236 insertions(+), 104 deletions(-)
>  create mode 100644 
> Documentation/devicetree/bindings/arm/samsung/exynos-srom.txt
>  delete mode 100644 arch/arm/mach-exynos/regs-srom.h
>  create mode 100644 drivers/soc/samsung/Kconfig
>  create mode 100644 drivers/soc/samsung/Makefile
>  create mode 100644 drivers/soc/samsung/exynos-srom.c
>  create mode 100644 drivers/soc/samsung/exynos-srom.h
> 
Hi Pankaj,

Can you please address comments as per Krzysztof's review?...

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] ARM: dts: Fix LEDs on exynos5422-odroidxu3

[Kukjin Kim]

On 09/17/15 08:09, Kukjin Kim wrote:
> On 09/02/15 23:48, Krzysztof Kozlowski wrote:
>> The LEDs on Odroid XU3 family boards could not properly probe because PWM
>> outputs were reduced only to PWM for fan. Fix this to:
>>  - Odroid XU3 and XU3-Lite: 4 outputs (although the PWM for MIPI
>>probably is redundant because board does not have MIPI connector
>>available);
>>  - Odroid XU4: 2 outputs.
>>
>> This fixes warnings on dmesg:
>> [4.838712] samsung-pwm 12dd.pwm: tried to request PWM channel 1 
>> without output
>> [4.838725] leds_pwm pwmleds: unable to request PWM for green:mmc0: -22
>> [4.838767] leds_pwm: probe of pwmleds failed with error -22
>>
>> Signed-off-by: Krzysztof Kozlowski 
>>
>> ---
>>
>> Patch depends/is rebased on latest DTS for Odroid XU4 board:
>>  - http://www.spinics.net/lists/arm-kernel/msg442474.html
>>  - http://www.spinics.net/lists/arm-kernel/msg442475.html
>> ---
> 
> Applied, thanks.
> 
Oops, I mean already this change is included in your another patch.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] ARM: dts: Fix LEDs on exynos5422-odroidxu3

[Kukjin Kim]

On 09/02/15 23:48, Krzysztof Kozlowski wrote:
> The LEDs on Odroid XU3 family boards could not properly probe because PWM
> outputs were reduced only to PWM for fan. Fix this to:
>  - Odroid XU3 and XU3-Lite: 4 outputs (although the PWM for MIPI
>probably is redundant because board does not have MIPI connector
>available);
>  - Odroid XU4: 2 outputs.
> 
> This fixes warnings on dmesg:
> [4.838712] samsung-pwm 12dd.pwm: tried to request PWM channel 1 
> without output
> [4.838725] leds_pwm pwmleds: unable to request PWM for green:mmc0: -22
> [4.838767] leds_pwm: probe of pwmleds failed with error -22
> 
> Signed-off-by: Krzysztof Kozlowski 
> 
> ---
> 
> Patch depends/is rebased on latest DTS for Odroid XU4 board:
>  - http://www.spinics.net/lists/arm-kernel/msg442474.html
>  - http://www.spinics.net/lists/arm-kernel/msg442475.html
> ---

Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] cpufreq: s5pv210: remove superfluous CONFIG_PM ifdefs

[Kukjin Kim]

On 09/09/15 10:14, Rafael J. Wysocki wrote:
> On Tuesday, September 08, 2015 07:02:12 PM Bartlomiej Zolnierkiewicz wrote:
>> CONFIG_PM ifdefs are superfluous and can be removed.
> 
> I guess Kukjin can apply this one?
> 
Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2] ARM: exynos_defconfig: Enable USB Video Class support

[Kukjin Kim]

On 09/15/15 09:02, Krzysztof Kozlowski wrote:
> On 14.09.2015 21:04, Javier Martinez Canillas wrote:
>> The Exynos5420 Peach Pit and Exynos5800 Peach Pi boards have a built-in
>> Silicon Motion USB UVC WebCam. Enable support for the USB Video Class
>> driver and its needed media Kconfig symbols so the camera is supported.
>>
>> Signed-off-by: Javier Martinez Canillas 
>>
>> ---
>>
>> Changes in v2:
>> - Enable tristate Kconfig options as module instead of built-in.
>>   Suggested by Krzysztof Kozlowski.
> 
> Reviewed-by: Krzysztof Kozlowski 
> 
Applied, thanks.

- Kukjin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2] ARM: dts: Fix LEDs on exynos5422-odroidxu3

[Kukjin Kim]

On 09/16/15 08:54, Krzysztof Kozlowski wrote:
> On 16.09.2015 08:35, Kukjin Kim wrote:
>> On 09/13/15 18:32, Krzysztof Kozlowski wrote:
>>> The LEDs on Odroid XU3 family boards could not properly probe because PWM
>>> outputs were reduced only to PWM for fan. Fix it for Odroid XU3 and
>>> XU3-Lite boards by switching to usage of all 4 outputs (although the PWM
>>> for MIPI probably is redundant because board does not have MIPI
>>> connector available).
>>>
>>> This fixes warnings on dmesg:
>>> [4.838712] samsung-pwm 12dd.pwm: tried to request PWM channel 1 
>>> without output
>>> [4.838725] leds_pwm pwmleds: unable to request PWM for green:mmc0: -22
>>> [4.838767] leds_pwm: probe of pwmleds failed with error -22
>>>
>>> Signed-off-by: Krzysztof Kozlowski 
>>>
>>> ---
>>>
>>> Changes since v1:
>>> 1. Do not rebase on patchset adding support for Odroid XU4 board. Rebase
>>>just on current next.
>>> ---
>>
>> Applied, thanks.
>>
> 
> Thanks. This is actually a candidate for current v4.3 cycle. It fixes
> issue with LEDs for Odroid XU3 caused by Anand's b685d540cc26:
> The offending commit b685d540cc26 was merged in v4.3.
> I forgot to add "fixes" tag.
>   Fixes: b685d540cc26 ("ARM: dts: Add pwm-fan node for 
> exynos5422-odroidxu3")
> 
> Can you send it to arm-soc during this cycle?
> 
Why not? Will do it ;-)

> For current v4.3 Bartlomiej's patch is also an important candidate:
> "ARM: dts: add suspend opp to exynos4412"
> 
Thanks for gentle reminder.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v4 0/4] cpufreq-dt: add suspend frequency support

[Kukjin Kim]

On 09/08/15 14:10, Viresh Kumar wrote:
> On 08-09-15, 13:48, Krzysztof Kozlowski wrote:
>> Somehow my mind stuck on solving Exynos4x12 cpufreq issues.
>>
>> Right, it should go through Rafael's, probably except DTS patch (4/4)
>> because it depends on previous DTS changes. These changes are still in
>> arm-soc, not in Linus' tree [0].
> 
> That's bad :(
> 
> Anyway, 4/4 is kind of independent to this series, in the sense that
> it wouldn't harm even if it gets applied separately.
> 
> So, go ahead and apply 4/4 to Samsung's tree and rest of this can be
> picked by Rafael.
> 
Applied 4/4 into samsung tree, thanks.

- Kukjin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] cpufreq: s5pv210: remove superfluous CONFIG_PM ifdefs

[Kukjin Kim]

On 09/09/15 10:14, Rafael J. Wysocki wrote:
> On Tuesday, September 08, 2015 07:02:12 PM Bartlomiej Zolnierkiewicz wrote:
>> CONFIG_PM ifdefs are superfluous and can be removed.
> 
> I guess Kukjin can apply this one?
> 
Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v4 0/4] cpufreq-dt: add suspend frequency support

[Kukjin Kim]

On 09/08/15 14:10, Viresh Kumar wrote:
> On 08-09-15, 13:48, Krzysztof Kozlowski wrote:
>> Somehow my mind stuck on solving Exynos4x12 cpufreq issues.
>>
>> Right, it should go through Rafael's, probably except DTS patch (4/4)
>> because it depends on previous DTS changes. These changes are still in
>> arm-soc, not in Linus' tree [0].
> 
> That's bad :(
> 
> Anyway, 4/4 is kind of independent to this series, in the sense that
> it wouldn't harm even if it gets applied separately.
> 
> So, go ahead and apply 4/4 to Samsung's tree and rest of this can be
> picked by Rafael.
> 
Applied 4/4 into samsung tree, thanks.

- Kukjin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2] ARM: exynos_defconfig: Enable USB Video Class support

[Kukjin Kim]

On 09/15/15 09:02, Krzysztof Kozlowski wrote:
> On 14.09.2015 21:04, Javier Martinez Canillas wrote:
>> The Exynos5420 Peach Pit and Exynos5800 Peach Pi boards have a built-in
>> Silicon Motion USB UVC WebCam. Enable support for the USB Video Class
>> driver and its needed media Kconfig symbols so the camera is supported.
>>
>> Signed-off-by: Javier Martinez Canillas 
>>
>> ---
>>
>> Changes in v2:
>> - Enable tristate Kconfig options as module instead of built-in.
>>   Suggested by Krzysztof Kozlowski.
> 
> Reviewed-by: Krzysztof Kozlowski 
> 
Applied, thanks.

- Kukjin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2 0/7] Add support for Exynos SROM Controller driver

[Kukjin Kim]

On 08/24/15 17:02, Pankaj Dubey wrote:
> This patch set adds support for Exynos SROM controller DT based driver.
> Currently SROM register sets are used only during S2R, so driver
> basically added for taking care of S2R. It will help us in removing
> static mapping from exynos.c and other extra code handline during S2R.
> 
> This patch set also updated exynos4 and exynos5 dtsi files for with device
> node for srom, and added binding documentation for the same.
> 
> First two patches are some minor cleanup in mach-exynos.
> 
> Patchset v1 was posted here[1]
> [1]: https://lkml.org/lkml/2015/4/29/98
> 
> Changes since v1:
>  - Rebased to latest kgene tree.
>  - Addressed review comments from Krzysztof Kozlowski.
>  - Add two new patches for minor cleanup in exynos.c and map.h
> 
> Pankaj Dubey (7):
>   ARM: EXYNOS: remove unused static mapping of CMU for exynos5
>   ARM: EXYNOS: code cleanup in map.h
>   drivers: soc: add support for exynos SROM driver
>   ARM: EXYNOS: Remove SROM related register settings from mach-exynos
>   ARM: dts: add SROM device node for exynos4
>   ARM: dts: add SROM device node for exynos5
>   Documentation: dt-bindings: add exynos-srom binding information
> 
>  .../bindings/arm/samsung/exynos-srom.txt   |  12 ++
>  arch/arm/boot/dts/exynos4.dtsi |   5 +
>  arch/arm/boot/dts/exynos5.dtsi |   5 +
>  arch/arm/mach-exynos/Kconfig   |   2 +
>  arch/arm/mach-exynos/common.h  |   2 -
>  arch/arm/mach-exynos/exynos.c  |  22 
>  arch/arm/mach-exynos/include/mach/map.h|   8 --
>  arch/arm/mach-exynos/regs-srom.h   |  53 
>  arch/arm/mach-exynos/suspend.c |  20 +--
>  arch/arm/plat-samsung/include/plat/map-s5p.h   |   1 -
>  drivers/soc/Kconfig|   1 +
>  drivers/soc/Makefile   |   1 +
>  drivers/soc/samsung/Kconfig|  13 ++
>  drivers/soc/samsung/Makefile   |   1 +
>  drivers/soc/samsung/exynos-srom.c  | 143 
> +
>  drivers/soc/samsung/exynos-srom.h  |  51 
>  16 files changed, 236 insertions(+), 104 deletions(-)
>  create mode 100644 
> Documentation/devicetree/bindings/arm/samsung/exynos-srom.txt
>  delete mode 100644 arch/arm/mach-exynos/regs-srom.h
>  create mode 100644 drivers/soc/samsung/Kconfig
>  create mode 100644 drivers/soc/samsung/Makefile
>  create mode 100644 drivers/soc/samsung/exynos-srom.c
>  create mode 100644 drivers/soc/samsung/exynos-srom.h
> 
Hi Pankaj,

Can you please address comments as per Krzysztof's review?...

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] ARM: dts: Fix LEDs on exynos5422-odroidxu3

[Kukjin Kim]

On 09/02/15 23:48, Krzysztof Kozlowski wrote:
> The LEDs on Odroid XU3 family boards could not properly probe because PWM
> outputs were reduced only to PWM for fan. Fix this to:
>  - Odroid XU3 and XU3-Lite: 4 outputs (although the PWM for MIPI
>probably is redundant because board does not have MIPI connector
>available);
>  - Odroid XU4: 2 outputs.
> 
> This fixes warnings on dmesg:
> [4.838712] samsung-pwm 12dd.pwm: tried to request PWM channel 1 
> without output
> [4.838725] leds_pwm pwmleds: unable to request PWM for green:mmc0: -22
> [4.838767] leds_pwm: probe of pwmleds failed with error -22
> 
> Signed-off-by: Krzysztof Kozlowski 
> 
> ---
> 
> Patch depends/is rebased on latest DTS for Odroid XU4 board:
>  - http://www.spinics.net/lists/arm-kernel/msg442474.html
>  - http://www.spinics.net/lists/arm-kernel/msg442475.html
> ---

Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] ARM: dts: Fix LEDs on exynos5422-odroidxu3

[Kukjin Kim]

On 09/17/15 08:09, Kukjin Kim wrote:
> On 09/02/15 23:48, Krzysztof Kozlowski wrote:
>> The LEDs on Odroid XU3 family boards could not properly probe because PWM
>> outputs were reduced only to PWM for fan. Fix this to:
>>  - Odroid XU3 and XU3-Lite: 4 outputs (although the PWM for MIPI
>>probably is redundant because board does not have MIPI connector
>>available);
>>  - Odroid XU4: 2 outputs.
>>
>> This fixes warnings on dmesg:
>> [4.838712] samsung-pwm 12dd.pwm: tried to request PWM channel 1 
>> without output
>> [4.838725] leds_pwm pwmleds: unable to request PWM for green:mmc0: -22
>> [4.838767] leds_pwm: probe of pwmleds failed with error -22
>>
>> Signed-off-by: Krzysztof Kozlowski <k.kozlowsk...@gmail.com>
>>
>> ---
>>
>> Patch depends/is rebased on latest DTS for Odroid XU4 board:
>>  - http://www.spinics.net/lists/arm-kernel/msg442474.html
>>  - http://www.spinics.net/lists/arm-kernel/msg442475.html
>> ---
> 
> Applied, thanks.
> 
Oops, I mean already this change is included in your another patch.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2] ARM: dts: Fix LEDs on exynos5422-odroidxu3

[Kukjin Kim]

On 09/16/15 08:54, Krzysztof Kozlowski wrote:
> On 16.09.2015 08:35, Kukjin Kim wrote:
>> On 09/13/15 18:32, Krzysztof Kozlowski wrote:
>>> The LEDs on Odroid XU3 family boards could not properly probe because PWM
>>> outputs were reduced only to PWM for fan. Fix it for Odroid XU3 and
>>> XU3-Lite boards by switching to usage of all 4 outputs (although the PWM
>>> for MIPI probably is redundant because board does not have MIPI
>>> connector available).
>>>
>>> This fixes warnings on dmesg:
>>> [4.838712] samsung-pwm 12dd.pwm: tried to request PWM channel 1 
>>> without output
>>> [4.838725] leds_pwm pwmleds: unable to request PWM for green:mmc0: -22
>>> [4.838767] leds_pwm: probe of pwmleds failed with error -22
>>>
>>> Signed-off-by: Krzysztof Kozlowski <k.kozlowsk...@gmail.com>
>>>
>>> ---
>>>
>>> Changes since v1:
>>> 1. Do not rebase on patchset adding support for Odroid XU4 board. Rebase
>>>just on current next.
>>> ---
>>
>> Applied, thanks.
>>
> 
> Thanks. This is actually a candidate for current v4.3 cycle. It fixes
> issue with LEDs for Odroid XU3 caused by Anand's b685d540cc26:
> The offending commit b685d540cc26 was merged in v4.3.
> I forgot to add "fixes" tag.
>   Fixes: b685d540cc26 ("ARM: dts: Add pwm-fan node for 
> exynos5422-odroidxu3")
> 
> Can you send it to arm-soc during this cycle?
> 
Why not? Will do it ;-)

> For current v4.3 Bartlomiej's patch is also an important candidate:
> "ARM: dts: add suspend opp to exynos4412"
> 
Thanks for gentle reminder.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2] ARM: dts: Fix LEDs on exynos5422-odroidxu3

[Kukjin Kim]

On 09/13/15 18:32, Krzysztof Kozlowski wrote:
> The LEDs on Odroid XU3 family boards could not properly probe because PWM
> outputs were reduced only to PWM for fan. Fix it for Odroid XU3 and
> XU3-Lite boards by switching to usage of all 4 outputs (although the PWM
> for MIPI probably is redundant because board does not have MIPI
> connector available).
> 
> This fixes warnings on dmesg:
> [4.838712] samsung-pwm 12dd.pwm: tried to request PWM channel 1 
> without output
> [4.838725] leds_pwm pwmleds: unable to request PWM for green:mmc0: -22
> [4.838767] leds_pwm: probe of pwmleds failed with error -22
> 
> Signed-off-by: Krzysztof Kozlowski 
> 
> ---
> 
> Changes since v1:
> 1. Do not rebase on patchset adding support for Odroid XU4 board. Rebase
>just on current next.
> ---

Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v3 1/2] ARM: dts: Split audio configuration to separateexynos5422-odroidxu3-audio

[Kukjin Kim]

On 09/14/15 09:47, Krzysztof Kozlowski wrote:
> The Odroid XU4 board does not have audio codec so before adding DTS for
> new board split the audio codec to separate DTSI file. Include the audio codec
> DTSI in Odroid XU3 and XU3-Lite boards.
> 
> Signed-off-by: Krzysztof Kozlowski 
> Reviewed-by: Javier Martinez Canillas 
> 
Applied 1-2.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v2] ARM: dts: Fix LEDs on exynos5422-odroidxu3

[Kukjin Kim]

On 09/13/15 18:32, Krzysztof Kozlowski wrote:
> The LEDs on Odroid XU3 family boards could not properly probe because PWM
> outputs were reduced only to PWM for fan. Fix it for Odroid XU3 and
> XU3-Lite boards by switching to usage of all 4 outputs (although the PWM
> for MIPI probably is redundant because board does not have MIPI
> connector available).
> 
> This fixes warnings on dmesg:
> [4.838712] samsung-pwm 12dd.pwm: tried to request PWM channel 1 
> without output
> [4.838725] leds_pwm pwmleds: unable to request PWM for green:mmc0: -22
> [4.838767] leds_pwm: probe of pwmleds failed with error -22
> 
> Signed-off-by: Krzysztof Kozlowski 
> 
> ---
> 
> Changes since v1:
> 1. Do not rebase on patchset adding support for Odroid XU4 board. Rebase
>just on current next.
> ---

Applied, thanks.

- Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH v3 1/2] ARM: dts: Split audio configuration to separateexynos5422-odroidxu3-audio

[Kukjin Kim]

On 09/14/15 09:47, Krzysztof Kozlowski wrote:
> The Odroid XU4 board does not have audio codec so before adding DTS for
> new board split the audio codec to separate DTSI file. Include the audio codec
> DTSI in Odroid XU3 and XU3-Lite boards.
> 
> Signed-off-by: Krzysztof Kozlowski 
> Reviewed-by: Javier Martinez Canillas 
> 
Applied 1-2.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [PATCH v2 1/3] mfd: documentation: dt: Document grounded ACOKB pin on S2MPS11

[Kukjin Kim]

Krzysztof Kozlowski wrote:
> 
> Document a new Device Tree property 'samsung,s2mps11-acokb-ground'
> indicating that ACOKB pin of S2MPS11 PMIC is connected to the ground so
> the PMIC must manually set PWRHOLD bit in CTRL1 register to turn off the
> power.
> 
> Signed-off-by: Krzysztof Kozlowski 
> Reviewed-by: Javier Martinez Canillas 
> Acked-by: Lee Jones 
> 
> ---
> 
> Changes since v1:
> 1. Split bindings documentation to separate patch (suggested by Lee).
> 2. Add Javier's reviewed-by and Lee's acked-by.
> ---
>  Documentation/devicetree/bindings/mfd/s2mps11.txt | 4 
>  1 file changed, 4 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/mfd/s2mps11.txt
> b/Documentation/devicetree/bindings/mfd/s2mps11.txt
> index 57a045016fca..90eaef393325 100644
> --- a/Documentation/devicetree/bindings/mfd/s2mps11.txt
> +++ b/Documentation/devicetree/bindings/mfd/s2mps11.txt
> @@ -15,6 +15,10 @@ Optional properties:
>  - interrupt-parent: Specifies the phandle of the interrupt controller to 
> which
>the interrupts from s2mps11 are delivered to.
>  - interrupts: Interrupt specifiers for interrupt sources.
> +- samsung,s2mps11-acokb-ground: Indicates that ACOKB pin of S2MPS11 PMIC is
> +  connected to the ground so the PMIC must manually set PWRHOLD bit in CTRL1
> +  register to turn off the power. Usually the ACOKB is pulled up to VBATT so
> +  when PWRHOLD pin goes low, the rising ACOKB will trigger power off.
> 
>  Optional nodes:
>  - clocks: s2mps11, s2mps13 and s5m8767 provide three(AP/CP/BT) buffered 
> 32.768
> --
> 2.1.4

Applied 1/3 and 3/3.

Thanks,
Kukjin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [PATCH v2 1/3] mfd: documentation: dt: Document grounded ACOKB pin on S2MPS11

[Kukjin Kim]

Krzysztof Kozlowski wrote:
 
 Document a new Device Tree property 'samsung,s2mps11-acokb-ground'
 indicating that ACOKB pin of S2MPS11 PMIC is connected to the ground so
 the PMIC must manually set PWRHOLD bit in CTRL1 register to turn off the
 power.
 
 Signed-off-by: Krzysztof Kozlowski k.kozlowsk...@gmail.com
 Reviewed-by: Javier Martinez Canillas jav...@osg.samsung.com
 Acked-by: Lee Jones lee.jo...@linaro.org
 
 ---
 
 Changes since v1:
 1. Split bindings documentation to separate patch (suggested by Lee).
 2. Add Javier's reviewed-by and Lee's acked-by.
 ---
  Documentation/devicetree/bindings/mfd/s2mps11.txt | 4 
  1 file changed, 4 insertions(+)
 
 diff --git a/Documentation/devicetree/bindings/mfd/s2mps11.txt
 b/Documentation/devicetree/bindings/mfd/s2mps11.txt
 index 57a045016fca..90eaef393325 100644
 --- a/Documentation/devicetree/bindings/mfd/s2mps11.txt
 +++ b/Documentation/devicetree/bindings/mfd/s2mps11.txt
 @@ -15,6 +15,10 @@ Optional properties:
  - interrupt-parent: Specifies the phandle of the interrupt controller to 
 which
the interrupts from s2mps11 are delivered to.
  - interrupts: Interrupt specifiers for interrupt sources.
 +- samsung,s2mps11-acokb-ground: Indicates that ACOKB pin of S2MPS11 PMIC is
 +  connected to the ground so the PMIC must manually set PWRHOLD bit in CTRL1
 +  register to turn off the power. Usually the ACOKB is pulled up to VBATT so
 +  when PWRHOLD pin goes low, the rising ACOKB will trigger power off.
 
  Optional nodes:
  - clocks: s2mps11, s2mps13 and s5m8767 provide three(AP/CP/BT) buffered 
 32.768
 --
 2.1.4

Applied 1/3 and 3/3.

Thanks,
Kukjin

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [PATCH v2] Remove unselectable rule for arm-exynos-cpufreq.o

[Kukjin Kim]

Krzysztof Kozlowski wrote:
> 
> 2015-08-13 20:33 GMT+09:00 Viresh Kumar :
> > On 13-08-15, 13:28, Jonas Rabenstein wrote:
> >> Commit "cpufreq: exynos: remove Exynos4x12 specific cpufreq driver
> >> support" deleted option ARM_EXYNOS_CPUFREQ but missed to delete a rule
> >> in drivers/cpufreq/Makefile which depends on that option.
> >>
> >> Remove unselectable rule for arm-exynos-cpufreq.o from
> >> drivers/cpufreq/Makefile.
> >>
> >> Signed-off-by: Jonas Rabenstein 
> >> ---
> >> I found this inconsistency using the undertaker and
> >> undertaker-checkpatch tools (https://undertaker.cs.fau.de/).
> >>
> >>  drivers/cpufreq/Makefile | 1 -
> >>  1 file changed, 1 deletion(-)
> >>
> >> diff --git a/drivers/cpufreq/Makefile b/drivers/cpufreq/Makefile
> >> index bbc4a9f..958be2b 100644
> >> --- a/drivers/cpufreq/Makefile
> >> +++ b/drivers/cpufreq/Makefile
> >> @@ -52,7 +52,6 @@ obj-$(CONFIG_ARM_DT_BL_CPUFREQ) += 
> >> arm_big_little_dt.o
> >>
> >>  obj-$(CONFIG_ARCH_DAVINCI)   += davinci-cpufreq.o
> >>  obj-$(CONFIG_UX500_SOC_DB8500)   += dbx500-cpufreq.o
> >> -obj-$(CONFIG_ARM_EXYNOS_CPUFREQ) += arm-exynos-cpufreq.o
> >>  obj-$(CONFIG_ARM_EXYNOS5440_CPUFREQ) += exynos5440-cpufreq.o
> >>  obj-$(CONFIG_ARM_HIGHBANK_CPUFREQ)   += highbank-cpufreq.o
> >>  obj-$(CONFIG_ARM_HISI_ACPU_CPUFREQ)  += hisi-acpu-cpufreq.o
> >
> > Acked-by: Viresh Kumar 
> 
> And again from me:
> Reviewed-by: Krzysztof Kozlowski 
> 
> Dear Kukjin,
> Can you take it and send in (updated) pull request with Exynos4x12
> cpufreq patches?
> 
OK, sure. I'll take this.

Thanks,
Kukjin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [PATCH v2] ARM: dts: exynos4412-odroidu3: Enable SPI1.

[Kukjin Kim]

Krzysztof Kozlowski wrote:
> 
> W dniu 13.08.2015 o 18:06, Alexis Ballier pisze:
> > SPI1 is available on IO Port #2 (as depicted on their website) in
> > PCB Revision 0.5 of Hardkernel Odroid U3 board.
> > The shield connects a 256KiB spi-nor flash on that bus.
> >
> > Signed-off-by: Alexis Ballier 
> >
> > ---
> >
> > Changes in v2: Use GPIO_ACTIVE_HIGH (Krzysztof Kozlowski)
> >
> >  arch/arm/boot/dts/exynos4412-odroidu3.dts | 8 
> >  1 file changed, 8 insertions(+)
> 
> Thanks for fixing, looks good:
> 
> Reviewed-by: Krzysztof Kozlowski 
> 
Applied, thanks.

- Kukjin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [PATCH v2] ARM: dts: exynos4412-odroidu3: Enable SPI1.

[Kukjin Kim]

Krzysztof Kozlowski wrote:
 
 W dniu 13.08.2015 o 18:06, Alexis Ballier pisze:
  SPI1 is available on IO Port #2 (as depicted on their website) in
  PCB Revision 0.5 of Hardkernel Odroid U3 board.
  The shield connects a 256KiB spi-nor flash on that bus.
 
  Signed-off-by: Alexis Ballier aball...@gentoo.org
 
  ---
 
  Changes in v2: Use GPIO_ACTIVE_HIGH (Krzysztof Kozlowski)
 
   arch/arm/boot/dts/exynos4412-odroidu3.dts | 8 
   1 file changed, 8 insertions(+)
 
 Thanks for fixing, looks good:
 
 Reviewed-by: Krzysztof Kozlowski k.kozlow...@samsung.com
 
Applied, thanks.

- Kukjin

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [PATCH v2] Remove unselectable rule for arm-exynos-cpufreq.o

[Kukjin Kim]

Krzysztof Kozlowski wrote:
 
 2015-08-13 20:33 GMT+09:00 Viresh Kumar viresh.ku...@linaro.org:
  On 13-08-15, 13:28, Jonas Rabenstein wrote:
  Commit cpufreq: exynos: remove Exynos4x12 specific cpufreq driver
  support deleted option ARM_EXYNOS_CPUFREQ but missed to delete a rule
  in drivers/cpufreq/Makefile which depends on that option.
 
  Remove unselectable rule for arm-exynos-cpufreq.o from
  drivers/cpufreq/Makefile.
 
  Signed-off-by: Jonas Rabenstein jonas.rabenst...@studium.uni-erlangen.de
  ---
  I found this inconsistency using the undertaker and
  undertaker-checkpatch tools (https://undertaker.cs.fau.de/).
 
   drivers/cpufreq/Makefile | 1 -
   1 file changed, 1 deletion(-)
 
  diff --git a/drivers/cpufreq/Makefile b/drivers/cpufreq/Makefile
  index bbc4a9f..958be2b 100644
  --- a/drivers/cpufreq/Makefile
  +++ b/drivers/cpufreq/Makefile
  @@ -52,7 +52,6 @@ obj-$(CONFIG_ARM_DT_BL_CPUFREQ) += 
  arm_big_little_dt.o
 
   obj-$(CONFIG_ARCH_DAVINCI)   += davinci-cpufreq.o
   obj-$(CONFIG_UX500_SOC_DB8500)   += dbx500-cpufreq.o
  -obj-$(CONFIG_ARM_EXYNOS_CPUFREQ) += arm-exynos-cpufreq.o
   obj-$(CONFIG_ARM_EXYNOS5440_CPUFREQ) += exynos5440-cpufreq.o
   obj-$(CONFIG_ARM_HIGHBANK_CPUFREQ)   += highbank-cpufreq.o
   obj-$(CONFIG_ARM_HISI_ACPU_CPUFREQ)  += hisi-acpu-cpufreq.o
 
  Acked-by: Viresh Kumar viresh.ku...@linaro.org
 
 And again from me:
 Reviewed-by: Krzysztof Kozlowski k.kozlow...@samsung.com
 
 Dear Kukjin,
 Can you take it and send in (updated) pull request with Exynos4x12
 cpufreq patches?
 
OK, sure. I'll take this.

Thanks,
Kukjin

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [PATCH] ARM: exynos_defconfig: Enable cpufreq-dt driver

[Kukjin Kim]

Javier Martinez Canillas wrote:
> 
> Hello Krzysztof,
> 
> On 08/11/2015 04:15 AM, Krzysztof Kozlowski wrote:
> > With the latest patches the cpufreq-dt can be used on multiple
> > Exynos SoCs: 3250, 4210, 4212, 4412 and 5250.
> >
> > Enable it along with default ondemand governor to conserve the energy,
> > reduce temperature while maintaining acceptable performance.
> >
> > Signed-off-by: Krzysztof Kozlowski 
> > ---
> >  arch/arm/configs/exynos_defconfig | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/arch/arm/configs/exynos_defconfig 
> > b/arch/arm/configs/exynos_defconfig
> > index 67965cedeb69..2263cd94cb93 100644
> > --- a/arch/arm/configs/exynos_defconfig
> > +++ b/arch/arm/configs/exynos_defconfig
> > @@ -27,6 +27,8 @@ CONFIG_ARM_APPENDED_DTB=y
> >  CONFIG_ARM_ATAG_DTB_COMPAT=y
> >  CONFIG_CMDLINE="root=/dev/ram0 rw ramdisk=8192 initrd=0x4100,8M 
> > console=ttySAC1,115200
> init=/linuxrc mem=256M"
> >  CONFIG_CPU_FREQ=y
> > +CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
> > +CONFIG_CPUFREQ_DT=y
> >  CONFIG_CPU_IDLE=y
> >  CONFIG_ARM_EXYNOS_CPUIDLE=y
> >  CONFIG_VFP=y
> >
> 
> Reviewed-by: Javier Martinez Canillas 
> 
Thanks, applied.

- Kukjin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [PATCH v4 0/6] cpufreq: use generic cpufreq drivers for Exynos4x12 platform

[Kukjin Kim]

Krzysztof Kozlowski wrote:
> 
> On 10.08.2015 10:27, Kukjin Kim wrote:
> > Krzysztof Kozlowski wrote:
> >>
> >> W dniu 08.08.2015 o 11:07, Viresh Kumar pisze:
> >>> On 08-08-15, 00:24, Rafael J. Wysocki wrote:
> >>>> OK, so please let me know which patches you want me to pick up.
> >>>>
> >>>> Ideally, I'd prefer them to be resent in a separate series with ACKs and 
> >>>> all
> >>>> with a cover letter clearly stating whose tree they are being targeted 
> >>>> at.
> >>>
> >>> He already sent it separately, let me send a confirmatory mail in
> >>> reply to that.
> >>
> >> Dear Kukjin,
> >>
> >> Can you apply the 2-5 of this series to v4.3? It's getting late but
> >> maybe they still could go?
> >>
> > Once my previous pull-request landed into arm-soc, I'll try to send out this
> > series 2-5 for v4.3.
> 
> Additionally (better late than never):

Sure ;-)

> Patches 2-5 tested on Trats2 board (Exynos4412)
> 
> Tested-by: Krzysztof Kozlowski 
> 
Applied with Krzysztof's 'Tested-by'.

Thanks,
Kukjin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [PATCH] ARM: exynos_defconfig: Enable cpufreq-dt driver

[Kukjin Kim]

Javier Martinez Canillas wrote:
 
 Hello Krzysztof,
 
 On 08/11/2015 04:15 AM, Krzysztof Kozlowski wrote:
  With the latest patches the cpufreq-dt can be used on multiple
  Exynos SoCs: 3250, 4210, 4212, 4412 and 5250.
 
  Enable it along with default ondemand governor to conserve the energy,
  reduce temperature while maintaining acceptable performance.
 
  Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
  ---
   arch/arm/configs/exynos_defconfig | 2 ++
   1 file changed, 2 insertions(+)
 
  diff --git a/arch/arm/configs/exynos_defconfig 
  b/arch/arm/configs/exynos_defconfig
  index 67965cedeb69..2263cd94cb93 100644
  --- a/arch/arm/configs/exynos_defconfig
  +++ b/arch/arm/configs/exynos_defconfig
  @@ -27,6 +27,8 @@ CONFIG_ARM_APPENDED_DTB=y
   CONFIG_ARM_ATAG_DTB_COMPAT=y
   CONFIG_CMDLINE=root=/dev/ram0 rw ramdisk=8192 initrd=0x4100,8M 
  console=ttySAC1,115200
 init=/linuxrc mem=256M
   CONFIG_CPU_FREQ=y
  +CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
  +CONFIG_CPUFREQ_DT=y
   CONFIG_CPU_IDLE=y
   CONFIG_ARM_EXYNOS_CPUIDLE=y
   CONFIG_VFP=y
 
 
 Reviewed-by: Javier Martinez Canillas jav...@osg.samsung.com
 
Thanks, applied.

- Kukjin

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [PATCH v4 0/6] cpufreq: use generic cpufreq drivers for Exynos4x12 platform

[Kukjin Kim]

Krzysztof Kozlowski wrote:
 
 On 10.08.2015 10:27, Kukjin Kim wrote:
  Krzysztof Kozlowski wrote:
 
  W dniu 08.08.2015 o 11:07, Viresh Kumar pisze:
  On 08-08-15, 00:24, Rafael J. Wysocki wrote:
  OK, so please let me know which patches you want me to pick up.
 
  Ideally, I'd prefer them to be resent in a separate series with ACKs and 
  all
  with a cover letter clearly stating whose tree they are being targeted 
  at.
 
  He already sent it separately, let me send a confirmatory mail in
  reply to that.
 
  Dear Kukjin,
 
  Can you apply the 2-5 of this series to v4.3? It's getting late but
  maybe they still could go?
 
  Once my previous pull-request landed into arm-soc, I'll try to send out this
  series 2-5 for v4.3.
 
 Additionally (better late than never):

Sure ;-)

 Patches 2-5 tested on Trats2 board (Exynos4412)
 
 Tested-by: Krzysztof Kozlowski k.kozlow...@samsung.com
 
Applied with Krzysztof's 'Tested-by'.

Thanks,
Kukjin

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: [GIT PULL] Samsung mach fixes for 4.2

[Kukjin Kim]

Hi arm-soc guys,

Can you please pull this into arm-soc fixes for v4.2 directly?
I don't have other samsung fixes in my tree at this moment.

Thanks,
Kukjin

Krzysztof Kozlowski wrote:
> 
> Dear Kukjin,
> 
> Please find latest two fixes for v4.2 cycle. You can find more detailed
> description with the tag.
> 
> Best regards,
> Krzysztof
> 
> 
> The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
> 
>   Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/krzk/linux.git tags/samsung-mach-fixes-4.2
> 
> for you to fetch changes up to 3e9f798784b30293012682021d5a0352f78658b8:
> 
>   ARM: EXYNOS: fix double of_node_put() on error path (2015-07-31 10:12:17 
> +0900)
> 
> 
> Two fixes for bugs in Exynos power domain error exit path:
> 1. kfree() of read-only memory (name of power domain returned
>by kstrdup_const()),
> 2. Doubled of_node_put() leading to invalid ref count for OF node.
> 
> 
> Vladimir Zapolskiy (2):
>   ARM: EXYNOS: Fix potentian kfree() of ro memory
>   ARM: EXYNOS: fix double of_node_put() on error path
> 
>  arch/arm/mach-exynos/pm_domains.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/