On Tue, 2017-12-12 at 14:50 -0600, Timur Tabi wrote:
> pinctrl-msm only accepts an array of GPIOs from 0 to n-1, and it
> expects
> each group to support have only one pin (npins == 1).
>
> We can support "sparse" GPIO maps if we allow for some groups to have
> zero
> pins (npins == 0). These pins are "hidden" from the rest of the
> driver
> and gpiolib.
>
> Access to unavailable GPIOs is blocked via a request callback. If the
> requested GPIO is unavailable, -EACCES is returned, which prevents
> further access to that GPIO.
We recently have some interesting BIOS/Windows driver design which makes
a need of something similar. Mika did patched pinctrl-intel for that. I
dunno that approach can be used here, or your proposal be utilized in
pinctrl-intel. Mika, any comments?
See some nitpicks below.
>
> seq_printf(s, " %-8s: %-3s %d", g->name, is_out ? "out" :
> "in", func);
> seq_printf(s, " %dmA", msm_regval_to_drive(drive));
> - seq_printf(s, " %s", pulls[pull]);
> + seq_printf(s, " %s\n", pulls[pull]);
I would rather do
seq_putc(s, '\n');
which makes code slightly more flexible for maintenance and reading.
> }
>
> static void msm_gpio_dbg_show(struct seq_file *s, struct gpio_chip
> *chip)
> @@ -524,23 +529,36 @@ static void msm_gpio_dbg_show(struct seq_file
> *s, struct gpio_chip *chip)
> unsigned gpio = chip->base;
> unsigned i;
>
> - for (i = 0; i < chip->ngpio; i++, gpio++) {
> + for (i = 0; i < chip->ngpio; i++, gpio++)
> msm_gpio_dbg_show_one(s, NULL, chip, i, gpio);
> - seq_puts(s, "\n");
> - }
This kind of change looks like a candidate to a separate patch,
though I mentioned it's just a nit.
--
Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
Intel Finland Oy
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
