mbox series

[v3,0/4] clk: qcom : add sm8250 LPASS GFM drivers

Message ID 20201016141241.5839-1-srinivas.kandagatla@linaro.org
Headers show
Series clk: qcom : add sm8250 LPASS GFM drivers | expand

Message

Srinivas Kandagatla Oct. 16, 2020, 2:12 p.m. UTC
This patchset adds support for GFM Muxes found in LPASS
(Low Power Audio SubSystem) IP in Audio Clock Controller
and Always ON clock controller.

Clocks derived from these muxes are consumed by LPASS Digital Codec.
Currently the driver for Audio and Always ON clock controller only
supports GFM Muxes, however it should be easy to add more clock
support when required

Changes since v2:
- updated Kconfig text and help as suggested by Stephen
- removed unnecessary header file include
- use fw_name instead of name for parents
- use devm_platform_ioremap_resource

verified dt_binding_check to pass on linux master,

Srinivas Kandagatla (4):
  dt-bindings: clock: Add support for LPASS Audio Clock Controller
  dt-bindings: clock: Add support for LPASS Always ON Controller
  clk: qcom: Add support to LPASS AUDIO_CC Glitch Free Mux clocks
  clk: qcom: Add support to LPASS AON_CC Glitch Free Mux clocks

 .../bindings/clock/qcom,aoncc-sm8250.yaml     |  58 ++++
 .../bindings/clock/qcom,audiocc-sm8250.yaml   |  58 ++++
 drivers/clk/qcom/Kconfig                      |   6 +
 drivers/clk/qcom/Makefile                     |   1 +
 drivers/clk/qcom/lpass-gfm-sm8250.c           | 320 ++++++++++++++++++
 .../clock/qcom,sm8250-lpass-aoncc.h           |  11 +
 .../clock/qcom,sm8250-lpass-audiocc.h         |  13 +
 7 files changed, 467 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/clock/qcom,aoncc-sm8250.yaml
 create mode 100644 Documentation/devicetree/bindings/clock/qcom,audiocc-sm8250.yaml
 create mode 100644 drivers/clk/qcom/lpass-gfm-sm8250.c
 create mode 100644 include/dt-bindings/clock/qcom,sm8250-lpass-aoncc.h
 create mode 100644 include/dt-bindings/clock/qcom,sm8250-lpass-audiocc.h

-- 
2.21.0

Comments

Rob Herring Oct. 19, 2020, 2:21 p.m. UTC | #1
On Fri, 16 Oct 2020 15:12:39 +0100, Srinivas Kandagatla wrote:
> Always ON Clock controller is a block inside LPASS which controls

> 1 Glitch free muxes to LPASS codec Macros.

> 

> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>

> ---

>  .../bindings/clock/qcom,aoncc-sm8250.yaml     | 58 +++++++++++++++++++

>  .../clock/qcom,sm8250-lpass-aoncc.h           | 11 ++++

>  2 files changed, 69 insertions(+)

>  create mode 100644 Documentation/devicetree/bindings/clock/qcom,aoncc-sm8250.yaml

>  create mode 100644 include/dt-bindings/clock/qcom,sm8250-lpass-aoncc.h

> 



My bot found errors running 'make dt_binding_check' on your patch:

Error: Documentation/devicetree/bindings/clock/qcom,aoncc-sm8250.example.dts:25.30-31 syntax error
FATAL ERROR: Unable to parse input tree
make[1]: *** [scripts/Makefile.lib:342: Documentation/devicetree/bindings/clock/qcom,aoncc-sm8250.example.dt.yaml] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1366: dt_binding_check] Error 2


See https://patchwork.ozlabs.org/patch/1383375

If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure dt-schema is up to date:

pip3 install git+https://github.com/devicetree-org/dt-schema.git@master --upgrade

Please check and re-submit.
Stephen Boyd Oct. 19, 2020, 10:42 p.m. UTC | #2
Quoting Srinivas Kandagatla (2020-10-16 07:12:37)
> This patchset adds support for GFM Muxes found in LPASS

> (Low Power Audio SubSystem) IP in Audio Clock Controller

> and Always ON clock controller.

> 

> Clocks derived from these muxes are consumed by LPASS Digital Codec.

> Currently the driver for Audio and Always ON clock controller only

> supports GFM Muxes, however it should be easy to add more clock

> support when required

> 

> Changes since v2:

> - updated Kconfig text and help as suggested by Stephen

> - removed unnecessary header file include

> - use fw_name instead of name for parents

> - use devm_platform_ioremap_resource

> 

> verified dt_binding_check to pass on linux master,


Which linux master? Can you try on linux-next?