public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: andy.shevchenko@gmail.com
To: "xingtong.wu" <xingtong_wu@163.com>
Cc: andy.shevchenko@gmail.com, simon.guinot@sequanux.org,
	Linus Walleij <linus.walleij@linaro.org>,
	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: Tue, 30 May 2023 13:53:47 +0300	[thread overview]
Message-ID: <ZHXVu-oARZKVOyzm@surfacebook> (raw)
In-Reply-To: <5428dcc3-bcaf-2fff-59db-62d3b3b45d17@163.com>

Tue, May 30, 2023 at 02:27:09PM +0800, xingtong.wu kirjoitti:
> On 2023/5/30 06:24, andy.shevchenko@gmail.com wrote:
> > Mon, May 29, 2023 at 03:54:36PM +0200, simon.guinot@sequanux.org kirjoitti:
> >> 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.
> >>
> >> 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).
> > 
> > What you want is against the architecture. To fix this, you might change
> > the architecture of the driver to have one chip for the controller, but
> > it's quite questionable change. Also how can you guarantee ordering of
> > the enumeration? You probably need to *disable* SMP on the boot time.
> > This will still be fragile as long as GPIO chip can be unbound at run
> > time. Order can be changed.
> > 
> > So, the patch is good and the correct way to go.
> > 
> > P.S. The root cause is that hardware engineers and documentation writers
> > do not consider their hardware in the multi-tasking, multi-user general
> > purpose operating system, such as Linux. I believe the ideal fix is to fix the
> > documentation (datasheet).
> 
> Thanks for your review.
> 
> The direct reason of this patch is that when "modprobe gpio-f7188x",
> it conflicts with INT34C6. I met this issue on an older kernel, but
> could not remember which version exactly.

This is interesting. But what I have noticed the v6.3.2 missing this
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpio/gpiolib.c?id=7dd3d9bd873f138675cb727eaa51a498d99f0e89
change. Can you apply and retest?

If this does not help, please share more details, exact steps of reproducing
the issue, including respective `dmesg` output, etc. (maybe via creating a
kernel bugzilla report).

> The error message is as the link below:
> https://elixir.bootlin.com/linux/v6.3.2/source/drivers/gpio/gpiolib.c#L798

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-05-30 10:53 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
2023-05-29 22:24         ` andy.shevchenko
2023-05-30  6:27           ` xingtong.wu
2023-05-30 10:53             ` andy.shevchenko [this message]
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=ZHXVu-oARZKVOyzm@surfacebook \
    --to=andy.shevchenko@gmail.com \
    --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=simon.guinot@sequanux.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