[GIT PULL 0/4] ARM: exynos: Third (last) round for v4.11

[GIT PULL 0/4] ARM: exynos: Third (last) round for v4.11

[Krzysztof Kozlowski]

Hi,

There was still some activity these days so I pushed to you second round of
updates a little bit earlier. I wanted to be sure it gets in and also make room
for new patches. These are the late commits but some of them were in a review
for quite long.

1. No conflicts expected.
2. Almost everything on top of previous pull requests.
3. No specific dependency of pulling.
4. External dependency pulled into 4/4.
5. 2/4 is also a stuff for other trees.

Best regards,
Krzysztof

[GIT PULL 1/4] soc: samsung: pm_domains for v4.11

[Krzysztof Kozlowski]

Hi,

Minor improvements of PM domain driver.

Best regards,
Krzysztof


The following changes since commit 0c744ea4f77d72b3dcebb7a8f2684633ec79be88:

  Linux 4.10-rc2 (2017-01-01 14:31:53 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-drivers-soc-pm-domains-4.11

for you to fetch changes up to b13b2330aab53af4ebaa2859f72f2c802d01abad:

  soc: samsung: pm_domains: Read domain name from the new label property (2017-01-31 21:30:07 +0200)

----------------------------------------------------------------
Improve the PM domains driver for Exynos by displaying a user-friendly name of
power domain.  Till now, the name of node from DT was used which mostly is just
"power-domain".  We need more than that.

----------------------------------------------------------------
Marek Szyprowski (4):
      soc: samsung: pm_domains: Use full names in subdomains registration log
      soc: samsung: pm_domains: Remove unused name field
      soc: samsung: pm_domains: Remove message about failed memory allocation
      soc: samsung: pm_domains: Read domain name from the new label property

 .../devicetree/bindings/power/pd-samsung.txt       |  4 ++++
 drivers/soc/samsung/pm_domains.c                   | 24 +++++++++++++---------
 2 files changed, 18 insertions(+), 10 deletions(-)

Re: [GIT PULL 1/4] soc: samsung: pm_domains for v4.11

[Arnd Bergmann]

On Thursday, February 2, 2017 8:30:05 PM CET Krzysztof Kozlowski wrote:
> Improve the PM domains driver for Exynos by displaying a user-friendly name of
> power domain.  Till now, the name of node from DT was used which mostly is just
> "power-domain".  We need more than that.
> 

Pulled into next/drivers, thanks!

	Arnd

[GIT PULL 2/4] soc: samsung: pmu for v4.11, third round

[Krzysztof Kozlowski]

Hi,

Last changes around PMU driver (the header)
On top of previous pull request.

This patch (and others below) might be also pulled by Linus or Lee for:
[PATCH v3 0/7] Pad retentions support for Exynos5433
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1321519.html

Best regards,
Krzysztof


Cc: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-gpio@vger.kernel.org
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: Tomasz Figa <tomasz.figa@gmail.com>
Cc: Lee Jones <lee.jones@linaro.org>


The following changes since commit ee55ae6194a5439bde3a3b8ee0abda63c610e740:

  soc: samsung: pmu: Remove duplicated define for ARM_L2_OPTION register (2017-01-27 11:32:31 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-drivers-soc-pmu-4.11-3

for you to fetch changes up to b343d77b94b6702082f4f402e1492e71ef87095b:

  soc: samsung: pmu: Add register defines for pad retention control (2017-02-02 20:00:28 +0200)

----------------------------------------------------------------
3rd round of improvements for Exynos PMU driver for v4.11:
1. Add defines in header for future patches changing the pad
   retention control.

----------------------------------------------------------------
Marek Szyprowski (1):
      soc: samsung: pmu: Add register defines for pad retention control

 include/linux/soc/samsung/exynos-regs-pmu.h | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

Re: [GIT PULL 2/4] soc: samsung: pmu for v4.11, third round

[Arnd Bergmann]

On Thursday, February 2, 2017 8:30:06 PM CET Krzysztof Kozlowski wrote:
> 3rd round of improvements for Exynos PMU driver for v4.11:
> 1. Add defines in header for future patches changing the pad
>    retention control.
> 

Pulled into next/drivers, thanks!

	Arnd

[GIT PULL 3/4] ARM: dts: exynos: DT for v4.11, third round

[Krzysztof Kozlowski]

Hi,

On top of previous pull request.

Best regards,
Krzysztof


The following changes since commit dfaf06baad0c088a55570f7a324949c498f2106c:

  ARM: dts: exynos: Fix indentation of EHCI and OHCI ports (2017-01-29 21:03:46 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-dt-4.11-3

for you to fetch changes up to 55d74adfa9758cad5dd989b22cb2558303fe9a0f:

  ARM: dts: exynos: Add labels to all existing power domains (2017-01-31 21:30:48 +0200)

----------------------------------------------------------------
Samsung DeviceTree update for v4.11, third round:
1. Add descriptive user-friendly label names for power domains. This
   makes debugging easier.

----------------------------------------------------------------
Marek Szyprowski (1):
      ARM: dts: exynos: Add labels to all existing power domains

 arch/arm/boot/dts/exynos4.dtsi    | 7 +++++++
 arch/arm/boot/dts/exynos4210.dtsi | 1 +
 arch/arm/boot/dts/exynos4412.dtsi | 1 +
 arch/arm/boot/dts/exynos5250.dtsi | 3 +++
 arch/arm/boot/dts/exynos5420.dtsi | 5 +++++
 5 files changed, 17 insertions(+)

Re: [GIT PULL 3/4] ARM: dts: exynos: DT for v4.11, third round

[Arnd Bergmann]

On Thursday, February 2, 2017 8:30:07 PM CET Krzysztof Kozlowski wrote:
> Samsung DeviceTree update for v4.11, third round:
> 1. Add descriptive user-friendly label names for power domains. This
>    makes debugging easier.
> 

Pulled into next/dt, thanks!

	Arnd

[GIT PULL 4/4] arm64: dts: exynos: DT64 for v4.11, third round

[Krzysztof Kozlowski]

Hi,

This includes clk-v4.11-samsung-dphy tag from Sylwester (clock) and a pinctrl
header acked by Linus pinctrl header. The header goes through my tree but I provided
a separate tag also for Linus.

On top of previous pull request.

Best regards,
Krzysztof


The following changes since commit 7547162ac351483df3641f64e99e10be329dd6a2:

  arm64: dts: exynos: Add clocks to Exynos5433 LPASS module (2017-01-26 22:04:20 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-dt64-4.11-3

for you to fetch changes up to 6629490aa027a8af3160e63cffcddc97c1602c96:

  arm64: dts: exynos: Add regulators for Vbus and Vbus-Boost (2017-02-02 19:54:05 +0200)

----------------------------------------------------------------
Samsung DeviceTree ARM64 update for v4.11, third round:
1. Add necessary initial configuration for clocks of display subsystem.
   Till now it worked mostly thanks to bootloader.
2. Use macro definitions instead of hard-coded values for pinctrl on Exynos7.
3. Enable USB 3.0 (DWC3) on Exynos7.

----------------------------------------------------------------
Krzysztof Kozlowski (2):
      Merge tag 'clk-v4.11-samsung-dphy' of git://linuxtv.org/snawrocki/samsung into next/dt64
      Merge tag 'samsung-pinctrl-4.11' into next/dt64

Marek Szyprowski (3):
      clk: samsung: exynos5433: Add IDs for PHYCLK_MIPIDPHY0_* clocks
      clk: samsung: exynos5433: Add data for 250MHz and 278MHz PLL rates
      arm64: dts: exynos: Add initial configuration for DISP clocks for TM2/TM2e

Pankaj Dubey (2):
      pinctrl: dt-bindings: samsung: Add Exynos7 specific pinctrl macro definitions
      arm64: dts: exynos: Use macros for pinctrl configuration on Exynos7

Vivek Gautam (2):
      arm64: dts: exynos: Add USB 3.0 controller node for Exynos7
      arm64: dts: exynos: Add regulators for Vbus and Vbus-Boost

 .../boot/dts/exynos/exynos5433-tm2-common.dtsi     |  12 -
 arch/arm64/boot/dts/exynos/exynos5433-tm2.dts      |  34 +++
 arch/arm64/boot/dts/exynos/exynos5433-tm2e.dts     |  34 +++
 arch/arm64/boot/dts/exynos/exynos7-espresso.dts    |  49 +++-
 arch/arm64/boot/dts/exynos/exynos7-pinctrl.dtsi    | 302 +++++++++++----------
 arch/arm64/boot/dts/exynos/exynos7.dtsi            |  34 +++
 drivers/clk/samsung/clk-exynos5433.c               |   8 +-
 include/dt-bindings/clock/exynos5433.h             |   5 +-
 include/dt-bindings/pinctrl/samsung.h              |   8 +
 9 files changed, 319 insertions(+), 167 deletions(-)

Re: [GIT PULL 4/4] arm64: dts: exynos: DT64 for v4.11, third round

[Arnd Bergmann]

On Thursday, February 2, 2017 8:30:08 PM CET Krzysztof Kozlowski wrote:
>  arch/arm64/boot/dts/exynos/exynos5433-tm2.dts      |  34 +++
>  arch/arm64/boot/dts/exynos/exynos5433-tm2e.dts     |  34 +++
>  arch/arm64/boot/dts/exynos/exynos7-espresso.dts    |  49 +++-
>  arch/arm64/boot/dts/exynos/exynos7-pinctrl.dtsi    | 302 +++++++++++----------
>  arch/arm64/boot/dts/exynos/exynos7.dtsi            |  34 +++
>  drivers/clk/samsung/clk-exynos5433.c               |   8 +-
>  include/dt-bindings/clock/exynos5433.h             |   5 +-
>  include/dt-bindings/pinctrl/samsung.h              |   8 +
> 

It seems a drivers/clk change slipped in there in addition to the header changes.
We are trying to keep the next/dt branches free of driver changes, are you
able to rework the branch without this?

Sorry for the late request.

	Arnd

Re: [GIT PULL 4/4] arm64: dts: exynos: DT64 for v4.11, third round

[Krzysztof Kozlowski]

On Thu, Feb 09, 2017 at 04:19:57PM +0100, Arnd Bergmann wrote:
> On Thursday, February 2, 2017 8:30:08 PM CET Krzysztof Kozlowski wrote:
> >  arch/arm64/boot/dts/exynos/exynos5433-tm2.dts      |  34 +++
> >  arch/arm64/boot/dts/exynos/exynos5433-tm2e.dts     |  34 +++
> >  arch/arm64/boot/dts/exynos/exynos7-espresso.dts    |  49 +++-
> >  arch/arm64/boot/dts/exynos/exynos7-pinctrl.dtsi    | 302 +++++++++++----------
> >  arch/arm64/boot/dts/exynos/exynos7.dtsi            |  34 +++
> >  drivers/clk/samsung/clk-exynos5433.c               |   8 +-
> >  include/dt-bindings/clock/exynos5433.h             |   5 +-
> >  include/dt-bindings/pinctrl/samsung.h              |   8 +
> > 
> 
> It seems a drivers/clk change slipped in there in addition to the header changes.
> We are trying to keep the next/dt branches free of driver changes, are you
> able to rework the branch without this?

+Cc Sylwester,

This came from clk tree from Sylwester. It contains two changes in
clocks:
1. Mew clock ID - we need only the header but Sylwester provided also
   the source file change,
2. Update of frequency (used in DTS as assigned clock rate) - this
   is strictly source file change and we need it.

Overall, rework would not be trivial and it would involve Sylwester.
I think it is better to stay with this as is. I will remember the policy
for future dependencies.

Best regards,
Krzysztof

Re: [GIT PULL 4/4] arm64: dts: exynos: DT64 for v4.11, third round

[Sylwester Nawrocki]

On 02/09/2017 07:56 PM, Krzysztof Kozlowski wrote:
> On Thu, Feb 09, 2017 at 04:19:57PM +0100, Arnd Bergmann wrote:
>> On Thursday, February 2, 2017 8:30:08 PM CET Krzysztof Kozlowski wrote:
>>>  arch/arm64/boot/dts/exynos/exynos5433-tm2.dts      |  34 +++
>>>  arch/arm64/boot/dts/exynos/exynos5433-tm2e.dts     |  34 +++
>>>  arch/arm64/boot/dts/exynos/exynos7-espresso.dts    |  49 +++-
>>>  arch/arm64/boot/dts/exynos/exynos7-pinctrl.dtsi    | 302 +++++++++++----------
>>>  arch/arm64/boot/dts/exynos/exynos7.dtsi            |  34 +++
>>>  drivers/clk/samsung/clk-exynos5433.c               |   8 +-
>>>  include/dt-bindings/clock/exynos5433.h             |   5 +-
>>>  include/dt-bindings/pinctrl/samsung.h              |   8 +
>>>
>> It seems a drivers/clk change slipped in there in addition to the header changes.
>> We are trying to keep the next/dt branches free of driver changes, are you
>> able to rework the branch without this?
>
> +Cc Sylwester,
> 
> This came from clk tree from Sylwester. It contains two changes in
> clocks:
> 1. Mew clock ID - we need only the header but Sylwester provided also
>    the source file change,

That's a one patch made so there is no runtime regression.  If we stick
to the next/dt branches being clean of driver changes I'm afraid we need
to be prepared for the bisection breaks.

> 2. Update of frequency (used in DTS as assigned clock rate) - this
>    is strictly source file change and we need it.
> 
> Overall, rework would not be trivial and it would involve Sylwester.
> I think it is better to stay with this as is. I will remember the policy
> for future dependencies.

The clk changes are already pulled into clk tree, we would get conflicts
with commits that are already in the clock tree if the branch is reworked
now.  This might not be a big issue but bisection would be broken for sure.

I'll also try to keep in future include/dt-bindings changes separate.

-- 
Regards,
Sylwester

Re: [GIT PULL 4/4] arm64: dts: exynos: DT64 for v4.11, third round

[Krzysztof Kozlowski]

On Fri, Feb 10, 2017 at 12:30:48PM +0100, Sylwester Nawrocki wrote:
> On 02/09/2017 07:56 PM, Krzysztof Kozlowski wrote:
> > On Thu, Feb 09, 2017 at 04:19:57PM +0100, Arnd Bergmann wrote:
> >> On Thursday, February 2, 2017 8:30:08 PM CET Krzysztof Kozlowski wrote:
> >>>  arch/arm64/boot/dts/exynos/exynos5433-tm2.dts      |  34 +++
> >>>  arch/arm64/boot/dts/exynos/exynos5433-tm2e.dts     |  34 +++
> >>>  arch/arm64/boot/dts/exynos/exynos7-espresso.dts    |  49 +++-
> >>>  arch/arm64/boot/dts/exynos/exynos7-pinctrl.dtsi    | 302 +++++++++++----------
> >>>  arch/arm64/boot/dts/exynos/exynos7.dtsi            |  34 +++
> >>>  drivers/clk/samsung/clk-exynos5433.c               |   8 +-
> >>>  include/dt-bindings/clock/exynos5433.h             |   5 +-
> >>>  include/dt-bindings/pinctrl/samsung.h              |   8 +
> >>>
> >> It seems a drivers/clk change slipped in there in addition to the header changes.
> >> We are trying to keep the next/dt branches free of driver changes, are you
> >> able to rework the branch without this?
> >
> > +Cc Sylwester,
> > 
> > This came from clk tree from Sylwester. It contains two changes in
> > clocks:
> > 1. Mew clock ID - we need only the header but Sylwester provided also
> >    the source file change,
> 
> That's a one patch made so there is no runtime regression.  If we stick
> to the next/dt branches being clean of driver changes I'm afraid we need
> to be prepared for the bisection breaks.
> 
> > 2. Update of frequency (used in DTS as assigned clock rate) - this
> >    is strictly source file change and we need it.
> > 
> > Overall, rework would not be trivial and it would involve Sylwester.
> > I think it is better to stay with this as is. I will remember the policy
> > for future dependencies.
> 
> The clk changes are already pulled into clk tree, we would get conflicts
> with commits that are already in the clock tree if the branch is reworked
> now.  This might not be a big issue but bisection would be broken for sure.
> 
> I'll also try to keep in future include/dt-bindings changes separate.

Arnd,

Any further comments? Are you going to pull it in?

Best regards,
Krzysztof

Re: [GIT PULL 4/4] arm64: dts: exynos: DT64 for v4.11, third round

[Arnd Bergmann]

On Tue, Feb 14, 2017 at 5:52 PM, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> On Fri, Feb 10, 2017 at 12:30:48PM +0100, Sylwester Nawrocki wrote:
>> On 02/09/2017 07:56 PM, Krzysztof Kozlowski wrote:
>> > On Thu, Feb 09, 2017 at 04:19:57PM +0100, Arnd Bergmann wrote:
>>
>> > 2. Update of frequency (used in DTS as assigned clock rate) - this
>> >    is strictly source file change and we need it.
>> >
>> > Overall, rework would not be trivial and it would involve Sylwester.
>> > I think it is better to stay with this as is. I will remember the policy
>> > for future dependencies.
>>
>> The clk changes are already pulled into clk tree, we would get conflicts
>> with commits that are already in the clock tree if the branch is reworked
>> now.  This might not be a big issue but bisection would be broken for sure.
>>
>> I'll also try to keep in future include/dt-bindings changes separate.
>
> Arnd,
>
> Any further comments? Are you going to pull it in?

Sorry, I haven't had a chance to discuss with Olof how we want to proceed.
I've pulled it into a next/late branch for now, which is similar to what we
did in the past, and we may or may not send it after the other pull
requests.

There is one other platform that has a similar problem and I'll pull that
in the same branch, while all the others have been able to rework their
trees to avoid it for 4.11.

      Arnd