From: Hans de Goede <hdegoede@redhat.com>
To: Rosen Penev <rosenp@gmail.com>, platform-driver-x86@vger.kernel.org
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: intel: int0002_vgpio: use gpiochip_get_data
Date: Wed, 4 Dec 2024 14:19:32 +0100 [thread overview]
Message-ID: <87f9c6ae-e409-4ef5-a2ad-319cdebdf577@redhat.com> (raw)
In-Reply-To: <20241203233505.184612-1-rosenp@gmail.com>
Hi Rosen,
Thank you for your patch.
On 4-Dec-24 12:35 AM, Rosen Penev wrote:
> Instead of using container_of, we can pass the pointer to
> gpiochip_add_data and use it.
Yes that is possible, but why? What is the advantage
of doing this?
Given that the struct gpio_chip is the first member
of struct int0002_data it is actually free as it
turns into a no-op.
Where as gpiochip_get_data() is a non inline helper,
so your replacing a no-op with a function call here
I don't see how this makes things better?
Regards,
Hans
>
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
> drivers/platform/x86/intel/int0002_vgpio.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/intel/int0002_vgpio.c b/drivers/platform/x86/intel/int0002_vgpio.c
> index 0cc80603a8a9..7ce0774b3896 100644
> --- a/drivers/platform/x86/intel/int0002_vgpio.c
> +++ b/drivers/platform/x86/intel/int0002_vgpio.c
> @@ -102,7 +102,7 @@ static void int0002_irq_mask(struct irq_data *data)
> static int int0002_irq_set_wake(struct irq_data *data, unsigned int on)
> {
> struct gpio_chip *chip = irq_data_get_irq_chip_data(data);
> - struct int0002_data *int0002 = container_of(chip, struct int0002_data, chip);
> + struct int0002_data *int0002 = gpiochip_get_data(chip);
>
> /*
> * Applying of the wakeup flag to our parent IRQ is delayed till system
> @@ -211,7 +211,7 @@ static int int0002_probe(struct platform_device *pdev)
> girq->default_type = IRQ_TYPE_NONE;
> girq->handler = handle_edge_irq;
>
> - ret = devm_gpiochip_add_data(dev, chip, NULL);
> + ret = devm_gpiochip_add_data(dev, chip, int0002);
> if (ret) {
> dev_err(dev, "Error adding gpio chip: %d\n", ret);
> return ret;
prev parent reply other threads:[~2024-12-04 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 23:35 [PATCH] platform/x86: intel: int0002_vgpio: use gpiochip_get_data Rosen Penev
2024-12-04 13:19 ` Hans de Goede [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=87f9c6ae-e409-4ef5-a2ad-319cdebdf577@redhat.com \
--to=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rosenp@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 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.