Home
last modified time | relevance | path

Searched refs:msg2638 (Results 1 – 3 of 3) sorted by relevance

/drivers/input/touchscreen/
A Dmsg2638.c102 input_report_key(msg2638->input_dev, msg2638->keycodes[i], in msg2138_report_keys()
264 msg2638_reset(msg2638); in msg2638_start()
299 msg2638_stop(msg2638); in msg2638_input_close()
337 if (!msg2638->prop.max_x || !msg2638->prop.max_y) { in msg2638_init_input_dev()
370 msg2638 = devm_kzalloc(dev, sizeof(*msg2638), GFP_KERNEL); in msg2638_ts_probe()
371 if (!msg2638) in msg2638_ts_probe()
388 msg2638->supplies); in msg2638_ts_probe()
409 } else if (msg2638->num_keycodes > ARRAY_SIZE(msg2638->keycodes)) { in msg2638_ts_probe()
411 msg2638->num_keycodes, ARRAY_SIZE(msg2638->keycodes)); in msg2638_ts_probe()
412 msg2638->num_keycodes = ARRAY_SIZE(msg2638->keycodes); in msg2638_ts_probe()
[all …]
A DMakefile67 obj-$(CONFIG_TOUCHSCREEN_MSG2638) += msg2638.o
A DKconfig637 tristate "MStar msg2638 touchscreen support"
641 Say Y here if you have an I2C touchscreen using MStar msg2638.
646 module will be called msg2638.

Completed in 10 milliseconds