On 2017-07-12 13:39, Linus Walleij wrote: > On Wed, Jul 12, 2017 at 1:30 PM, Jan Kiszka <jan.kiszka@xxxxxxxxxxx> wrote: >> On 2017-07-12 11:30, Linus Walleij wrote: > >>> What you are talking about should be hardware-and-vendor specific >>> info and prefixed "exar,*". >> >> "exar," or rather "gpio-exar,", like in [1]? > > HW-specific DT bindings have this form: "vendor,foo". > > So "exar,gpio-first-exported-pin" is some kind of overstating of the > fact, but correct. OK. > > The bindings (put with the rest of the exar DT bindings if there > are such somewhere in Documentation/devicetree/bindings/* else > in a new file) should make it very clear that this is a > hardware-specific thing telling us which hardware pin is the > first offset to be used for GPIO. This binding will lack any compatible value, so I'm not yet sure how to name/document things properly. Is there a precedence for such a case? Well, I can add some gpio-exar.txt and just put those two properties in it. Jan -- Siemens AG, Corporate Technology, CT RDA ITP SES-DE Corporate Competence Center Embedded Linux -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
