From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Rich Felker <dalias@libc.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] sh: sh7722/sh7757i/sh7264/sh7269: Fix pinctrl registration
Date: Mon, 14 Aug 2017 14:53:53 +0200 [thread overview]
Message-ID: <CAMuHMdUQJ38mtsrgY2HJ83RsnCtWRB6dCU=d5RfA3Eq1Q_oQfA@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdXMA7Ux2yiYUrPMGKKJ2AxTLwHOYbnKQHYRwjaSY5+Z7w@mail.gmail.com>
On Fri, Jun 30, 2017 at 10:10 AM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> On Thu, May 11, 2017 at 10:03 AM, Geert Uytterhoeven
> <geert+renesas@glider.be> wrote:
>> Magnus reported that on sh7722/Migo-R, pinctrl registration fails with:
>>
>> sh-pfc pfc-sh7722: pin 0 already registered
>> sh-pfc pfc-sh7722: error during pin registration
>> sh-pfc pfc-sh7722: could not register: -22
>> sh-pfc: probe of pfc-sh7722 failed with error -22
>>
>> pinmux_pins[] is initialized through PINMUX_GPIO(), using designated
>> array initializers, where the GPIO_* enums serve as indices.
>> Apparently GPIO_PTQ7 was defined in the enum, but never used.
>> If enum values are defined, but never used, pinmux_pins[] contains
>> (zero-filled) holes. Hence such entries are treated as pin zero, which
>> was registered before, and pinctrl registration fails.
>>
>> I can't see how this ever worked, as at the time of commit f5e25ae52feff2dc
>> ("sh-pfc: Add sh7722 pinmux support"), pinmux_gpios[] in
>> drivers/pinctrl/sh-pfc/pfc-sh7722.c already had the hole, and
>> drivers/pinctrl/core.c already had the check.
>>
>> Some scripting revealed a few more broken drivers:
>> - sh7757 has four holes, due to nonexistent GPIO_PT[JLNQ]7_RESV.
>> - sh7264 and sh7269 define GPIO_PH[0-7], but don't use it with
>> PINMUX_GPIO().
>>
>> Patch 1 fixes the issue on sh7722, and was tested.
>> Patches 3-4 should fix the issue on the other 3 SoCs, but was untested due
>> to lack of hardware.
>>
>> Changes compared to v1:
>> - Replace fake error messages by references to sh7722,
>> - Add Reviewed-by, Tested-by.
>>
>> Thanks for applying!
>>
>> Geert Uytterhoeven (4):
>> sh: sh7722: Remove nonexistent GPIO_PTQ7 to fix pinctrl registration
>> sh: sh7757: Remove nonexistent GPIO_PT[JLNQ]7_RESV to fix pinctrl
>> registration
>> sh: sh7264: Remove nonexistent GPIO_PH[0-7] to fix pinctrl
>> registration
>> sh: sh7269: Remove nonexistent GPIO_PH[0-7] to fix pinctrl
>> registration
>>
>> arch/sh/include/cpu-sh2a/cpu/sh7264.h | 4 +---
>> arch/sh/include/cpu-sh2a/cpu/sh7269.h | 4 +---
>> arch/sh/include/cpu-sh4/cpu/sh7722.h | 2 +-
>> arch/sh/include/cpu-sh4/cpu/sh7757.h | 8 ++++----
>> 4 files changed, 7 insertions(+), 11 deletions(-)
>
> Are these patches planned for inclusion in v4.13?
> I don't see them in next-2016.
In v4.14, perhaps?
I don't see them in next-20170811...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2017-08-14 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 8:03 [PATCH v2 0/4] sh: sh7722/sh7757i/sh7264/sh7269: Fix pinctrl registration Geert Uytterhoeven
2017-05-11 8:03 ` [PATCH v2 1/4] sh: sh7722: Remove nonexistent GPIO_PTQ7 to fix " Geert Uytterhoeven
2017-05-11 8:03 ` [PATCH v2 2/4] sh: sh7757: Remove nonexistent GPIO_PT[JLNQ]7_RESV " Geert Uytterhoeven
2017-05-11 8:03 ` [PATCH v2 3/4] sh: sh7264: Remove nonexistent GPIO_PH[0-7] " Geert Uytterhoeven
2017-05-11 8:03 ` [PATCH v2 4/4] sh: sh7269: " Geert Uytterhoeven
2017-06-30 8:10 ` [PATCH v2 0/4] sh: sh7722/sh7757i/sh7264/sh7269: Fix " Geert Uytterhoeven
2017-08-14 12:53 ` Geert Uytterhoeven [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='CAMuHMdUQJ38mtsrgY2HJ83RsnCtWRB6dCU=d5RfA3Eq1Q_oQfA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=dalias@libc.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
--cc=ysato@users.sourceforge.jp \
/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).