Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1485859 > unrolled thread

[GIT PULL 0/3] ARM: exynos: Second round of stuff for v4.9

Back to article view | Back to linux.kernel

Contents

  [GIT PULL 0/3] ARM: exynos: Second round of stuff for v4.9 Krzysztof Kozlowski <krzk@kernel.org> - 2016-09-18 18:50 +0200
    [GIT PULL 1/3] ARM: soc: exynos: Drivers for v4.9 Krzysztof Kozlowski <krzk@kernel.org> - 2016-09-18 18:50 +0200
      Re: [GIT PULL 1/3] ARM: soc: exynos: Drivers for v4.9 Arnd Bergmann <arnd@arndb.de> - 2016-09-19 17:10 +0200
        Re: [GIT PULL 1/3] ARM: soc: exynos: Drivers for v4.9 Krzysztof Kozlowski <krzk@kernel.org> - 2016-09-19 18:00 +0200

#1485859 — [GIT PULL 0/3] ARM: exynos: Second round of stuff for v4.9

From: Krzysztof Kozlowski <k.kozlowski@samsung.com>

Hi,

I know it is late but it is not a big pull request. Mostly DT cleanup.
One change touching clocksource was acked by Daniel Lezcano (he
mentioned it can go through arm-soc).

Some stuff moved into topic branch. No conflicts expected, no specific
order of pulling.

Best regards,
Krzysztof

[toc] | [next] | [standalone]

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

From: Krzysztof Kozlowski <k.kozlowski@samsung.com>

Hi,

Drivers related changes.


Best regards,
Krzysztof


The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc:

  Linux 4.8-rc1 (2016-08-07 18:18:00 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-drivers-4.9-2

for you to fetch changes up to 8bc6bf178b671eb9b9fa806804f3990cb4c332aa:

  dt-bindings: EXYNOS: Add Exynos5433 PMU compatible (2016-09-16 13:21:04 +0200)

----------------------------------------------------------------
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).

----------------------------------------------------------------
Chanwoo Choi (2):
      clocksource: exynos_mct: Add the support for ARM64
      dt-bindings: EXYNOS: Add Exynos5433 PMU compatible

 Documentation/devicetree/bindings/arm/samsung/pmu.txt | 1 +
 drivers/clocksource/Kconfig                           | 2 +-
 drivers/clocksource/exynos_mct.c                      | 4 ++++
 3 files changed, 6 insertions(+), 1 deletion(-)

[toc] | [prev] | [next] | [standalone]

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

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?

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?

	Arnd

[toc] | [prev] | [next] | [standalone]

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

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.

Best regards,
Krzysztof

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web