From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Wang, Annie" <Annie.Wang@amd.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Vinod Koul <vinod.koul@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>, "Huang, Ray" <Ray.Huang@amd.com>,
"Wan, Vincent" <Vincent.Wan@amd.com>,
"Xue, Ken" <Ken.Xue@amd.com>, Robin Murphy <robin.murphy@arm.com>,
Graeme Gregory <gg@slimlogic.co.uk>, "Li, Tony" <Tony.Li@amd.com>,
"Yu, Xiangliang" <Xiangliang.Yu@amd.com>
Subject: Re: [PATCH 3/6] ACPI: add 2 parameters to function acpi dma controller register
Date: Thu, 7 Jan 2016 11:52:38 +0200 [thread overview]
Message-ID: <20160107095238.GY1770@lahna.fi.intel.com> (raw)
In-Reply-To: <BLUPR12MB0433A702DB5903D6A20232B781F40@BLUPR12MB0433.namprd12.prod.outlook.com>
On Wed, Jan 06, 2016 at 06:46:37AM +0000, Wang, Annie wrote:
> Acpi_dma_xlate mainly converts an acpi_dma structure into a dma_chan structure.
> Without proper request line, wrong acpi_dma structure may be get.
>
> And as Andy says in http://article.gmane.org/gmane.linux.kernel.iommu/11675
> How about add a hook into acpi_dma_controller_register?
Hmm, you can pass custom data in acpi_dma_controller_register() which
will be assigned to adma->data. If you put your request line
information there, I think your custom acpi_dma_xlate() should be able
to use that information to find proper channel, no?
next prev parent reply other threads:[~2016-01-07 9:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 5:31 [PATCH 0/6] 8250: AMD Carrizo UART PL300 DMA enablement Wang Hongcheng
2016-01-04 5:31 ` [PATCH 1/6] 8250/Kconfig: add config option CONFIG_SERIAL_8250_AMD Wang Hongcheng
2016-01-04 14:41 ` Borislav Petkov
2016-01-06 2:08 ` Wang, Annie
2016-01-06 10:46 ` Borislav Petkov
2016-01-11 7:26 ` Wang, Annie
2016-01-04 5:31 ` [PATCH 2/6] ACPI: create setup_quirk in acpi_apd Wang Hongcheng
2016-01-04 14:21 ` Andy Shevchenko
2016-01-04 5:31 ` [PATCH 3/6] ACPI: add 2 parameters to function acpi dma controller register Wang Hongcheng
2016-01-04 14:36 ` Andy Shevchenko
2016-01-04 14:45 ` Mika Westerberg
2016-01-06 6:46 ` Wang, Annie
2016-01-07 9:52 ` Mika Westerberg [this message]
2016-01-07 10:08 ` Andy Shevchenko
2016-01-04 5:31 ` [PATCH 4/6] dmaengine: pl330: add new items for pl330 private data Wang Hongcheng
2016-01-04 5:43 ` kbuild test robot
2016-01-04 14:38 ` Andy Shevchenko
2016-01-04 5:31 ` [PATCH 5/6] dmaengine: pl330: provide ACPI dmaengine interface Wang Hongcheng
2016-01-04 14:46 ` Andy Shevchenko
2016-01-04 5:31 ` [PATCH 6/6] Serial:8250: New Port Type PORT_AMD_8250 Wang Hongcheng
2016-01-04 5:47 ` kbuild test robot
2016-01-05 12:01 ` Heikki Krogerus
2016-01-14 6:23 ` Wang, Annie
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=20160107095238.GY1770@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Annie.Wang@amd.com \
--cc=Ken.Xue@amd.com \
--cc=Ray.Huang@amd.com \
--cc=Tony.Li@amd.com \
--cc=Vincent.Wan@amd.com \
--cc=Xiangliang.Yu@amd.com \
--cc=andy.shevchenko@gmail.com \
--cc=bp@alien8.de \
--cc=dmaengine@vger.kernel.org \
--cc=gg@slimlogic.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robin.murphy@arm.com \
--cc=vinod.koul@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