All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrew F. Davis" <afd@ti.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/5] Documentation: tps65912: Add DT bindings for the TPS65912 PMIC
Date: Fri, 30 Oct 2015 14:21:02 -0500	[thread overview]
Message-ID: <5633C31E.5030408@ti.com> (raw)
In-Reply-To: <20151030190622.GN4058@x1>

On 10/30/2015 02:06 PM, Lee Jones wrote:
> On Fri, 30 Oct 2015, Andrew F. Davis wrote:
>
>> On 10/30/2015 12:10 PM, Lee Jones wrote:
>>> On Thu, 29 Oct 2015, Andrew F. Davis wrote:
>>>
>>>> The TPS65912 PMIC contains several regulators and a GPIO controller.
>>>> Add bindings for the TPS65912 PMIC.
>>>>
>>>> Signed-off-by: Andrew F. Davis <afd@ti.com>
>>>> ---
>>>>   .../devicetree/bindings/gpio/gpio-tps65912.txt     | 16 +++++++
>>>
>>> Why have you dropped Linus' Review-by?
>>>
>>
>> Strange, I thought I made a change to this. Well this brings up a question,
>> how much change can we have before we are supposed to drop Reviewed/Acked-by?
>
> Common sense call I'm afraid. ;)
>
> [...]
>
>>>> +     the second cell is used to specify flags.
>>>> +     See include/dt-bindings/gpio/gpio.h for possible values.
>>>
>>> This is a Linuxisum and shouldn't really live in here.
>>>
>>> I think it would be better to document them in ../gpio/gpio.txt and
>>> reference that instead.
>>>
>>
>> Looks like that is already in ../gpio/gpio.txt:57
>
> There is a mention of GPIO_ACTIVE_HIGH, as it's used in an example.
> However GPIO_ACTIVE_LOW is missing.  I think both could do with
> documenting properly, then you can refer to them from here.
>

I mean the lines above the example, they say to use the macros
defined in include/dt-bindings/gpio/gpio.h whenever possible,
that's really all I would say.

> [...]
>
>>>> +Required properties:
>>>> + - compatible : Should be "ti,tps65912".
>>>> + - reg : Slave address or chip select number (I2C / SPI).
>>>> + - interrupt-parent : The parent interrupt controller.
>>>> + - interrupts : The interrupt line the device is connected to.
>>>> + - interrupt-controller : Marks the device node as an interrupt controller.
>>>> + - #interrupt-cells: The number of cells to describe an IRQ, this should be 2.
>>>> +     The first cell is the IRQ number.
>>>> +     The second cell is the flags, encoded as the trigger masks from
>>>> +     ../interrupt-controller/interrupts.txt
>>>
>>> Nit: We *normally* treat these as bullet-points and not place
>>> full-stops on them:
>>>
>>> $ git grep "compatible" -- Documentation/devicetree/bindings/ | grep -v "\.$" | wc -l
>>> 5227
>>> $ git grep "compatible.*\.$" -- Documentation/devicetree/bindings/ | wc -l
>>> 486
>>>
>>
>> What about for multi-sentence descriptions, we need the middle full-stops, then to not
>> have one on the end seems kinda odd looking.
>
> That's the way I usually do it -- doesn't look too bad. ;)
>
> [...]
>

WARNING: multiple messages have this Message-ID (diff)
From: "Andrew F. Davis" <afd@ti.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, <devicetree@vger.kernel.org>,
	<linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 1/5] Documentation: tps65912: Add DT bindings for the TPS65912 PMIC
Date: Fri, 30 Oct 2015 14:21:02 -0500	[thread overview]
Message-ID: <5633C31E.5030408@ti.com> (raw)
In-Reply-To: <20151030190622.GN4058@x1>

