linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: Azael Avalos <coproscefalo@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Jonathan Buzzard <jonathan@buzzard.org.uk>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH] toshiba_acpi: Add /dev/toshiba_acpi device
Date: Mon, 20 Jul 2015 14:36:31 -0700	[thread overview]
Message-ID: <20150720213631.GA34611@vmdeb7> (raw)
In-Reply-To: <1437089564-4242-1-git-send-email-coproscefalo@gmail.com>

On Thu, Jul 16, 2015 at 05:32:44PM -0600, Azael Avalos wrote:
> There were previous attempts to "merge" the toshiba SMM module to the
> toshiba_acpi one, they were trying to imitate what the old toshiba
> module does, however, some models (TOS1900 devices) come with a
> "crippled" implementation and do not provide all the "features" a
> "genuine" Toshiba BIOS does.
> 
> This patch adds a new device called toshiba_acpi, which aim is to
> enable userspace to access the SMM on Toshiba laptops via ACPI calls.
> 
> Creating a new convenience _IOWR command to access the SCI functions
> by opening/closing the SCI internally to avoid buggy BIOS, while at
> the same time providing backwards compatibility.
> 
> Older programs who wish to access the SMM on newer models can do it
> without much code change, as the toshiba.h header was modified to
> reflect these changes as well as adds all the toshiba_acpi paths
> and commands.

To clarify, the newer models didn't work at all previously, so this is not
changing the user:kernel interface, but rather enabling it on newer machines,
and programs wishing to take advantage of that can do so with minimal change.

Correct?

-- 
Darren Hart
Intel Open Source Technology Center

  parent reply	other threads:[~2015-07-20 21:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 23:32 [PATCH] toshiba_acpi: Add /dev/toshiba_acpi device Azael Avalos
2015-07-17  6:42 ` Darren Hart
2015-07-20 21:36 ` Darren Hart [this message]
2015-07-20 21:55   ` Azael Avalos

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=20150720213631.GA34611@vmdeb7 \
    --to=dvhart@infradead.org \
    --cc=coproscefalo@gmail.com \
    --cc=corbet@lwn.net \
    --cc=jonathan@buzzard.org.uk \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@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).