linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: richardcochran@gmail.com (Richard Cochran)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] gpio: dwapb: Use human understandable gpio numbering.
Date: Thu, 16 Jul 2015 19:19:30 +0200	[thread overview]
Message-ID: <20150716171930.GB27060@localhost.localdomain> (raw)
In-Reply-To: <CACRpkdY+prqSeohT5BEoOKS6sfXdFTA6ZzuKzH4GSPX5jcjgzA@mail.gmail.com>

On Thu, Jul 16, 2015 at 09:50:44AM +0200, Linus Walleij wrote:
> NACK. And it has been NACKed before again and again, search
> the mailinglist for repetitive answers.

Yeah, ok, I give up.

This happens with every DT discussion that tries to make things
logical for the end user.

> The GPIO numbers inside the Linux kernel are Linux specific and
> have nothing to do with the hardware numbers. If they sometimes
> match it is a lucky coincidence.

Someone should tell the users that.

> The same goes for IRQ numbers
> in the kernel FWIW.

Isn't there a mapping interface for irq numbers?
 
> So this "binding" has nothing to do with describing the hardware,
> which device tree is for. If it ever comes to exist it needs to be
> a "linux-*" property. But I doubt it will.

How can you say that the GPIO numbers associated with the pins and
appearing in published data sheets (and used in every schematic) are
not part of the hardware?

Thanks,
Richard

  parent reply	other threads:[~2015-07-16 17:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 19:34 [PATCH 0/2] gpio: dwapb: allow sane gpio numbering Richard Cochran
2015-07-01 19:34 ` [PATCH 1/2] gpio: dwapb: Use human understandable " Richard Cochran
2015-07-02  7:05   ` Michael van der Westhuizen
2015-07-02 14:20     ` Richard Cochran
2015-07-16  7:57       ` Linus Walleij
2015-07-16  8:18         ` Michael van der Westhuizen
2015-07-16 18:19         ` Richard Cochran
2015-07-03  9:13     ` Richard Cochran
2015-07-03  9:18       ` Michael van der Westhuizen
2015-07-03 10:36         ` Richard Cochran
2015-07-03 10:55           ` Russell King - ARM Linux
2015-07-16  7:52     ` Linus Walleij
2015-07-16  8:16       ` Michael van der Westhuizen
2015-07-02  7:36   ` Sebastian Andrzej Siewior
2015-07-02 14:26     ` Richard Cochran
2015-07-02 14:30       ` Sebastian Andrzej Siewior
2015-07-02 15:21         ` Richard Cochran
2015-07-02 15:54           ` Sebastian Andrzej Siewior
2015-07-02 16:02             ` Michael van der Westhuizen
2015-07-03 13:30               ` Michael van der Westhuizen
2015-07-16  7:50   ` Linus Walleij
2015-07-16 17:10     ` Richard Cochran
2015-07-16 17:19     ` Richard Cochran [this message]
2015-07-27 10:19       ` Linus Walleij
2015-07-27 11:28         ` Richard Cochran
2015-07-27 12:26         ` Sebastian Andrzej Siewior
2015-07-01 19:34 ` [PATCH 2/2] arm: dts: socfpga: Provide the gpio numbers in the controller nodes Richard Cochran

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=20150716171930.GB27060@localhost.localdomain \
    --to=richardcochran@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;
as well as URLs for NNTP newsgroup(s).