linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "nikita.shubin@maquefel.me" <nikita.shubin@maquefel.me>
To: Hartley Sweeten <hartleys@visionengravers.com>,
	Alexander Sverdlin <alexander.sverdlin@gmail.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	"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:48:47 +0300	[thread overview]
Message-ID: <36281616430257@mail.yandex.ru> (raw)
In-Reply-To: BYAPR01MB5621066B411F68EF840B8417D0659@BYAPR01MB5621.prod.exchangelabs.com

Dear Alexander and Hartley.

22.03.2021, 19:14, "Hartley Sweeten" <hartleys@visionengravers.com>:
> On Monday, March 22, 2021 9:00 AM, Alexander Sverdlin wrote:
>>  On Mon, 2021-03-22 at 15:43 +0000, Hartley Sweeten wrote:
>>>  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.
>
>>  I'm sceptical about this DT convertion.
>
> I'm in the same boat. One of the reasons I have not tried to convert it...

I find this a bit confusing, so you think ep93xx shouldn't be touched at all ?

AFAIK the question is reworking to DT or it will be dropped eventually:

https://lore.kernel.org/lkml/CAK8P3a2VW8T+yYUG1pn1yR-5eU4jJXe1+M_ot6DAvfr2KyXCzQ@mail.gmail.com/



  reply	other threads:[~2021-03-22 16:49 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 [this message]
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

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=36281616430257@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 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).