On 12 November 2014 13:00, Kamlakant Patel <[email protected]> wrote:
>
> Hi Jonas,
>
> This is an updated version of the previous patch with some fixes.
> Could you please try it out.
Thanks, it works, tested on UC-7112-LX hardware.
I have one additional nit..
The GPIO base number is implicitly changed from 0 to 224
(ARCH_NR_GPIOS (256) - ngpio (32)) which happen because of
bgpio_init() (it sets base -1 / gpiochip_find_base() on
gpiochip_add()). Which is confusing since the valid range (from user
space) used to be 0-31. So on export we now get:
[root@zurkon ~]# echo 24 > /sys/class/gpio/export
[ 61.640000] gpio-24 (?): gpiod_request: status -517
[ 61.650000] export_store: status -19
I see other drivers explicitly set base after bgpio_init(), my
suggestion is that we do the same here e.g. :
> + bgc->gc.label = "moxart-gpio";
> + bgc->gc.request = moxart_gpio_request;
> + bgc->gc.free = moxart_gpio_free;
> + bgc->gc.get = moxart_gpio_get;
> + bgc->data = bgc->read_reg(bgc->reg_set);
> + bgc->gc.ngpio = 32;
> + bgc->gc.dev = dev;
> + bgc->gc.owner = THIS_MODULE;
bgc->gc.base = 0;
Tested-by: Jonas Jensen <[email protected]>
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
