From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Vincent Pelletier <plr.vincent@gmail.com>
Cc: linux-leds@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: leds-gpio on x86
Date: Thu, 6 Aug 2015 20:35:58 +0300 [thread overview]
Message-ID: <20150806173558.GZ1540@lahna.fi.intel.com> (raw)
In-Reply-To: <20150806191727.0bf87a3a@x2>
On Thu, Aug 06, 2015 at 07:17:27PM +0200, Vincent Pelletier wrote:
> On Thu, 6 Aug 2015 19:59:24 +0300, Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
> > Does it list the GPIO controller itself in the DSDT? If it does not, you
> > would need to patch that there as well.
>
> I do see this in the dsdt:
> Name (_HID, "INT33FC" /* Intel Baytrail GPIO Controller */) // _HID: Hardware ID
> Name (_CID, "INT33FC" /* Intel Baytrail GPIO Controller */) // _CID: Compatible ID
>
> I do not know the distinction between a gpio controller and the chip
> which has the pins directly, though.
Do you know which GPIOs are used for leds?
Since the GPIO host controller is listed in the DSDT, I think patching
the leds device should be pretty simple.
> > Just in case, can you provide me the DSDT? I can take a look.
>
> (sent off-list)
Got it, thanks.
next prev parent reply other threads:[~2015-08-06 17:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 20:09 leds-gpio on x86 Vincent Pelletier
2015-08-06 16:59 ` Mika Westerberg
2015-08-06 17:17 ` Vincent Pelletier
2015-08-06 17:35 ` Mika Westerberg [this message]
2015-08-06 18:18 ` Vincent Pelletier
2015-08-07 10:57 ` Mika Westerberg
2015-08-08 12:06 ` Vincent Pelletier
2015-08-11 12:00 ` Mika Westerberg
2015-08-11 17:42 ` Vincent Pelletier
2015-08-12 12:53 ` Mika Westerberg
2015-08-15 10:36 ` Vincent Pelletier
2015-08-17 21:08 ` Vincent Pelletier
2015-08-18 7:32 ` Vincent Pelletier
2015-08-18 9:02 ` Mika Westerberg
2015-08-18 11:38 ` Vincent Pelletier
2015-08-18 22:56 ` Vincent Pelletier
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=20150806173558.GZ1540@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=plr.vincent@gmail.com \
/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.