All of lore.kernel.org
 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 v3] gpio: sim: don't fiddle with GPIOLIB private members
Date: Tue, 5 Sep 2023 15:05:17 +0300	[thread overview]
Message-ID: <ZPcZfd5UtzMmIUvm@smile.fi.intel.com> (raw)
In-Reply-To: <20230905082413.21954-1-brgl@bgdev.pl>

On Tue, Sep 05, 2023 at 10:24:13AM +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 iterate over the children
> devices of the top-level platform device and compare their fwnodes
> against the one passed to the init function from probe.
> 
> While at it: fix one line break and remove the untrue part about
> configfs callbacks using dev_get_drvdata() from a comment.

...

> v2 -> v3:
> - don't use fwnode internal fields, instead: iterate over the platform
>   device's children and locate the GPIO device

Thank you!

...

> @@ -181,7 +178,7 @@ static int gpio_sim_get_direction(struct gpio_chip *gc, unsigned int offset)

>  static int gpio_sim_set_config(struct gpio_chip *gc,
> -				  unsigned int offset, unsigned long config)
> +			       unsigned int offset, unsigned long config)

Looking at other prototypes, it can be

static int gpio_sim_set_config(struct gpio_chip *gc, unsigned int offset,
			       unsigned long config)

...

> +static int gpio_sim_chip_set_device(struct device *dev, void *data)
> +{
> +	struct gpio_sim_chip *chip = data;

> +	if (chip->swnode == dev->fwnode) {

Please do not dereference fwnode from the struct device, we have an API!
device_match_fwnode()

> +		chip->dev = dev;
> +		return 1;
> +	}
> +
> +	return 0;
> +}

...

> +	chip->swnode = swnode;
> +	ret = device_for_each_child(dev, chip, gpio_sim_chip_set_device);
> +	if (!ret)
> +		return -ENODEV;

Can bus_find_device_by_fwnode() be used here?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-09-05 16:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05  8:24 [PATCH v3] gpio: sim: don't fiddle with GPIOLIB private members Bartosz Golaszewski
2023-09-05 12:05 ` Andy Shevchenko [this message]
2023-09-05 12:08   ` Andy Shevchenko
2023-09-05 12:10     ` Bartosz Golaszewski
2023-09-05 12:35       ` Andy Shevchenko
2023-09-05 12:09   ` 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=ZPcZfd5UtzMmIUvm@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.