The clock IP used on the Maxim PMICs max77686 and max77802 are
same. The configuration of clock register is also same except
the number of clocks.
Part of common code utilisation, there is 3 files for these chips
clock driver, one for common and two files for driver registration.
Combine both drivers into single file and move common code into
same common file reduces the 2 files and make max77686 and max77802
clock driver in single fine. This driver does not depends on the
parent driver structure. The regmap handle is acquired through
regmap APIs for the register access.
After comining the driver and DT files, extend the support to MAX77620.
This series is based on discussion from the series
clk: max77620: Add clock driver for MAX77620/MAX20024
On this series, it is proposed to combine all files together.
Changes form V1:
- Incorporated all review comment.
- Collected Testedby/reviewed by.
Changes from V2:
- Nit fixes and colleced all RB/TB
Laxman Dewangan (4):
clk: max77686: Combine Maxim max77686 and max77802 driver
clk: Combine DT binding doc for max77686 and max77802
clk: max77686: Add DT binding details for PMIC MAX77620
clk: max77686: Add support for MAX77620 clocks
.../devicetree/bindings/clock/maxim,max77686.txt | 118 ++++++++--
.../devicetree/bindings/clock/maxim,max77802.txt | 44 ----
drivers/clk/Kconfig | 18 +-
drivers/clk/Makefile | 2 -
drivers/clk/clk-max-gen.c | 194 ---------------
drivers/clk/clk-max-gen.h | 32 ---
drivers/clk/clk-max77686.c | 262 ++++++++++++++++++++-
drivers/clk/clk-max77802.c | 96 --------
include/dt-bindings/clock/maxim,max77620.h | 21 ++
9 files changed, 368 insertions(+), 419 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/clock/maxim,max77802.txt
delete mode 100644 drivers/clk/clk-max-gen.c
delete mode 100644 drivers/clk/clk-max-gen.h
delete mode 100644 drivers/clk/clk-max77802.c
create mode 100644 include/dt-bindings/clock/maxim,max77620.h
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
