lkml.org 
[lkml]   [2018]   [Sep]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH mfd+gpio 2/2] drivers: gpio: Add support for GPIOs over Moxtet bus
Hi Marek!

Your DT bindings patch should ideally be in a separate patch and
must be sent to devicetree@vger.kernel.org as well.

On Thu, Aug 30, 2018 at 4:44 PM Marek Behún <marek.behun@nic.cz> wrote:

> + - moxtet,input-mask : Bitmask. Those bits which correspond to input GPIOs
> + when read from Moxtet bus should be set here.
> + For example if bit 0 and bit 3 are input GPIO bits,
> + this should be set to 0x9.
> + Since there are only 4 input bits, 0xf is max value.
> + - moxtet,output-mask : Bitmask. Those bits which correspond to output GPIOs
> + when written to Moxtet bus should be set here.
> + For example if bit 1 and bit 6 are output GPIO bits,
> + this should be set to 0x41.
> + Since there are at most 8 output bits, 0xff is max
> + value.

Please don't do it like this. Let the consumers decide if they want
to use a certain line as input or output.

Enumerate ALL GPIOs from 0 to N and let a consumer pick
GPIO x and then decide if it will be used as input or output.
Re-enumerating the GPIOs presented from the chip is complicating
things by shuffleing around the local offset (HW numbering)
space.

For GPIOs that are not usable at all, use the
gpio-reserved-ranges = <> property, see gpio.txt

If you want to indicate that some lines can just be used for
input and some can just be used for output and some cannot
be used at all, let the .set_direction_output() and
.set_direction_input() callbacks fail for these pins with
-EINVAL or so.

If these masks cannot be derived from the compatible
strings, then create generic bindings to mark lines
as input-only or output-only in gpio.txt and use the
same syntax as gpio-reserved-ranges, and handle it
in the gpiolib just as with gpio-reserved-ranges, not
in your local driver.

For example gpio-output-only-ranges and
gpio-input-only-ranges.

But first convince us that you really need that.

> +#include <linux/gpio/consumer.h>
> +#include <linux/gpio.h>

This is a driver so only #include <linux/gpio/driver.h>
Skip the two above.

> +#include <linux/mfd/moxtet.h>
> +#include <linux/module.h>
> +#include <linux/of_gpio.h>

You don't need this either. Delete that include.

> +static int moxtet_gpio_dir_mask(struct gpio_chip *gc, unsigned int offset,
> + int *dir, u8 *mask)
> +{
> + struct moxtet_gpio_chip *chip = gpiochip_get_data(gc);
> + int i;
> +
> + *dir = 0;
> + for (i = 0; i < 4; ++i) {
> + *mask = 1 << i;

#include <linux/bitops.h>

*mask = BIT(i);

> + if (*mask & chip->in_mask) {
> + if (offset == 0)
> + return 0;
> + --offset;
> + }
> + }
> +
> + *dir = 1;
> + for (i = 0; i < 8; ++i) {
> + *mask = 1 << i;
> + if (*mask & chip->out_mask) {
> + if (offset == 0)
> + return 0;
> + }
> + }
> +
> + return -EINVAL;
> +}

This looks convoluted and I think will go away with my suggestion to
cut the masks.

Otherwise use primitives such as for_each_set_bit() etc.

> +static int moxtet_gpio_get_value(struct gpio_chip *gc, unsigned int offset)
> +{
> + struct moxtet_gpio_chip *chip = gpiochip_get_data(gc);
> + int ret, dir;
> + u8 mask;
> +
> + if (moxtet_gpio_dir_mask(gc, offset, &dir, &mask) < 0)
> + return -EINVAL;
> +
> + if (dir)
> + ret = moxtet_device_written(chip->dev);
> + else
> + ret = moxtet_device_read(chip->dev);
> +
> + if (ret < 0)
> + return ret;
> +
> + return (ret & mask) ? 1 : 0;
> +}
> +
> +static void moxtet_gpio_set_value(struct gpio_chip *gc, unsigned int offset,
> + int val)
> +{
> + struct moxtet_gpio_chip *chip = gpiochip_get_data(gc);
> + int state, dir;
> + u8 mask;
> +
> + if (moxtet_gpio_dir_mask(gc, offset, &dir, &mask) < 0)
> + return;

So skip this and trust the consumers to ask for the right GPIO and set
it up.

Yours,
Linus Walleij

\
 
 \ /
  Last update: 2018-09-05 12:08    [W:0.066 / U:1.584 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site