From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Kent Gibson <warthog618@gmail.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH] gpio: sim: don't fiddle with GPIOLIB private members
Date: Sat, 2 Sep 2023 00:10:39 +0300 [thread overview]
Message-ID: <ZPJTT/l9fX1lhu6O@smile.fi.intel.com> (raw)
In-Reply-To: <20230901183240.102701-1-brgl@bgdev.pl>
On Fri, Sep 01, 2023 at 08:32:40PM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> We access internals of struct gpio_device and struct gpio_desc because
> it's easier but it can actually be avoided and we're working towards a
> better encapsulation of GPIO data structures across the kernel so let's
> start at home.
>
> Instead of checking gpio_desc flags, let's just track the requests of
> GPIOs in the driver. We also already store the information about
> direction of simulated lines.
>
> For kobjects needed by sysfs callbacks: we can leverage the fact that
> once created for a software node, struct device is accessible from that
> fwnode_handle. We don't need to dereference gpio_device.
>
> While at it: fix one line break and remove the untrue part about
> configfs callbacks using dev_get_drvdata() from a comment.
...
> -static void gpio_sim_free(struct gpio_chip *gc, unsigned int offset)
Why is this?
> +static int gpio_sim_request(struct gpio_chip *gc, unsigned int offset)
> {
> struct gpio_sim_chip *chip = gpiochip_get_data(gc);
>
> scoped_guard(mutex, &chip->lock)
> + __set_bit(offset, chip->request_map);
> +
> + return 0;
> +}
> +
> +static void gpio_sim_free(struct gpio_chip *gc, unsigned int offset)
> +{
> + struct gpio_sim_chip *chip = gpiochip_get_data(gc);
> +
> + scoped_guard(mutex, &chip->lock) {
> __assign_bit(offset, chip->value_map,
> !!test_bit(offset, chip->pull_map));
> + __clear_bit(offset, chip->request_map);
> + }
> }
Seems to me like you. shuffled the order of the two functions.
Can you leave _free() at the same location in the file?
...
> - /* Used by sysfs and configfs callbacks. */
> - dev_set_drvdata(&gc->gpiodev->dev, chip);
> + /* Used by sysfs callbacks. */
> + dev_set_drvdata(swnode->dev, chip);
dev pointer of firmware node is solely for dev links. Is it the case here?
Seems to me you luckily abuse it.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-09-01 22:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 18:32 [PATCH] gpio: sim: don't fiddle with GPIOLIB private members Bartosz Golaszewski
2023-09-01 21:10 ` Andy Shevchenko [this message]
2023-09-02 14:40 ` Bartosz Golaszewski
2023-09-04 8:58 ` Andy Shevchenko
2023-09-04 9:22 ` Bartosz Golaszewski
2023-09-04 9:40 ` Andy Shevchenko
2023-09-04 9:47 ` Bartosz Golaszewski
2023-09-04 10:05 ` Andy Shevchenko
2023-09-04 10:12 ` Bartosz Golaszewski
2023-09-04 10:29 ` Andy Shevchenko
2024-02-21 1:46 ` Saravana Kannan
2024-02-21 9:34 ` Bartosz Golaszewski
2024-02-21 12:59 ` Andy Shevchenko
2024-02-23 1:01 ` Saravana Kannan
2024-02-23 14:54 ` Andy Shevchenko
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=ZPJTT/l9fX1lhu6O@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog618@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.