From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Tzuyi Chang <tychang@realtek.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andy@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] gpio: realtek: Add GPIO support for RTD SoC variants
Date: Wed, 1 Nov 2023 08:15:43 +0100 [thread overview]
Message-ID: <e18a7ee0-a5e3-4180-9f8a-99b21d1303e6@linaro.org> (raw)
In-Reply-To: <20231101025802.3744-2-tychang@realtek.com>
On 01/11/2023 03:58, Tzuyi Chang wrote:
> This commit adds GPIO support for Realtek DHC RTD SoCs.
Please do not use "This commit/patch", but imperative mood. See longer
explanation here:
https://elixir.bootlin.com/linux/v5.17.1/source/Documentation/process/submitting-patches.rst#L95
>
> This driver enables configuration of GPIO direction, GPIO values, GPIO
> debounce settings and handles GPIO interrupts.
>
> Signed-off-by: Tzuyi Chang <tychang@realtek.com>
> ---
...
> +
> +static int rtd_gpio_probe(struct platform_device *pdev)
> +{
> + struct rtd_gpio *data;
> + const struct of_device_id *match;
> + struct device_node *node;
> + int ret;
> + int i;
> +
> + node = pdev->dev.of_node;
> + match = of_match_node(rtd_gpio_of_matches, pdev->dev.of_node);
> + if (!match || !match->data)
> + return -EINVAL;
> +
> + data = devm_kzalloc(&pdev->dev, sizeof(*data), GFP_KERNEL);
> + if (!data)
> + return -ENOMEM;
> +
> + data->assert_irq = irq_of_parse_and_map(node, 0);
> + if (!data->assert_irq)
> + goto deferred;
> +
> + data->deassert_irq = irq_of_parse_and_map(node, 1);
> + if (!data->deassert_irq)
> + goto deferred;
So this goes to cleanup path...
> +
> + data->info = match->data;
> + spin_lock_init(&data->lock);
> +
> + data->base = of_iomap(node, 0);
> + if (!data->base)
> + return -ENXIO;
But this does not? What?
> +
> + data->irq_base = of_iomap(node, 1);
> + if (!data->irq_base)
> + return -ENXIO;
> +
> + data->gpio_chip.parent = &pdev->dev;
> + data->gpio_chip.label = dev_name(&pdev->dev);
> + data->gpio_chip.of_gpio_n_cells = 2;
> + data->gpio_chip.base = data->info->gpio_base;
> + data->gpio_chip.ngpio = data->info->num_gpios;
> + data->gpio_chip.request = rtd_gpio_request;
> + data->gpio_chip.free = rtd_gpio_free;
> + data->gpio_chip.get_direction = rtd_gpio_get_direction;
> + data->gpio_chip.direction_input = rtd_gpio_direction_input;
> + data->gpio_chip.direction_output = rtd_gpio_direction_output;
> + data->gpio_chip.set = rtd_gpio_set;
> + data->gpio_chip.get = rtd_gpio_get;
> + data->gpio_chip.set_config = rtd_gpio_set_config;
> + data->gpio_chip.to_irq = rtd_gpio_to_irq;
> + data->irq_chip = rtd_gpio_irq_chip;
> + data->irq_chip.name = data->info->name;
> +
> + ret = devm_gpiochip_add_data(&pdev->dev, &data->gpio_chip, data);
> + if (ret) {
> + dev_err(&pdev->dev, "Adding GPIO chip failed (%d)\n", ret);
And here no cleanup? It's some random choice.
> + return ret;
> + }
> +
> + data->domain = irq_domain_add_linear(node, data->gpio_chip.ngpio,
> + &irq_domain_simple_ops, data);
> + if (!data->domain) {
> + devm_kfree(&pdev->dev, data);
NAK, test your patch.
> + return -ENOMEM;
> + }
> +
> + for (i = 0; i < data->gpio_chip.ngpio; i++) {
> + int irq = irq_create_mapping(data->domain, i);
> +
> + irq_set_chip_data(irq, data);
> + irq_set_chip_and_handler(irq, &data->irq_chip, handle_simple_irq);
> + }
> +
> + irq_set_chained_handler_and_data(data->assert_irq, rtd_gpio_assert_irq_handle, data);
> + irq_set_chained_handler_and_data(data->deassert_irq, rtd_gpio_deassert_irq_handle, data);
> +
> + dev_dbg(&pdev->dev, "probed\n");
Nop, drop all silly, simple entry/exit messages.
> +
> + return 0;
> +
> +deferred:
> + devm_kfree(&pdev->dev, data);
NAK, test your patch.
> + return -EPROBE_DEFER;
> +}
> +
> +static struct platform_driver rtd_gpio_platform_driver = {
> + .driver = {
> + .name = "gpio-rtd",
> + .of_match_table = rtd_gpio_of_matches,
> + },
> + .probe = rtd_gpio_probe,
> +};
> +
> +static int rtd_gpio_init(void)
> +{
> + return platform_driver_register(&rtd_gpio_platform_driver);
> +}
> +
> +subsys_initcall(rtd_gpio_init);
> +
> +static void __exit rtd_gpio_exit(void)
> +{
> + platform_driver_unregister(&rtd_gpio_platform_driver);
> +}
> +module_exit(rtd_gpio_exit);
> +
> +MODULE_DESCRIPTION("Realtek DHC SoC gpio driver");
> +MODULE_LICENSE("GPL v2");
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-11-01 7:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 2:58 [PATCH 0/2] Add gpio driver support for Realtek DHC SoCs Tzuyi Chang
2023-11-01 2:58 ` [PATCH 1/2] gpio: realtek: Add GPIO support for RTD SoC variants Tzuyi Chang
2023-11-01 7:15 ` Krzysztof Kozlowski [this message]
2023-11-02 3:30 ` TY_Chang[張子逸]
2023-11-02 7:11 ` Krzysztof Kozlowski
2023-11-03 9:09 ` TY_Chang[張子逸]
2023-11-01 8:39 ` Linus Walleij
2023-11-02 12:40 ` TY_Chang[張子逸]
2023-11-02 14:52 ` Linus Walleij
2023-11-01 2:58 ` [PATCH 2/2] dt-bindings: gpio: realtek: Add realtek,rtd-gpio bindings Tzuyi Chang
2023-11-01 7:13 ` Krzysztof Kozlowski
2023-11-02 3:11 ` TY_Chang[張子逸]
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=e18a7ee0-a5e3-4180-9f8a-99b21d1303e6@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=tychang@realtek.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).