Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1618657
| From | Linus Walleij <linus.walleij@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC] Documentation: pinctrl: Add "pinmux" property |
| Date | 2017-04-07 12:20 +0200 |
| Message-ID | <ttz9L-5L0-5@gated-at.bofh.it> (permalink) |
| References | <ttcZA-7iO-29@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Apr 6, 2017 at 12:35 PM, Jacopo Mondi <jacopo+renesas@jmondi.org> wrote: > Document "pinmux" property as part of generic pin controller > documentation. > Fix 2 minor typos in documentation while at there. > > Signed-off-by: Jacopo Mondi <jacopo+renesas@jmondi.org> Patch applied. This is documenting what is already the case and is as such very helpful. > Sending this one as RFC to collect feedback. I just applied it. It is already much better than what we have. If more adjustments are needed, people can send additional patches. > If the change is not rejected is it > worth adding to pin controller core helper functions to parse the newly > documented property, as this commit > <https://patchwork.kernel.org/patch/9411231/> > did for "pinctrl-pin-array" one? > > All drivers using "pinmux" exhibit the same behavior which is fine as long as > "pinmux" only accepts a list of u32 parameters. > > ... > pins = of_find_property(node, "pinmux", NULL); > ... > npins = pins->length / sizeof(u32); > ... > of_property_read_u32_index(node, "pinmux", > i, &pinfunc); > ... It makes sense. Just make sure to move users over to use the helpers. Yours, Linus Walleij
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[RFC] Documentation: pinctrl: Add "pinmux" property Jacopo Mondi <jacopo+renesas@jmondi.org> - 2017-04-06 12:40 +0200 Re: [RFC] Documentation: pinctrl: Add "pinmux" property Linus Walleij <linus.walleij@linaro.org> - 2017-04-07 12:20 +0200
csiph-web