linux-kernel - Re: [PATCH 22/22 v4] Input: atmel_mxt_ts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGS+omDgwEYMOPxsk4gjbZSO7ocz=PPzqtowBEsfnRb=0ogi4w@mail.gmail.com>
Date:	Mon, 18 Jun 2012 23:29:59 +0800
From:	Daniel Kurtz <djkurtz@...omium.org>
To:	Nick Dyer <nick.dyer@...ev.co.uk>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Henrik Rydberg <rydberg@...omail.se>,
	Joonyoung Shim <jy0922.shim@...sung.com>,
	linux-input@...r.kernel.org,
	Iiro Valkonen <iiro.valkonen@...el.com>,
	Benson Leung <bleung@...omium.org>,
	Yufeng Shen <miletus@...omium.org>,
	Olof Johansson <olofj@...omium.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 22/22 v4] Input: atmel_mxt_ts - parse T6 reports

On Mon, Jun 18, 2012 at 11:09 PM, Nick Dyer <nick.dyer@...ev.co.uk> wrote:
> 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()?

Sounds good to me.

>
> --
> Nick Dyer
> Software Engineer, ITDev Ltd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/