public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: chauveau.julien@gmail.com (Julien Chauveau)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] Documentation: devicetree: Clean up gpio-keys example
Date: Fri, 11 Mar 2016 00:08:56 +0100	[thread overview]
Message-ID: <A62AD22E-ECB3-4DC7-8156-22BC84795412@gmail.com> (raw)
In-Reply-To: <56DEA4D6.10008@suse.de>


> Le 8 mars 2016 ? 11:09, Andreas F?rber <afaerber@suse.de> a ?crit :
> 
> Am 08.03.2016 um 09:54 schrieb Geert Uytterhoeven:
>> On Mon, Mar 7, 2016 at 7:24 PM, Andreas F?rber <afaerber@suse.de> wrote:
>>> Drop #address-cells and #size-cells, which are not required by the
>>> gpio-keys binding documentation, as button sub-nodes are not devices.
>>> 
>>> Reported-by: Julien Chauveau <chauveau.julien@gmail.com>
>>> Signed-off-by: Andreas F?rber <afaerber@suse.de>
>>> ---
>>> Documentation/devicetree/bindings/input/gpio-keys.txt | 2 --
>>> 1 file changed, 2 deletions(-)
>>> 
>>> diff --git a/Documentation/devicetree/bindings/input/gpio-keys.txt b/Documentation/devicetree/bindings/input/gpio-keys.txt
>>> index 21641236c095..1552a11f6786 100644
>>> --- a/Documentation/devicetree/bindings/input/gpio-keys.txt
>>> +++ b/Documentation/devicetree/bindings/input/gpio-keys.txt
>>> @@ -34,8 +34,6 @@ Example nodes:
>>> 
>>>        gpio_keys {
> 
> While at it, I was told the preferred node naming would be dashes, not
> underscores. The deeper we dig, the more we find.

I agree, here we should use dashes, not underscores. So "gpio-keys" instead of "gpio_keys".

> 
>>>                        compatible = "gpio-keys";
>>> -                       #address-cells = <1>;
>>> -                       #size-cells = <0>;
>>>                        autorepeat;
> 
> Also a white line here may be optically more pleasant.

I agree.

> 
>>>                        button at 21 {
>> 
>> FYI, with "[PATCH] scripts/dtc: Update to upstream version 53bf130b1cdd":
>> (http://www.spinics.net/lists/devicetree/msg117206.html) applied:
>> 
>> Warning (unit_address_vs_reg): Node /keyboard/button at 21 has a unit
>> name, but no reg property
> 
> My v2 GeekBox patch did have *-cells and a reg property, but Julien
> asked I drop that: https://patchwork.kernel.org/patch/8246481/
> 
> Are you suggesting we should add a reg property here and drop this patch
> or go with this patch but follow up to not use @21?

I may be wrong but I think that if the unit-address has no meaning and is not used, then it should be removed.

By the way, I think the warning message is wrong. It should be _address_ instead of name: "Node has a unit address, but no reg property".

Julien

      reply	other threads:[~2016-03-10 23:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07 18:24 [PATCH RESEND] Documentation: devicetree: Clean up gpio-keys example Andreas Färber
2016-03-07 18:34 ` Javier Martinez Canillas
2016-03-07 19:25   ` Andreas Färber
2016-03-08  8:54 ` Geert Uytterhoeven
2016-03-08  9:41   ` Julien Chauveau
2016-03-08 10:16     ` Andreas Färber
2016-03-10 23:08       ` Julien Chauveau
2016-03-08 10:09   ` Andreas Färber
2016-03-10 23:08     ` Julien Chauveau [this message]

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=A62AD22E-ECB3-4DC7-8156-22BC84795412@gmail.com \
    --to=chauveau.julien@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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