public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: "Jan Beulich" <JBeulich@suse.com>
Cc: dmitry.torokhov@gmail.com, hpa@linux.intel.com,
	"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org
Subject: Re: your patch "x86, 8042: Enable A20 using KBC to fix S3 resume on some MSI laptops"
Date: Mon, 14 Jan 2013 09:29:38 +0100	[thread overview]
Message-ID: <201301140929.38462.linux@rainbow-software.org> (raw)
In-Reply-To: <50F3CAFD02000078000B52BE@nat28.tlf.novell.com>

On Monday 14 January 2013, Jan Beulich wrote:
> Ondrej,
>
> I see two problems with this patch: For one, on a system without
> i8042 the code at the place it got inserted ought to incur a stall of
> 1s (50us * I8042_CTL_TIMEOUT [10000] * 2). I believe that this
> code should not be run before i8042_controller_check() completed
> successfully, but at the very least the second call to
> i8042_command() should be conditional upon the first being
> successful (effectively halving the stall).

I believe that all PnP-capable systems without 8042 will exit with -ENODEV 
after x86_platform.i8042_detect(). Old non-PnP systems usually have 8042.

> Second, considering that enabling A20 (even if just in a fake way),
> is a core system operation, I don't think it belongs into a driver
> that is only optionally present in the kernel.

The first version of this patch added A20 enabling to early init code. But 
that could be dangerous as it was run before any 8042 detection, possibly 
breaking systems without 8042. I haven't found a better place for this.

-- 
Ondrej Zary

  reply	other threads:[~2013-01-14  8:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14  8:08 your patch "x86, 8042: Enable A20 using KBC to fix S3 resume on some MSI laptops" Jan Beulich
2013-01-14  8:29 ` Ondrej Zary [this message]
2013-01-14  8:37   ` Jan Beulich
2013-01-14  8:54     ` Ondrej Zary
2013-01-14  9:02       ` Jan Beulich
2013-01-16  1:16         ` H. Peter Anvin

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=201301140929.38462.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=JBeulich@suse.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hpa@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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