From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Lee Jones <lee.jones@linaro.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: Re: [PATCH v1 3/3] mfd: Add support for Intel Sunrisepoint LPSS devices
Date: Wed, 29 Apr 2015 09:42:39 +0300 [thread overview]
Message-ID: <55407D5F.20207@linux.intel.com> (raw)
In-Reply-To: <20150428175735.GG9169@x1>
Hi
On 04/28/2015 08:57 PM, Lee Jones wrote:
> On Tue, 28 Apr 2015, Mika Westerberg wrote:
>> On Tue, Apr 28, 2015 at 02:32:59PM +0100, Lee Jones wrote:
>>> I'm not convinced it's really an MFD. What does this hardware look
>>> like? Are the Designware devices really in the same memory/register
>>> space as the LPSS registers?
>>
>> Yes they are - there is only single MMIO BAR per PCI device holding, the
>> host controller, iDMA and convergence layer registers.
>
> Are there publicly available docs?
>
https://download.01.org/future-platform-configuration-hub/skylake/register-definitions/332219_001_Final.pdf
For instance UART Memory Mapped Registers (Chapter 1.2) starts from UART
MMIO BAR + offset 0 (LPSS_DEV_OFFSET in the patch), UART Additional
Registers (Ch 1.3) from offset 0x200 (LPSS_PRIV_OFFSET) and UART DMA
Controller Register (Ch 1.4) from offset 0x800 (LPSS_IDMA_OFFSET).
Idea here is that MFD layer here takes case of reset and clock control
as well as register the host controllers and integrated DMAs as platform
devices (not all have the iDMA and thus conditional registering of it
using the intel_lpss_has_idma()).
That allow us to keep this MFD part, host controller drivers and
drivers/dma/dw/ changes independent from each other. Fox example host
controller driver can detect the iDMA by checking is there a "lpss_priv"
resource and set the slave DMA parameters and DMA filter function
accordingly (which picks the channel only from associated iDMA device).
--
Jarkko
next prev parent reply other threads:[~2015-04-29 6:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 11:59 [PATCH v1 0/3] mfd: introduce a driver for LPSS devices on SPT Andy Shevchenko
2015-03-31 11:59 ` [PATCH v1 1/3] PM / QoS: Make it possible to expose device latency tolerance to userspace Andy Shevchenko
2015-03-31 11:59 ` [PATCH v1 2/3] ACPI / PM: Attach ACPI power domain only once Andy Shevchenko
2015-03-31 11:59 ` [PATCH v1 3/3] mfd: Add support for Intel Sunrisepoint LPSS devices Andy Shevchenko
2015-04-28 13:32 ` Lee Jones
2015-04-28 13:48 ` Mika Westerberg
2015-04-28 17:57 ` Lee Jones
2015-04-29 6:42 ` Jarkko Nikula [this message]
2015-04-29 9:08 ` Mika Westerberg
2015-04-29 8:23 ` Lee Jones
2015-04-29 13:58 ` Andy Shevchenko
2015-04-29 15:06 ` Lee Jones
2015-04-29 15:43 ` Mika Westerberg
2015-05-25 15:18 ` Andy Shevchenko
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=55407D5F.20207@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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