[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <568FBB6D.2020904@nvidia.com>
Date: Fri, 8 Jan 2016 19:06:45 +0530
From: Laxman Dewangan <ldewangan@...dia.com>
To: Mark Brown <broonie@...nel.org>
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 Friday 08 January 2016 07:06 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Fri, Jan 08, 2016 at 06:34:29PM +0530, Laxman Dewangan wrote:
>
>> If we get the parent device, regmap handle and interrupt number from mfd
>> core independent of the PMIC (MAX77620 or MAX77686), then same driver can be
>> used here.
>> Two way which I can think of here:
> Parent device is just dev->parent, you can use dev_get_regmap() to get a
> regmap given a struct device and you can use platform resources to pass
> the interrupts to the children from the MFD (there's some examples,
> wm831x is one).
>
>
I think it should work with named regmap. mfd whould init regmap with
name and rtc driver should ask with same name.
I saw three drivers which looks same:
rtc-max77620.c (new from me) and already available rtc-max77686.c,
rtc-max77802.c
Seems I can develop IP based rtc driver as rtc-max77xxx.c
Powered by blists - more mailing lists