linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jianmin Lv <lvjianmin@loongson.cn>
To: lpieralisi@kernel.org, robin.murphy@arm.com, chenhuacai@loongson.cn
Cc: guohanjun@huawei.com, sudeep.holla@arm.com, rafael@kernel.org,
	lenb@kernel.org, robert.moore@intel.com,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	loongarch@lists.linux.dev
Subject: [PATCH V5 0/2] DMA: update acpi_dma_get_range to return dma map regions
Date: Sun, 11 Sep 2022 17:06:33 +0800	[thread overview]
Message-ID: <20220911090635.5559-1-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

V2 -> V3
- Add kerneldoc for acpi_dma_get_range changing
- Remove redundant code in acpi_arch_dma_setup, and check map

V3 -> V4
- Change title to "Use acpi_arch_dma_setup() and remove ARCH_HAS_PHYS_TO_DMA"
- Use resource_size() to get size 

V4 -> V5
- Change commit log for patch: Support multiple dma windows with different offsets
- Remove a unnecessary blank line
- Fix a bug of acpi_dma_get_range

Jianmin Lv (2):
  ACPI / scan: Support multiple dma windows with different offsets
  LoongArch: Use acpi_arch_dma_setup() and remove ARCH_HAS_PHYS_TO_DMA

 arch/loongarch/Kconfig        |  1 -
 arch/loongarch/kernel/dma.c   | 52 ++++++++++++++--------------------
 arch/loongarch/kernel/setup.c |  2 +-
 drivers/acpi/arm64/dma.c      | 28 ++++++++++--------
 drivers/acpi/scan.c           | 53 +++++++++++++++--------------------
 include/acpi/acpi_bus.h       |  3 +-
 include/linux/acpi.h          | 12 ++++----
 7 files changed, 70 insertions(+), 81 deletions(-)

-- 
2.31.1


             reply	other threads:[~2022-09-11  9:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11  9:06 Jianmin Lv [this message]
2022-09-11  9:06 ` [PATCH V5 1/2] ACPI / scan: Support multiple dma windows with different offsets Jianmin Lv
2022-09-13  8:21   ` Lorenzo Pieralisi
2022-09-24 16:40     ` Rafael J. Wysocki
2022-10-18  2:08   ` Jeremy Linton
2022-10-18  9:33   ` Yicong Yang
2022-10-18 10:08     ` Rafael J. Wysocki
2022-10-18 12:00       ` Robin Murphy
2022-10-18 12:32         ` Yicong Yang
2022-10-18 12:50           ` Jianmin Lv
2022-10-18 12:56             ` Rafael J. Wysocki
2022-10-18 13:00               ` Jianmin Lv
2022-10-18 13:06                 ` Robin Murphy
2022-10-18 13:14                   ` Jianmin Lv
2022-10-19  8:21       ` Lorenzo Pieralisi
2022-09-11  9:06 ` [PATCH V5 2/2] LoongArch: Use acpi_arch_dma_setup() and remove ARCH_HAS_PHYS_TO_DMA Jianmin Lv

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=20220911090635.5559-1-lvjianmin@loongson.cn \
    --to=lvjianmin@loongson.cn \
    --cc=chenhuacai@loongson.cn \
    --cc=guohanjun@huawei.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --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).