Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1620999
| From | Linus Walleij <linus.walleij@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v4 3/9] dt-bindings: pinctrl: Add RZ/A1 bindings doc |
| Date | 2017-04-11 10:00 +0200 |
| Message-ID | <tuYSt-463-13@gated-at.bofh.it> (permalink) |
| References | <tsTNf-3DV-13@gated-at.bofh.it> <tsTNg-3DV-21@gated-at.bofh.it> <tuM4W-4ll-21@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Apr 10, 2017 at 8:12 PM, Rob Herring <robh@kernel.org> wrote:
> On Wed, Apr 05, 2017 at 04:07:21PM +0200, Jacopo Mondi wrote:
>> + The allowed generic formats for a pin multiplexing sub-node are the
>> + following ones:
>> +
>> + node-1 {
>> + pinmux = <PIN_ID_AND_MUX>, <PIN_ID_AND_MUX>, ... ;
>> + GENERIC_PINCONFIG;
>
> What's GENERIC_PINCONFIG? I see this in some other binding docs, but not
> used anywhere. If this is a boolean property then get rid of the all
> caps. If this is a define, then don't use complex defines that expand to
> dts source.
I guess it is a wildcard for everything under the heading in
"Generic pin configuration node content"
in Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
I'm all for documenting it properly.
It's kind of useful, but I don't know the recent ambtions about being
formal with DT bindings. The GPIO bindings are just over the top
with BNF notation in its formalism. Dunno what is best here :/
Yours,
Linus Walleij
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH v4 3/9] dt-bindings: pinctrl: Add RZ/A1 bindings doc Rob Herring <robh@kernel.org> - 2017-04-10 20:20 +0200 Re: [PATCH v4 3/9] dt-bindings: pinctrl: Add RZ/A1 bindings doc jmondi <jacopo@jmondi.org> - 2017-04-10 21:20 +0200 Re: [PATCH v4 3/9] dt-bindings: pinctrl: Add RZ/A1 bindings doc Linus Walleij <linus.walleij@linaro.org> - 2017-04-11 10:00 +0200
csiph-web