From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Mark Brown <broonie@kernel.org>
Cc: Hanjun Guo <guohanjun@huawei.com>, qiujiang <qiujiang@huawei.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
charles.chenxin@huawei.com, linuxarm@huawei.com,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
linux-spi@vger.kernel.org
Subject: Re: [RFC PATCH] SPI/ACPI: DesignWare: Add ACPI support for Designware SPI driver
Date: Mon, 15 Feb 2016 18:09:21 +0000 [thread overview]
Message-ID: <20160215180921.2692941e@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20160215174540.GS18988@sirena.org.uk>
On Mon, 15 Feb 2016 17:45:40 +0000
Mark Brown <broonie@kernel.org> wrote:
> On Mon, Feb 15, 2016 at 04:27:51PM +0800, Hanjun Guo wrote:
> > On 2016/2/5 19:09, Mark Brown wrote:
>
> > > Intel are heavy users of this driver on their systems which also use
> > > ACPI. Have you discussed this binding with them? I've copied Andy and
> > > Jarkko who've worked on the driver recently.
>
> > There is no ACPI code in this driver yet, seems "PRP0001" is used to reuse
> > this driver directly.
>
> No, on Intel systems the devices appear on the PCI bus.
They may be ACPI or PCI enumerated - depends upon the system and
firmware. See drivers/acpi/acpi_lpss.c
Alan
next prev parent reply other threads:[~2016-02-15 18:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 7:11 [RFC PATCH] SPI/ACPI: DesignWare: Add ACPI support for Designware SPI driver qiujiang
2016-02-05 11:09 ` Mark Brown
2016-02-14 9:31 ` Jiang Qiu
2016-02-15 17:44 ` Mark Brown
2016-02-15 8:27 ` Hanjun Guo
2016-02-15 17:45 ` Mark Brown
2016-02-15 18:09 ` One Thousand Gnomes [this message]
2016-02-05 15:55 ` Andy Shevchenko
2016-02-05 16:11 ` Mark Brown
2016-02-14 9:47 ` Jiang Qiu
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=20160215180921.2692941e@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=charles.chenxin@huawei.com \
--cc=guohanjun@huawei.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=qiujiang@huawei.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).