[RFC v2 1/2] clk: hisilicon: add CRG driver Hi3521a SoC

Marty E. Plummer hanetzer at startmail.com
Wed Jun 1 04:06:16 PDT 2022


On Wed, Jun 01, 2022 at 01:00:38PM +0200, Krzysztof Kozlowski wrote:
> On 01/06/2022 12:58, Marty E. Plummer wrote:
> > On Tue, May 03, 2022 at 01:37:42PM +0200, Krzysztof Kozlowski wrote:
> >> On 01/05/2022 19:34, 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 at startmail.com>
> >>> ---
> >>>  drivers/clk/hisilicon/Kconfig             |   8 ++
> >>>  drivers/clk/hisilicon/Makefile            |   1 +
> >>>  drivers/clk/hisilicon/crg-hi3521a.c       | 141 ++++++++++++++++++++++
> >>>  include/dt-bindings/clock/hi3521a-clock.h |  34 ++++++
> >>
> >> Bindings go to separate patch. Your patchset is unmerge'able.
> >>
> > So, assuming I have the following patches:
> > 1: +include/dt-bindings/clock/hi3521a-clock.h
> > 2: +drivers/clk/hisilicon/crg-hi3521a.c
> > 3: +Documentation/devicetree/bindings/whatever
> > 
> > In what order should they be applied?
> 
> Applied or sent? The maintainer will apply them in proper order, this is
> bisectable.
> 
> 
Either or. Whatever makes the workload easier is what I'm looking for.
> Best regards,
> Krzysztof



More information about the linux-arm-kernel mailing list