From: Lee Jones <lee.jones@linaro.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: 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, treding@nvidia.com,
Mallikarjun Kasoju <mkasoju@nvidia.com>
Subject: Re: [PATCH V10 2/6] mfd: max77620: add core driver for MAX77620/MAX20024
Date: Thu, 28 Apr 2016 08:25:59 +0100 [thread overview]
Message-ID: <20160428072559.GK4892@dell> (raw)
In-Reply-To: <572104AA.7080500@nvidia.com>
On Wed, 27 Apr 2016, Laxman Dewangan wrote:
>
> On Wednesday 27 April 2016 08:49 PM, Lee Jones wrote:
> >On Wed, 30 Mar 2016, Laxman Dewangan wrote:
> >
> >>+#define MAX77620_MFD_CELL_RES(_name, _res) \
> >>+ { \
> >>+ .name = (_name), \
> >>+ .resources = (_res), \
> >>+ .num_resources = ARRAY_SIZE((_res)), \
> >>+ }
> >I'm *still* not accepting this.
> >
> >>+
> >>+static struct mfd_cell max20024_children[] = {
> >>+ MAX77620_MFD_CELL_NAME("max20024-pinctrl"),
> >>+ MAX77620_MFD_CELL_RES("max20024-gpio", gpio_resources),
> >>+ MAX77620_MFD_CELL_NAME("max20024-pmic"),
> >>+ MAX77620_MFD_CELL_RES("max77620-rtc", rtc_resources),
> >>+ MAX77620_MFD_CELL_RES("max20024-power", power_resources),
> >>+ MAX77620_MFD_CELL_NAME("max20024-watchdog"),
> >>+ MAX77620_MFD_CELL_NAME("max20024-clock"),
> >>+};
> >If you want this submission to be accepted this cycle, you're going to
> >have to convert this to the traditional way of defining MFD children.
>
> Yaah, I want to have this in current cycle.
> Will it be fine as follows? (To have quick agreement)
>
> static const struct mfd_cell max77620_children[] = {
> {
> .name = "max77620-pinctrl",
> }, {
> .name = "max77620-gpio",
> .resource = gpio_resources,
> .num_resources = ARRAY_SIZE(gpio_resources),
> }, {
> /* and so on */
> },
> };
Yes. Although, if there are no run-time ordering dependencies, I
usually like to a) have the one line entries on one line i.e.
{ .name = "max77620-pinctrl" }
... and b) for all the one line entries to be grouped together and
the multi line ones grouped together as well.
> >
> >>+ if (x >= tperiod)
> >>+ return i;
> >>+ }
> >>+
> >>+ return i;
> >>+}
> >>+
> >>+static int max77620_config_fps(struct max77620_chip *chip,
> >>+ struct device_node *fps_np)
> >Lots of mention of 'FPS' here, but noting to so what that is?
> >
> >What does FPS stand for and what does the FPS do?
>
> FPS is Flexible Power Sequence. It is explained in DT binding doc.
>
> However, I will document the function to make it more clear in next
> revision.
>
--
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-28 7:25 UTC|newest]
Thread overview: 36+ 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 ` Laxman Dewangan
2016-03-30 14:29 ` [PATCH V10 1/6] mfd: add device-tree binding doc for PMIC max77620/max20024 Laxman Dewangan
2016-03-30 14:29 ` Laxman Dewangan
2016-04-27 12:49 ` Lee Jones
2016-04-27 15:04 ` Thierry Reding
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-03-30 14:29 ` Laxman Dewangan
2016-04-27 15:06 ` Thierry Reding
2016-04-27 15:06 ` Thierry Reding
2016-04-27 15:29 ` Lee Jones
2016-04-27 15:19 ` Lee Jones
2016-04-27 15:19 ` Lee Jones
2016-04-27 18:27 ` Laxman Dewangan
2016-04-27 18:27 ` Laxman Dewangan
2016-04-28 7:25 ` Lee Jones [this message]
2016-04-28 7:18 ` Laxman Dewangan
2016-04-28 7:18 ` Laxman Dewangan
2016-04-28 8:51 ` Lee Jones
2016-04-28 8:51 ` Lee Jones
2016-04-27 18:43 ` Laxman Dewangan
2016-04-27 18:43 ` Laxman Dewangan
2016-04-28 7:23 ` Lee Jones
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 ` 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 ` 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 ` Laxman Dewangan
2016-03-30 14:29 ` [PATCH V10 6/6] gpio: max77620: add gpio driver for MAX77620/MAX20024 Laxman Dewangan
2016-03-30 14:29 ` Laxman Dewangan
2016-04-15 16:57 ` [PATCH V10 0/6] Add support for MAXIM MAX77620/MAX20024 PMIC Laxman Dewangan
2016-04-15 16:57 ` 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=20160428072559.GK4892@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 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.