linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>,
	linux-kernel@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH] ACPI: add support for CSRT table
Date: Wed, 16 Jan 2013 06:42:16 +0200	[thread overview]
Message-ID: <20130116044216.GP13897@intel.com> (raw)
In-Reply-To: <2369015.SBxXlM67PJ@vostro.rjw.lan>

On Wed, Jan 16, 2013 at 12:35:56AM +0100, Rafael J. Wysocki wrote:
> On Monday, January 14, 2013 11:51:51 AM Mika Westerberg wrote:
> > Core System Resources Table (CSRT) is a proprietary ACPI table that
> > contains resources for certain devices that are not found in the DSDT
> > table. Typically a shared DMA controller might be found here.
> > 
> > This patch adds support for this table. We go through all entries in the
> > table and make platform devices of them. The resources from the table are
> > passed with the platform device.
> > 
> > There is one special resource in the table and it is the DMA request line
> > base and number of request lines. This information might be needed by the
> > DMA controller driver as it needs to map the ACPI DMA request line number
> > to the actual request line understood by the hardware. This range is passed
> > as IORESOURCE_DMA resource.
> 
> I have a question: Who's going to bind to those platform devices created
> by the code in this patch and how exactly this is going to happen?

Typically it is the DMA driver (but not limited to that). It is supposed to
work so that either the driver name (in the platform driver struct) matches
the device name in the CSRT or like with the dw_dmac case we do something
like:

/* The platform device created is "INTL9C60.0.auto" */

static const struct platform_device_id dw_dma_ids[] = {
        { "INTL9C60", 0 },
	{ }
}

static struct platform_driver dw_driver = {
	...
	.id_table = dw_dma_ids,
};

  reply	other threads:[~2013-01-16  4:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14  9:51 [PATCH] ACPI: add support for CSRT table Mika Westerberg
2013-01-15 23:35 ` Rafael J. Wysocki
2013-01-16  4:42   ` Mika Westerberg [this message]
2013-01-16 15:05     ` Rafael J. Wysocki
2013-01-16 15:10       ` Mika Westerberg
2013-01-16 16:13 ` [PATCH v2] " Mika Westerberg
2013-01-16 23:27   ` Rafael J. Wysocki
2013-01-17  4:50     ` 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=20130116044216.GP13897@intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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).