On Fri, Aug 9, 2013 at 6:57 PM, Stephen Warren <[email protected]> wrote:
> From: Stephen Warren <[email protected]> > > This change makes documentation of the the gpio-ranges property shorter > and more succinct, more consistent with the style of the rest of the > document, and not mention Linux-specifics such as the API > pinctrl_request_gpio(); DT binding documents should be OS independant > where at all possible. As part of this, the gpio-ranges property's format > is described in BNF form, in order to match the rest of the document. > > This change also deprecates the #gpio-range-cells property. Such > properties are useful when one node references a second node, and that > second node dictates the format of the reference. However, that is not > the case here; the definition of gpio-ranges itself always dictates its > format entirely, and hence the value #gpio-range-cells must always be 3, > and hence there is no point requiring any referenced node to include > this property. The only remaining need for this property is to ensure > compatibility of DTs with older SW that was written to support the > previous version of the binding. > > Signed-off-by: Stephen Warren <[email protected]> > Acked-by: Mark Rutland <[email protected]> > --- > v4: Patch applied. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
