From: Yicong Yang <yangyicong@huawei.com>
To: Weilong Chen <chenweilong@huawei.com>, <f.fangjian@huawei.com>
Cc: <linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linus.walleij@linaro.org>,
<brgl@bgdev.pl>, <yangyicong@hisilicon.com>, <robh+dt@kernel.org>,
<xuwei5@huawei.com>, <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH next v3 1/2] gpio: hisi: Add initial device tree support
Date: Thu, 3 Nov 2022 20:19:42 +0800 [thread overview]
Message-ID: <bb081979-10d6-5d6e-8e87-9a317fb09455@huawei.com> (raw)
In-Reply-To: <20221101082442.263448-1-chenweilong@huawei.com>
On 2022/11/1 16:24, Weilong Chen wrote:
> Add support for HiSilicon GPIO controller in embedded platform, which
> boot from devicetree.
>
> Signed-off-by: Weilong Chen <chenweilong@huawei.com>
Reviewed-by: Yicong Yang <yangyicong@hisilicon.com>
> ---
> Change since v2:
> - Drop wrong use ACPI_PTR/of_match_ptr
> Link: https://lore.kernel.org/lkml/20221028022453.163186-1-chenweilong@huawei.com/
>
> drivers/gpio/Kconfig | 2 +-
> drivers/gpio/gpio-hisi.c | 7 +++++++
> 2 files changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index e034f752e7ce..71a7880af59d 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -310,7 +310,7 @@ config GPIO_GRGPIO
>
> config GPIO_HISI
> tristate "HiSilicon GPIO controller driver"
> - depends on (ARM64 && ACPI) || COMPILE_TEST
> + depends on ARM64 || COMPILE_TEST
> select GPIO_GENERIC
> select GPIOLIB_IRQCHIP
> help
> diff --git a/drivers/gpio/gpio-hisi.c b/drivers/gpio/gpio-hisi.c
> index 3caabef5c7a2..55bd69043bf4 100644
> --- a/drivers/gpio/gpio-hisi.c
> +++ b/drivers/gpio/gpio-hisi.c
> @@ -221,6 +221,12 @@ static const struct acpi_device_id hisi_gpio_acpi_match[] = {
> };
> MODULE_DEVICE_TABLE(acpi, hisi_gpio_acpi_match);
>
> +static const struct of_device_id hisi_gpio_dts_match[] = {
> + { .compatible = "hisilicon,ascend910-gpio", },
> + { }
> +};
> +MODULE_DEVICE_TABLE(of, hisi_gpio_dts_match);
> +
> static void hisi_gpio_get_pdata(struct device *dev,
> struct hisi_gpio *hisi_gpio)
> {
> @@ -311,6 +317,7 @@ static struct platform_driver hisi_gpio_driver = {
> .driver = {
> .name = HISI_GPIO_DRIVER_NAME,
> .acpi_match_table = hisi_gpio_acpi_match,
> + .of_match_table = hisi_gpio_dts_match,
> },
> .probe = hisi_gpio_probe,
> };
>
next prev parent reply other threads:[~2022-11-03 12:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 8:24 Weilong Chen
2022-11-01 8:24 ` [PATCH next v3 2/2] dt-bindings: gpio: add entry for hisilicon,ascend910-gpio Weilong Chen
2022-11-02 17:13 ` Rob Herring
2022-11-03 12:36 ` Yicong Yang
2022-11-02 12:49 ` [PATCH next v3 1/2] gpio: hisi: Add initial device tree support Bartosz Golaszewski
2022-11-03 1:07 ` chenweilong
2022-11-03 8:40 ` Jay Fang
2022-11-03 8:50 ` chenweilong
2022-11-07 20:37 ` Bartosz Golaszewski
2022-11-03 12:19 ` Yicong Yang [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-29 11:35 Weilong Chen
2022-11-03 8:33 ` Jay Fang
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=bb081979-10d6-5d6e-8e87-9a317fb09455@huawei.com \
--to=yangyicong@huawei.com \
--cc=brgl@bgdev.pl \
--cc=chenweilong@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fangjian@huawei.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=xuwei5@huawei.com \
--cc=yangyicong@hisilicon.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
all inboxes | Powered by JetHome®