From: simon.guinot@sequanux.org
To: Linus Walleij <linus.walleij@linaro.org>
Cc: xingtong_wu@163.com, brgl@bgdev.pl, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, henning.schild@siemens.com,
xingtong.wu@siemens.com
Subject: Re: [PATCH v2 1/1] gpio-f7188x: fix base values conflicts with other gpio pins
Date: Mon, 29 May 2023 15:54:36 +0200 [thread overview]
Message-ID: <ZHSunJyh2AU1eb0H@localhost> (raw)
In-Reply-To: <CACRpkdbiRsJqxVZPNLvLPK-MzEhyjSBGffuaTgP7tt40pGGoRw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On Mon, May 29, 2023 at 03:03:28PM +0200, Linus Walleij wrote:
> On Mon, May 29, 2023 at 2:27 PM <simon.guinot@sequanux.org> wrote:
>
> > It would be nice if a pin number found in the device datasheet could
> > still be converted into a Linux GPIO number by adding the base of the
> > first bank.
>
> We actively discourage this kind of mapping because of reasons stated
> in drivers/gpio/TODO: we want dynamic number allocation to be the
> norm.
Hi Linus,
Sure but it would be nice to have a dynamic base applied to a controller
(and not to each chip of this controller), and to respect the interval
between the chips (as stated in the controllers datasheets).
This way the assignation would be dynamic and the pin numbers found in
controller datasheet would be meaningful as well.
Simon
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-29 13:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 2:50 [PATCH v2 0/1] gpio-f7188x: fix base values conflicts with other gpio pins xingtong_wu
2023-05-29 2:50 ` [PATCH v2 1/1] " xingtong_wu
2023-05-29 12:26 ` simon.guinot
2023-05-29 13:03 ` Linus Walleij
2023-05-29 13:54 ` simon.guinot [this message]
2023-05-29 22:24 ` andy.shevchenko
2023-05-30 6:27 ` xingtong.wu
2023-05-30 10:53 ` andy.shevchenko
2023-05-30 11:10 ` andy.shevchenko
2023-05-30 17:53 ` simon.guinot
2023-05-30 21:42 ` Andy Shevchenko
2023-05-30 10:57 ` Henning Schild
2023-05-30 17:57 ` simon.guinot
2023-05-30 11:40 ` Linus Walleij
2023-05-29 13:02 ` Linus Walleij
2023-03-02 13:48 ` xingtong.wu
2023-06-16 7:53 ` Henning Schild
2023-08-31 7:28 ` xingtong.wu
2023-09-01 9:10 ` Bartosz Golaszewski
2023-09-11 7:04 ` Bartosz Golaszewski
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=ZHSunJyh2AU1eb0H@localhost \
--to=simon.guinot@sequanux.org \
--cc=brgl@bgdev.pl \
--cc=henning.schild@siemens.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xingtong.wu@siemens.com \
--cc=xingtong_wu@163.com \
/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).