From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Jon Hunter <jonathanh@nvidia.com>,
linux-tegra <linux-tegra@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] gpio: tegra: Add missing dependencies
Date: Tue, 19 Jan 2021 13:37:33 +0100 [thread overview]
Message-ID: <CAMpxmJW4uAJggA+yuO8Ntgi_px1fmZ3e3WCtszvc+prpYY=DGA@mail.gmail.com> (raw)
In-Reply-To: <20210118194925.819610-1-thierry.reding@gmail.com>
On Mon, Jan 18, 2021 at 8:49 PM Thierry Reding <thierry.reding@gmail.com> wrote:
>
> From: Thierry Reding <treding@nvidia.com>
>
> Commit efcdca286eef ("gpio: tegra: Convert to gpio_irq_chip") moved the
> Tegra GPIO driver to the generic GPIO IRQ chip infrastructure and made
> the IRQ domain hierarchical, so the driver needs to pull in the support
> infrastructure via the GPIOLIB_IRQCHIP and IRQ_DOMAIN_HIERARCHY Kconfig
> options.
>
> Fixes: efcdca286eef ("gpio: tegra: Convert to gpio_irq_chip")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> drivers/gpio/Kconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index 75f6c37620ea..013a1055939d 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -597,6 +597,8 @@ config GPIO_TEGRA
> default ARCH_TEGRA
> depends on ARCH_TEGRA || COMPILE_TEST
> depends on OF_GPIO
> + select GPIOLIB_IRQCHIP
> + select IRQ_DOMAIN_HIERARCHY
> help
> Say yes here to support GPIO pins on NVIDIA Tegra SoCs.
>
> --
> 2.30.0
>
Applied, thanks!
Bartosz
prev parent reply other threads:[~2021-01-19 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 19:49 [PATCH] gpio: tegra: Add missing dependencies Thierry Reding
2021-01-19 12:37 ` Bartosz Golaszewski [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='CAMpxmJW4uAJggA+yuO8Ntgi_px1fmZ3e3WCtszvc+prpYY=DGA@mail.gmail.com' \
--to=bgolaszewski@baylibre.com \
--cc=jonathanh@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lkp@intel.com \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).