All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Carlos Corbacho <carlos@strangeworlds.co.uk>
Cc: linux-acpi@vger.kernel.org, Matthew Garrett <mjg59@srcf.ucam.org>,
	Alexey Starikovskiy <aystarik@gmail.com>
Subject: Re: [PATCH 0/5] WMI patches for acpi-test
Date: Mon, 4 Feb 2008 01:30:08 -0500	[thread overview]
Message-ID: <200802040130.08938.lenb@kernel.org> (raw)
In-Reply-To: <200802030945.06398.carlos@strangeworlds.co.uk>


> For future patches - do you want me to resend them, or send you incremental 
> patches against what is currently in your tree?

I can handle either way,
but if they are revisions of the existing patches rather
than adding additional logically independent changes,
then it is cleaner to re-send the series.

> > acer-wmi needs a MAINTAINER
> 
> Oversight on my part - will do.
> 
> > tc1100-wmi needs a MAINTAINER
> 
> I'll add myself for now; but if anyone else wants the job, I don't mind.
> 
> > I don't understand the WMI user/kernel sysfs API.
> 
> I did have some documentation on this - I'll refresh it and send another 
> patch.

okay, good.

> > I guess i had originally expected it to live in /sys/firmware/wmi,
> > but I see that they put dmi a subset of DMI under /sys/class/dmi,
> > so i guess there is precident...  I got my main wish, which was
> > to have not _not_ be under some ACPI specific directory:-)
> 
> I can probably put a symlink in for /sys/firmware/wmi, if you like?

No, don't bother.

> The /sys/class is done simply because using a class and virtual devices is far 
> simpler, and appears less prone to the sysfs-rework-of-the-week (and makes 
> autoload support based on a GUID trivial to implement).
> 
> > #2 is the better route -- move forward using workaround,
> > and revert the workaround when it is no longer needed.
> > The risk is if somebody in user-space starts actually
> > programming to 19-character GUIDS.
> 
> Ok.
> 
> > I loaded this driver on an HP nx6325 as well as a Lenovo T61.
> 
> Interesting - do Lenovo actually use WMI for anything? I thought they had 
> their own custom HID's supported by thinkpad-acpi?

Apparently they do.

The T61 also has IBM and LENOVO HIDs.

No, I don't know why the '*' is in "*pnp0c14", but we've
run into that before so we ignore it.

[lenb@d975xbx2 t61]$ grep _HID DSDT.dsl
            Name (_HID, EisaId ("PNP0C0F"))
            Name (_HID, EisaId ("PNP0C0F"))
            Name (_HID, EisaId ("PNP0C0F"))
            Name (_HID, EisaId ("PNP0C0F"))
            Name (_HID, EisaId ("PNP0C0F"))
            Name (_HID, EisaId ("PNP0C0F"))
            Name (_HID, EisaId ("PNP0C0F"))
            Name (_HID, EisaId ("PNP0C0F"))
            Name (_HID, EisaId ("PNP0C01"))
            Name (_HID, EisaId ("PNP0C0D"))
            Name (_HID, EisaId ("PNP0C0E"))
                    Name (_HID, EisaId ("PNP0C02"))
                    Name (_HID, EisaId ("PNP0000"))
                    Name (_HID, EisaId ("PNP0100"))
                    Name (_HID, EisaId ("PNP0103"))
                    Name (_HID, EisaId ("PNP0200"))
                    Name (_HID, EisaId ("PNP0800"))
                    Name (_HID, EisaId ("PNP0C04"))
                    Name (_HID, EisaId ("PNP0B00"))
                    Name (_HID, EisaId ("PNP0303"))
                    Name (_HID, EisaId ("IBM3780"))
                            Store (0x80374D24, _HID)
                            Store (0x57004D24, _HID)
                    Name (_HID, EisaId ("PNP0700"))
                        Name (_HID, EisaId ("PNP0501"))
                        Name (_HID, EisaId ("PNP0501"))
                        Name (_HID, EisaId ("PNP0400"))
                        Name (_HID, EisaId ("PNP0400"))
                        Name (_HID, EisaId ("PNP0401"))
                        Name (_HID, EisaId ("PNP0401"))
                    Name (_HID, EisaId ("ATM1200"))
                    Name (_HID, EisaId ("PNP0C09"))
                        Name (_HID, EisaId ("PNP0C0A"))
                        Name (_HID, EisaId ("PNP0C0A"))
                        Name (_HID, "ACPI0003")
                        Name (_HID, EisaId ("IBM0068"))
            Name (_HID, EisaId ("PNP0A08"))
                        Name (_HID, "*pnp0c14")
                Name (_HID, EisaId ("IBM0069"))
                            Store (\_SB.PCI0.LPC.FDC._HID, Index (XPCK, 0x02))
                        Store (\_SB.PCI0.LPC.EC.BAT1._HID, Index (XPCK, 0x02))
                Name (_HID, EisaId ("IBM0079"))
                Name (_HID, EisaId ("LEN0001"))

> > just for kicks i tried to dump the data attributes,
> > but on both machines I found that some of them oops
> > in wmi_data_read like below.
> 
> Hmm - I'll look into this and see if I can see what's going wrong.

thanks.  Let me know if you need help testing.

cheers,
-Len

ps. note that your code shipped in 2.6.24-mm1




      reply	other threads:[~2008-02-04  6:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-02 12:17 [PATCH 0/5] WMI patches for acpi-test Carlos Corbacho
2008-02-02 12:17 ` [PATCH 1/5] ACPI: WMI: Add ACPI-WMI mapping driver Carlos Corbacho
2008-02-02 12:17 ` [PATCH 2/5] acer-wmi: Add driver for newer Acer laptops Carlos Corbacho
2008-02-02 12:17 ` [PATCH 3/5] [RFC] tc1100-wmi: Add driver for HP Compaq TC1100 Tablets Carlos Corbacho
2008-02-02 12:17 ` [PATCH 4/5] [RFC] ACPI: WMI: Add sysfs userspace interface Carlos Corbacho
2008-02-02 12:17 ` [PATCH 5/5] [WIP] ACPI: WMI: Limit size of device string to 19 characters Carlos Corbacho
2008-02-03  3:44 ` [PATCH 0/5] WMI patches for acpi-test Len Brown
2008-02-03  9:45   ` Carlos Corbacho
2008-02-04  6:30     ` Len Brown [this message]

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=200802040130.08938.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=aystarik@gmail.com \
    --cc=carlos@strangeworlds.co.uk \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.