Re: [PATCH] pinctrl: copy per-pin driver private data to struct pin_desc

2016-05-31 Thread Linus Walleij
On Wed, May 25, 2016 at 7:09 AM, Masahiro Yamada wrote: > Currently, struct pinctrl_pin_desc can have per-pin driver private > data, but it is not copied to struct pin_desc. > > For a driver with sparse pin space, for-loop search like below would > be necessary in

Re: [PATCH] pinctrl: copy per-pin driver private data to struct pin_desc

2016-05-31 Thread Linus Walleij
On Wed, May 25, 2016 at 7:09 AM, Masahiro Yamada wrote: > Currently, struct pinctrl_pin_desc can have per-pin driver private > data, but it is not copied to struct pin_desc. > > For a driver with sparse pin space, for-loop search like below would > be necessary in order to get the

[PATCH] pinctrl: copy per-pin driver private data to struct pin_desc

2016-05-24 Thread Masahiro Yamada
Currently, struct pinctrl_pin_desc can have per-pin driver private data, but it is not copied to struct pin_desc. For a driver with sparse pin space, for-loop search like below would be necessary in order to get the driver-specific data for a desired pin number. for (i = 0; i <

[PATCH] pinctrl: copy per-pin driver private data to struct pin_desc

2016-05-24 Thread Masahiro Yamada
Currently, struct pinctrl_pin_desc can have per-pin driver private data, but it is not copied to struct pin_desc. For a driver with sparse pin space, for-loop search like below would be necessary in order to get the driver-specific data for a desired pin number. for (i = 0; i <