On 22/11/2015 20:26, Noble Pepper wrote:
> Hi, thanks for looking at this.
>
> I actually tried this approach before deciding groups that are not a
> fixed set of pins would require modifying pinctrl/pinmux.c and possibly
> pinctrl/core.c thus would affect a lot more than just the ralink
> driv
Hi, thanks for looking at this.
I actually tried this approach before deciding groups that are not a
fixed set of pins would require modifying pinctrl/pinmux.c and possibly
pinctrl/core.c thus would affect a lot more than just the ralink
drivers.
The problem arises when pinmux_enable_setting() i
Hi,
i had a closer look at the code. what you want to do instead of adding 2
dummy muxes is to modify
static int rt2880_pmx_group_enable(struct pinctrl_dev *pctrldev,
and change this part
/* mark the pins as gpio */
for (i = 0; i < p->groups[group].func[0].pin_count; i++)
This should fix the white space issue. I don't understand why it looks
like a forwarding, if you can provide details I'll be glad to fix it.
Thanks for your patience, this is my first attempt at an openwrt patch.
Noble
Existing pinctrl-rt2880.c code only kept track of one pin group that
functio
Hi,
the patch is white space broken and for some reason this seems to be a
forwarding. could you fix and resend please
John
On 03/11/2015 13:26, Noble Pepper wrote:
>
> Signed-off-by: Noble Pepper
> ---
> Existing pinctrl-rt2880.c code only kept track of one pin group that
> functions
Signed-off-by: Noble Pepper
---
Existing pinctrl-rt2880.c code only kept track of one pin group that
functions other than gpio may use. Functions in rt305x.c had differing
numbers of pins which caused rt2880_get_group_pins() to sometimes return
incorrect pins. Example: when trying to use "gpio ua
