From: Bartosz Golaszewski <brgl@bgdev.pl> To: Sekhar Nori <nsekhar@ti.com>, Kevin Hilman <khilman@kernel.org>, Russell King <linux@armlinux.org.uk>, Keerthy <j-keerthy@ti.com>, Linus Walleij <linus.walleij@linaro.org>, Grygorii Strashko <grygorii.strashko@ti.com> Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org, Bartosz Golaszewski <bgolaszewski@baylibre.com>, stable@vger.kernel.org Subject: [PATCH 09/12] ARM: davinci: dm646x: set the GPIO base to 0 Date: Wed, 21 Nov 2018 10:35:20 +0100 [thread overview] Message-ID: <20181121093523.12503-10-brgl@bgdev.pl> (raw) In-Reply-To: <20181121093523.12503-1-brgl@bgdev.pl> From: Bartosz Golaszewski <bgolaszewski@baylibre.com> Commit 587f7a694f01 ("gpio: davinci: Use dev name for label and automatic base selection") broke the GPIO support on DaVinci boards in legacy mode by allowing gpiolib to set the GPIO base automatically. DaVinci board files use the legacy GPIO API with hard-coded GPIO line numbers. Use the new fields in struct davinci_gpio_platform_data to manually set the GPIO base to 0. Fixes: 587f7a694f01 ("gpio: davinci: Use dev name for label and automatic base selection") Cc: stable@vger.kernel.org Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com> --- arch/arm/mach-davinci/dm646x.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/mach-davinci/dm646x.c b/arch/arm/mach-davinci/dm646x.c index d9b93e2806d2..7dc54b2a610f 100644 --- a/arch/arm/mach-davinci/dm646x.c +++ b/arch/arm/mach-davinci/dm646x.c @@ -458,6 +458,8 @@ static struct resource dm646x_gpio_resources[] = { }; static struct davinci_gpio_platform_data dm646x_gpio_platform_data = { + .no_auto_base = true, + .base = 0, .ngpio = 43, }; -- 2.19.1
WARNING: multiple messages have this Message-ID (diff)
From: brgl@bgdev.pl (Bartosz Golaszewski) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 09/12] ARM: davinci: dm646x: set the GPIO base to 0 Date: Wed, 21 Nov 2018 10:35:20 +0100 [thread overview] Message-ID: <20181121093523.12503-10-brgl@bgdev.pl> (raw) In-Reply-To: <20181121093523.12503-1-brgl@bgdev.pl> From: Bartosz Golaszewski <bgolaszewski@baylibre.com> Commit 587f7a694f01 ("gpio: davinci: Use dev name for label and automatic base selection") broke the GPIO support on DaVinci boards in legacy mode by allowing gpiolib to set the GPIO base automatically. DaVinci board files use the legacy GPIO API with hard-coded GPIO line numbers. Use the new fields in struct davinci_gpio_platform_data to manually set the GPIO base to 0. Fixes: 587f7a694f01 ("gpio: davinci: Use dev name for label and automatic base selection") Cc: stable at vger.kernel.org Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com> --- arch/arm/mach-davinci/dm646x.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/mach-davinci/dm646x.c b/arch/arm/mach-davinci/dm646x.c index d9b93e2806d2..7dc54b2a610f 100644 --- a/arch/arm/mach-davinci/dm646x.c +++ b/arch/arm/mach-davinci/dm646x.c @@ -458,6 +458,8 @@ static struct resource dm646x_gpio_resources[] = { }; static struct davinci_gpio_platform_data dm646x_gpio_platform_data = { + .no_auto_base = true, + .base = 0, .ngpio = 43, }; -- 2.19.1
next prev parent reply other threads:[~2018-11-21 9:35 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-11-21 9:35 [PATCH 00/12] ARM: davinci: fix GPIO breakage after v4.19 Bartosz Golaszewski 2018-11-21 9:35 ` Bartosz Golaszewski 2018-11-21 9:35 ` [PATCH 01/12] ARM: davinci: da8xx: define gpio interrupts as separate resources Bartosz Golaszewski 2018-11-21 9:35 ` Bartosz Golaszewski 2018-11-21 9:35 ` [PATCH 02/12] ARM: davinci: dm365: " Bartosz Golaszewski 2018-11-21 9:35 ` Bartosz Golaszewski 2018-11-21 9:35 ` Bartosz Golaszewski 2018-11-21 9:35 ` [PATCH 03/12] ARM: davinci: dm646x: " Bartosz Golaszewski 2018-11-21 9:35 ` Bartosz Golaszewski 2018-11-21 9:35 ` [PATCH 04/12] ARM: davinci: dm355: " Bartosz Golaszewski 2018-11-21 9:35 ` Bartosz Golaszewski 2018-11-21 9:35 ` [PATCH 05/12] ARM: davinci: dm644x: " Bartosz Golaszewski 2018-11-21 9:35 ` Bartosz Golaszewski 2018-11-21 9:35 ` [PATCH 06/12] gpio: davinci: restore a way to manually specify the GPIO base Bartosz Golaszewski 2018-11-21 9:35 ` Bartosz Golaszewski 2018-11-21 9:35 ` [PATCH 07/12] ARM: davinci: da850: set the GPIO base to 0 Bartosz Golaszewski 2018-11-21 9:35 ` Bartosz Golaszewski 2018-11-21 9:35 ` [PATCH 08/12] ARM: davinci: dm365: " Bartosz Golaszewski 2018-11-21 9:35 ` Bartosz Golaszewski 2018-11-21 9:35 ` Bartosz Golaszewski [this message] 2018-11-21 9:35 ` [PATCH 09/12] ARM: davinci: dm646x: " Bartosz Golaszewski 2018-11-21 9:35 ` [PATCH 10/12] ARM: davinci: dm355: " Bartosz Golaszewski 2018-11-21 9:35 ` Bartosz Golaszewski 2018-11-21 9:35 ` [PATCH 11/12] ARM: davinci: da830: " Bartosz Golaszewski 2018-11-21 9:35 ` Bartosz Golaszewski 2018-11-21 9:35 ` [PATCH 12/12] ARM: davinci: dm644x: " Bartosz Golaszewski 2018-11-21 9:35 ` Bartosz Golaszewski 2018-11-27 12:20 ` [PATCH 00/12] ARM: davinci: fix GPIO breakage after v4.19 Sekhar Nori 2018-11-27 12:20 ` Sekhar Nori 2018-11-27 12:20 ` Sekhar Nori
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=20181121093523.12503-10-brgl@bgdev.pl \ --to=brgl@bgdev.pl \ --cc=bgolaszewski@baylibre.com \ --cc=grygorii.strashko@ti.com \ --cc=j-keerthy@ti.com \ --cc=khilman@kernel.org \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=nsekhar@ti.com \ --cc=stable@vger.kernel.org \ /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.