From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-pm <linux-pm@lists.linux-foundation.org>,
linux-i2c <linux-i2c@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"Len, Brown" <lenb@kernel.org>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Grant Likely <grant.likely@secretlab.ca>,
Dirk Brandewie <dirk.brandewie@gmail.com>
Subject: Re: [RFC PATCH 0/6] ACPI: ACPI 5.0 device enumeration proposal
Date: Mon, 1 Oct 2012 09:44:33 +0300 [thread overview]
Message-ID: <20121001064433.GF15548@intel.com> (raw)
In-Reply-To: <1348817863.10877.320.camel@rui.sh.intel.com>
On Fri, Sep 28, 2012 at 03:37:43PM +0800, Zhang Rui wrote:
>
> the main idea is that, for Serial Buses like I2C and SPI, we enumerate
> the controller as a platform device, and then enumerate the slaves via
> i2c/spi_register_board_info. And then, when the controller is really
> probed and enabled in the platform driver, the SPI/I2C bus code will
> enumerate I2C/SPI slaves automatically.
> And for the other devices, we will enumerate all of them as platform
> devices, which is not covered in this patch set yet.
Can you show some example how we could use this new code for example with
an existing I2C/SPI slave driver? Let's say the device uses few GPIOs, one
for interrupt and other for triggering firmware download. In addition to
that it needs a special parameters that can be extracted running the "_DSM"
method of the device.
Normally the driver would get this stuff from the platform data or from
Device Tree but how it is done with these patches?
next prev parent reply other threads:[~2012-10-01 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 7:37 [RFC PATCH 0/6] ACPI: ACPI 5.0 device enumeration proposal Zhang Rui
2012-10-01 6:44 ` Mika Westerberg [this message]
2012-10-01 14:30 ` Zhang, Rui
2012-10-02 6:19 ` 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=20121001064433.GF15548@intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=dirk.brandewie@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=rui.zhang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox