From: Lee Jones <lee.jones@linaro.org>
To: Thierry Reding <treding@nvidia.com>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
linus.walleij@linaro.org, robh+dt@kernel.org,
mark.rutland@arm.com, gnurou@gmail.com,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, ijc+devicetree@hellion.org.uk,
swarren@nvidia.com, Mallikarjun Kasoju <mkasoju@nvidia.com>
Subject: Re: [PATCH V10 2/6] mfd: max77620: add core driver for MAX77620/MAX20024
Date: Wed, 27 Apr 2016 16:29:37 +0100 [thread overview]
Message-ID: <20160427152937.GE4892@dell> (raw)
In-Reply-To: <20160427150559.GD4176@ulmo.ba.sec>
On Wed, 27 Apr 2016, Thierry Reding wrote:
> On Wed, Mar 30, 2016 at 07:59:44PM +0530, Laxman Dewangan wrote:
> > MAX77620/MAX20024 are Power Management IC from the MAXIM.
> > It supports RTC, multiple GPIOs, multiple DCDC and LDOs,
> > watchdog, clock etc.
> >
> > Add MFD drier to provides common support for accessing the
> > device; additional drivers is developed on respected subsystem
> > in order to use the functionality of the device.
> >
> > Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> > Signed-off-by: Mallikarjun Kasoju <mkasoju@nvidia.com>
> > Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> >
> > ---
> > Changes from V1:
> > - Code cleanups per review from V1.
> > - Move register acccess APIs from header to c file.
> > - Remove some of non required variable, remove duplication in error message
> > and simplify some of function implementation.
> > - Register RTC driver such that it can get the regmap handle form parent device
> >
> > Changes from V2:
> > - Run coccicheck and checkpatch in strict mode for the alignment.
> > - Drop RTC driver and its i2c client registration.
> >
> > Changes from V3:
> > - Change all sys initcall to module driver.
> > - change the max77620_read argument to unisgned int from u8.
> >
> > Changes from V4:
> > - Take care of fps nodes.
> > - Drop the battery charger and low battery binding and related code as
> > it need to go on power driver.
> >
> > Changes from V5:
> > -None
> >
> > Changes from V6:
> > - Taken care of Lee's comment like used defines for irqs, remove max77620
> > register accesss abstractions, remove DTof module and use ID table only,
> > reduce the copyright lines.
> > - Drop configuration for hard power off time chnage as it will be in
> > power driver.
> > - Use direct regmap from all drivers instead of using abstractions.
> > - This depends on patch
> >
> > Change from V7:
> > - Use MFD defines for making mfd cells.
> > - Use new property name.
> >
> > Changes from V8:
> > - Remove the usage of MFD defines. Remove mutex_config as not needed.
> >
> > Changes from V9:
> > - Use the devm_regmap_add_irq_chip() for irq registration.
> >
> > drivers/mfd/Kconfig | 15 ++
> > drivers/mfd/Makefile | 1 +
> > drivers/mfd/max77620.c | 544 +++++++++++++++++++++++++++++++++++++++++++
> > include/linux/mfd/max77620.h | 337 +++++++++++++++++++++++++++
> > 4 files changed, 897 insertions(+)
> > create mode 100644 drivers/mfd/max77620.c
> > create mode 100644 include/linux/mfd/max77620.h
>
> Lee,
>
> Were you going to pick this up along with the corresponding DT bindings?
I will, once I'm happy with the driver.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-04-27 15:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 14:29 [PATCH V10 0/6] Add support for MAXIM MAX77620/MAX20024 PMIC Laxman Dewangan
2016-03-30 14:29 ` [PATCH V10 1/6] mfd: add device-tree binding doc for PMIC max77620/max20024 Laxman Dewangan
2016-04-27 12:49 ` Lee Jones
2016-04-27 15:04 ` Thierry Reding
2016-04-27 15:30 ` Lee Jones
[not found] ` <1459348188-11726-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-30 14:29 ` [PATCH V10 2/6] mfd: max77620: add core driver for MAX77620/MAX20024 Laxman Dewangan
2016-04-27 15:06 ` Thierry Reding
2016-04-27 15:29 ` Lee Jones [this message]
2016-04-27 15:19 ` Lee Jones
2016-04-27 18:27 ` Laxman Dewangan
2016-04-28 7:25 ` Lee Jones
2016-04-28 7:18 ` Laxman Dewangan
2016-04-28 8:51 ` Lee Jones
2016-04-27 18:43 ` Laxman Dewangan
2016-04-28 7:23 ` Lee Jones
2016-03-30 14:29 ` [PATCH V10 3/6] pinctrl: add DT binding doc for pincontrol of PMIC max77620/max20024 Laxman Dewangan
2016-03-30 14:29 ` [PATCH V10 4/6] pinctrl: max77620: add pincontrol driver for MAX77620/MAX20024 Laxman Dewangan
2016-03-30 14:29 ` [PATCH V10 5/6] gpio: add DT binding doc for gpio of PMIC max77620/max20024 Laxman Dewangan
2016-03-30 14:29 ` [PATCH V10 6/6] gpio: max77620: add gpio driver for MAX77620/MAX20024 Laxman Dewangan
2016-04-15 16:57 ` [PATCH V10 0/6] Add support for MAXIM MAX77620/MAX20024 PMIC Laxman Dewangan
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=20160427152937.GE4892@dell \
--to=lee.jones@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ldewangan@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mkasoju@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=swarren@nvidia.com \
--cc=treding@nvidia.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).