On Tue, Mar 27, 2018 at 03:52:57PM +0200, Sebastian Reichel wrote: > This updates the GE ACHC binding, so that different compatible > strings are used for the programming interface, which is the > ezport interface from NXP MK20FN1M0VMD12 and the microcontroller's > normal SPI interface. > > Signed-off-by: Sebastian Reichel <sebastian.reichel@xxxxxxxxxxxxxxx> > --- > Documentation/devicetree/bindings/misc/ge-achc.txt | 19 ++++++++++++++++--- > 1 file changed, 16 insertions(+), 3 deletions(-) > > diff --git a/Documentation/devicetree/bindings/misc/ge-achc.txt b/Documentation/devicetree/bindings/misc/ge-achc.txt > index 77df94d7a32f..6c6bd6568504 100644 > --- a/Documentation/devicetree/bindings/misc/ge-achc.txt > +++ b/Documentation/devicetree/bindings/misc/ge-achc.txt > @@ -7,7 +7,13 @@ Note: This device does not expose the peripherals as USB devices. > > Required properties: > > -- compatible : Should be "ge,achc" > +- compatible : Should be > + "ge,achc" (normal interface) > + "ge,achc-ezport" (flashing interface) > + > +Required properties (flashing interface only): > + > +- reset-gpios: GPIO Specifier for the reset GPIO Does the reset only affect the flashing interface and are the data pins shared? If not for both, then I think the correct thing to do here is just extend reg to support multiple values to represent multiple chip selects. Rob -- 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
