[RFC,0/1] Potential binding MStar clk muxes.

Message ID	20210212111649.3251306-1-daniel@0x0f.com
Headers	show Return-Path: <devicetree-owner@vger.kernel.org> From: Daniel Palmer <daniel@0x0f.com> To: devicetree@vger.kernel.org, linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org Cc: Daniel Palmer <daniel@0x0f.com> Subject: [RFC PATCH 0/1] Potential binding MStar clk muxes. Date: Fri, 12 Feb 2021 20:16:48 +0900 Message-Id: <20210212111649.3251306-1-daniel@0x0f.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk
Series	Potential binding MStar clk muxes. \| expand [RFC,0/1] Potential binding MStar clk muxes. [RFC,1/1] dt-bindings: clk: Mstar msc313 clkgen mux

Message ID

20210212111649.3251306-1-daniel@0x0f.com

Headers

From: Daniel Palmer <daniel@0x0f.com>
To: devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
        linux-arm-kernel@lists.infradead.org
Cc: Daniel Palmer <daniel@0x0f.com>
Subject: [RFC PATCH 0/1] Potential binding MStar clk muxes.
Date: Fri, 12 Feb 2021 20:16:48 +0900
Message-Id: <20210212111649.3251306-1-daniel@0x0f.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Series

Potential binding MStar clk muxes. | expand

Message

Daniel Palmer Feb. 12, 2021, 11:16 a.m. UTC

Hi all,

While getting this driver ready to send I realised the current
binding I have is pretty unwieldly. I'm thinking of refactoring
the driver to work like this binding desribes and would like
some feedback before I rework the driver.

Thanks,

Daniel

Daniel Palmer (1):
  dt-bindings: clk: Mstar msc313 clkgen mux

 .../clock/mstar,msc313-clkgen-mux.yaml        | 87 +++++++++++++++++++
 1 file changed, 87 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/clock/mstar,msc313-clkgen-mux.yaml