linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Romain Baeriswyl <romain.baeriswyl@alitech.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Christian Ruppert <christian.ruppert@alitech.com>,
	Anton Vorontsov <cbouatmailru@gmail.com>,
	Rojhalat Ibrahim <imr@rtschenk.de>,
	abdoulaye berthe <berthe.ab@gmail.com>,
	Anthony Fee <anthony.fee@emutex.com>,
	Alexander Shiyan <shc_work@mail.ru>
Subject: Re: [PATCH] added device tree support to gpio-generic driver
Date: Wed, 24 Jun 2015 13:07:57 +0200	[thread overview]
Message-ID: <CAMuHMdUCNQV=9vEmNPHtuwXw3jZ_NWwpJaTb6eBXvYJiDKhGaw@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdbWhtkMgz2qTg1y7AguLQCJXnAoi7gVnFvPb1sR7eES_g@mail.gmail.com>

On Wed, Jun 10, 2015 at 10:42 AM, Linus Walleij
<linus.walleij@linaro.org> wrote:
> On Fri, Jun 5, 2015 at 8:51 AM, Romain Baeriswyl
> <romain.baeriswyl@alitech.com> wrote:
>
>> +Required properties:
>> +- compatible : "basic-mmio-gpio" for little endian register access or
>> +               "basic-mmio-gpio-be" for big endian register access
>
> Basic I don't know.
>
> "single-register-gpio" is more to the point, don't you think?
>
>> +- ngpios: Specifies the number of gpio mapped in the register. The value is
>> +          limited to the number of bits of the LONG type.
>
> So if it is 8 for a 32 bit register, does it mean bits 0..7 little endian or
> big endian, or does it depend on endianness? Clarify this
> in the binding.

LONG can be 64-bit too.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      parent reply	other threads:[~2015-06-24 11:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05  6:51 [PATCH] added device tree support to gpio-generic driver Romain Baeriswyl
2015-06-05  7:17 ` Alexander Shiyan
2015-06-08  4:19 ` Alexandre Courbot
2015-06-08  6:26   ` Romain Baeriswyl
2015-06-08  6:39     ` Alexandre Courbot
2015-06-24  7:42   ` Romain Baeriswyl
2015-06-10  8:42 ` Linus Walleij
2015-06-11 10:32   ` [PATCH V2] " Romain Baeriswyl
2015-06-11 10:42     ` Alexander Shiyan
2015-06-11 11:40       ` Sascha Hauer
2015-06-16  9:15     ` Linus Walleij
2015-06-24  9:54       ` [PATCH V3] " Romain Baeriswyl
2015-06-24 11:55         ` Masahiro Yamada
2015-06-24 11:07   ` Geert Uytterhoeven [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='CAMuHMdUCNQV=9vEmNPHtuwXw3jZ_NWwpJaTb6eBXvYJiDKhGaw@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=anthony.fee@emutex.com \
    --cc=berthe.ab@gmail.com \
    --cc=cbouatmailru@gmail.com \
    --cc=christian.ruppert@alitech.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gnurou@gmail.com \
    --cc=imr@rtschenk.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romain.baeriswyl@alitech.com \
    --cc=shc_work@mail.ru \
    /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).