Good bug hunting in this thread! Please see if you can use libgpiod or the tools from the kernel tools/gpio directory to test GPIO lines, I usually use that since the global GPIO numberspace only constantly confuse me. Especially when there is a really many many GPIOs the local numberspace and the global GPIO numberspace approach the same values and I get totally lost sometimes. Yours, Linus Walleij
Re: pinctrl-icelake: driver writes to wrong offsets?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: pinctrl-icelake: driver writes to wrong offsets?
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Thu, 20 Sep 2018 08:14:14 -0700
- In-reply-to: <CACK8Z6ECjwWqDnaXKrmEbEXzmiX41Sbzys=FSCqMwh8eYLPH9A@mail.gmail.com>
- References: <CACK8Z6ECjwWqDnaXKrmEbEXzmiX41Sbzys=FSCqMwh8eYLPH9A@mail.gmail.com>
- References:
- pinctrl-icelake: driver writes to wrong offsets?
- From: Rajat Jain
- pinctrl-icelake: driver writes to wrong offsets?
- Prev by Date: Re: [PATCH] gpiolib: Show correct direction from the beginning
- Next by Date: Re: [PATCH 1/2] pinctrl: tegra: do not export tegra_pinctrl_probe
- Previous by thread: Re: pinctrl-icelake: driver writes to wrong offsets?
- Next by thread: [PATCH] pinctrl: cannonlake: Fix gpio base for GPP-E
- Index(es):
 |