On 10/30/2015 02:06 PM, Lee Jones wrote:
> On Fri, 30 Oct 2015, Andrew F. Davis wrote:
>
>> On 10/30/2015 12:10 PM, Lee Jones wrote:
>>> On Thu, 29 Oct 2015, Andrew F. Davis wrote:
>>>
>>>> The TPS65912 PMIC contains several regulators and a GPIO controller.
>>>> Add bindings for the TPS65912 PMIC.
>>>>
>>>> Signed-off-by: Andrew F. Davis <afd@ti.com>
>>>> ---
>>>>   .../devicetree/bindings/gpio/gpio-tps65912.txt     | 16 +++++++
>>>
>>> Why have you dropped Linus' Review-by?
>>>
>>
>> Strange, I thought I made a change to this. Well this brings up a question,
>> how much change can we have before we are supposed to drop Reviewed/Acked-by?
>
> Common sense call I'm afraid. ;)
>
> [...]
>
>>>> +     the second cell is used to specify flags.
>>>> +     See include/dt-bindings/gpio/gpio.h for possible values.
>>>
>>> This is a Linuxisum and shouldn't really live in here.
>>>
>>> I think it would be better to document them in ../gpio/gpio.txt and
>>> reference that instead.
>>>
>>
>> Looks like that is already in ../gpio/gpio.txt:57
>
> There is a mention of GPIO_ACTIVE_HIGH, as it's used in an example.
> However GPIO_ACTIVE_LOW is missing.  I think both could do with
> documenting properly, then you can refer to them from here.
>

I mean the lines above the example, they say to use the macros
defined in include/dt-bindings/gpio/gpio.h whenever possible,
that's really all I would say.

> [...]
>
>>>> +Required properties:
>>>> + - compatible : Should be "ti,tps65912".
>>>> + - reg : Slave address or chip select number (I2C / SPI).
>>>> + - interrupt-parent : The parent interrupt controller.
>>>> + - interrupts : The interrupt line the device is connected to.
>>>> + - interrupt-controller : Marks the device node as an interrupt controller.
>>>> + - #interrupt-cells: The number of cells to describe an IRQ, this should be 2.
>>>> +     The first cell is the IRQ number.
>>>> +     The second cell is the flags, encoded as the trigger masks from
>>>> +     ../interrupt-controller/interrupts.txt
>>>
>>> Nit: We *normally* treat these as bullet-points and not place
>>> full-stops on them:
>>>
>>> $ git grep "compatible" -- Documentation/devicetree/bindings/ | grep -v "\.$" | wc -l
>>> 5227
>>> $ git grep "compatible.*\.$" -- Documentation/devicetree/bindings/ | wc -l
>>> 486
>>>
>>
>> What about for multi-sentence descriptions, we need the middle full-stops, then to not
>> have one on the end seems kinda odd looking.
>
> That's the way I usually do it -- doesn't look too bad. ;)
>
> [...]
>

  reply	other threads:[~2015-10-30 19:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 23:38 [PATCH v5 0/5] mfd: tps65912: Driver rewrite with DT support Andrew F. Davis
2015-10-29 23:38 ` Andrew F. Davis
2015-10-29 23:38 ` [PATCH v5 1/5] Documentation: tps65912: Add DT bindings for the TPS65912 PMIC Andrew F. Davis
2015-10-29 23:38   ` Andrew F. Davis
2015-10-30 17:10   ` Lee Jones
2015-10-30 18:01     ` Andrew F. Davis
2015-10-30 18:01       ` Andrew F. Davis
2015-10-30 19:06       ` Lee Jones
2015-10-30 19:21         ` Andrew F. Davis [this message]
2015-10-30 19:21           ` Andrew F. Davis
2015-11-02  9:17           ` Lee Jones
2015-11-02  9:17             ` Lee Jones
2015-11-02 15:15             ` Andrew F. Davis
2015-11-02 15:15               ` Andrew F. Davis
2015-10-29 23:38 ` [PATCH v5 2/5] mfd: tps65912: Remove old driver in preparation for new driver Andrew F. Davis
2015-10-29 23:38   ` Andrew F. Davis
2015-10-29 23:38 ` [PATCH v5 3/5] mfd: tps65912: Add driver for the TPS65912 PMIC Andrew F. Davis
2015-10-29 23:38   ` Andrew F. Davis
2015-10-30 16:55   ` Lee Jones
2015-10-29 23:38 ` [PATCH v5 4/5] regulator: tps65912: Add regulator " Andrew F. Davis
2015-10-29 23:38   ` Andrew F. Davis
2015-10-29 23:38 ` [PATCH v5 5/5] gpio: tps65912: Add GPIO " Andrew F. Davis
2015-10-29 23:38   ` Andrew F. Davis
2015-10-30 14:13   ` Linus Walleij
     [not found]     ` <CACRpkdb+C1M=cFKDNbJW74hUEA=87aA_weR0u22-9bDKgif6xQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-30 17:10       ` Lee Jones
2015-10-30 17:10         ` Lee Jones

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=5633C31E.5030408@ti.com \
    --to=afd@ti.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=gnurou@gmail.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sameo@linux.intel.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.