Linux GPIO subsystem development
 help / color / mirror / Atom feed
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 2/2 v2] gpio: sim: simplify code with cleanup helpers
Date: Fri, 11 Aug 2023 17:24:43 +0300	[thread overview]
Message-ID: <ZNZEq5wo655rttb/@smile.fi.intel.com> (raw)
In-Reply-To: <20230811131427.40466-2-brgl@bgdev.pl>

On Fri, Aug 11, 2023 at 03:14:27PM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> 
> Use macros defined in linux/cleanup.h to automate resource lifetime
> control in gpio-sim.

...

>  	struct gpio_sim_chip *chip = gpiochip_get_data(gc);
>  	int ret;
>  
> -	mutex_lock(&chip->lock);
> -	ret = !!test_bit(offset, chip->value_map);
> -	mutex_unlock(&chip->lock);
> +	scoped_guard(mutex, &chip->lock)
> +		ret = !!test_bit(offset, chip->value_map);
>  
>  	return ret;

Isn't the same approach applicable here?

...

>  {
>  	struct gpio_sim_chip *chip = gpiochip_get_data(gc);

With

	unsigned long *map = ...->value_map;

> -	mutex_lock(&chip->lock);
> -	bitmap_replace(chip->value_map, chip->value_map, bits, mask, gc->ngpio);
> -	mutex_unlock(&chip->lock);
> +	scoped_guard(mutex, &chip->lock)
> +		bitmap_replace(chip->value_map, chip->value_map, bits, mask,
> +			       gc->ngpio);

...you can satisfy me as well :-)

		bitmap_replace(map, map, bits, mask, gc->ngpio);

>  }

...

>  {
>  	struct gpio_sim_chip *chip = gpiochip_get_data(gc);
>  
> -	mutex_lock(&chip->lock);
> -	__assign_bit(offset, chip->value_map, !!test_bit(offset, chip->pull_map));
> -	mutex_unlock(&chip->lock);
> +	scoped_guard(mutex, &chip->lock)
> +		__assign_bit(offset, chip->value_map,
> +			     !!test_bit(offset, chip->pull_map));

Ditto (I checked the line size).

>  }

...

>  	struct gpio_sim_device *dev = gpio_sim_bank_get_device(bank);
>  	struct gpio_sim_chip_name_ctx ctx = { bank->swnode, page };
> -	int ret;
>  
> -	mutex_lock(&dev->lock);
> +	guard(mutex)(&dev->lock);
> +
>  	if (gpio_sim_device_is_live_unlocked(dev))
> -		ret = device_for_each_child(&dev->pdev->dev, &ctx,
> -					    gpio_sim_emit_chip_name);
> -	else
> -		ret = sprintf(page, "none\n");
> -	mutex_unlock(&dev->lock);
> +		return device_for_each_child(&dev->pdev->dev, &ctx,
> +					     gpio_sim_emit_chip_name);
>  
> -	return ret;
> +	return sprintf(page, "none\n");

I looked at the original and at the change and maybe it could be done as

	struct device *parent = &dev->pdev->dev; // Naming?
	bool live;

	live = gpio_sim_device_is_live_unlocked(dev);
	if (!live)
		return sprintf(page, "none\n");

	return device_for_each_child(parent, &ctx, gpio_sim_emit_chip_name);

...

>  	int ret;
>  
> -	mutex_lock(&dev->lock);
> -	ret = sprintf(page, "%s\n", hog->name ?: "");
> -	mutex_unlock(&dev->lock);
> +	scoped_guard(mutex, &dev->lock)
> +		ret = sprintf(page, "%s\n", hog->name ?: "");
>  
>  	return ret;

guard() ?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-08-11 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 13:14 [PATCH 1/2] gpio: sim: simplify gpio_sim_device_config_live_store() Bartosz Golaszewski
2023-08-11 13:14 ` [PATCH 2/2 v2] gpio: sim: simplify code with cleanup helpers Bartosz Golaszewski
2023-08-11 14:24   ` Andy Shevchenko [this message]
2023-08-11 14:28     ` Bartosz Golaszewski
2023-08-11 14:31       ` Andy Shevchenko
2023-08-11 14:41     ` Bartosz Golaszewski
2023-08-11 14:03 ` [PATCH 1/2] gpio: sim: simplify gpio_sim_device_config_live_store() Andy Shevchenko
2023-08-12 18:32 ` Bartosz Golaszewski

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=ZNZEq5wo655rttb/@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox