From: Jianmin Lv <lvjianmin@loongson.cn>
To: lpieralisi@kernel.org, robin.murphy@arm.com,
guohanjun@huawei.com, sudeep.holla@arm.com, rafael@kernel.org,
lenb@kernel.org, robert.moore@intel.com
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: [PATCH V2 0/2] DMA: update acpi_dma_get_range to return dma map regions
Date: Fri, 5 Aug 2022 15:31:12 +0800 [thread overview]
Message-ID: <1659684674-40612-1-git-send-email-lvjianmin@loongson.cn> (raw)
The patch series changed acpi_dma_get_range to return dma regions
as of_dma_get_range, so that dev->dma_range_map can be initialized
conveniently.
And acpi_arch_dma_setup for ARM64 is changed wih removing dma_base
and size from it's parameters.
Remove ARCH_HAS_PHYS_TO_DMA for LoongArch and use generic
phys_to_dma/dma_to_phys in include/linux/dma-direct.h.
V1 -> V2
- Removed dma_base and size from acpi_arch_dma_setup' parameters
- Add patch to remove ARCH_HAS_PHYS_TO_DMA for LoongArch
Jianmin Lv (2):
ACPI / scan: Support multiple dma windows with different offsets
LoongArch: Remove ARCH_HAS_PHYS_TO_DMA
arch/loongarch/Kconfig | 1 -
arch/loongarch/kernel/dma.c | 62 +++++++++++++++++++++----------------------
arch/loongarch/kernel/setup.c | 2 +-
drivers/acpi/arm64/dma.c | 44 ++++++++++++++++++++++--------
drivers/acpi/scan.c | 48 ++++++++++++++++-----------------
include/acpi/acpi_bus.h | 3 +--
include/linux/acpi.h | 12 +++++----
7 files changed, 97 insertions(+), 75 deletions(-)
--
1.8.3.1
next reply other threads:[~2022-08-05 7:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 7:31 Jianmin Lv [this message]
2022-08-05 7:31 ` [PATCH V2 1/2] ACPI / scan: Support multiple dma windows with different offsets Jianmin Lv
2022-08-05 12:46 ` Robin Murphy
2022-08-06 6:13 ` Jianmin Lv
2022-08-06 7:21 ` Jianmin Lv
2022-08-08 8:24 ` Lorenzo Pieralisi
2022-08-12 7:52 ` Lorenzo Pieralisi
2022-08-29 13:00 ` Jianmin Lv
2022-08-05 7:31 ` [PATCH V2 2/2] LoongArch: Remove ARCH_HAS_PHYS_TO_DMA Jianmin Lv
2022-08-05 16:36 ` kernel test robot
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=1659684674-40612-1-git-send-email-lvjianmin@loongson.cn \
--to=lvjianmin@loongson.cn \
--cc=guohanjun@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=robin.murphy@arm.com \
--cc=sudeep.holla@arm.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 NNTP newsgroup(s).