From: matthieu castet <castet.matthieu@free.fr>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org, Adam Belay <ambx1@neo.rr.com>,
bjorn.helgaas@hp.com, vojtech@suse.cz
Subject: Re: [PATCH] PNP support for i8042 driver
Date: Sun, 14 Nov 2004 13:22:21 +0100 [thread overview]
Message-ID: <41974DFD.5070603@free.fr> (raw)
In-Reply-To: <200411140148.02811.dtor_core@ameritech.net>
Dmitry Torokhov wrote:
> On Saturday 13 November 2004 08:23 am, matthieu castet wrote:
>
>>Hi,
>>this patch add PNP support for the i8042 driver in 2.6.10-rc1-mm5. Acpi
>>is try before the pnp driver so if you don't disable ACPI or apply
>>others pnpacpi patches, it won't change anything.
>>
>>Please review it and apply if possible
>>
>>thanks,
>>
>>Matthieu CASTET
>>
>>Signed-Off-By: Matthieu Castet <castet.matthieu@free.fr>
>>
>
> Hi,
>
Hi,
> Do we really need to keep those drivers loaded - i8042 will not
> be hotplugged and ports are reserved anyway. We are only interested
> in presence of the keyboard and mouse ports. Can we unregister
> the drivers (both ACPI and PNP) right after registering and mark
> all that stuff as __init/__initdata as in the patch below?
It is better to keep pnp driver loaded because when it unload, the
resources will be disabled, so for the motherboards that allow it the
irq won't work anymore, and so the keyboard and mouse won't work...
Also it avoid the user to do
"echo disable > /sys/bus/pnp/xx\:xx/resources". Actually, it disables
the resources for the mouse even if the driver is using the resource...
> I also adjusted init logic so ACPI/PNP can be enabled/disabled
> independently of each other.
>
No problem as long as :
-if there is no acpi support, pnp can be used
-if acpi driver detect nothing, and there is pnp support, pnp driver
will be tried before returning an error (it is important because, in the
future pnpacpi will "lock" the acpi device, so the acpi driver will find
nothing even if there are devices)
Regards,
Matthieu
next prev parent reply other threads:[~2004-11-14 12:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-13 13:23 [PATCH] PNP support for i8042 driver matthieu castet
2004-11-14 6:48 ` Dmitry Torokhov
2004-11-14 12:22 ` matthieu castet [this message]
2004-11-15 14:41 ` Dmitry Torokhov
2004-11-15 19:51 ` matthieu castet
2004-11-15 20:28 ` Dmitry Torokhov
2004-11-15 22:52 ` matthieu castet
2004-11-15 23:09 ` matthieu castet
2004-11-16 5:52 ` Adam Belay
2004-11-16 6:27 ` Dmitry Torokhov
2004-11-16 5:37 ` Adam Belay
2004-11-16 5:44 ` Greg KH
2004-11-16 6:06 ` Dmitry Torokhov
2004-11-16 6:24 ` Adam Belay
2004-11-17 10:07 ` Vojtech Pavlik
2005-02-04 17:37 ` matthieu castet
2005-02-04 18:28 ` Vojtech Pavlik
2005-02-04 22:54 ` matthieu castet
2005-02-05 13:48 ` matthieu castet
2005-02-05 18:51 ` Dmitry Torokhov
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=41974DFD.5070603@free.fr \
--to=castet.matthieu@free.fr \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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