From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Bruno Randolf <br1@einfach.org>,
platform-driver-x86 <platform-driver-x86@vger.kernel.org>,
Seth Heasley <seth.heasley@intel.com>,
Darren Hart <dvhart@linux.intel.com>,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
Wim Van Sebroeck <wim@iguana.be>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
David Cohen <david.a.cohen@intel.com>,
Simon Guinot <simon.guinot@sequanux.org>
Subject: Re: [PATCH] gpio: add GPIO support for SMSC SCH311x
Date: Tue, 10 Dec 2013 17:05:27 +0000 [thread overview]
Message-ID: <20131210170527.GB26978@srcf.ucam.org> (raw)
In-Reply-To: <CACRpkdZxjKamJvOMqdgN5zG5DrZvDNTCaVSiyaHSawkLxvUrFA@mail.gmail.com>
On Tue, Dec 10, 2013 at 12:51:30PM +0100, Linus Walleij wrote:
> Matthew is this how discovery and registration of x86 platform
> drivers for port-mapped devices should work or are we doing
> something weird here?
This is pretty awful, but typical. LPC devices *should* be present in
ACPI to some extent, but often you'll just find (at best) a reference to
a superIO chip and no child devices. Do we have an example DSDT for a
device with this part?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2013-12-10 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1386116613-5241-1-git-send-email-br1@einfach.org>
2013-12-10 11:51 ` [PATCH] gpio: add GPIO support for SMSC SCH311x Linus Walleij
2013-12-10 17:05 ` Matthew Garrett [this message]
2013-12-11 4:05 ` Vivien Didelot
2013-12-12 19:50 ` Linus Walleij
2013-12-16 2:46 ` Vivien Didelot
2013-12-20 9:07 ` Linus Walleij
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=20131210170527.GB26978@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=br1@einfach.org \
--cc=david.a.cohen@intel.com \
--cc=dvhart@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=seth.heasley@intel.com \
--cc=simon.guinot@sequanux.org \
--cc=vivien.didelot@savoirfairelinux.com \
--cc=wim@iguana.be \
/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