Keyboard drivers, polling vs. non-polling mode

[Maxim Ignatenko]

On 14 May 2014 06:11, Ruslan Bukin <br at bsdpad.com> wrote:
> On Tue, May 13, 2014 at 11:17:58AM +0100, Maxim Ignatenko wrote:
>> I keep getting "fdb0: i2c transfer returned 6" and none of the printfs
>> I've added to iicbus_transfer_gen in sys/dev/iicbus/iiconf.c.
>
> You have problems with communication to EC.
>
> Forget about keyboard for a while and check i2c CS (chip select) and/or
> EC arbitration pins. Something is definitely goes different in HP
> implementation of Chromebook. Probably they used different GPIO pins.

It's even more funny: i2c-arbitrator was removed from FDT (compared to
Samsung Chromebook), so removing a call to bus_claim() from
ec_attach() does the trick, keyboard works in kdb :) (but not in
mountroot prompt)
u-boot actually does the same: it claims control over bus only if it
sees "google,ap-claim-gpios" and "google,ec-claim-gpios" properties on
i2c-arbitrator and just returns success otherwise.

Thanks for the help, now I'll try to make built-in USB hub work.

-- 
Best regards,
Maxim