On Tue, 2018-01-09 at 17:58 -0800, Stephen Boyd wrote: > Some qcom platforms make some GPIOs or pins unavailable for use > by non-secure operating systems, and thus reading or writing the > registers for those pins will cause access control issues. > Introduce a DT property to describe the set of GPIOs that are > available for use so that higher level OSes are able to know what > pins to avoid reading/writing. > +- ngpios-ranges: > + Usage: optional > + Value type: <prop-encoded-array> > + Definition: Tuples of GPIO ranges (base, size) indicating > + GPIOs available for use. Can be name more particular? We have on one hand gpio-range-list for mapping, on the other this one might become generic. So, there are few options (at least?) to consider: 1) re-use gpio-ranges 2) add a valid property to gpio-ranges 3) rename ngpios-ranges to something like gpio-valid-ranges (I don't like it so much either, but for me it looks more descriptive than ngpios-ranges) -- Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> Intel Finland Oy -- 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
