From: nikita.shubin@maquefel.me
To: Hartley Sweeten <hartleys@visionengravers.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Alexander Sverdlin <alexander.sverdlin@gmail.com>,
"bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>
Subject: Re: RFC Need advice on reworking gpio-ep93xx.c to DT support
Date: Mon, 22 Mar 2021 19:20:04 +0300 [thread overview]
Message-ID: <1095441616429409@mail.yandex.ru> (raw)
In-Reply-To: <BYAPR01MB5621E8956FDBF8F194ABB598D0659@BYAPR01MB5621.prod.exchangelabs.com>
Dear Hartley,
> Are you just going to drop the other GPIO ports?
Of course i am not going to drop anything, i just showed binding for three types of ep93xx ports to shrink letter a bit.
This part is just an example of what i proposing for device tree.
We generally have:
- A/B port that share IRQ
- F port with IRQ for each line
- other ports that have nothing more than direction and data registers
> Note that the GPIO banks are registered a bit goofy, Ports C and F are not in order. They have been that way since the original Cirrus "crater" code base. If I remember correctly this was somewhere back in the 2.6.x kernel. Please make sure the GPIO numbers stay the same so that any userspace code does not break.
Thank you for pointing this out.
prev parent reply other threads:[~2021-03-22 16:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 12:19 RFC Need advice on reworking gpio-ep93xx.c to DT support nikita.shubin
2021-03-22 12:25 ` Linus Walleij
2021-03-22 15:43 ` Hartley Sweeten
2021-03-22 15:59 ` Alexander Sverdlin
2021-03-22 16:14 ` Hartley Sweeten
2021-03-22 16:48 ` nikita.shubin
2021-03-22 17:00 ` Alexander Sverdlin
2021-03-22 22:31 ` Arnd Bergmann
2021-03-23 6:57 ` Alexander Sverdlin
2021-03-23 8:45 ` Arnd Bergmann
2021-05-25 8:44 ` Geert Uytterhoeven
2021-03-23 8:21 ` Linus Walleij
2021-03-22 16:20 ` nikita.shubin [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=1095441616429409@mail.yandex.ru \
--to=nikita.shubin@maquefel.me \
--cc=alexander.sverdlin@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=hartleys@visionengravers.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.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 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.