linux-kernel - Re: [PATCH v5 0/3] ARM: S5PV210: move to common clk framework

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131021121605.11944.74007@quantum>
Date:	Mon, 21 Oct 2013 05:16:05 -0700
From:	Mike Turquette <mturquette@...aro.org>
To:	Kukjin Kim <kgene.kim@...sung.com>,
	Tomasz Figa <tomasz.figa@...il.com>
Cc:	rjw@...k.pl, kgene.kim@...sung.com, mark.rutland@....com,
	swarren@...dotorg.org, linux-doc@...r.kernel.org,
	viresh.kumar@...aro.org, s.nawrocki@...sung.com,
	m.szyprowski@...sung.com, linux-samsung-soc@...r.kernel.org,
	linux@....linux.org.uk,
	Mateusz Krawczuk <m.krawczuk@...tner.samsung.com>,
	linux-pm@...r.kernel.org, cpufreq@...r.kernel.org,
	thomas.abraham@...aro.org, b.zolnierkie@...sung.com,
	t.stanislaws@...sung.com, devicetree@...r.kernel.org,
	pawel.moll@....com, ijc+devicetree@...lion.org.uk,
	rob.herring@...xeda.com, ben-linux@...ff.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	kyungmin.park@...sung.com, rob@...dley.net
Subject: Re: [PATCH v5 0/3] ARM: S5PV210: move to common clk framework

Quoting Kukjin Kim (2013-10-20 13:51:42)
> On 10/20/13 01:03, Tomasz Figa wrote:
> > Hi Mike, Kukjin, Rafael,
> >
> > On Tuesday 24 of September 2013 14:50:06 Mateusz Krawczuk wrote:
> >> This patch series is the new s5pv210 clock implementation
> >> (using common clk framework).
> >>
> >> This implementation is compatible with device tree definition and board
> >> files.
> >>
> >> This patch series is based on linux-next and has been tested on goni and
> >> aquila
> >> boards using board file.
> >>
> >> Since v4:
> >> Corrected mux flags for finpll.
> >>
> >> Since v3:
> >>
> >> Replace s5pv210_clk_register_finpll, by creating mux finpll
> >> with xusbxti and xxti as parrents.
> >>
> >>
> >> Mateusz Krawczuk (3):
> >>    clk: samsung: Add clock driver for s5pc110/s5pv210
> >>    Cpufreq: s5pv210 cpufreq fixes for CCF
> >>    ARM: s5pv210: Migrate clock handling to Common Clock Framework
> >>
> >>   .../bindings/clock/samsung,s5pv210-clock.txt       |  75 +++
> >>   arch/arm/mach-s5pv210/Kconfig                      |   9 +
> >>   arch/arm/mach-s5pv210/Makefile                     |   4 +-
> >>   arch/arm/mach-s5pv210/common.c                     |  17 +
> >>   arch/arm/mach-s5pv210/common.h                     |  10 +
> >>   arch/arm/mach-s5pv210/mach-goni.c                  |   2 +-
> >>   arch/arm/mach-s5pv210/mach-smdkv210.c              |   2 +-
> >>   arch/arm/plat-samsung/Kconfig                      |   2 +-
> >>   drivers/clk/samsung/Makefile                       |   3 +
> >>   drivers/clk/samsung/clk-s5pv210.c                  | 673
> >> +++++++++++++++++++++ drivers/cpufreq/s5pv210-cpufreq.c
> >>   |   6 +-
> >>   include/dt-bindings/clock/samsung,s5pv210-clock.h  | 224 +++++++
> >>   12 files changed, 1019 insertions(+), 8 deletions(-)
> >>   create mode 100644
> >> Documentation/devicetree/bindings/clock/samsung,s5pv210-clock.txt
> >> create mode 100644 drivers/clk/samsung/clk-s5pv210.c
> >>   create mode 100644 include/dt-bindings/clock/samsung,s5pv210-clock.h
> >
> > I believe this series is reasonable to be applied. Could we agree on
> > the tree it would go through and get all tne required acks?
> >
> > Best regards,
> > Tomasz
> 
> I agree.
> 
> Mike, how do you think the common clk stuff for s5pv210?

Clock code looks good to me. Which tree do you want to take it through?

Regards,
Mike

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