linux-kernel - Re: [PATCH] n-trig digitizer quirks

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: <alpine.LNX.1.10.0811191505340.19853@jikos.suse.cz>
Date:	Wed, 19 Nov 2008 15:07:40 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Rafi Rubin <rafi@...s.upenn.edu>
cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] n-trig digitizer quirks

On Wed, 19 Nov 2008, Rafi Rubin wrote:

> >> Also, if you do prefer using driver data like that, is the probe 
> >> function necessary to make it work?
> > Probe function is necesary, you need to parse the report descriptor 
> > (hid_parse()), activate the hardware (hid_hw_start()), etc.
> Just to confirm then, its not necessary if I'm not checking the driver 
> data for the quirk?

Correct; if you don't need to do anything special in the _probe function, 
the HID core will do everything necessary (descriptor parsing, 
low-level hardware initialization) for you.

-- 
Jiri Kosina
SUSE Labs
--
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/