From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Carlos Corbacho <carlos@strangeworlds.co.uk>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH, RFC] i8042: add Dritek keyboard extension quirk
Date: Tue, 15 Jan 2008 16:35:32 -0500 [thread overview]
Message-ID: <20080115163052.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <200801120122.38648.carlos@strangeworlds.co.uk>
Hi Carlos,
On Sat, Jan 12, 2008 at 01:22:38AM +0000, Carlos Corbacho wrote:
>
> Can you please check the i8042_command() call is correct, I'm having
> trouble getting my head around the call semantics. What I'm trying to do
> is send the command 0x59 with one argument, 0x90.
>
Yep, this should work.
> +static unsigned int i8042_dritek = 0;
> +module_param_named(dritek, i8042_dritek, bool, 0);
> +MODULE_PARM_DESC(dritek, "Force enable the Dritek keyboard extension");
I think this should be wrapped in CONFIG_X86. Also it does not make sense
to 0-initialize static variables.
> @@ -1171,6 +1176,13 @@ static int __devinit i8042_probe(struct platform_device *dev)
> */
> i8042_register_ports();
>
> + if (i8042_dritek) {
> + param = 0x90;
> + error = i8042_command(¶m, 0x1059);
> + if (error)
> + goto out_fail;
> + }
> +
I think this call should be moved above i8042_register_ports() so atkbd
will have i8042 fully setup before pribing.
Let me know if you agree, I have the above fixedon my side. Thanks!
--
Dmitry
next prev parent reply other threads:[~2008-01-15 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 1:22 [PATCH, RFC] i8042: add Dritek keyboard extension quirk Carlos Corbacho
2008-01-15 21:35 ` Dmitry Torokhov [this message]
2008-01-16 1:23 ` Carlos Corbacho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080115163052.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=carlos@strangeworlds.co.uk \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).