From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Lan Tianyu <tianyu.lan@intel.com>,
khali@linux-fr.org, ben-linux@fluff.org, w.sang@pengutronix.de,
lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
jkosina@suse.cz, chatty@enac.fr, jj_ding@emc.com.tw
Subject: Re: Fwd: Hid over I2C and ACPI interaction
Date: Fri, 6 Jul 2012 08:52:34 +0300 [thread overview]
Message-ID: <20120706055234.GC2237@intel.com> (raw)
In-Reply-To: <1341471717.1682.125.camel@rui.sh.intel.com>
On Thu, Jul 05, 2012 at 03:01:57PM +0800, Zhang Rui wrote:
> +Note that although these are ACPI devices, we prefer to use PnP drivers
> for them,
> +this is because:
> +1. all the non-ACPI-predefined Devices are exported as PnP devices as
> well
> +2. PnP bus is a well designed bus. Probing via PnP layer saves a lot of
> work
> + for the device driver, e.g. getting & parsing ACPI resources.
(Nice BKM, thanks for sharing)
I have few questions about using PnP drivers instead of pure ACPI drivers.
ACPI 5.0 defined some new resources, for example "Fixed DMA descriptor"
that has information about the request line + channel for the device to
use. Hovewer, PnP drivers pass resources as 'struct resource', which
basically only has start and end - how do you represent all this new stuff
using 'struct resource'?
Or should we use acpi_walk_resources() where 'struct resource' is not
suitable?
next prev parent reply other threads:[~2012-07-06 5:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 13:46 Hid over I2C and ACPI interaction Benjamin Tissoires
[not found] ` <4FF52C70.9010601@intel.com>
2012-07-05 7:01 ` Fwd: " Zhang Rui
2012-07-05 7:20 ` Zhang Rui
2012-07-05 8:44 ` Benjamin Tissoires
2012-07-09 0:41 ` Zhang Rui
2012-07-06 5:52 ` Mika Westerberg [this message]
2012-07-09 3:24 ` Lan Tianyu
2012-07-09 4:02 ` Moore, Robert
2012-07-09 7:28 ` Lan Tianyu
2012-07-09 7:51 ` Mika Westerberg
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=20120706055234.GC2237@intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=ben-linux@fluff.org \
--cc=chatty@enac.fr \
--cc=jj_ding@emc.com.tw \
--cc=jkosina@suse.cz \
--cc=khali@linux-fr.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=tianyu.lan@intel.com \
--cc=w.sang@pengutronix.de \
/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).