On 06/21/2013 12:09 PM, Gerhard Sittig wrote: > introduce support to optionally run a binary column address bit pattern > on column GPIO pins in contrast to the formerly assumed one-out-of-N approach > diff --git a/Documentation/devicetree/bindings/input/gpio-matrix-keypad.txt b/Documentation/devicetree/bindings/input/gpio-matrix-keypad.txt > +The driver assumes that each row and column line of the keypad matrix is Here, I would definitely: s/The driver/This binding/. > +connected to a specific GPIO pin. Alternatively column addresses can get > +encoded in binary form to reduce the number of GPIO pins involved, at the > +cost of adding an external decoder which translates the binary pattern of N > +GPIO coloumn pins into one of 2**N column lines of the matrix. A mere s/coloumn/column/ > +circuit of two inverting open collector drivers in series connected to one > +output pin is a special case of this generic decoder approach. Such a > +decoder may be desirable since it's cheap and protects the SoC from damage > +by unwanted interaction of signals when any combination of multiple keys > +gets pressed, regardless of the software's operating the column GPIO pins. > +The row GPIO pins won't interfere either since they all are inputs. I'm not sure it's worth mentioning that; it presumably makes no semantic difference to how SW interfaces to the HW this binding describes. > +- col-gpios-binary: boolean, switches from the 'one GPIO pin for each > + column' approach to the 'n GPIO pins to address > + 2**n columns' approach (binary encoding of column > + addresses in contrast to a one-out-of-many pattern > + for the column GPIO pins) Thinking about the keypad,num-rows/keypad,num-columns properties from the previous patch, "num" might not be enough to describe all HW. "num" assumes that the decoder outputs 0..num-1 are used and that num..N-1 are not. What if the unused decoder outputs are 0..(N-num-1)? Instead, it may be better to define a property col-values-mask, with one bit set for each valid/useful integer value to be output on the column GPIOs? BTW, I think some of the new properties in either/both these patches and the original matrix-keypad binding doc are prefixed with "keypad," and some not. It would be best to be consistent. Given these properties are specific to this one binding, rather than some kind of generic infra-structure, having the prefix on as many properties as possible seems correct to me. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
