From: Linus Walleij <linus.walleij@linaro.org> To: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>, Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Cc: Simon Guinot <simon.guinot@sequanux.org>, Thomas Petazzoni <thomas.petazzoni@free-electrons.com>, Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>, Gregory Clement <gregory.clement@free-electrons.com> Subject: Strange message from Kirkwood pinctrl driver Date: Wed, 25 Nov 2015 11:27:46 +0100 [thread overview] Message-ID: <CACRpkdah4w-=qHS+q_=Ab-RiJyvbCKY-Rp5Ya0x+F=3DL2iuBA@mail.gmail.com> (raw) Hi Sebastian, trying to use the Kirkwood pinctrl driver with compatible = "marvell,88f6192-pinctrl"; on a Pogoplug series 4 yields the following message when instantiating the driver: kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 36 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 37 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 38 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 39 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 40 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 41 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 42 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 43 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 44 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 45 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 46 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 47 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 48 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 49 kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver It looks harmless but seems like a bug and make me uncertain. The following naive patch fixes it: diff --git a/drivers/pinctrl/mvebu/pinctrl-kirkwood.c b/drivers/pinctrl/mvebu/pinctrl-kirkwood.c index 0f07dc554a1d..6c7c2c8819b8 100644 --- a/drivers/pinctrl/mvebu/pinctrl-kirkwood.c +++ b/drivers/pinctrl/mvebu/pinctrl-kirkwood.c @@ -411,7 +411,7 @@ static struct mvebu_pinctrl_soc_info mv88f6190_info = { .controls = mv88f619x_mpp_controls, .ncontrols = ARRAY_SIZE(mv88f619x_mpp_controls), .modes = mv88f6xxx_mpp_modes, - .nmodes = ARRAY_SIZE(mv88f6xxx_mpp_modes), + .nmodes = ARRAY_SIZE(mv88f6xxx_mpp_modes) - 14, .gpioranges = mv88f619x_gpio_ranges, .ngpioranges = ARRAY_SIZE(mv88f619x_gpio_ranges), }; @@ -421,7 +421,7 @@ static struct mvebu_pinctrl_soc_info mv88f6192_info = { .controls = mv88f619x_mpp_controls, .ncontrols = ARRAY_SIZE(mv88f619x_mpp_controls), .modes = mv88f6xxx_mpp_modes, - .nmodes = ARRAY_SIZE(mv88f6xxx_mpp_modes), + .nmodes = ARRAY_SIZE(mv88f6xxx_mpp_modes) - 14, .gpioranges = mv88f619x_gpio_ranges, .ngpioranges = ARRAY_SIZE(mv88f619x_gpio_ranges), }; What is the proper way to fix this? Yours, Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij) To: linux-arm-kernel@lists.infradead.org Subject: Strange message from Kirkwood pinctrl driver Date: Wed, 25 Nov 2015 11:27:46 +0100 [thread overview] Message-ID: <CACRpkdah4w-=qHS+q_=Ab-RiJyvbCKY-Rp5Ya0x+F=3DL2iuBA@mail.gmail.com> (raw) Hi Sebastian, trying to use the Kirkwood pinctrl driver with compatible = "marvell,88f6192-pinctrl"; on a Pogoplug series 4 yields the following message when instantiating the driver: kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 36 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 37 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 38 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 39 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 40 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 41 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 42 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 43 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 44 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 45 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 46 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 47 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 48 kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 49 kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver It looks harmless but seems like a bug and make me uncertain. The following naive patch fixes it: diff --git a/drivers/pinctrl/mvebu/pinctrl-kirkwood.c b/drivers/pinctrl/mvebu/pinctrl-kirkwood.c index 0f07dc554a1d..6c7c2c8819b8 100644 --- a/drivers/pinctrl/mvebu/pinctrl-kirkwood.c +++ b/drivers/pinctrl/mvebu/pinctrl-kirkwood.c @@ -411,7 +411,7 @@ static struct mvebu_pinctrl_soc_info mv88f6190_info = { .controls = mv88f619x_mpp_controls, .ncontrols = ARRAY_SIZE(mv88f619x_mpp_controls), .modes = mv88f6xxx_mpp_modes, - .nmodes = ARRAY_SIZE(mv88f6xxx_mpp_modes), + .nmodes = ARRAY_SIZE(mv88f6xxx_mpp_modes) - 14, .gpioranges = mv88f619x_gpio_ranges, .ngpioranges = ARRAY_SIZE(mv88f619x_gpio_ranges), }; @@ -421,7 +421,7 @@ static struct mvebu_pinctrl_soc_info mv88f6192_info = { .controls = mv88f619x_mpp_controls, .ncontrols = ARRAY_SIZE(mv88f619x_mpp_controls), .modes = mv88f6xxx_mpp_modes, - .nmodes = ARRAY_SIZE(mv88f6xxx_mpp_modes), + .nmodes = ARRAY_SIZE(mv88f6xxx_mpp_modes) - 14, .gpioranges = mv88f619x_gpio_ranges, .ngpioranges = ARRAY_SIZE(mv88f619x_gpio_ranges), }; What is the proper way to fix this? Yours, Linus Walleij
next reply other threads:[~2015-11-25 10:27 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-11-25 10:27 Linus Walleij [this message] 2015-11-25 10:27 ` Strange message from Kirkwood pinctrl driver Linus Walleij 2015-11-25 14:46 ` Andrew Lunn 2015-11-25 14:46 ` Andrew Lunn 2015-11-25 14:55 ` Linus Walleij 2015-11-25 14:55 ` Linus Walleij 2015-11-25 15:24 ` Simon Guinot 2015-11-25 15:24 ` Simon Guinot 2015-11-26 13:33 ` Sebastian Hesselbarth 2015-11-26 13:33 ` Sebastian Hesselbarth
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='CACRpkdah4w-=qHS+q_=Ab-RiJyvbCKY-Rp5Ya0x+F=3DL2iuBA@mail.gmail.com' \ --to=linus.walleij@linaro.org \ --cc=andrew@lunn.ch \ --cc=gregory.clement@free-electrons.com \ --cc=jason@lakedaemon.net \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-gpio@vger.kernel.org \ --cc=sebastian.hesselbarth@gmail.com \ --cc=simon.guinot@sequanux.org \ --cc=thomas.petazzoni@free-electrons.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.