Re: [PATCH] auxdisplay: ht16k33: Keyscan function should be optional

2017-08-17 Thread Rob Herring
On Wed, Aug 16, 2017 at 12:28:49PM +0200, Robin van der Gracht wrote: > keyscan should be optional to support simple LED matrix displays (output > only). > > Reported-by: Michael Kaplan > Signed-off-by: Robin van der Gracht > --- > >

Re: [PATCH] auxdisplay: ht16k33: Keyscan function should be optional

2017-08-17 Thread Rob Herring
On Wed, Aug 16, 2017 at 12:28:49PM +0200, Robin van der Gracht wrote: > keyscan should be optional to support simple LED matrix displays (output > only). > > Reported-by: Michael Kaplan > Signed-off-by: Robin van der Gracht > --- > > Documentation/devicetree/bindings/display/ht16k33.txt | 15

[PATCH] auxdisplay: ht16k33: Keyscan function should be optional

2017-08-16 Thread Robin van der Gracht
keyscan should be optional to support simple LED matrix displays (output only). Reported-by: Michael Kaplan Signed-off-by: Robin van der Gracht --- Documentation/devicetree/bindings/display/ht16k33.txt | 15 +-- drivers/auxdisplay/ht16k33.c

[PATCH] auxdisplay: ht16k33: Keyscan function should be optional

2017-08-16 Thread Robin van der Gracht
keyscan should be optional to support simple LED matrix displays (output only). Reported-by: Michael Kaplan Signed-off-by: Robin van der Gracht --- Documentation/devicetree/bindings/display/ht16k33.txt | 15 +-- drivers/auxdisplay/ht16k33.c | 14