From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: Sender: =?UTF-8?Q?Krzysztof_Koz=C5=82owski?= Subject: Re: [PATCH v3 2/5] mfd: sec: Add support for S2MPS15 PMIC To: Alim Akhtar , Lee Jones References: <1445863883-5187-1-git-send-email-alim.akhtar@samsung.com> <1445863883-5187-3-git-send-email-alim.akhtar@samsung.com> <20151026143411.GL597@x1> <563021AF.6030100@samsung.com> <20151028084609.GG5828@x1> <5630AFC7.2030901@samsung.com> Cc: k.kozlowski.k@gmail.com, broonie@kernel.org, mturquette@baylibre.com, linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org, rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org, Thomas Abraham From: Krzysztof Kozlowski Message-ID: <5630D20E.6010409@samsung.com> Date: Wed, 28 Oct 2015 22:47:58 +0900 MIME-Version: 1.0 In-Reply-To: <5630AFC7.2030901@samsung.com> Content-Type: text/plain; charset=utf-8 List-ID: W dniu 28.10.2015 o 20:21, Alim Akhtar pisze: > Hello, > > On 10/28/2015 02:16 PM, Lee Jones wrote: >> On Wed, 28 Oct 2015, Krzysztof Kozlowski wrote: >> >>> On 26.10.2015 23:34, Lee Jones wrote: >>>> On Mon, 26 Oct 2015, Alim Akhtar wrote: >>>> >>>>> From: Thomas Abraham >>>>> >>>>> Add support for S2MPS15 PMIC which is similar to S2MPS11 PMIC. The >>>>> S2MPS15 >>>>> PMIC supports 27 LDO regulators, 10 buck regulators, RTC, three >>>>> 32.768KHz >>>>> clock outputs and battery charger. This patch adds initial support for >>>>> LDO and buck regulators of S2MPS15 device. >>>>> >>>>> Signed-off-by: Thomas Abraham >>>>> Signed-off-by: Alim Akhtar >>>>> [Alim: Added s2mps15_devs like rtc and clk and related changes] >>>>> Reviewed-by: Krzysztof Kozlowski >>>>> --- >>>>> drivers/mfd/sec-core.c | 31 +++++++ >>>>> drivers/mfd/sec-irq.c | 8 ++ >>>>> include/linux/mfd/samsung/core.h | 1 + >>>>> include/linux/mfd/samsung/s2mps15.h | 158 >>>>> +++++++++++++++++++++++++++++++++++ >>>>> 4 files changed, 198 insertions(+) >>>>> create mode 100644 include/linux/mfd/samsung/s2mps15.h >>>> >>>> I replied to the previous set and won't be reviewing this one until >>>> all of the open points are solved. >>> >>> The naming and compatibles used by the driver are confusing but how it >>> was at beginning. Beside the confusion, the names are correct: >>> >>> 1. Main mfd driver: >>> - compatible: samsung,s2mps1*-pmic >>> - driver name: sec_pmic >>> >>> 2. Regulator driver: >>> - no compatible (because it always searches for "regulators" >>> subnode of >>> its parent... that is the convention/legacy behaviour) >>> - driver name: s2mps1*-pmic >>> >>> I hope that explains your concerns. >> >> It explains *why*, but doesn't ease my concerns in any way. >> >> Unfortunately I've only just realised the disparity we have between >> MFD and the Regulator subsystem, which is annoying because it's now >> almost impossible to rectify. >> >> We should have taken one of two views. Either a) The MFD is the PMIC >> device which encompasses regulator control. In which case the MFD >> and it's corresponding compatible string would be named *-pmic and the >> regulator driver would be called *-regulator. Or b) The MFD could be >> considered a normal MFD and be named after the model number, then the >> regulator 'could' be named *-pmic. >> >> However, with reference to b), how much other Power Management does >> the regulator driver do besides control regulators? I suspect not >> much. Therefore my preference would be for a). My second choice >> would be a mixuture of the two where nothing gets named *-pmic. The >> last option on my list would be the current situation where we seem to >> be calling both the MFD (PMIC) itself and the Regulator driver >> *-pmic, which is not good. >> > Well, I would have also preferred option a), but keeping existing DT > bindings, looks like we need to go with the current situation. > Krzysztof any thought on this? > Looks good to me. Please, go ahead. Best regards, Krzysztof From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com. [2607:f8b0:400e:c03::229]) by gmr-mx.google.com with ESMTPS id fa8si4837509pab.1.2015.10.28.06.48.03 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Oct 2015 06:48:03 -0700 (PDT) Received: by mail-pa0-x229.google.com with SMTP id z6so7895634pas.2 for ; Wed, 28 Oct 2015 06:48:03 -0700 (PDT) Sender: rtc-linux@googlegroups.com Subject: [rtc-linux] Re: [PATCH v3 2/5] mfd: sec: Add support for S2MPS15 PMIC To: Alim Akhtar , Lee Jones References: <1445863883-5187-1-git-send-email-alim.akhtar@samsung.com> <1445863883-5187-3-git-send-email-alim.akhtar@samsung.com> <20151026143411.GL597@x1> <563021AF.6030100@samsung.com> <20151028084609.GG5828@x1> <5630AFC7.2030901@samsung.com> Cc: k.kozlowski.k@gmail.com, broonie@kernel.org, mturquette@baylibre.com, linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org, rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org, Thomas Abraham From: Krzysztof Kozlowski Message-ID: <5630D20E.6010409@samsung.com> Date: Wed, 28 Oct 2015 22:47:58 +0900 MIME-Version: 1.0 In-Reply-To: <5630AFC7.2030901@samsung.com> Content-Type: text/plain; charset=UTF-8 Reply-To: rtc-linux@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , W dniu 28.10.2015 o 20:21, Alim Akhtar pisze: > Hello, > > On 10/28/2015 02:16 PM, Lee Jones wrote: >> On Wed, 28 Oct 2015, Krzysztof Kozlowski wrote: >> >>> On 26.10.2015 23:34, Lee Jones wrote: >>>> On Mon, 26 Oct 2015, Alim Akhtar wrote: >>>> >>>>> From: Thomas Abraham >>>>> >>>>> Add support for S2MPS15 PMIC which is similar to S2MPS11 PMIC. The >>>>> S2MPS15 >>>>> PMIC supports 27 LDO regulators, 10 buck regulators, RTC, three >>>>> 32.768KHz >>>>> clock outputs and battery charger. This patch adds initial support for >>>>> LDO and buck regulators of S2MPS15 device. >>>>> >>>>> Signed-off-by: Thomas Abraham >>>>> Signed-off-by: Alim Akhtar >>>>> [Alim: Added s2mps15_devs like rtc and clk and related changes] >>>>> Reviewed-by: Krzysztof Kozlowski >>>>> --- >>>>> drivers/mfd/sec-core.c | 31 +++++++ >>>>> drivers/mfd/sec-irq.c | 8 ++ >>>>> include/linux/mfd/samsung/core.h | 1 + >>>>> include/linux/mfd/samsung/s2mps15.h | 158 >>>>> +++++++++++++++++++++++++++++++++++ >>>>> 4 files changed, 198 insertions(+) >>>>> create mode 100644 include/linux/mfd/samsung/s2mps15.h >>>> >>>> I replied to the previous set and won't be reviewing this one until >>>> all of the open points are solved. >>> >>> The naming and compatibles used by the driver are confusing but how it >>> was at beginning. Beside the confusion, the names are correct: >>> >>> 1. Main mfd driver: >>> - compatible: samsung,s2mps1*-pmic >>> - driver name: sec_pmic >>> >>> 2. Regulator driver: >>> - no compatible (because it always searches for "regulators" >>> subnode of >>> its parent... that is the convention/legacy behaviour) >>> - driver name: s2mps1*-pmic >>> >>> I hope that explains your concerns. >> >> It explains *why*, but doesn't ease my concerns in any way. >> >> Unfortunately I've only just realised the disparity we have between >> MFD and the Regulator subsystem, which is annoying because it's now >> almost impossible to rectify. >> >> We should have taken one of two views. Either a) The MFD is the PMIC >> device which encompasses regulator control. In which case the MFD >> and it's corresponding compatible string would be named *-pmic and the >> regulator driver would be called *-regulator. Or b) The MFD could be >> considered a normal MFD and be named after the model number, then the >> regulator 'could' be named *-pmic. >> >> However, with reference to b), how much other Power Management does >> the regulator driver do besides control regulators? I suspect not >> much. Therefore my preference would be for a). My second choice >> would be a mixuture of the two where nothing gets named *-pmic. The >> last option on my list would be the current situation where we seem to >> be calling both the MFD (PMIC) itself and the Regulator driver >> *-pmic, which is not good. >> > Well, I would have also preferred option a), but keeping existing DT > bindings, looks like we need to go with the current situation. > Krzysztof any thought on this? > Looks good to me. Please, go ahead. Best regards, Krzysztof -- -- You received this message because you are subscribed to "rtc-linux". Membership options at http://groups.google.com/group/rtc-linux . Please read http://groups.google.com/group/rtc-linux/web/checklist before submitting a driver. --- You received this message because you are subscribed to the Google Groups "rtc-linux" group. To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout.