linux-kernel - Re: [PATCH v2 1/3] clk: hisilicon: add CRG driver Hi3521A SoC

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] [day] [month] [year] [list]

Message-ID: <20171121115611.bmdriap3uoazmyiw@proprietary-killer.fossland>
Date:   Tue, 21 Nov 2017 05:56:12 -0600
From:   "Marty E. Plummer" <hanetzer@...rtmail.com>
To:     Rob Herring <robh@...nel.org>
Cc:     linux-arm-kernel@...ts.infradead.org, mturquette@...libre.com,
        sboyd@...eaurora.org, mark.rutland@....com,
        xuejiancheng@...ilicon.com, zhangfei.gao@...aro.org,
        wnpan@...ilicon.com, linux-kernel@...r.kernel.org,
        linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
        xuwei5@...ilicon.com, linux@...linux.org.uk
Subject: Re: [PATCH v2 1/3] clk: hisilicon: add CRG driver Hi3521A SoC

On Tue, Oct 24, 2017 at 01:42:50PM -0500, Rob Herring wrote:
> On Tue, Oct 17, 2017 at 05:38:52PM -0500, Marty E. Plummer wrote:
> > Add CRG driver for Hi3521A SoC. CRG (Clock and Reset Generator) module
> > generates clock and reset signals used by other module blocks on SoC.
> > 
> > Signed-off-by: Marty E. Plummer <hanetzer@...rtmail.com>
> > ---
> > Changes in v2:
> >   - Switched to SPDX tags and GPL-2.0+
> > 
> >  drivers/clk/hisilicon/Kconfig             |   7 ++
> >  drivers/clk/hisilicon/Makefile            |   1 +
> >  drivers/clk/hisilicon/crg-hi3521a.c       | 196 ++++++++++++++++++++++++++++++
> 
> >  include/dt-bindings/clock/hi3521a-clock.h |  23 ++++
> 
> Acked-by: Rob Herring <robh@...nel.org>
Actually nack this for now. I need to change some stuff over to use a
different clock for the sp804 timer@...00000, apparently I'm going to
need to use CLK_OF_DECLARE to get the clock in question working that
early in boot.