Daniel Kurtz wrote: > The normal messages sent after boot or NVRAM update are T6 reports, > containing a status, and the config memory checksum. Parse them and dump > a useful info message. This can cause a lot of dmesg output - for instance you get 2 messages per calibration, and the chip can trigger them itself if noise suppression or anti-touch calibration are enabled. So perhaps dev_dbg()? -- Nick Dyer Software Engineer, ITDev Ltd -- 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