devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Lee Jones <lee.jones@linaro.org>
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 12:48:58 +0530	[thread overview]
Message-ID: <5721B962.4090503@nvidia.com> (raw)
In-Reply-To: <20160428072559.GK4892@dell>


On Thursday 28 April 2016 12:55 PM, Lee Jones wrote:
> 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.
>


It is turning like as follows:

static const struct mfd_cell max77620_children[] = {
         { .name = "max77620-pinctrl", },
         { .name = "max77620-clock", },
         { .name = "max77620-pmic", },
         { .name = "max77620-watchdog", },
         {
                 .name = "max77620-gpio",
                 .resources = gpio_resources,
                 .num_resources = ARRAY_SIZE(gpio_resources),
         }, {
                 .name = "max77620-rtc",
                 .resources = rtc_resources,
                 .num_resources = ARRAY_SIZE(rtc_resources),
         }, {
                 .name = "max77620-power",
                 .resources = power_resources,
                 .num_resources = ARRAY_SIZE(power_resources),
         }, {
                 .name = "max77620-thermal",
                 .resources = thermal_resources,
                 .num_resources = ARRAY_SIZE(thermal_resources),
         },
};



Will it be fine?

  reply	other threads:[~2016-04-28  7:18 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
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 [this message]
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=5721B962.4090503@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gnurou@gmail.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=lee.jones@linaro.org \
    --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).