From: Tony Xie <tony.xie@rock-chips.com> To: heiko@sntech.de Cc: broonie@kernel.org, lee.jones@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com, a.zummo@towertech.it, alexandre.belloni@bootlin.com, sboyd@kernel.org, linux-clk@vger.kernel.org, linux-rtc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, chenjh@rock-chips.com, xsf@rock-chips.com, zhangqing@rock-chips.com, huangtao@rock-chips.com, tony.xie@rock-chips.com Subject: [PATCH v9 0/6] support a new type of PMIC,including two chips(rk817 and rk809) Date: Thu, 13 Jun 2019 23:14:19 -0400 [thread overview] Message-ID: <20190614031425.15741-1-tony.xie@rock-chips.com> (raw) Most of functions and registers of the rk817 and rk808 are the same, so they can share allmost all codes. Their specifications are as follows: 1) The RK809 and RK809 consist of 5 DCDCs, 9 LDOs and have the same registers for these components except dcdc5. 2) The dcdc5 is a boost dcdc for RK817 and is a buck for RK809. 3) The RK817 has one switch but The Rk809 has two. Changes in V2: 1. initialize the pm_pwroff_fn to NULL. 2. use EXPORT_SYMBOL_GPL to export pm_power_off_prepare. 3. change patch 2/3/4/5 subjects. Changes in V3 1. change patch 4 subjects 2. replace pr_ with dev_ for printing in patch 2 3. modify switch1 and switch2 configs in patch 2 4. explain gpio information for rk809 and rk817 in patch 4 Changes in V4: 1. modify some codes for patch 2 and patch 5 according to comments 2. add reviewer mail lists for patch 3 and 4 Changes in V5: modify some codes for patch 1 according to reveiw comments for v3. 1) remove the pm_power_off_prepare() and replace with shutdown call-back from syscore 2) move the macro REGMAP_IRQ_M into the regmap.h and rename it REGMAP_IRQ_LINE 3) make some dev_warn() log clear Changes in V6: modify some codes according to reveiw comments for v5. Changes in V7: modify some codes for patch 2 according to reveiw comments. Changes in V8: For helping me promote this work, Heiko send the V8 Changes in V9: 1.base on the V8 2.modify some codes according to reveiw comments for V8 from Mark Brown Tony Xie (6): mfd: rk808: remove the id_table mfd: rk808: Add RK817 and RK809 support regulator: rk808: add RK809 and RK817 support. dt-bindings: mfd: rk808: Add binding information for RK809 and RK817. rtc: rk808: add RK809 and RK817 support. clk: RK808: add RK809 and RK817 support. .../devicetree/bindings/mfd/rk808.txt | 44 ++ drivers/clk/Kconfig | 9 +- drivers/clk/clk-rk808.c | 64 +- drivers/mfd/Kconfig | 6 +- drivers/mfd/rk808.c | 199 +++++- drivers/regulator/Kconfig | 4 +- drivers/regulator/rk808-regulator.c | 646 +++++++++++++++++- drivers/rtc/Kconfig | 4 +- drivers/rtc/rtc-rk808.c | 68 +- include/linux/mfd/rk808.h | 175 +++++ 10 files changed, 1155 insertions(+), 64 deletions(-) -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Tony Xie <tony.xie@rock-chips.com> To: heiko@sntech.de Cc: mark.rutland@arm.com, a.zummo@towertech.it, alexandre.belloni@bootlin.com, tony.xie@rock-chips.com, huangtao@rock-chips.com, devicetree@vger.kernel.org, sboyd@kernel.org, zhangqing@rock-chips.com, linux-kernel@vger.kernel.org, robh+dt@kernel.org, xsf@rock-chips.com, linux-rockchip@lists.infradead.org, broonie@kernel.org, chenjh@rock-chips.com, lee.jones@linaro.org, linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rtc@vger.kernel.org Subject: [PATCH v9 0/6] support a new type of PMIC, including two chips(rk817 and rk809) Date: Thu, 13 Jun 2019 23:14:19 -0400 [thread overview] Message-ID: <20190614031425.15741-1-tony.xie@rock-chips.com> (raw) Most of functions and registers of the rk817 and rk808 are the same, so they can share allmost all codes. Their specifications are as follows: 1) The RK809 and RK809 consist of 5 DCDCs, 9 LDOs and have the same registers for these components except dcdc5. 2) The dcdc5 is a boost dcdc for RK817 and is a buck for RK809. 3) The RK817 has one switch but The Rk809 has two. Changes in V2: 1. initialize the pm_pwroff_fn to NULL. 2. use EXPORT_SYMBOL_GPL to export pm_power_off_prepare. 3. change patch 2/3/4/5 subjects. Changes in V3 1. change patch 4 subjects 2. replace pr_ with dev_ for printing in patch 2 3. modify switch1 and switch2 configs in patch 2 4. explain gpio information for rk809 and rk817 in patch 4 Changes in V4: 1. modify some codes for patch 2 and patch 5 according to comments 2. add reviewer mail lists for patch 3 and 4 Changes in V5: modify some codes for patch 1 according to reveiw comments for v3. 1) remove the pm_power_off_prepare() and replace with shutdown call-back from syscore 2) move the macro REGMAP_IRQ_M into the regmap.h and rename it REGMAP_IRQ_LINE 3) make some dev_warn() log clear Changes in V6: modify some codes according to reveiw comments for v5. Changes in V7: modify some codes for patch 2 according to reveiw comments. Changes in V8: For helping me promote this work, Heiko send the V8 Changes in V9: 1.base on the V8 2.modify some codes according to reveiw comments for V8 from Mark Brown Tony Xie (6): mfd: rk808: remove the id_table mfd: rk808: Add RK817 and RK809 support regulator: rk808: add RK809 and RK817 support. dt-bindings: mfd: rk808: Add binding information for RK809 and RK817. rtc: rk808: add RK809 and RK817 support. clk: RK808: add RK809 and RK817 support. .../devicetree/bindings/mfd/rk808.txt | 44 ++ drivers/clk/Kconfig | 9 +- drivers/clk/clk-rk808.c | 64 +- drivers/mfd/Kconfig | 6 +- drivers/mfd/rk808.c | 199 +++++- drivers/regulator/Kconfig | 4 +- drivers/regulator/rk808-regulator.c | 646 +++++++++++++++++- drivers/rtc/Kconfig | 4 +- drivers/rtc/rtc-rk808.c | 68 +- include/linux/mfd/rk808.h | 175 +++++ 10 files changed, 1155 insertions(+), 64 deletions(-) -- 2.17.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-06-14 3:22 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-14 3:14 Tony Xie [this message] 2019-06-14 3:14 ` [PATCH v9 0/6] support a new type of PMIC, including two chips(rk817 and rk809) Tony Xie 2019-06-14 3:14 ` [PATCH v9 1/6] mfd: rk808: remove the id_table Tony Xie 2019-06-14 3:14 ` Tony Xie 2019-06-14 3:14 ` [PATCH v9 2/6] mfd: rk808: Add RK817 and RK809 support Tony Xie 2019-06-14 3:14 ` Tony Xie 2019-06-14 3:14 ` [PATCH v9 3/6] regulator: rk808: add RK809 and RK817 support Tony Xie 2019-06-14 3:14 ` Tony Xie 2019-06-14 18:24 ` Mark Brown 2019-06-14 18:24 ` Mark Brown 2019-06-14 3:14 ` [PATCH v9 4/6] dt-bindings: mfd: rk808: Add binding information for RK809 and RK817 Tony Xie 2019-06-14 3:14 ` Tony Xie 2019-06-14 3:17 ` [PATCH v9 5/6] rtc: rk808: add RK809 and RK817 support Tony Xie 2019-06-14 3:17 ` Tony Xie 2019-06-14 3:17 ` [PATCH v9 6/6] clk: RK808: " Tony Xie 2019-06-14 3:17 ` Tony Xie
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190614031425.15741-1-tony.xie@rock-chips.com \ --to=tony.xie@rock-chips.com \ --cc=a.zummo@towertech.it \ --cc=alexandre.belloni@bootlin.com \ --cc=broonie@kernel.org \ --cc=chenjh@rock-chips.com \ --cc=devicetree@vger.kernel.org \ --cc=heiko@sntech.de \ --cc=huangtao@rock-chips.com \ --cc=lee.jones@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-clk@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rockchip@lists.infradead.org \ --cc=linux-rtc@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=robh+dt@kernel.org \ --cc=sboyd@kernel.org \ --cc=xsf@rock-chips.com \ --cc=zhangqing@rock-chips.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.