[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160108125117.GM6588@sirena.org.uk>
Date: Fri, 8 Jan 2016 12:51:17 +0000
From: Mark Brown <broonie@...nel.org>
To: Laxman Dewangan <ldewangan@...dia.com>
Cc: Krzysztof Kozlowski <k.kozlowski@...sung.com>,
rtc-linux@...glegroups.com, robh+dt@...nel.org, pawel.moll@....com,
mark.rutland@....com, ijc+devicetree@...lion.org.uk,
galak@...eaurora.org, linus.walleij@...aro.org, gnurou@...il.com,
lee.jones@...aro.org, a.zummo@...ertech.it,
alexandre.belloni@...e-electrons.com, lgirdwood@...il.com,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org, swarren@...dia.com, treding@...dia.com,
Chaitanya Bandi <bandik@...dia.com>
Subject: Re: [rtc-linux] [PATCH 5/6] rtc: max77620: add support for
max77620/max20024 RTC driver
On Fri, Jan 08, 2016 at 03:50:46PM +0530, Laxman Dewangan wrote:
> Yaah, that is the issue on IP based PMIC system and it happen with the Maxim
> and TI.
> The MFD and its sub module drivers are too much couped and hence dificult
> to use the IP driver across PMIC. For almost all Maxim PMIC, we end up of
> same type of RTC driver.
> Probably, we need to enhance the mfd sub system to allow sub module driver
> to decoupe from its APIs.
Could you be more specific about the issues here please? I can't think
of any barriers and you've not mentioned any barriers...
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists