public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Erik Andrén" <erik.andren@gmail.com>
To: linux-acpi@vger.kernel.org
Subject: Writing to the EC
Date: Sun, 04 Nov 2007 20:55:40 +0100	[thread overview]
Message-ID: <472E23BC.2010909@gmail.com> (raw)

Hello,

I'm currently in the process of trying to write routines for controlling
the backlight on my Clevo M72R.

Pressing the hotkeys do work but I do belive this is the result of that
the embedded controller is hardwired to the keyboard.

To make a long story short, I've hacked up a kernel module that dumps
the EC (with inspiration from the ibm acpi driver) using the exported
ec_read and ec_write symbols from the ec.c in the kernel acpi source and
I've been able to locate a register which change when I manually push
the brightness hotkey buttons (0xC9).

The bad part is that writing to the EC using the ec_write function
doesn't work at all. Sure it completes the operation, but when probing
the register afterwards, no change of value is seen.

My questions to you ACPI and EC gurus are:

1. Is it possible that the EC is read-only from the OS perspective?

2. Are there any common quirks / initialization that is needed to
getting the EC to register commands?

3. Does anyone have a recommendation of programs to use for snooping I/O
accesses in windows?

With kind regards
Erik Andrén
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2007-11-04 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-04 19:55 Erik Andrén [this message]
2007-11-04 21:23 ` Writing to the EC Richard Hughes
2007-11-04 21:31   ` Pavel Troller
2007-11-05  0:55 ` Carlos Corbacho
2007-11-05 19:00   ` Ângelo Miguel Arrifano

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=472E23BC.2010909@gmail.com \
    --to=erik.andren@gmail.com \
    --cc=linux-acpi@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